Version 60 (Adrian Georgescu, 05/26/2012 03:34 pm) → Version 61/109 (Adrian Georgescu, 05/26/2012 03:35 pm)

h1. Device Configuration

There are thousands of SIP devices on the market, for how to configure them we advise you to consult the support forum of the device manufacturer.

Please do not open a ticket related to how a particular device must be configured.

Setup your SIP device as follows:

h2. Account Credentials

Account credentials are used for authentication and authorization of SIP requests performed by the SIP device.

| Username| XXX|
| Password| YYY|
| Domain/Realm||

Register must be turned On in order to receive incoming calls.

[[SipDevices|Specific SIP devices configuration]]

h2. Outbound Proxy

There are multiple servers distributed in multiple geographic locations. To locate them, the SIP device must always perform DNS lookups as defined in SIP standard "RFC3263": RFC3263 (NAPTR + SRV + A DNS lookups)

You should never set manually an IP address belonging to SIP2SIP infrastructure into your SIP device. You must use proper DNS lookups instead of hardwiring these setting into your SIP device.

| Host | Port | Protocol |
|| 5060| UDP |
|| 5060| TCP |
|| 5061| TLS |

h2. TLS settings

You may use TLS transport, the server has a valid certificate issued by RapidSSL corresponding to the hostname of the proxy. If the client does not RapidSSL certificate authority loaded, it may fail to validate the certificate. If the client allows it you can download the "RapidSSL root CA": into it. Turn TLS certificate validation off to circumvent the problem.

h2. XCAP Root

If you use SIMPLE presence you need to set XCAP root:

| XCAP Root ||

h2. MSRP Relay

If you use SIMPLE instant messaging based on MSRP, a relay is available for helping traverse the NAT. You need to use the relay if you are the receiving party and you are behind a NAT-ed router. The MSRP relays can be found in the DNS by using SRV lookup for

h2. STUN Servers

You may use STUN for ICE NAT traversal. The STUN servers can be found in the DNS by using SRV lookup for

h2. NAT Traversal

SIP2SIP infrastructure is smart enough to handle the NAT traversal for both SIP signaling and RTP and MSRP media sessions. Practically you should not set any NAT traversal feature in the client, some people do this and can only break things.

* Do not use STUN for Register purposes
* Do not set your client to discover a global IP address