Product SiteDocumentation Site

2.3. Configuring

 

2.3.1. Configuring SIP Connectors

You can add SIP Connectors in the same way that you add HTTP Connectors: by adding a Connector element under the Service element in the container's server.xml configuration file.
For example, to add a SIP Connector on the IP address 127.0.0.1, on port 5080, using the UDP transport protocol, you should insert the following XML element:
Provided here are descriptions of the SIP Connector element's attributes:
port
The number of the port on which the container will be able to receive SIP messages.
ipAddress
The IP address at which the container will be able to receive SIP messages.
protocol
This attribute specifies that this is a SIP Connector and not an HTTP Connector. There is no need to change this property.
signalingTransport
the transport on which the container will be able to receive SIP messages: “udp” for example
useStun
Setting this attribute to “true” enables STUN support for this Connector. If you set it to “true”, ensure that the ipAddress attribute is not set to 127.0.0.1. This attribute defaults to “false”. Refer to the documentation on STUN support for more information regarding STUN support.
stunServerAddress
Set this to the STUN server address that will be used to discover the public IP address of this SIP Connector. This attribute is only required if the useStun attribute is set to “true”. Refer to the documentation on STUN support for more information regarding STUN support.
stunServerPort
This attribute should be set to the STUN server port of the STUN server used in the stunServerAddress attribute. You should rarely need to change this attribute; also, it is only needed if the useStun attribute is set to “true”. Refer to the documentation on STUN support for more information regarding STUN support.
sipStackPropertiesFile
The underlying JAIN SIP stack implementation can be further configured through a set of properties (see JAIN SIP configuration properties and the NIST SIP implementation configuration properties ). You should set this property to the location of the file that that contains key-value pairs corresponding to the stack configuration properties. If this property is omitted, the following default values are assumed:
  • gov.nist.javax.sip.LOG_MESSAGE_CONTENT=true
  • gov.nist.javax.sip.TRACE_LEVEL=32
  • gov.nist.javax.sip.DEBUG_LOG=logs/mss-jsip-debuglog.txt
  • gov.nist.javax.sip.SERVER_LOG=logs/mss-jsip-messages.xml
  • javax.sip.STACK_NAME=Mobicents-SIP-Servlets
  • javax.sip.AUTOMATIC_DIALOG_SUPPORT=off
  • gov.nist.javax.sip.DELIVER_UNSOLICITED_NOTIFY=true
  • gov.nist.javax.sip.THREAD_POOL_SIZE=64
  • gov.nist.javax.sip.REENTRANT_LISTENER=true
logLevel
The log level of the underlying JAIN SIP stack.
debugLog
The debug log location of the underlying JAIN SIP stack.
serverLog
The server log location of the underlying JAIN SIP stack.
sipStackName
The name of the underlying JAIN SIP sack.
sipPathName
The JAIN SIP stack implementation to use. You will probably never need to change the value of this attribute. It defaults to the famous NIST SIP stack. If you ever do change this value, you should remember to insert the JAIN SIP JAR implementation in the container's lib directory.