Difference between revisions of "TELES configuration"
From Kolmisoft Wiki
Jump to navigationJump to search
Line 8: | Line 8: | ||
<--- SIP read from ''' | <--- SIP read from '''181.29.146.70:1831''' ---> | ||
ACK sip:393932891230@ | ACK sip:393932891230@162.192.26.181:5060 SIP/2.0 | ||
Via: SIP/2.0/UDP | Via: SIP/2.0/UDP 181.29.146.70:1831;branch=z9hG4bK00E0F51004B48887365D000000C5 | ||
Route: <sip:''' | Route: <sip:'''181.29.146.70:5060'''> | ||
From: <sip:4369910439372@ | From: <sip:4369910439372@181.29.146.70>;tag=00E0F51004B48887365D00001AEC | ||
To: <sip:393932891230@ | To: <sip:393932891230@162.192.26.181>;tag=as7fcd3c74 | ||
Call-ID: 00E0F51004B48887365D000016D6@ | Call-ID: 00E0F51004B48887365D000016D6@181.29.146.70 | ||
CSeq: 42891 ACK | CSeq: 42891 ACK | ||
Max-Forwards: 70 | Max-Forwards: 70 | ||
To accept calls from such device, you need to set correct port for it in MOR. | To accept calls from such device, you need to set correct port for it in MOR. |
Revision as of 16:14, 23 December 2008
TELES has some weirdness with SIP.
It reports that sends calls from port 5060 but actually sends calls from different port. In our case it was 1831:
Useragent: TELES.iSWITCH
<--- SIP read from 181.29.146.70:1831 ---> ACK sip:393932891230@162.192.26.181:5060 SIP/2.0 Via: SIP/2.0/UDP 181.29.146.70:1831;branch=z9hG4bK00E0F51004B48887365D000000C5 Route: <sip:181.29.146.70:5060> From: <sip:4369910439372@181.29.146.70>;tag=00E0F51004B48887365D00001AEC To: <sip:393932891230@162.192.26.181>;tag=as7fcd3c74 Call-ID: 00E0F51004B48887365D000016D6@181.29.146.70 CSeq: 42891 ACK Max-Forwards: 70
To accept calls from such device, you need to set correct port for it in MOR.