Below are instructions for configuring typical network, SIP identity, and SIP server user-agent settings.

  • If you haven’t already, first deploy the sample SIP services into Rhino (see Quickstart or Manual Installation).

  • The following settings must be configured correctly before using the sample SIP services with Rhino (or any SIP server).

Default network port

A SIP user agent must listen on a network port, so that it can receive incoming calls or messages. The default port for SIP is 5060. Most user agents will attempt to use this port, and this is almost always the correct configuration.

However, if Rhino and a user agent are running on the same host, then there may be a conflict (because Rhino’s SIP resource adaptor defaults to port 5060 as well). If this is the case, you must change the port that either the SIP RA or the user agent uses. See Manual Installation for instructions on changing the port that the SIP RA uses.

If your user agent is running on a different host to Rhino, then no additional network configuration should be necessary.

SIP identity

Your SIP identity (sometimes called "address of record") is the public SIP address that you share with others so they can contact you. It is like your phone number or email address, and usually looks like sip:username@domain (for example,

When your user agent starts, it will register your SIP identity with the SIP server. The SIP server binds your SIP identity to the network address of your user agent (its contact address). This lets other users call you without knowing your user agent’s network address.

Unless you are integrating with an existing SIP network, the SIP identity you choose can be anything. However, the domain part of your identity ( should be one of the domains known by the sample Proxy service (see the PROXY_DOMAINS property described in Quickstart). This is so the proxy service forwards requests to your user agent’s contact address.

SIP servers

You need to tell your user agent which SIP servers it will use. Depending on the particular user agent, you may have to configure several SIP server addresses, for different SIP services. (Often a user agent will just require a single server address that it uses for everything.)

The typical types of server that you may need to configure are:

Server What it does


Receives registration and unregistration requests from your user agent, and updates a location service with your SIP identity and the user agent’s network address.

Proxy (or outbound proxy)

Receives messages or calls from the user agent, and figures out how to route them to their destination.


Provides the status of other users to the user agent (for example, for buddy lists), and lets it publish its own status information (such as "available", "busy", or "away").

Tip Some user agents may assume that the same server will provide all these services.

To configure your SIP servers, enter the address of your Rhino server in the appropriate fields. Often this will need to be in the form of a SIP URI. For example if Rhino is running on the machine and using port 5060, then the SIP address of the server would be

Previous page Next page