SipDeviceConfiguration

Version 58 (Adrian Georgescu, 05/26/2012 03:28 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 1 Adrian Georgescu
* Always Register must be On
21 51 Adrian Georgescu
* There are multiple servers available in multiple locations. To locate them, the SIP device must always perform DNS lookups as defined in SIP standard RFC3263.
22 1 Adrian Georgescu
23 51 Adrian Georgescu
[[SipDevices|Specific SIP devices configuration]]
24 48 Adrian Georgescu
25 1 Adrian Georgescu
26 1 Adrian Georgescu
h2. Outbound Proxy
27 51 Adrian Georgescu
28 55 Adrian Georgescu
We use a variable numbers of geographically distributed SIP servers. You should never set manually an IP address into your SIP device. You must use proper DNS lookups (NAPTR + SRV + A lookups) instead of hardwiring these setting into your SIP device.
29 38 Adrian Georgescu
30 51 Adrian Georgescu
| Host | Port | Protocol |
31 51 Adrian Georgescu
| proxy.sipthor.net| 5060| UDP |
32 1 Adrian Georgescu
| proxy.sipthor.net| 5060| TCP |
33 1 Adrian Georgescu
| proxy.sipthor.net| 5061| TLS |
34 57 Adrian Georgescu
35 57 Adrian Georgescu
h2. TLS settings
36 57 Adrian Georgescu
37 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. 
38 57 Adrian Georgescu
39 34 Adrian Georgescu
40 50 Adrian Georgescu
41 51 Adrian Georgescu
h2. XCAP Root
42 51 Adrian Georgescu
43 34 Adrian Georgescu
If you use SIMPLE presence you need to set XCAP root:
44 1 Adrian Georgescu
45 54 Adrian Georgescu
| XCAP Root | https://xcap.sipthor.net/xcap-root/|
46 51 Adrian Georgescu
47 51 Adrian Georgescu
h2. MSRP Relay
48 1 Adrian Georgescu
49 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.
50 53 Adrian Georgescu
51 53 Adrian Georgescu
h2. STUN Servers
52 1 Adrian Georgescu
53 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.
54 56 Adrian Georgescu
55 56 Adrian Georgescu
h2. NAT Traversal
56 56 Adrian Georgescu
57 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.
58 56 Adrian Georgescu
59 56 Adrian Georgescu
 * Do not use STUN for Register purposes
60 56 Adrian Georgescu
 * Do not set your client to discover a global IP address