What does debugging log and siptrace show?
sofia global siptrace on
You can also look at the Sofia SIP stack debugging information to see if there's an error occuring in the stack that's ignoring the packet.
sofia loglevel all 9
-Steve 2011/1/19 ZILOT <yurazilot1@list.ru>
I have one problem - my FS doesn't answer on OK from the provider. Probably the problem consists in an incorrectness incoming OK. Please help.
U 2011/01/19 11:04:05.243062 194.190.211.190:5060 -> 77.72.17.23:5060 INVITE sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23>SIP/2.0. Via: SIP/2.0/UDP 194.190.211.190;rport;branch=z9hG4bK6rQjK6B04ZeNN. Max-Forwards: 69. From: "DEN78141_120" <sip:TCAPI_User@77.72.17.23<sip%3ATCAPI_User@77.72.17.23> ;transport=udp>;tag=vZcKXKa0Q7B1e. To: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23>>. Call-ID: 86959393-9e45-122e-1782-33002db2a994. CSeq: 7376058 INVITE. Contact: <sip:gw+trunk_8@194.190.211.190:5060;transport=udp;gw=trunk_8>. User-Agent: Configured by 2600hz. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE. Supported: precondition, path, replaces. Allow-Events: talk, presence, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer. Content-Type: application/sdp. Content-Disposition: session. Content-Length: 298. X-FS-Support: update_display. Remote-Party-ID: "DEN78141_120" <sip:DEN78141_120@77.72.17.23<sip%3ADEN78141_120@77.72.17.23>
;party=calling;screen=yes;privacy=off. . v=0. o=FreeSWITCH 1295404175 1295404176 IN IP4 194.190.211.190. s=FreeSWITCH. c=IN IP4 194.190.211.190. t=0 0. m=audio 20070 RTP/AVP 0 9 8 101 13. a=rtpmap:0 PCMU/8000. a=rtpmap:9 G722/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=rtpmap:13 CN/8000. a=ptime:30.
U 2011/01/19 11:04:05.288882 77.72.17.23:5060 -> 194.190.211.190:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP 194.190.211.190:5060;rport;branch=z9hG4bK6rQjK6B04ZeNN. From: "DEN78141_120" <sip:TCAPI_User@77.72.17.23<sip%3ATCAPI_User@77.72.17.23> ;transport=udp>;tag=vZcKXKa0Q7B1e. To: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23>
;tag=0eff5d003cff3610ff00001372630472. Call-ID: 86959393-9e45-122e-1782-33002db2a994. CSeq: 7376058 INVITE. Contact: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23> ;user=phone>. Server: MERA MSIP v.1.0.2. Content-Length: 0. .
U 2011/01/19 11:04:06.609863 77.72.17.23:5060 -> 194.190.211.190:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP 194.190.211.190:5060;rport;branch=z9hG4bK6rQjK6B04ZeNN. From: "DEN78141_120" <sip:TCAPI_User@77.72.17.23<sip%3ATCAPI_User@77.72.17.23> ;transport=udp>;tag=vZcKXKa0Q7B1e. To: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23>
;tag=0eff5d003cff3610ff00001372630472. Call-ID: 86959393-9e45-122e-1782-33002db2a994. CSeq: 7376058 INVITE. Contact: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23> ;user=phone>. Server: MERA MSIP v.1.0.2. Content-Type: application/sdp. Content-Length: 212. . v=0. o=- 1295424317 1295424317 IN IP4 77.72.17.23. s=-. c=IN IP4 77.72.17.23. t=0 0. m=audio 18360 RTP/AVP 0 8 101. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15.
U 2011/01/19 11:04:14.238660 77.72.17.23:5060 -> 194.190.211.190:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 194.190.211.190:5060;rport;branch=z9hG4bK6rQjK6B04ZeNN. From: "DEN78141_120" <sip:TCAPI_User@77.72.17.23<sip%3ATCAPI_User@77.72.17.23> ;transport=udp>;tag=vZcKXKa0Q7B1e. To: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23>
;tag=0eff5d003cff3610ff00001372630472. Call-ID: 86959393-9e45-122e-1782-33002db2a994. CSeq: 7376058 INVITE. Contact: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23> ;user=phone>. Server: MERA MSIP v.1.0.2. Content-Type: application/sdp. Content-Length: 212. . v=0. o=- 1295424325 1295424325 IN IP4 77.72.17.23. s=-. c=IN IP4 77.72.17.23. t=0 0. m=audio 18360 RTP/AVP 0 8 101. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15.
U 2011/01/19 11:04:14.246657 77.72.17.23:5060 -> 194.190.211.190:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 194.190.211.190:5060;rport;branch=z9hG4bK6rQjK6B04ZeNN. From: "DEN78141_120" <sip:TCAPI_User@77.72.17.23<sip%3ATCAPI_User@77.72.17.23> ;transport=udp>;tag=vZcKXKa0Q7B1e. To: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23>
;tag=0eff5d003cff3610ff00001372630472. Call-ID: 86959393-9e45-122e-1782-33002db2a994. CSeq: 7376058 INVITE. Contact: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23> ;user=phone>. Server: MERA MSIP v.1.0.2. Content-Type: application/sdp. Content-Length: 212. . v=0. o=- 1295424325 1295424325 IN IP4 77.72.17.23. s=-. c=IN IP4 77.72.17.23. t=0 0. m=audio 18360 RTP/AVP 0 8 101. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15.
U 2011/01/19 11:04:14.747863 77.72.17.23:5060 -> 194.190.211.190:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 194.190.211.190:5060;rport;branch=z9hG4bK6rQjK6B04ZeNN. From: "DEN78141_120" <sip:TCAPI_User@77.72.17.23<sip%3ATCAPI_User@77.72.17.23> ;transport=udp>;tag=vZcKXKa0Q7B1e. To: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23>
;tag=0eff5d003cff3610ff00001372630472. Call-ID: 86959393-9e45-122e-1782-33002db2a994. CSeq: 7376058 INVITE. Contact: <sip:74742515541@77.72.17.23 <sip%3A74742515541@77.72.17.23> ;user=phone>. Server: MERA MSIP v.1.0.2. Content-Type: application/sdp. Content-Length: 212. . v=0. o=- 1295424325 1295424325 IN IP4 77.72.17.23. s=-. c=IN IP4 77.72.17.23. t=0 0. m=audio 18360 RTP/AVP 0 8 101. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15.
-- Почта@Mail.Ru в твоем мобильном. Просто зайди с телефона на m.mail.ru
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org