any ideas anyone? seems like SER does not respond to CANCEL requests and eventually takes the failure route.
I have the following in my failure route, but it never gets hit, since SER does not send the 200 OK back or pass the CANCEL message forward. log file attached.
failure_route[1] { if(t_check_status("487")) { # don't continue on cancellation xlog("L_WARN", "OH OH OH\n"); break; }
ac
--- a c lra101@yahoo.com wrote:
Seems like SER does not respond back to CANCEL Requests. Is this a issue / some config problem on my side? ngrep traces attached
interface: eth0 (192.168.0.0/255.255.255.0) filter: ip and ( port 5060 ) # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 INVITE..Max-Forwards: 70..Content-Type: application/sdp..Use r-Agent: X-Lite release 1103m..Content-Length: 258....v=0..o=102 7659613 76 59633 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 80 00 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpma p:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fm tp:96 0-15..
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16
8.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com. .Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVIT E..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Warn ing: 392 192.168.0.5:5060 "Noisy feedback tells: pid=2943 req_src_ip=192.1 68.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999 999@voip.com via_cnt==1"....
# U 192.168.0.5:5060 -> 192.168.0.3:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: <sip:192.168.0.5;ftag =3282942385;lr=on>..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034.1018c5d 1.0..Via: SIP/2.0/UDP
192.168.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8C
F4A479B6D9DDB17C5CFC1..From: 102 sip:102@voip.com:5062;tag=3282942385..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVITE..Max-For wards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103m. .Content-Length: 258....v=0..o=102 7659613 7659633 IN IP4 192.168.0.2..s=X- Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96..a=rtpm ap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:98 iLBC /8000..a=rtpmap:96 telephone-event/8000..a=fmtp:96 0-15.. # U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=3282942385..To: < sip:9999999999@voip.com>..Call-Id: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192 .168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034 .1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKE29 503D9D8CF4A479B6D9DDB17C5CFC1..Content-Length: 0....
# U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch= z9hG4bKe034.1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch =z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date: Mon, 23 May 2005 22:15:14 G MT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT)..Accept-Langua ge: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0 ....
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062;rp
ort=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date:
Mon, 23 May 2005 22:15:14 GMT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT) ..Accept-Language: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOT IFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Co ntent-Length: 0....
# U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0....
# U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0....
# U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0....
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b
ranch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From: 102 <sip:102@voip.com: 5062>;tag=3282942385..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-6e9f..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0 .2..CSeq: 940 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Cont ent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid=29 51 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com
=== message truncated ===
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
<<< Log from 192.168.0.5 started May 26, 2005, 10:53:10 >>> # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 INVITE..Max-Forwards: 70..Content-Type: application/sdp..U ser-Agent: X-Lite release 1103m..Content-Length: 262....v=0..o=102 24393782 4 243937884 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=au dio 8000 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a =rtpmap:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000 ..a=fmtp:96 0-15.. # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16 8.0.2:5062;rport=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com. .Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..CSeq: 55437 INV ITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Wa rning: 392 192.168.0.5:5060 "Noisy feedback tells: pid=991 req_src_ip=192. 168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:999999 9999@voip.com via_cnt==1".... # U 192.168.0.5:5060 -> 192.168.0.2:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: <sip:192.168.0.5;ftag =2354273279;lr=on>..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d58ef0f 1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKC51A010562E F4A59816876A6DEACF5BF..From: 102 sip:102@voip.com:5062;tag=2354273279..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..CSeq: 55437 INVITE..Max-F orwards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103 m..Content-Length: 262....v=0..o=102 243937824 243937884 IN IP4 192.168.0.2 ..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96.. a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:9 8 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fmtp:96 0-15.. # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=2354273279..To: < sip:9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192 .168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK07 8b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKC 51A010562EF4A59816876A6DEACF5BF..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68-8191-05684 A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branc h=z9hG4bK078b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;bran ch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 May 2005 15:53:13 GMT..Contact: sip:192.168.0.2..User-Agent: sipX/2.5.2 (WinNT)..Accept-Lang uage: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER , SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68-8191-05684 A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062; rport=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 Ma y 2005 15:53:13 GMT..Contact: sip:192.168.0.2..User-Agent: sipX/2.5.2 (WinN T)..Accept-Language: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, N OTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces.. Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... # U 192.168.0.5:5060 -> 192.168.0.2:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.5;branch =z9hG4bK078b.d58ef0f1.0..From: 102 sip:102@voip.com:5062;tag=2354273279.. Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..To: <sip:9999999 999@voip.com>..CSeq: 55437 CANCEL..User-Agent: Sip EXpress router(0.9.2 (i3 86/linux))..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 200 OK..From: 102 sip:102@voip.com:5062;tag=2354273279..To: <sip: 9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168 .0.2..Cseq: 55437 CANCEL..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d 58ef0f1.0..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 487 Request Terminated..From: 102 sip:102@voip.com:5062;tag=23542 73279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68 -8191-05684A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.16 8.0.5;branch=z9hG4bK078b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rpor t=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 May 20 05 15:53:43 GMT..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, R EGISTER, SUBSCRIBE..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Su pported: sip-cc, sip-cc-01, timer, replaces..Contact: sip:192.168.0.2..Cont ent-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5060 ACK sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.5;branch=z9 hG4bK078b.d58ef0f1.0..From: 102 sip:102@voip.com:5062;tag=2354273279..Cal l-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..To: <sip:9999999999 @voip.com>;tag=19901..CSeq: 55437 ACK..User-Agent: Sip EXpress router(0.9.2 (i386/linux))..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 200 OK..From: 102 sip:102@voip.com:5062;tag=2354273279..To: <sip: 9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168 .0.2..Cseq: 55437 CANCEL..Contact: sip:9999999999@192.168.0.2:5060..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d58ef0f1.0..Date: Thu, 26 May 20 05 15:53:43 GMT..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, R EGISTER, SUBSCRIBE..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Su pported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... <<< Log from 192.168.0.5 ended May 26, 2005, 10:54:17 >>>
I am having a similar problem. I am not yet convinced that it is SER as much as my configuration but if SER does have difficulty processing CANCEL messages it would be helpful to understand under what circumstances.
By the way I have been using t_check_status in a similar way since v 0.8 code. When I upgraded to 0.9.0, .0 and now .2 the t_check_status fails to be matched.
-Steve
Thanks,Steve
a c wrote:
any ideas anyone? seems like SER does not respond to CANCEL requests and eventually takes the failure route.
I have the following in my failure route, but it never gets hit, since SER does not send the 200 OK back or pass the CANCEL message forward. log file attached.
failure_route[1] { if(t_check_status("487")) { # don't continue on cancellation xlog("L_WARN", "OH OH OH\n"); break; }
ac
--- a c lra101@yahoo.com wrote:
Seems like SER does not respond back to CANCEL Requests. Is this a issue / some config problem on my side? ngrep traces attached
interface: eth0 (192.168.0.0/255.255.255.0) filter: ip and ( port 5060 ) # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 INVITE..Max-Forwards: 70..Content-Type: application/sdp..Use r-Agent: X-Lite release 1103m..Content-Length: 258....v=0..o=102 7659613 76 59633 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 80 00 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpma p:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fm tp:96 0-15..
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16
8.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com. .Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVIT E..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Warn ing: 392 192.168.0.5:5060 "Noisy feedback tells: pid=2943 req_src_ip=192.1 68.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999 999@voip.com via_cnt==1"....
# U 192.168.0.5:5060 -> 192.168.0.3:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: <sip:192.168.0.5;ftag =3282942385;lr=on>..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034.1018c5d 1.0..Via: SIP/2.0/UDP
192.168.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8C
F4A479B6D9DDB17C5CFC1..From: 102 sip:102@voip.com:5062;tag=3282942385..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVITE..Max-For wards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103m. .Content-Length: 258....v=0..o=102 7659613 7659633 IN IP4 192.168.0.2..s=X- Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96..a=rtpm ap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:98 iLBC /8000..a=rtpmap:96 telephone-event/8000..a=fmtp:96 0-15.. # U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=3282942385..To: < sip:9999999999@voip.com>..Call-Id: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192 .168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034 .1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKE29 503D9D8CF4A479B6D9DDB17C5CFC1..Content-Length: 0....
# U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch= z9hG4bKe034.1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch =z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date: Mon, 23 May 2005 22:15:14 G MT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT)..Accept-Langua ge: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0 ....
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062;rp
ort=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date:
Mon, 23 May 2005 22:15:14 GMT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT) ..Accept-Language: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOT IFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Co ntent-Length: 0....
# U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0....
# U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0....
# U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0....
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b
ranch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From: 102 <sip:102@voip.com: 5062>;tag=3282942385..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-6e9f..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0 .2..CSeq: 940 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Cont ent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid=29 51 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com
=== message truncated ===
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
<<< Log from 192.168.0.5 started May 26, 2005, 10:53:10 >>> # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 INVITE..Max-Forwards: 70..Content-Type: application/sdp..U ser-Agent: X-Lite release 1103m..Content-Length: 262....v=0..o=102 24393782 4 243937884 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=au dio 8000 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a =rtpmap:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000 ..a=fmtp:96 0-15.. # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16 8.0.2:5062;rport=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com. .Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..CSeq: 55437 INV ITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Wa rning: 392 192.168.0.5:5060 "Noisy feedback tells: pid=991 req_src_ip=192. 168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:999999 9999@voip.com via_cnt==1".... # U 192.168.0.5:5060 -> 192.168.0.2:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: <sip:192.168.0.5;ftag =2354273279;lr=on>..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d58ef0f 1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKC51A010562E F4A59816876A6DEACF5BF..From: 102 sip:102@voip.com:5062;tag=2354273279..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..CSeq: 55437 INVITE..Max-F orwards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103 m..Content-Length: 262....v=0..o=102 243937824 243937884 IN IP4 192.168.0.2 ..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96.. a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:9 8 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fmtp:96 0-15.. # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=2354273279..To: < sip:9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192 .168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK07 8b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKC 51A010562EF4A59816876A6DEACF5BF..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68-8191-05684 A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branc h=z9hG4bK078b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;bran ch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 May 2005 15:53:13 GMT..Contact: sip:192.168.0.2..User-Agent: sipX/2.5.2 (WinNT)..Accept-Lang uage: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER , SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68-8191-05684 A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062; rport=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 Ma y 2005 15:53:13 GMT..Contact: sip:192.168.0.2..User-Agent: sipX/2.5.2 (WinN T)..Accept-Language: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, N OTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces.. Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... # U 192.168.0.5:5060 -> 192.168.0.2:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.5;branch =z9hG4bK078b.d58ef0f1.0..From: 102 sip:102@voip.com:5062;tag=2354273279.. Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..To: <sip:9999999 999@voip.com>..CSeq: 55437 CANCEL..User-Agent: Sip EXpress router(0.9.2 (i3 86/linux))..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 200 OK..From: 102 sip:102@voip.com:5062;tag=2354273279..To: <sip: 9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168 .0.2..Cseq: 55437 CANCEL..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d 58ef0f1.0..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 487 Request Terminated..From: 102 sip:102@voip.com:5062;tag=23542 73279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68 -8191-05684A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.16 8.0.5;branch=z9hG4bK078b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rpor t=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 May 20 05 15:53:43 GMT..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, R EGISTER, SUBSCRIBE..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Su pported: sip-cc, sip-cc-01, timer, replaces..Contact: sip:192.168.0.2..Cont ent-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5060 ACK sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.5;branch=z9 hG4bK078b.d58ef0f1.0..From: 102 sip:102@voip.com:5062;tag=2354273279..Cal l-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..To: <sip:9999999999 @voip.com>;tag=19901..CSeq: 55437 ACK..User-Agent: Sip EXpress router(0.9.2 (i386/linux))..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 200 OK..From: 102 sip:102@voip.com:5062;tag=2354273279..To: <sip: 9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168 .0.2..Cseq: 55437 CANCEL..Contact: sip:9999999999@192.168.0.2:5060..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d58ef0f1.0..Date: Thu, 26 May 20 05 15:53:43 GMT..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, R EGISTER, SUBSCRIBE..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Su pported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... <<< Log from 192.168.0.5 ended May 26, 2005, 10:54:17 >>>
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I believe the 487 does not get matched because the UA which does the CANCEL never gets a 200 OK back since the CANCEL was not send out to the terminating UA by SER. For CANCEL, are we supposed to have special config? I don't have any specifically handles CANCEL {other than 487}.
ac
--- Steve Blair blairs@isc.upenn.edu wrote:
I am having a similar problem. I am not yet convinced that it is SER as much as my configuration but if SER does have difficulty processing CANCEL messages it would be helpful to understand under what circumstances.
By the way I have been using t_check_status in a similar way since v 0.8 code. When I upgraded to 0.9.0, .0 and now .2 the t_check_status fails to be matched.
-Steve
Thanks,Steve
a c wrote:
any ideas anyone? seems like SER does not respond
to
CANCEL requests and eventually takes the failure route.
I have the following in my failure route, but it
never
gets hit, since SER does not send the 200 OK back
or
pass the CANCEL message forward. log file attached.
failure_route[1] { if(t_check_status("487")) { # don't continue on cancellation xlog("L_WARN", "OH OH OH\n"); break; }
ac
--- a c lra101@yahoo.com wrote:
Seems like SER does not respond back to CANCEL Requests. Is this a issue / some config problem on my side? ngrep traces attached
interface: eth0 (192.168.0.0/255.255.255.0) filter: ip and ( port 5060 ) # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 INVITE..Max-Forwards: 70..Content-Type: application/sdp..Use r-Agent: X-Lite release 1103m..Content-Length: 258....v=0..o=102 7659613 76 59633 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 80 00 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpma p:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fm tp:96 0-15..
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16
8.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com. .Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVIT E..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Warn ing: 392 192.168.0.5:5060 "Noisy feedback tells:
pid=2943 req_src_ip=192.1 68.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999 999@voip.com via_cnt==1"....
# U 192.168.0.5:5060 -> 192.168.0.3:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: <sip:192.168.0.5;ftag =3282942385;lr=on>..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034.1018c5d 1.0..Via: SIP/2.0/UDP
192.168.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8C
F4A479B6D9DDB17C5CFC1..From: 102 sip:102@voip.com:5062;tag=3282942385..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVITE..Max-For wards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103m. .Content-Length: 258....v=0..o=102 7659613
7659633
IN IP4 192.168.0.2..s=X- Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96..a=rtpm ap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:98 iLBC /8000..a=rtpmap:96
telephone-event/8000..a=fmtp:96
0-15.. # U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=3282942385..To: < sip:9999999999@voip.com>..Call-Id: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192 .168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034 .1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKE29 503D9D8CF4A479B6D9DDB17C5CFC1..Content-Length: 0....
# U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch= z9hG4bKe034.1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch =z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date: Mon, 23 May 2005 22:15:14 G MT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT)..Accept-Langua ge: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0 ....
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062;rp
=== message truncated ===
__________________________________ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html
a c wrote:
I believe the 487 does not get matched because the UA which does the CANCEL never gets a 200 OK back since the CANCEL was not send out to the terminating UA by SER. For CANCEL, are we supposed to have special config? I don't have any specifically handles CANCEL {other than 487}.
I didn't think I had any "special" handles in my 0.8 code but I may be mistaken. I believe CANCELs matched an ELSE clause that simply did a t_relay. Adding a CANCEL method check and the subsequent t_relay did not automatically fix the issue for me.
ac
--- Steve Blair blairs@isc.upenn.edu wrote:
I am having a similar problem. I am not yet convinced that it is SER as much as my configuration but if SER does have difficulty processing CANCEL messages it would be helpful to understand under what circumstances.
By the way I have been using t_check_status in a similar way since v 0.8 code. When I upgraded to 0.9.0, .0 and now .2 the t_check_status fails to be matched.
-Steve
Thanks,Steve
a c wrote:
any ideas anyone? seems like SER does not respond
to
CANCEL requests and eventually takes the failure route.
I have the following in my failure route, but it
never
gets hit, since SER does not send the 200 OK back
or
pass the CANCEL message forward. log file attached.
failure_route[1] { if(t_check_status("487")) { # don't continue on cancellation xlog("L_WARN", "OH OH OH\n"); break; }
ac
--- a c lra101@yahoo.com wrote:
Seems like SER does not respond back to CANCEL Requests. Is this a issue / some config problem on my side? ngrep traces attached
interface: eth0 (192.168.0.0/255.255.255.0) filter: ip and ( port 5060 ) # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 sip:102@voi p.com:5062;tag=3282942385..To: sip:9999999999@voip.com..Contact: sip:10 2@192.168.0.2:5062..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 INVITE..Max-Forwards: 70..Content-Type: application/sdp..Use r-Agent: X-Lite release 1103m..Content-Length: 258....v=0..o=102 7659613 76 59633 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 80 00 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpma p:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fm tp:96 0-15..
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16
8.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com. .Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVIT E..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Warn ing: 392 192.168.0.5:5060 "Noisy feedback tells:
pid=2943 req_src_ip=192.1 68.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999 999@voip.com via_cnt==1"....
# U 192.168.0.5:5060 -> 192.168.0.3:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: sip:192.168.0.5;ftag =3282942385;lr=on..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034.1018c5d 1.0..Via: SIP/2.0/UDP
192.168.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8C
F4A479B6D9DDB17C5CFC1..From: 102 sip:102@voip.com:5062;tag=3282942385..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVITE..Max-For wards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103m. .Content-Length: 258....v=0..o=102 7659613
7659633
IN IP4 192.168.0.2..s=X- Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96..a=rtpm ap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:98 iLBC /8000..a=rtpmap:96
telephone-event/8000..a=fmtp:96
0-15.. # U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=3282942385..To: < sip:9999999999@voip.com>..Call-Id: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192 .168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034 .1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKE29 503D9D8CF4A479B6D9DDB17C5CFC1..Content-Length: 0....
# U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch= z9hG4bKe034.1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch =z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date: Mon, 23 May 2005 22:15:14 G MT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT)..Accept-Langua ge: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0 ....
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062;rp
=== message truncated ===
__________________________________ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html
Are you relaying the cancel message to the other side?
if (method=="CANCEL"){ t_relay(); };
a c wrote:
any ideas anyone? seems like SER does not respond to CANCEL requests and eventually takes the failure route.
I have the following in my failure route, but it never gets hit, since SER does not send the 200 OK back or pass the CANCEL message forward. log file attached.
failure_route[1] { if(t_check_status("487")) { # don't continue on cancellation xlog("L_WARN", "OH OH OH\n"); break; }
ac
--- a c lra101@yahoo.com wrote:
Seems like SER does not respond back to CANCEL Requests. Is this a issue / some config problem on my side? ngrep traces attached
interface: eth0 (192.168.0.0/255.255.255.0) filter: ip and ( port 5060 ) # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 INVITE..Max-Forwards: 70..Content-Type: application/sdp..Use r-Agent: X-Lite release 1103m..Content-Length: 258....v=0..o=102 7659613 76 59633 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 80 00 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpma p:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fm tp:96 0-15..
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16
8.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com. .Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVIT E..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Warn ing: 392 192.168.0.5:5060 "Noisy feedback tells: pid=2943 req_src_ip=192.1 68.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999 999@voip.com via_cnt==1"....
# U 192.168.0.5:5060 -> 192.168.0.3:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: <sip:192.168.0.5;ftag =3282942385;lr=on>..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034.1018c5d 1.0..Via: SIP/2.0/UDP
192.168.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8C
F4A479B6D9DDB17C5CFC1..From: 102 sip:102@voip.com:5062;tag=3282942385..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVITE..Max-For wards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103m. .Content-Length: 258....v=0..o=102 7659613 7659633 IN IP4 192.168.0.2..s=X- Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96..a=rtpm ap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:98 iLBC /8000..a=rtpmap:96 telephone-event/8000..a=fmtp:96 0-15.. # U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=3282942385..To: < sip:9999999999@voip.com>..Call-Id: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192 .168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034 .1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKE29 503D9D8CF4A479B6D9DDB17C5CFC1..Content-Length: 0....
# U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch= z9hG4bKe034.1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch =z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date: Mon, 23 May 2005 22:15:14 G MT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT)..Accept-Langua ge: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0 ....
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062;rp
ort=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date:
Mon, 23 May 2005 22:15:14 GMT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT) ..Accept-Language: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOT IFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Co ntent-Length: 0....
# U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0....
# U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0....
# U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0....
# U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b
ranch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From: 102 <sip:102@voip.com: 5062>;tag=3282942385..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-6e9f..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0 .2..CSeq: 940 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Cont ent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid=29 51 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com
=== message truncated ===
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
<<< Log from 192.168.0.5 started May 26, 2005, 10:53:10 >>> # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 INVITE..Max-Forwards: 70..Content-Type: application/sdp..U ser-Agent: X-Lite release 1103m..Content-Length: 262....v=0..o=102 24393782 4 243937884 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=au dio 8000 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a =rtpmap:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000 ..a=fmtp:96 0-15.. # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16 8.0.2:5062;rport=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com. .Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..CSeq: 55437 INV ITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Wa rning: 392 192.168.0.5:5060 "Noisy feedback tells: pid=991 req_src_ip=192. 168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:999999 9999@voip.com via_cnt==1".... # U 192.168.0.5:5060 -> 192.168.0.2:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: <sip:192.168.0.5;ftag =2354273279;lr=on>..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d58ef0f 1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKC51A010562E F4A59816876A6DEACF5BF..From: 102 sip:102@voip.com:5062;tag=2354273279..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..CSeq: 55437 INVITE..Max-F orwards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103 m..Content-Length: 262....v=0..o=102 243937824 243937884 IN IP4 192.168.0.2 ..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96.. a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:9 8 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fmtp:96 0-15.. # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=2354273279..To: < sip:9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192 .168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK07 8b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKC 51A010562EF4A59816876A6DEACF5BF..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68-8191-05684 A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branc h=z9hG4bK078b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;bran ch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 May 2005 15:53:13 GMT..Contact: sip:192.168.0.2..User-Agent: sipX/2.5.2 (WinNT)..Accept-Lang uage: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER , SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68-8191-05684 A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062; rport=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 Ma y 2005 15:53:13 GMT..Contact: sip:192.168.0.2..User-Agent: sipX/2.5.2 (WinN T)..Accept-Language: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, N OTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces.. Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... # U 192.168.0.5:5060 -> 192.168.0.2:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.5;branch =z9hG4bK078b.d58ef0f1.0..From: 102 sip:102@voip.com:5062;tag=2354273279.. Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..To: <sip:9999999 999@voip.com>..CSeq: 55437 CANCEL..User-Agent: Sip EXpress router(0.9.2 (i3 86/linux))..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 200 OK..From: 102 sip:102@voip.com:5062;tag=2354273279..To: <sip: 9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168 .0.2..Cseq: 55437 CANCEL..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d 58ef0f1.0..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 487 Request Terminated..From: 102 sip:102@voip.com:5062;tag=23542 73279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68 -8191-05684A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.16 8.0.5;branch=z9hG4bK078b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rpor t=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 May 20 05 15:53:43 GMT..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, R EGISTER, SUBSCRIBE..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Su pported: sip-cc, sip-cc-01, timer, replaces..Contact: sip:192.168.0.2..Cont ent-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5060 ACK sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.5;branch=z9 hG4bK078b.d58ef0f1.0..From: 102 sip:102@voip.com:5062;tag=2354273279..Cal l-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..To: <sip:9999999999 @voip.com>;tag=19901..CSeq: 55437 ACK..User-Agent: Sip EXpress router(0.9.2 (i386/linux))..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 200 OK..From: 102 sip:102@voip.com:5062;tag=2354273279..To: <sip: 9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168 .0.2..Cseq: 55437 CANCEL..Contact: sip:9999999999@192.168.0.2:5060..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d58ef0f1.0..Date: Thu, 26 May 20 05 15:53:43 GMT..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, R EGISTER, SUBSCRIBE..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Su pported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... <<< Log from 192.168.0.5 ended May 26, 2005, 10:54:17 >>>
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I tried that earlier and it did not change the nature of the problem. I still need to make sure this section of code is hit at the appropriate point in the call however.
Mik Cheez wrote:
Are you relaying the cancel message to the other side?
if (method=="CANCEL"){ t_relay(); };a c wrote:
any ideas anyone? seems like SER does not respond to CANCEL requests and eventually takes the failure route. I have the following in my failure route, but it never gets hit, since SER does not send the 200 OK back or pass the CANCEL message forward. log file attached.
failure_route[1] { if(t_check_status("487")) { # don't continue on cancellation xlog("L_WARN", "OH OH OH\n"); break; }
ac
--- a c lra101@yahoo.com wrote:
Seems like SER does not respond back to CANCEL Requests. Is this a issue / some config problem on my side? ngrep traces attached
interface: eth0 (192.168.0.0/255.255.255.0) filter: ip and ( port 5060 ) # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 INVITE..Max-Forwards: 70..Content-Type: application/sdp..Use r-Agent: X-Lite release 1103m..Content-Length: 258....v=0..o=102 7659613 76 59633 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 80 00 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpma p:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fm tp:96 0-15.. # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16
8.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com. .Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVIT E..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Warn ing: 392 192.168.0.5:5060 "Noisy feedback tells: pid=2943 req_src_ip=192.1 68.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999 999@voip.com via_cnt==1".... # U 192.168.0.5:5060 -> 192.168.0.3:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: <sip:192.168.0.5;ftag =3282942385;lr=on>..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034.1018c5d 1.0..Via: SIP/2.0/UDP
192.168.0.2:5062;rport=5062;branch=z9hG4bKE29503D9D8C
F4A479B6D9DDB17C5CFC1..From: 102 sip:102@voip.com:5062;tag=3282942385..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID:
29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0.2..CSeq:
940 INVITE..Max-For wards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103m. .Content-Length: 258....v=0..o=102 7659613 7659633 IN IP4 192.168.0.2..s=X- Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96..a=rtpm ap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:98 iLBC /8000..a=rtpmap:96 telephone-event/8000..a=fmtp:96 0-15.. # U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=3282942385..To: < sip:9999999999@voip.com>..Call-Id: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192 .168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bKe034 .1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKE29 503D9D8CF4A479B6D9DDB17C5CFC1..Content-Length: 0.... # U 192.168.0.3:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch= z9hG4bKe034.1018c5d1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch =z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date: Mon, 23 May 2005 22:15:14 G MT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT)..Accept-Langua ge: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0 .... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=3282942385..To: sip:9999999999@voip.com;tag=27378..Call-Id: 29469D19-CDF1-49ED-8245-A67E1 B1DBB88@192.168.0.2..Cseq: 940 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062;rp
ort=5062;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..Date:
Mon, 23 May 2005 22:15:14 GMT..Contact: sip:192.168.0.3..User-Agent: sipX/2.5.2 (WinNT) ..Accept-Language: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOT IFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Co ntent-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
102 <sip:102@voi p.com:5062>;tag=3282942385..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168. 0.2..CSeq: 940 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m.. Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b
ranch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From: 102 <sip:102@voip.com: 5062>;tag=3282942385..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-6e9f..Call-ID: 29469D19-CDF1-49ED-8245-A67E1B1DBB88@192.168.0 .2..CSeq: 940 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Cont ent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid=29 51 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com
=== message truncated ===
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
<<< Log from 192.168.0.5 started May 26, 2005, 10:53:10 >>> # U 192.168.0.2:5062 -> 192.168.0.5:5060 INVITE sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 INVITE..Max-Forwards: 70..Content-Type: application/sdp..U ser-Agent: X-Lite release 1103m..Content-Length: 262....v=0..o=102 24393782 4 243937884 IN IP4 192.168.0.2..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=au dio 8000 RTP/AVP 0 8 3 98 96..a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a =rtpmap:3 gsm/8000..a=rtpmap:98 iLBC/8000..a=rtpmap:96 telephone-event/8000 ..a=fmtp:96 0-15.. # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.16 8.0.2:5062;rport=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From:
102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com. .Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..CSeq: 55437 INV ITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Wa rning: 392 192.168.0.5:5060 "Noisy feedback tells: pid=991 req_src_ip=192. 168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:999999 9999@voip.com via_cnt==1".... # U 192.168.0.5:5060 -> 192.168.0.2:5060 INVITE sip:9999999999@voip.com SIP/2.0..Record-Route: <sip:192.168.0.5;ftag =2354273279;lr=on>..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d58ef0f 1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKC51A010562E F4A59816876A6DEACF5BF..From: 102 sip:102@voip.com:5062;tag=2354273279..To : sip:9999999999@voip.com..Contact: sip:102@192.168.0.2:5062..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..CSeq: 55437 INVITE..Max-F orwards: 16..Content-Type: application/sdp..User-Agent: X-Lite release 1103 m..Content-Length: 262....v=0..o=102 243937824 243937884 IN IP4 192.168.0.2 ..s=X-Lite..c=IN IP4 192.168.0.2..t=0 0..m=audio 8000 RTP/AVP 0 8 3 98 96.. a=rtpmap:0 pcmu/8000..a=rtpmap:8 pcma/8000..a=rtpmap:3 gsm/8000..a=rtpmap:9 8 iLBC/8000..a=rtpmap:96 telephone-event/8000..a=fmtp:96 0-15.. # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 100 Trying..From: 102 sip:102@voip.com:5062;tag=2354273279..To: < sip:9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192 .168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK07 8b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;branch=z9hG4bKC 51A010562EF4A59816876A6DEACF5BF..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68-8191-05684 A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.5;branc h=z9hG4bK078b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;bran ch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 May 2005 15:53:13 GMT..Contact: sip:192.168.0.2..User-Agent: sipX/2.5.2 (WinNT)..Accept-Lang uage: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, REGISTER , SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces..Content-Length:
0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 180 Ringing..From: 102 sip:102@voip.com:5062;tag=2354273279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68-8191-05684 A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.168.0.2:5062; rport=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 Ma y 2005 15:53:13 GMT..Contact: sip:192.168.0.2..User-Agent: sipX/2.5.2 (WinN T)..Accept-Language: en..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, N OTIFY, REGISTER, SUBSCRIBE..Supported: sip-cc, sip-cc-01, timer, replaces.. Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.2:5062 -> 192.168.0.5:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:5062;r port;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voi p.com:5062>;tag=2354273279..To: sip:9999999999@voip.com..Contact: <sip:10 2@192.168.0.2:5062>..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168. 0.2..CSeq: 55437 CANCEL..Max-Forwards: 70..User-Agent: X-Lite release 1103m ..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... # U 192.168.0.5:5060 -> 192.168.0.2:5060 CANCEL sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.5;branch =z9hG4bK078b.d58ef0f1.0..From: 102 sip:102@voip.com:5062;tag=2354273279.. Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..To: <sip:9999999 999@voip.com>..CSeq: 55437 CANCEL..User-Agent: Sip EXpress router(0.9.2 (i3 86/linux))..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 200 OK..From: 102 sip:102@voip.com:5062;tag=2354273279..To: <sip: 9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168 .0.2..Cseq: 55437 CANCEL..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d 58ef0f1.0..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 487 Request Terminated..From: 102 sip:102@voip.com:5062;tag=23542 73279..To: sip:9999999999@voip.com;tag=19901..Call-Id: 60D7D848-8486-4E68 -8191-05684A2A3EEF@192.168.0.2..Cseq: 55437 INVITE..Via: SIP/2.0/UDP 192.16 8.0.5;branch=z9hG4bK078b.d58ef0f1.0..Via: SIP/2.0/UDP 192.168.0.2:5062;rpor t=5062;branch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..Date: Thu, 26 May 20 05 15:53:43 GMT..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, R EGISTER, SUBSCRIBE..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Su pported: sip-cc, sip-cc-01, timer, replaces..Contact: sip:192.168.0.2..Cont ent-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5060 ACK sip:9999999999@voip.com SIP/2.0..Via: SIP/2.0/UDP 192.168.0.5;branch=z9 hG4bK078b.d58ef0f1.0..From: 102 sip:102@voip.com:5062;tag=2354273279..Cal l-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0.2..To: <sip:9999999999 @voip.com>;tag=19901..CSeq: 55437 ACK..User-Agent: Sip EXpress router(0.9.2 (i386/linux))..Content-Length: 0.... # U 192.168.0.2:5060 -> 192.168.0.5:5060 SIP/2.0 200 OK..From: 102 sip:102@voip.com:5062;tag=2354273279..To: <sip: 9999999999@voip.com>..Call-Id: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168 .0.2..Cseq: 55437 CANCEL..Contact: sip:9999999999@192.168.0.2:5060..Via: SIP/2.0/UDP 192.168.0.5;branch=z9hG4bK078b.d58ef0f1.0..Date: Thu, 26 May 20 05 15:53:43 GMT..Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, R EGISTER, SUBSCRIBE..User-Agent: sipX/2.5.2 (WinNT)..Accept-Language: en..Su pported: sip-cc, sip-cc-01, timer, replaces..Content-Length: 0.... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... # U 192.168.0.5:5060 -> 192.168.0.2:5062 SIP/2.0 408 Request Timeout..Via: SIP/2.0/UDP 192.168.0.2:5062;rport=5062;b ranch=z9hG4bKC51A010562EF4A59816876A6DEACF5BF..From: 102 <sip:102@voip.com: 5062>;tag=2354273279..To: sip:9999999999@voip.com;tag=a6a1c5f60faecf035a1 ae5b6e96e979a-7cb8..Call-ID: 60D7D848-8486-4E68-8191-05684A2A3EEF@192.168.0 .2..CSeq: 55437 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Co ntent-Length: 0..Warning: 392 192.168.0.5:5060 "Noisy feedback tells: pid= 996 req_src_ip=192.168.0.2 req_src_port=5062 in_uri=sip:9999999999@voip.com out_uri=sip:9999999999@voip.com via_cnt==0".... <<< Log from 192.168.0.5 ended May 26, 2005, 10:54:17 >>>
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi,
Does anybody knows how can i have ser working with mysql in another box?
I'm getting this:
0(78861) new_connection(): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) 0(78861) db_init(): Could not create a connection 0(78861) ERROR:domain_db_init: cannot initialize database connection 0(78861) ERROR: domain:child_init(): Unable to connect to the database
When i try to run it :S
Thanks in advance.
-
a c -
Elton Machado -
Mik Cheez -
Steve Blair