The sample SIP services which can be deployed with Rhino are: the Proxy, Registrar and Presence services. Together, these services provide basic SIP-server functionality, and are intended to work "out of the box" with minimal configuration.
To get the default SIP examples up and running straight away, follow the quick start instructions here. For more detailed information on building, installing and configuring the examples, see Manual Installation.
Below are instructions on configuring and deploying the sample services.
|
Files referred to in the instructions are in the directory created when extracting the examples, e.g. $RHINO_HOME/rhino-connectivity/sip-2.3.1.0
|
Configure sample SIP services
Before deploying the examples, you must first change the default configuration of the Proxy service to suit your environment. It is configured in the sip.properties file. Edit this file, changing the PROXY_DOMAINS property as follows:
# Proxy SBB configuration # Add domains that the proxy is authoritative for PROXY_DOMAINS=opencloud.com,opencloud.co.nz
The default domains opencloud.com and opencloud.co.nz are just examples — change this property to use the correct domains for your environment.
The PROXY_DOMAINS property contains the domains that the proxy SBB considers to be local. This means that if the proxy SBB receives a request addressed to a user in one of these domains (such as sip:bob@opencloud.com), it will use the location service to find the registered contact address of that user. If the user cannot be found, the Proxy service will return an error response.
If the Proxy service receives a request addressed to a user in an unknown domain, it will forward the request according to normal SIP routing rules.
|
On a Windows host (e.g. running in a VM or via WSL), with user agents on separate PCs, the Windows firewall may block SIP messages sent over the network. You may need to re-configure the firewall to ensure that Rhino can receive SIP messages. |
Deploy sample SIP services
By default, the Ant build script build.xml builds and deploys the Registrar, Proxy and Presence sample services with the components they need (including the SIP resource adaptor and location service), into Rhino.
To deploy the examples, run Ant with the deployexamples target:
$ ant deployexamples
If you don’t have Ant installed, you can use a copy that is bundled with Rhino: run the deployexamples.sh script.
Once you have deployed the sample Registrar, Proxy and Presence services, see Using the Services for instructions on how to test them with your SIP user agents.
