Posted by eltjoboersma
on April 22, 2008 at 8:03 AM PDT
SailFin adds SIP to the JEE equation, SIP takes a slight different, more elaborate, approach on address and ports than HTTP does. Here I will provide an overview how the configuration model for SailFin looks like and how you can configure it to your needs.
SailFin adds SIP to the JEE equation, SIP takes a slight different, more elaborate, approach on address and ports than HTTP does.
Approach and concepts
Still for SailFin we tried to align as much as possible to the configuration model of the web container.
I.e. we introduced sip-service
much in line with the http-service
(however we do not use the concept of virual servers) and have sip-listeners
within this sip-service similar to the http-listeners
Note that these concepts are how you'll find them when using the asadmin console commands and in the domain.xml. In the GUI they are indicated with some more friendly names.
There is also the concept of a sip-container
that is derived from the web-container
and other containers.
I won't go into every tiny detail of these concepts, but will focus on the address and port settings. Also I will not talk about the converged loadbalancer settings and I won't go much into details on cluster settings either, that is perhaps stuff for a future blog. For configuring addresses and ports we have to take a closer look at the sip-listener and sip-container.
The server port on which the sip container listens on for things like incoming INVITES can be configured using a sip-listener. There can be multiple configured. SailFin comes with the default port as defined in the SIP specification 5060. Lets have a look at these settings: Type the following on the console of a running SailFin with default domain.
asadmin> list server.sip-service.sip-listener.*
This should result in the following list:
There are two sip-listeners; sip-listener-1 and sip-listener-2 (which has a ssl part attached it). They relate to what in SIP terms are called the SIP and a SIPS port. Let