SipDeviceConfiguration
Version 104 (Adrian Georgescu, 09/27/2013 08:23 am)
1 | 65 | Adrian Georgescu | h1. SIP Device Configuration |
---|---|---|---|
2 | 1 | Adrian Georgescu | |
3 | 94 | 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. Please do not open a ticket related to how a particular device must be configured. Setup your SIP device as follows: |
4 | 1 | Adrian Georgescu | |
5 | 1 | Adrian Georgescu | h2. SIP Account Credentials |
6 | 1 | Adrian Georgescu | |
7 | 94 | Adrian Georgescu | Account credentials are used for authentication and authorization of SIP requests performed by the SIP device. Your SIP address is XXX@sip2sip.info replace XXX with the username chosen during the account enrollment. |
8 | 65 | Adrian Georgescu | |
9 | 49 | Adrian Georgescu | | Username| XXX| |
10 | 51 | Adrian Georgescu | | Password| YYY| |
11 | 1 | Adrian Georgescu | | Domain/Realm|sip2sip.info| |
12 | 1 | Adrian Georgescu | |
13 | 94 | Adrian Georgescu | Register must be turned On in order to receive incoming calls. 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. |
14 | 51 | Adrian Georgescu | |
15 | 64 | Adrian Georgescu | [[SipDevices|Specific SIP devices configuration]] |
16 | 1 | Adrian Georgescu | |
17 | 74 | Adrian Georgescu | h2. Server Location |
18 | 1 | Adrian Georgescu | |
19 | 95 | 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). 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. 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. |
20 | 73 | Adrian Georgescu | |
21 | 51 | Adrian Georgescu | | Host | Port | Protocol | |
22 | 51 | Adrian Georgescu | | proxy.sipthor.net| 5060| UDP | |
23 | 1 | Adrian Georgescu | | proxy.sipthor.net| 5060| TCP | |
24 | 103 | Adrian Georgescu | | proxy.sipthor.net| 443| TLS | |
25 | 77 | Adrian Georgescu | |
26 | 96 | Adrian Georgescu | h2. Presence |
27 | 51 | Adrian Georgescu | |
28 | 96 | Adrian Georgescu | h3. XCAP Root |
29 | 1 | Adrian Georgescu | |
30 | 54 | Adrian Georgescu | | XCAP Root | https://xcap.sipthor.net/xcap-root/| |
31 | 51 | Adrian Georgescu | |
32 | 96 | Adrian Georgescu | h3. Required functionality |
33 | 81 | Adrian Georgescu | |
34 | 82 | Adrian Georgescu | To use SIMPLE presence the SIP client must support the following standards related to SIP and XCAP protocols: |
35 | 82 | Adrian Georgescu | |
36 | 90 | Adrian Georgescu | * SIP Presence Agent mode (PUBLISH method) RFC3903 |
37 | 1 | Adrian Georgescu | * Event packages: *presence* and *presence.winfo* |
38 | 98 | Adrian Georgescu | * RLS SUBSCRIBE RFC4662 and RLMI NOTIFY RFC4662 |
39 | 100 | Adrian Georgescu | * XCAP *rls-services* and *resource-lists* for contacts storage RFC4826 |
40 | 100 | Adrian Georgescu | * XCAP *org.openmobilealliance.pres-rules* for authorization rules OMA XML 1.1 |
41 | 90 | Adrian Georgescu | |
42 | 90 | Adrian Georgescu | h3. Optional |
43 | 96 | Adrian Georgescu | |
44 | 96 | Adrian Georgescu | Additional the SIP end-point may support the following extensions: |
45 | 82 | Adrian Georgescu | |
46 | 99 | Adrian Georgescu | * Event packages: *xcap-diff* for synchronizing XCAP documents between clients |
47 | 99 | Adrian Georgescu | * XCAP *org.openmobilealliance.pres-content* document for serving user icon |
48 | 99 | Adrian Georgescu | * XCAP *pidf-manipulation* for offline status |
49 | 99 | Adrian Georgescu | * XCAP *xcap-caps* and *org.openmobilealliance.xcap-directory* for listing all XCAP documents on the server |
50 | 82 | Adrian Georgescu | |
51 | 79 | Adrian Georgescu | Example: Blink SIP client implementation http://projects.ag-projects.com/news/15 |
52 | 79 | Adrian Georgescu | |
53 | 51 | Adrian Georgescu | h2. MSRP Relay |
54 | 1 | Adrian Georgescu | |
55 | 101 | Adrian Georgescu | If you use SIMPLE instant messaging based on "MSRP":http://tools.ietf.org/html/rfc4975, a MSRP "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. |
56 | 53 | Adrian Georgescu | |
57 | 53 | Adrian Georgescu | h2. STUN Servers |
58 | 1 | Adrian Georgescu | |
59 | 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. |
60 | 56 | Adrian Georgescu | |
61 | 56 | Adrian Georgescu | h2. NAT Traversal |
62 | 56 | Adrian Georgescu | |
63 | 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. |
64 | 70 | Adrian Georgescu | |
65 | 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. |
66 | 56 | Adrian Georgescu | |
67 | 1 | Adrian Georgescu | * Do not set your client to discover a global IP address |
68 | 104 | Adrian Georgescu | * "Turn off SIP ALG support in your router":http://www.voip-info.org/wiki/view/Routers+SIP+ALG |