[Spce-user] NGCP 2.6 - mis-routed replys after 180 ringing

Andrew Pogrebennyk apogrebennyk at sipwise.com
Sun Oct 7 10:42:39 EDT 2012


Hello Klaus,

Well, I'm not sure what is wrong, signaling looks perfectly fine to me
and 200 OK has proper Contact and Record-Route headers. But there's no
ACK from the caller. Is it possible to check the trace on machine with
T38Modem? Any debug information from it?

Also kamailio-proxy log doesn't say about mis-routed packets in this
case because neither proxy nor lb received an ACK from T38Modem, right?

Andrew

On 10/05/2012 10:11 PM, Klaus Peter v. Friedeburg wrote:
> Hi Andrew,
> 
> I have sended the PCAP-File dirercly to your Email-account.
> When I see it right the ports in the contact header fields from T38Modem are the same as the sending ports.
> 
> I don’t know what is wrong ....
> 
> I have made an other test: Relaying the calls from T38Modem over an Asterisk, there are no misrouted packets. 2 from 5 faxes are sended without any errors. But this is no solution because asterisk (1.4) dont make T38 passthrougt with fallback to G711 right.
> My target is to build up a fax solution which is transparent for ngcp and handled as a normal SIP-CPE, so that no patches in the kamailio scripts are nessesary.
> 
> 
> Klaus Peter
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Andrew Pogrebennyk [mailto:apogrebennyk at sipwise.com]
>> Gesendet: Freitag, 5. Oktober 2012 15:14
>> An: Klaus Peter v. Friedeburg
>> Cc: spce-user at lists.sipwise.com
>> Betreff: Re: [Spce-user] NGCP 2.6 - mis-routed replys after 180 ringing
>>
>> Hi Klaus,
>>
>> Maybe a full trace for the failed case including replies and ACK and
>> port numbers would help, I just don't see the port information in this one.
>>
>> The problem I've had with T38modem is it was sending the request from
>> different port than it puts into Contact and Via, but the log says ACK
>> is incorrect so we need to check Record-Routing and RURI in the ACK too.
>>
>> On 10/05/2012 03:06 PM, Klaus Peter v. Friedeburg wrote:
>>> Hi,
>>>
>>> I have problems with mis-routed replys in NGCP 2.6:
>>>
>>> This is an initial Invite that works:
>>> *******************************************************************
>>> INVITE sip:9830355 at sip-test.aco-connect.de SIP/2.0
>>> Date: Fri, 05 Oct 2012 12:05:51 GMT
>>> CSeq: 2 INVITE
>>> Via: SIP/2.0/UDP 81.90.192.217:25614;branch=z9hG4bKdc6301ad-520d-e211-9999-000c296dbef0;rport
>>> User-Agent: T38Modem/1.2.0
>>> From: "root" <sip:004956199797437 at sip-test.aco-connect.de>;tag=a061f9ac-520d-e211-9999-000c296dbef0
>>> Call-ID: 3270f9ac-520d-e211-9999-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Organization: Vyacheslav Frolov
>>> To: <sip:9830355 at sip-test.aco-connect.de>
>>> Contact: <sip:004956199797437 at 81.90.192.217:25614>
>>> Proxy-Authorization: Digest username="004956199797437", realm="sip-test.aco-connect.de",
>> nonce="xxxxxxxxx", uri="sip:9830355 at sip-test.aco-connect.de", algorithm=MD5, response="xxxxxxxxxx"
>>> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING
>>> Content-Type: application/sdp
>>> Content-Length: 264
>>> Max-Forwards: 70
>>>
>>> v=0
>>> o=- 1349438751 1 IN IP4 81.90.192.217
>>> s=Opal SIP Session
>>> c=IN IP4 81.90.192.217
>>> t=0 0
>>> m=audio 5000 RTP/AVP 8 101 100
>>> a=sendrecv
>>> a=rtpmap:8 PCMA/8000/1
>>> a=rtpmap:101 telephone-event/8000
>>> a=fmtp:101 0-16,32,36
>>> a=rtpmap:100 NSE/8000
>>> a=fmtp:100 192-193
>>> *******************************************************************
>>>
>>> This is an other initial Invite from the same machine that does not work!
>>> *******************************************************************
>>> INVITE sip:9830355 at sip-test.aco-connect.de SIP/2.0
>>> CSeq: 2 INVITE
>>> Via: SIP/2.0/UDP 81.90.192.217:32770;branch=z9hG4bK50a6fce0-580d-e211-964b-000c296dbef0;rport
>>> User-Agent: T38Modem/2.0.0
>>> From: "root" <sip:004956199797437 at sip-test.aco-connect.de>;tag=707ff4e0-580d-e211-964b-000c296dbef0
>>> Call-ID: e087f4e0-580d-e211-964b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Organization: Vyacheslav Frolov
>>> To: <sip:9830355 at sip-test.aco-connect.de>
>>> Contact: <sip:004956199797437 at 81.90.192.217:32770>
>>> Proxy-Authorization: Digest username="004956199797437", realm="sip-test.aco-connect.de", nonce="
>> xxxxxxxxx", uri="sip:9830355 at sip-test.aco-connect.de", algorithm=MD5, response=" xxxxxxxxx"
>>> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING
>>> Content-Type: application/sdp
>>> Content-Length: 231
>>> Max-Forwards: 70
>>>
>>> v=0
>>> o=- 1349441415 1 IN IP4 81.90.192.217
>>> s=T38Modem/2.0.0
>>> c=IN IP4 81.90.192.217
>>> t=0 0
>>> m=audio 5000 RTP/AVP 8 101
>>> a=sendrecv
>>> a=rtpmap:8 PCMA/8000/1
>>> a=rtpmap:101 telephone-event/8000
>>> a=fmtp:101 0-16,32,36
>>> a=maxptime:240
>>> *******************************************************************
>>>
>>> The kamailio-proxy log show this:
>>> *******************************************************************
>>> Oct  5 14:50:15 sip3 /usr/sbin/kamailio[2436]: INFO: <script>: Appending P-D-URI
>> 'sip:192.168.100.55:5060;received='sip:62.180.237.70:5060;transport=udp'' - R=sip:4
>>> 95619830355 at 62.180.237.70:5060;transport=udp ID=e087f4e0-580d-e211-964b-000c296dbef0 at fax2fax-
>> test.aco-connect.de
>>> Oct  5 14:50:15 sip3 /usr/sbin/kamailio[2436]: INFO: <script>: Forcing request via B2BUA
>> 'sip:192.168.100.55:5080' - R=sip:495619830355 at 62.180.237.70:5060;transport
>>> =udp ID=e087f4e0-580d-e211-964b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:15 sip3 /usr/sbin/kamailio[2436]: INFO: <script>: Setting P-Caller-UUID to '18205f5a-cfe6-49fc-
>> 9937-0a64d090498b' - R=sip:495619830355 at 62.180.237.70:50
>>> 60;transport=udp ID=e087f4e0-580d-e211-964b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:15 sip3 /usr/sbin/kamailio[2436]: INFO: <script>: Setting P-Callee-UUID to '0' -
>> R=sip:495619830355 at 62.180.237.70:5060;transport=udp ID=e087f4e0-580d-e
>>> 211-964b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:15 sip3 /usr/sbin/kamailio[2436]: INFO: <script>: Request leaving server, D-
>> URI='sip:192.168.100.55:5080' - R=sip:495619830355 at 62.180.237.70:5060;trans
>>> port=udp ID=e087f4e0-580d-e211-964b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:15 sip3 /usr/sbin/kamailio[2439]: INFO: <script>: NAT-Reply - S=100 - Connecting M=INVITE
>> IP=81.90.192.217:32770 (192.168.100.55:5080) ID=e087f4e0-580d
>>> -e211-964b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:18 sip3 /usr/sbin/kamailio[2428]: INFO: <script>: NAT-Reply - S=180 - Ringing M=INVITE
>> IP=81.90.192.217:32770 (192.168.100.55:5080) ID=e087f4e0-580d-e2
>>> 11-964b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:23 sip3 /usr/sbin/kamailio[2444]: INFO: <script>: NAT-Reply - S=200 - OK M=INVITE
>> IP=81.90.192.217:32770 (192.168.100.55:5080) ID=e087f4e0-580d-e211-96
>>> 4b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:23 sip3 /usr/sbin/kamailio[2448]: INFO: <script>: New request - M=ACK R=sip:9830355 at sip-
>> test.aco-connect.de F=sip:004956199797437 at sip-test.aco-connect.
>>> de T=sip:9830355 at sip-test.aco-connect.de IP=81.90.192.217:32770 (192.168.100.55:5060) ID=e087f4e0-
>> 580d-e211-964b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:23 sip3 /usr/sbin/kamailio[2448]: INFO: <script>: Relaying request, du='<null>' -
>> R=sip:9830355 at sip-test.aco-connect.de ID=e087f4e0-580d-e211-964b-000c
>>> 296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:23 sip3 /usr/sbin/kamailio[2442]: INFO: <script>: New request - M=ACK R=sip:9830355 at sip-
>> test.aco-connect.de F=sip:056199797437 at sip-test.aco-connect.de
>>> T=sip:9830355 at sip-test.aco-connect.de IP=81.90.192.214:5060 (192.168.100.55:5060) ID=e087f4e0-580d-
>> e211-964b-000c296dbef0 at fax2fax-test.aco-connect.de
>>> Oct  5 14:50:23 sip3 /usr/sbin/kamailio[2442]: INFO: <script>: Dropping mis-routed request -
>> R=sip:9830355 at sip-test.aco-connect.de ID=e087f4e0-580d-e211-964b-000c29
>>> 6dbef0 at fax2fax-test.aco-connect.de
>>> *******************************************************************
>>>
>>> Nothing in sems log!
>>>
>>> The differences are in the SDP body
>>> But what is wrong?????
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/listinfo/spce-user
>>>
> 





More information about the Spce-user mailing list