SipDeviceConfiguration » History » Version 56
Adrian Georgescu, 05/26/2012 03:09 PM
| 1 | 51 | Adrian Georgescu | h1. Device Configuration |
|---|---|---|---|
| 2 | 1 | Adrian Georgescu | |
| 3 | 51 | Adrian Georgescu | |
| 4 | |||
| 5 | |||
| 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 | Setup your SIP device as follows: |
||
| 11 | |||
| 12 | 51 | Adrian Georgescu | h2. Account Credentials |
| 13 | 1 | Adrian Georgescu | |
| 14 | 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 | * Always Register must be On |
||
| 21 | 51 | Adrian Georgescu | * Set the Registration refresh interval to 600 seconds |
| 22 | 54 | Adrian Georgescu | * You may use TLS transport, the server has a valid certificate issued by RapidSSL |
| 23 | 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. |
| 24 | 1 | Adrian Georgescu | |
| 25 | 51 | Adrian Georgescu | [[SipDevices|Specific SIP devices configuration]] |
| 26 | 48 | Adrian Georgescu | |
| 27 | 1 | Adrian Georgescu | |
| 28 | h2. Outbound Proxy |
||
| 29 | 51 | Adrian Georgescu | |
| 30 | 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. |
| 31 | 38 | Adrian Georgescu | |
| 32 | 51 | Adrian Georgescu | | Host | Port | Protocol | |
| 33 | | proxy.sipthor.net| 5060| UDP | |
||
| 34 | | proxy.sipthor.net| 5060| TCP | |
||
| 35 | | proxy.sipthor.net| 5061| TLS | |
||
| 36 | 34 | Adrian Georgescu | |
| 37 | 50 | Adrian Georgescu | |
| 38 | 51 | Adrian Georgescu | h2. XCAP Root |
| 39 | |||
| 40 | 34 | Adrian Georgescu | If you use SIMPLE presence you need to set XCAP root: |
| 41 | 1 | Adrian Georgescu | |
| 42 | 54 | Adrian Georgescu | | XCAP Root | https://xcap.sipthor.net/xcap-root/| |
| 43 | 51 | Adrian Georgescu | |
| 44 | h2. MSRP Relay |
||
| 45 | 1 | Adrian Georgescu | |
| 46 | 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. |
||
| 47 | 53 | Adrian Georgescu | |
| 48 | h2. STUN Servers |
||
| 49 | 1 | Adrian Georgescu | |
| 50 | 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. |
| 51 | |||
| 52 | h2. NAT Traversal |
||
| 53 | |||
| 54 | 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. |
||
| 55 | |||
| 56 | * Do not use STUN for Register purposes |
||
| 57 | * Do not set your client to discover a global IP address |