SipDeviceConfiguration

Version 74 (Adrian Georgescu, 11/04/2012 05:25 pm)

1 65 Adrian Georgescu
h1. SIP Device Configuration
2 1 Adrian Georgescu
3 35 Adrian Georgescu
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. 
4 1 Adrian Georgescu
5 35 Adrian Georgescu
Please do not open a ticket related to how a particular device must be configured.
6 1 Adrian Georgescu
7 1 Adrian Georgescu
Setup your SIP device as follows:
8 1 Adrian Georgescu
9 65 Adrian Georgescu
h2.  SIP Account Credentials
10 1 Adrian Georgescu
 
11 1 Adrian Georgescu
Account credentials are used for authentication and authorization of SIP requests performed by the SIP device.
12 65 Adrian Georgescu
13 65 Adrian Georgescu
Your SIP address is XXX@sip2sip.info replace XXX with the username chosen during the account enrollment.
14 49 Adrian Georgescu
15 51 Adrian Georgescu
| Username| XXX|
16 1 Adrian Georgescu
| Password| YYY|
17 52 Adrian Georgescu
| Domain/Realm|sip2sip.info|
18 1 Adrian Georgescu
19 1 Adrian Georgescu
Register must be turned On in order to receive incoming calls.
20 1 Adrian Georgescu
21 64 Adrian Georgescu
If your SIP devices is smart enough, there is no need to set manually anything else than the above settings. If you need to manually fine tune the configuration read below.
22 51 Adrian Georgescu
23 64 Adrian Georgescu
[[SipDevices|Specific SIP devices configuration]]
24 1 Adrian Georgescu
25 74 Adrian Georgescu
h2. Server Location
26 1 Adrian Georgescu
27 62 Adrian Georgescu
There are multiple SIP servers distributed in multiple geographic locations. To locate them, the SIP device must always perform DNS lookups as defined in SIP standard "RFC3263":http://www.ietf.org/rfc/rfc3263.txt (NAPTR + SRV + A DNS lookups)
28 59 Adrian Georgescu
29 74 Adrian Georgescu
You must never set manually a host address or transport belonging to SIP2SIP server infrastructure into your SIP device as it may and will change over time. Your device must use DNS lookups instead of hardwiring any such settings into your SIP device.
30 1 Adrian Georgescu
31 73 Adrian Georgescu
For informational purposes, the servers are reachable at the following addresses, but again you must query the DNS to discover them as they may and will change in the future.
32 73 Adrian Georgescu
33 51 Adrian Georgescu
| Host | Port | Protocol |
34 51 Adrian Georgescu
| proxy.sipthor.net| 5060| UDP |
35 1 Adrian Georgescu
| proxy.sipthor.net| 5060| TCP |
36 72 Adrian Georgescu
| proxy.sipthor.net| 5061| TLS |
37 57 Adrian Georgescu
38 63 Adrian Georgescu
h2. TLS Settings
39 60 Adrian Georgescu
40 63 Adrian Georgescu
You may use TLS transport, the SIP servers have a valid X.509 certificate issued by "RapidSSL":http://www.rapidssl.com corresponding to the proxy.sipthor.net 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":http://www.geotrust.com/resources/root_certificates/certificates/Equifax_Secure_Certificate_Authority.cer  into it. Turn TLS certificate validation off to circumvent the problem. 
41 1 Adrian Georgescu
42 73 Adrian Georgescu
TLS as  any other transport like UDP or TCP may not be always available, set your SIP device to use DNS to discover which transport is available.
43 50 Adrian Georgescu
44 51 Adrian Georgescu
h2. XCAP Root
45 51 Adrian Georgescu
46 34 Adrian Georgescu
If you use SIMPLE presence you need to set XCAP root:
47 1 Adrian Georgescu
48 54 Adrian Georgescu
| XCAP Root | https://xcap.sipthor.net/xcap-root/|
49 51 Adrian Georgescu
50 51 Adrian Georgescu
h2. MSRP Relay
51 1 Adrian Georgescu
52 69 Adrian Georgescu
If you use SIMPLE instant messaging based on "MSRP":http://tools.ietf.org/html/rfc4975, a "relay":http://tools.ietf.org/html/rfc4976 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 _msrps._tcp.sip2sip.info.
53 53 Adrian Georgescu
54 53 Adrian Georgescu
h2. STUN Servers
55 1 Adrian Georgescu
56 56 Adrian Georgescu
You may use STUN for ICE NAT traversal. The STUN servers can be found in the DNS by using SRV lookup for _stun._udp.sip2sip.info.
57 56 Adrian Georgescu
58 56 Adrian Georgescu
h2. NAT Traversal
59 56 Adrian Georgescu
60 70 Adrian Georgescu
SIP2SIP infrastructure is smart enough to handle the NAT traversal for both SIP signaling, RTP and MSRP media sessions. Also it supports ICE negotiation in the clients and provides automatically a TURN relay candidate. 
61 70 Adrian Georgescu
62 70 Adrian Georgescu
Practically, you should not set any NAT traversal features in the client as the chance of fixing things is much smaller than breaking them.
63 56 Adrian Georgescu
64 56 Adrian Georgescu
 * Do not use STUN for Register purposes
65 56 Adrian Georgescu
 * Do not set your client to discover a global IP address