---

layout: config

title: Spectrum 2

---

> * [service.server_mode](#serviceserver_mode)

> * [service.jid](#servicejid)

### Types of configuration fields

Following types are used:

integer - Examples: key=0

string - Examples: key=something

boolean - Examples: key=0 or key=1

list - List of strings (or Jabber IDs). You can specify this options more than once:

	allowed_servers=domain.tld

	allowed_servers=example.com

#### service.server_mode

Key | val

----|----

Description:|Configures if Spectrum 2 works in server mode or gateway mode

Context:|server-mode and gateway-mode

Type:|boolean

Default:|0

If this option is true, Spectrum 2 works in server-mode and acts as standalone server.

User then logins legacy networks by logging XMPP account like this one: `my_msn_name%hotmail.com@msn.domain.tld`.

*Advantages:*

* Passwords are not stored on server.

* Roster synchronization is easy, because Spectrum 2 acts as normal server.

* If you want to use Spectrum 2 as wrapper between different networks, you don't need database or Jabber server as another layer.

* Using SRV records you can easily run Spectrum 2 on different machines to scale it.

*Disadvantages:*

* Clients have to support more accounts to connect more legacy networks (Therefore they will need have to use more TCP connections).

If this option is false, Spectrum 2 acts as normal XMPP component (gateway).

You then have to configure an external XMPP server (like Prosody or Ejabberd) to serve the subdomain you want to use for Spectrum 2 (for example "icq.domain.tld"). Spectrum 2 in gateway mode then connects the XMPP server as its component and users are able to find out "icq.domain.tld" in Service Discovery, register it and use it.

*Advantages:*

* Users can use more legacy networks using single XMPP account (and using single TCP connection).

* It's easy to extend existing XMPP servers using gateway mode.

*Disadvantages:*