3.2.1 Voipswitch

Voipswitch’s configuration is done through VSM (admin portal). The changes applied there are reflected in the database and taken into effect immediately.  Some of the settings are in the voipswitch_config.xml file, which is located in the Voipswitch’s main directory, usually Program files/Voipswitch. Changes in the file require restarting voipswitch application.

Below instruction pertains only to the RCS part of configuration. Detailed documentation on Voipswitch’s core functions is located here.

TLS SIP listener

The RCS clients communicates with voipswitch using encrypted SIP protocol. In order to enable the TLS listeners you have to add appropriate entries in the voipwitc_conifg.xml file:

<listener type="sip">

  <param name="ipaddr" value="1.2.3.4" />

  <param name="port" value="5061" />

  <param name="transport" value="tls-tcp" />

  <param name="tls-certificate" value="VPS.cert" />

</listener>

<listener type="registrar">

  <param name="ipaddr" value="1.2.3.4" />

  <param name="port" value="5061" />

  <param name="register-expiration" value="3600" />

  <param name="subscribe-expiration" value="3600" />

  <param name="transport" value="tls-tcp" />

</listener>

The above two entries are for the main SIP listener (calls, messages) and the SIP Registrar (Registration, Presence).

TLS requires a certificate used by its encryption procedures. In the tls-certificate value enter the name of the certificate file which should be located in the main voipswitch directory.

It is sufficient to define the certificate only for the main SIP listener, the Registrar will use the same settings.

TODO opisac jak sprawdzic czy jest cert? Co jak nie ma albo wygasl? Jak widac na vpsie ze listenere wystartowal screen.

STUN listener

The clients use STUN protocol to get information about its reflexive IP addresses which are then used in ICE mechanism for peer to peer calling and NAT traversal.

STUN is implemented in voipswitch application as a separate listener. As it is not enabled by default you have to check if the appropriate entry is added to the voipswitch_config.xml file.

<listener type="stun">

  <param name="ipaddr" value="1.2.3.4"/>

  <param name="port" value="3478"/>

</listener>

The RCS clients communicates with voipswitch using encrypted SIP protocol. In order to enable the TLS listeners you have to add appropriate entries in the voipwitc_conifg.xml file:

TODO jak sprawdzic czy diala? Screen z logs vpsa

Buddy list URL

This setting is in the voipswitch_config.xml file.  The service key is the name of the EMCI method which is called by the voipswitch every time when a client sends SUBSCRIBE requests. The method’s name is by default bl.ashx.

The ipaddr value should be the IP address of the EMCI server used for connection with voipswitch. It can be either public or private IP.

The method is secured by the username and password. TODO gdzie to ustawiac w EMCI?

<web_service>

    <param name="ipaddr" value="1.2.3.4"/> - IP WebApi

    <param name="port" value="81"/>

    <param name="username" value=""/>

    <param name="password" value=""/>

    <param name="service" value="bl.ashx"/>

</web_service>