Re: [Serusers] problem with BYE

Hi all, I have very strange problem with SER. I am making incoming call from PSTN to SER, then number translation (exec_dset) from 12124051759 -> 250000007 And then it hitting my ATA (same with motorolla, innomedia) When I then hung up on ATA side it sends BYE (which goes as loose routing) to SER -> CISCO, CISCO answer OK to SER then to ATA but ATA looks like does not like this OK... sending BYE again and again I have attached config to the letter.. pleas look at it and may be you will have some correction PS: Absolutely same problem I have with incoming call via TCP from another provider Thank you! [root@ser etc]# ngrepcr -q 12124051759 U 209.227.182.44:51835 -> 209.227.182.43:5060 INVITE sip:12124051759@209.227.182.43:5060 SIP/2.0 Via: SIP/2.0/UDP 209.227.182.44:5060 From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43> Date: Fri, 30 Apr 2004 15:30:12 GMT Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 Supported: timer,100rel Min-SE: 1800 Cisco-Guid: 459440422-2582778328-2951146144-256312224 User-Agent: Cisco-SIPGateway/IOS-12.x Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO CSeq: 101 INVITE Max-Forwards: 6 Remote-Party-ID: <sip:2126882781@209.227.182.44>;party=calling;screen=yes;privacy=off Timestamp: 1083339012 Contact: <sip:2126882781@209.227.182.44:5060> Expires: 180 Allow-Events: telephone-event Content-Type: application/sdp Content-Length: 426 v=0 o=CiscoSystemsSIP-GW-UserAgent 2183 5028 IN IP4 209.227.182.44 s=SIP Call c=IN IP4 209.227.182.44 t=0 0 m=audio 19266 RTP/AVP 18 4 0 100 101 19 c=IN IP4 209.227.182.44 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=yes a=rtpmap:4 G723/8000 a=fmtp:4 annexa=no a=rtpmap:0 PCMU/8000 a=rtpmap:100 X-NSE/8000 a=fmtp:100 192-194 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:19 CN/8000 a=direction:active U 209.227.182.43:5060 -> 209.227.182.44:5060 SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP 209.227.182.44:5060 From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43> Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 101 INVITE Server: Sip EXpress router (0.8.12-tcp_nonb (i386/linux)) Content-Length: 0 Warning: 392 209.227.182.43:5060 "Noisy feedback tells: pid=6791 req_src_ip=209.227.182.44 req_src_port=51835 in_uri=sip:1212 4051759@209.227.182.43:5060 out_uri=sip:250000007@216.236.137.226:1102;user=phone;transport=udp via_cnt==1" U 209.227.182.43:5060 -> 216.236.137.226:1102 INVITE sip:250000007@216.236.137.226:1102;user=phone;transport=udp SIP/2.0 Record-Route: <sip:12124051759@209.227.182.43;ftag=DC7456A0-3FE;lr=on> Via: SIP/2.0/UDP 209.227.182.43;branch=z9hG4bK8198.2b7612d2.0 Via: SIP/2.0/UDP 209.227.182.44:5060 From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43> Date: Fri, 30 Apr 2004 15:30:12 GMT Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 Supported: timer,100rel Min-SE: 1800 Cisco-Guid: 459440422-2582778328-2951146144-256312224 User-Agent: Cisco-SIPGateway/IOS-12.x Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO CSeq: 101 INVITE Max-Forwards: 5 Remote-Party-ID: <sip:2126882781@209.227.182.44>;party=calling;screen=yes;privacy=off Timestamp: 1083339012 Contact: <sip:2126882781@209.227.182.44:5060> Expires: 180 Allow-Events: telephone-event Content-Type: application/sdp Content-Length: 426 P-hint: request forced to rtp proxy v=0 o=CiscoSystemsSIP-GW-UserAgent 2183 5028 IN IP4 209.227.182.44 s=SIP Call c=IN IP4 209.227.182.43 t=0 0 m=audio 55824 RTP/AVP 18 4 0 100 101 19 c=IN IP4 209.227.182.43 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=yes a=rtpmap:4 G723/8000 a=fmtp:4 annexa=no a=rtpmap:0 PCMU/8000 a=rtpmap:100 X-NSE/8000 a=fmtp:100 192-194 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtpmap:19 CN/8000 a=direction:active U 216.236.137.226:1102 -> 209.227.182.43:5060 SIP/2.0 100 Trying Via: SIP/2.0/UDP 209.227.182.43;branch=z9hG4bK8198.2b7612d2.0 Via: SIP/2.0/UDP 209.227.182.44:5060 From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43>;tag=3720024524 Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 101 INVITE Timestamp: 1083339012 Server: Cisco ATA 186 v3.0.0 atasip (031210A) Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER Content-Length: 0 U 216.236.137.226:1102 -> 209.227.182.43:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP 209.227.182.43;branch=z9hG4bK8198.2b7612d2.0 Via: SIP/2.0/UDP 209.227.182.44:5060 From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43>;tag=3720024524 Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 101 INVITE Timestamp: 1083339012 Server: Cisco ATA 186 v3.0.0 atasip (031210A) Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER Content-Length: 0 U 209.227.182.43:5060 -> 209.227.182.44:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP 209.227.182.44:5060 From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43>;tag=3720024524 Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 101 INVITE Timestamp: 1083339012 Server: Cisco ATA 186 v3.0.0 atasip (031210A) Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER Content-Length: 0 P-hint: fixed NAT contact for response U 216.236.137.226:1102 -> 209.227.182.43:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 209.227.182.43;branch=z9hG4bK8198.2b7612d2.0 Via: SIP/2.0/UDP 209.227.182.44:5060 Record-Route: <sip:12124051759@209.227.182.43;ftag=DC7456A0-3FE;lr=on> From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43>;tag=3720024524 Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 101 INVITE Timestamp: 1083339012 Contact: <sip:250000007@172.30.200.59:5060;user=phone;transport=udp> Server: Cisco ATA 186 v3.0.0 atasip (031210A) Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER Content-Length: 204 Content-Type: application/sdp v=0 o=250000007 85231 85231 IN IP4 172.30.200.59 s=ATA186 Call c=IN IP4 172.30.200.59 t=0 0 m=audio 16386 RTP/AVP 18 101 a=rtpmap:18 G729/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 U 209.227.182.43:5060 -> 209.227.182.44:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 209.227.182.44:5060 Record-Route: <sip:12124051759@209.227.182.43;ftag=DC7456A0-3FE;lr=on> From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43>;tag=3720024524 Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 101 INVITE Timestamp: 1083339012 Contact: <sip:250000007@216.236.137.226:1102;user=phone;transport=udp> Server: Cisco ATA 186 v3.0.0 atasip (031210A) Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER Content-Length: 205 Content-Type: application/sdp P-hint: fixed NAT contact for response P-hint: response forced to rtp proxy v=0 o=250000007 85231 85231 IN IP4 172.30.200.59 s=ATA186 Call c=IN IP4 209.227.182.43 t=0 0 m=audio 55824 RTP/AVP 18 101 a=rtpmap:18 G729/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 U 209.227.182.44:57102 -> 209.227.182.43:5060 ACK sip:12124051759@209.227.182.43:5060;ftag=DC7456A0-3FE;lr=on SIP/2.0 Via: SIP/2.0/UDP 209.227.182.44:5060 From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43>;tag=3720024524 Date: Fri, 30 Apr 2004 15:30:12 GMT Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 Route: <sip:250000007@216.236.137.226:1102;user=phone;transport=udp> Max-Forwards: 6 Content-Length: 0 CSeq: 101 ACK U 209.227.182.43:5060 -> 216.236.137.226:1102 ACK sip:250000007@216.236.137.226:1102;user=phone;transport=udp SIP/2.0 Via: SIP/2.0/UDP 209.227.182.43;branch=0 Via: SIP/2.0/UDP 209.227.182.44:5060 From: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE To: <sip:12124051759@209.227.182.43>;tag=3720024524 Date: Fri, 30 Apr 2004 15:30:12 GMT Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 Max-Forwards: 5 Content-Length: 0 CSeq: 101 ACK U 216.236.137.226:1102 -> 209.227.182.43:5060 BYE sip:12124051759@209.227.182.43 SIP/2.0 Route: <sip:2126882781@209.227.182.44> Via: SIP/2.0/UDP 172.30.200.59:5060 From: sip:12124051759@209.227.182.43;tag=3720024524 To: sip:2126882781@209.227.182.44;tag=DC7456A0-3FE Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 1 BYE User-Agent: Cisco ATA 186 v3.0.0 atasip (031210A) Content-Length: 0 U 209.227.182.43:5060 -> 209.227.182.44:5060 BYE sip:2126882781@209.227.182.44 SIP/2.0 Max-Forwards: 10 Via: SIP/2.0/UDP 209.227.182.43;branch=z9hG4bKb7a6.78fba574.0 Via: SIP/2.0/UDP 172.30.200.59:5060;rport=1102;received=216.236.137.226 From: sip:12124051759@209.227.182.43;tag=3720024524 To: sip:2126882781@209.227.182.44;tag=DC7456A0-3FE Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 1 BYE User-Agent: Cisco ATA 186 v3.0.0 atasip (031210A) Content-Length: 0 U 209.227.182.44:5060 -> 209.227.182.43:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 209.227.182.43;branch=z9hG4bKb7a6.78fba574.0,SIP/2.0/UDP 172.30.200.59:5060;rport=1102;received=216.236.137.2 26 From: <sip:12124051759@209.227.182.43>;tag=3720024524 To: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE Date: Fri, 30 Apr 2004 15:30:21 GMT Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 Server: Cisco-SIPGateway/IOS-12.x Content-Length: 0 CSeq: 1 BYE U 209.227.182.43:5060 -> 216.236.137.226:1102 SIP/2.0 200 OK Via: SIP/2.0/UDP 172.30.200.59:5060;rport=1102;received=216.236.137.226 From: <sip:12124051759@209.227.182.43>;tag=3720024524 To: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE Date: Fri, 30 Apr 2004 15:30:21 GMT Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 Server: Cisco-SIPGateway/IOS-12.x Content-Length: 0 CSeq: 1 BYE U 216.236.137.226:1102 -> 209.227.182.43:5060 BYE sip:12124051759@209.227.182.43 SIP/2.0 Route: <sip:2126882781@209.227.182.44> Via: SIP/2.0/UDP 172.30.200.59:5060 From: sip:12124051759@209.227.182.43;tag=3720024524 To: sip:2126882781@209.227.182.44;tag=DC7456A0-3FE Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 1 BYE User-Agent: Cisco ATA 186 v3.0.0 atasip (031210A) Content-Length: 0 U 209.227.182.43:5060 -> 216.236.137.226:1102 SIP/2.0 200 OK Via: SIP/2.0/UDP 172.30.200.59:5060;rport=1102;received=216.236.137.226 From: <sip:12124051759@209.227.182.43>;tag=3720024524 To: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE Date: Fri, 30 Apr 2004 15:30:21 GMT Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 Server: Cisco-SIPGateway/IOS-12.x Content-Length: 0 CSeq: 1 BYE U 216.236.137.226:1102 -> 209.227.182.43:5060 BYE sip:12124051759@209.227.182.43 SIP/2.0 Route: <sip:2126882781@209.227.182.44> Via: SIP/2.0/UDP 172.30.200.59:5060 From: sip:12124051759@209.227.182.43;tag=3720024524 To: sip:2126882781@209.227.182.44;tag=DC7456A0-3FE Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 1 BYE User-Agent: Cisco ATA 186 v3.0.0 atasip (031210A) Content-Length: 0 U 209.227.182.43:5060 -> 216.236.137.226:1102 SIP/2.0 200 OK Via: SIP/2.0/UDP 172.30.200.59:5060;rport=1102;received=216.236.137.226 From: <sip:12124051759@209.227.182.43>;tag=3720024524 To: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE Date: Fri, 30 Apr 2004 15:30:21 GMT Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 Server: Cisco-SIPGateway/IOS-12.x Content-Length: 0 CSeq: 1 BYE U 216.236.137.226:1102 -> 209.227.182.43:5060 BYE sip:12124051759@209.227.182.43 SIP/2.0 Route: <sip:2126882781@209.227.182.44> Via: SIP/2.0/UDP 172.30.200.59:5060 From: sip:12124051759@209.227.182.43;tag=3720024524 To: sip:2126882781@209.227.182.44;tag=DC7456A0-3FE Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 1 BYE User-Agent: Cisco ATA 186 v3.0.0 atasip (031210A) Content-Length: 0 U 209.227.182.43:5060 -> 216.236.137.226:1102 SIP/2.0 200 OK Via: SIP/2.0/UDP 172.30.200.59:5060;rport=1102;received=216.236.137.226 From: <sip:12124051759@209.227.182.43>;tag=3720024524 To: <sip:2126882781@209.227.182.44>;tag=DC7456A0-3FE Date: Fri, 30 Apr 2004 15:30:21 GMT Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 Server: Cisco-SIPGateway/IOS-12.x Content-Length: 0 CSeq: 1 BYE U 216.236.137.226:1102 -> 209.227.182.43:5060 BYE sip:12124051759@209.227.182.43 SIP/2.0 Route: <sip:2126882781@209.227.182.44> Via: SIP/2.0/UDP 172.30.200.59:5060 From: sip:12124051759@209.227.182.43;tag=3720024524 To: sip:2126882781@209.227.182.44;tag=DC7456A0-3FE Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 1 BYE User-Agent: Cisco ATA 186 v3.0.0 atasip (031210A) Content-Length: 0 U 209.227.182.43:5060 -> 209.227.182.44:5060 BYE sip:2126882781@209.227.182.44 SIP/2.0 Max-Forwards: 10 Via: SIP/2.0/UDP 209.227.182.43;branch=z9hG4bKb7a6.88fba574.0 Via: SIP/2.0/UDP 172.30.200.59:5060;rport=1102;received=216.236.137.226 From: sip:12124051759@209.227.182.43;tag=3720024524 To: sip:2126882781@209.227.182.44;tag=DC7456A0-3FE Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 1 BYE User-Agent: Cisco ATA 186 v3.0.0 atasip (031210A) Content-Length: 0 U 209.227.182.44:5060 -> 209.227.182.43:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist Via: SIP/2.0/UDP 209.227.182.43;branch=z9hG4bKb7a6.88fba574.0,SIP/2.0/UDP 172.30.200.59:5060;rport=1102;received=216.236.137.2 26 From: sip:12124051759@209.227.182.43;tag=3720024524 To: sip:2126882781@209.227.182.44;tag=DC7456A0-3FE Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 1 BYE Content-Length: 0 U 209.227.182.43:5060 -> 216.236.137.226:1102 SIP/2.0 481 Call Leg/Transaction Does Not Exist Via: SIP/2.0/UDP 172.30.200.59:5060;rport=1102;received=216.236.137.226 From: sip:12124051759@209.227.182.43;tag=3720024524 To: sip:2126882781@209.227.182.44;tag=DC7456A0-3FE Call-ID: 1B72FBC0-99F211D8-AFEAEAA0-F4703A0(a)209.227.182.44 CSeq: 1 BYE Content-Length: 0

_______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers