SipDeviceConfiguration

Version 59 (Adrian Georgescu, 05/26/2012 03:33 pm)

1 51 Adrian Georgescu
h1. Device Configuration
2 1 Adrian Georgescu
3 51 Adrian Georgescu
4 51 Adrian Georgescu
5 51 Adrian Georgescu
6 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. 
7 1 Adrian Georgescu
8 35 Adrian Georgescu
Please do not open a ticket related to how a particular device must be configured.
9 1 Adrian Georgescu
10 1 Adrian Georgescu
Setup your SIP device as follows:
11 1 Adrian Georgescu
12 51 Adrian Georgescu
h2.  Account Credentials
13 1 Adrian Georgescu
 
14 1 Adrian Georgescu
Account credentials are used for authentication and authorization of SIP requests performed by the SIP device.
15 49 Adrian Georgescu
16 51 Adrian Georgescu
| Username| XXX|
17 1 Adrian Georgescu
| Password| YYY|
18 52 Adrian Georgescu
| Domain/Realm|sip2sip.info|
19 1 Adrian Georgescu
20 59 Adrian Georgescu
Register must be turned On in order to receive incoming calls.
21 1 Adrian Georgescu
22 51 Adrian Georgescu
[[SipDevices|Specific SIP devices configuration]]
23 48 Adrian Georgescu
24 1 Adrian Georgescu
25 1 Adrian Georgescu
h2. Outbound Proxy
26 1 Adrian Georgescu
27 59 Adrian Georgescu
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 (NAPTR + SRV + A DNS lookups)
28 59 Adrian Georgescu
29 59 Adrian Georgescu
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.
30 38 Adrian Georgescu
31 51 Adrian Georgescu
| Host | Port | Protocol |
32 51 Adrian Georgescu
| proxy.sipthor.net| 5060| UDP |
33 1 Adrian Georgescu
| proxy.sipthor.net| 5060| TCP |
34 1 Adrian Georgescu
| proxy.sipthor.net| 5061| TLS |
35 57 Adrian Georgescu
36 57 Adrian Georgescu
h2. TLS settings
37 57 Adrian Georgescu
38 58 Adrian Georgescu
You may use TLS transport, the server has a valid certificate issued by RapidSSL 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. Turn TLS certificate validation off to circumvent the problem. 
39 57 Adrian Georgescu
40 34 Adrian Georgescu
41 50 Adrian Georgescu
42 51 Adrian Georgescu
h2. XCAP Root
43 51 Adrian Georgescu
44 34 Adrian Georgescu
If you use SIMPLE presence you need to set XCAP root:
45 1 Adrian Georgescu
46 54 Adrian Georgescu
| XCAP Root | https://xcap.sipthor.net/xcap-root/|
47 51 Adrian Georgescu
48 51 Adrian Georgescu
h2. MSRP Relay
49 1 Adrian Georgescu
50 1 Adrian Georgescu
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 _msrps._tcp.sip2sip.info.
51 53 Adrian Georgescu
52 53 Adrian Georgescu
h2. STUN Servers
53 1 Adrian Georgescu
54 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.
55 56 Adrian Georgescu
56 56 Adrian Georgescu
h2. NAT Traversal
57 56 Adrian Georgescu
58 56 Adrian Georgescu
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.
59 56 Adrian Georgescu
60 56 Adrian Georgescu
 * Do not use STUN for Register purposes
61 56 Adrian Georgescu
 * Do not set your client to discover a global IP address