The Services tab allows you define additional services for your IM Server.
You can define conference services, user database services, transports and other modules, but not user accounts.
|
In order to use a transport service, such as an ICQ gateway, you should specify a unique domain (e.g. icq.icewarpdemo.com) and create a DNS A-type record for it. This domain should not be defined as a IceWarp Server domain. |
Selecting the tab offers a list of defined services:

Use the Delete button to delete the currently selected service.
Use the Edit File button to open a simple text file containing your service definitions, you can edit this file if you wish, examples are given.
Use the Add or Edit buttons to create or modify a record. The Service dialog opens:

Field |
Description |
Service |
Specify a domain name or host name here. You should also create a DNS A record for the domain. |
Description |
Short description for identification purposes. |
Category |
Choose the category of service this will be: You have three options: conference Provides a multi-user chat service (conference room). gateway Provides a link to another Instant Messaging network or messaging gateway. The 'jabber:iq:register' namespace should be used to gain access to such networks, and the 'jabber:iq:gateway' namespace is also needed. proxy Provides a proxy. NOTE: Category selection impacts composition of other drop-down lists. Items are preselected according to the Category what simplifies setting. |
Type |
Choose the type of service this will be: Private For the conference category service. A conference room is dynamically created each time it is required. Public For the conference category service. A conference room is created once and left open for use. Service For non-IM services, such as events and monitoring (see later sections). icq For the gateway category service. ICQ Instant Messenger transport. aim For the gateway category service. AOL Instant Messenger transport. yahoo For the gateway category service. Yahoo! Instant Messenger transport. msn For the gateway category service. Microsoft Instant Messenger transport. irc For the gateway category service.. Internet Relay Chat transport. myspace For the gateway category service. MySpaceIM transport. For the gateway category service. Tencent QQ transport. gadu-gadu For the gateway category service. Gadu-Gadu transport. xmpp For the gateway category service. Extensible Messaging and Presence Protocol transport. For the gateway category service. Twitter transport. |
|
simple For the gateway category service. Simple Instant Messenger transport. sametime For the gateway category service. IBM Lotus Sametime transport. silc For the gateway category service. Secure Internet Live Conferencing transport. groupwise For the gateway category service. Novell GroupWise transport. bonjour For the gateway category service. Bonjour Instant Messaging transport. For the gateway category service. Email transport. bytestreams For a SOCKS proxy category for IM file transfers when required. |
Namespace |
For the service type of the gateway category service. Enter a namespace defined within the XMPP/Jabber IM protocol There can be any namespace defined within XMPP/Jabber IM Protocol. But you need to use jabber:iq:register jabber:iq:gateway (delimited by semi-colon) if you want to set transport gateway for ICQ, MSN, etc. and you do not have to set any if you want to set a conference room. |
Module |
The appropriate module is automatically pre-filled when Type is selected. Modules are:
All modules are stored in the <install_dir>\modules folder. NOTE: These files have the .so suffix on GNU/Linux. |
Parameters |
Parameters of the selected gateway (the Category field) that are used by the libpurple library. When Type is selected, this field is pre-filled with the appropriate value.
|
Browse |
Determines if the service/conference is available to any user. In other words, if the server lists it within its services/conferences when any XMPP/Jabber Client asks for. Public The Service/Conference will be shown when the client "discovers services". Private The Service/Conference will not be visible to a "discover service" request. The user must explicitly know the service exists. |
Privacy |
You can restrict which accounts can access the services/conference via the IMServices.dat text file. You have to define email addresses which can access it in a special file (plus define the appropriate path to it). The syntax (XEP-0016) is as follows: <item type='jid' value='juliet@example.com' action='allow' order='6'/> <item type='jid' value='benvolio@example.org' action='deny' order='7'/> <item type='jid' value='benvolio@example.org' action='allow' order='8'> <item type='jid' value='mercutio@example.org' action='allow' order='42'/> <item action='deny' order='444'/> </list> To edit this file, use the Edit File button see above. |
|
NOTE: Gateway registration for Facebook is slightly different. For details, refer to the end of the Purple IM Module chapter. |