[Serusers] Re: SER CANCEL Processing

a c lra101 at yahoo.com
Thu May 26 17:55:51 CEST 2005 

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 at 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 at voip.com SIP/2.0..Via:
> SIP/2.0/UDP 192.168.0.2:5062;r
>  
>
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
> 102 <sip:102 at voi
>   p.com:5062>;tag=3282942385..To:
> <sip:9999999999 at voip.com>..Contact: <sip:10
>   2 at 192.168.0.2:5062>..Call-ID:
> 29469D19-CDF1-49ED-8245-A67E1B1DBB88 at 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 at voip.com:5062>;tag=3282942385..To:
> <sip:9999999999 at voip.com>.
>   .Call-ID:
>
29469D19-CDF1-49ED-8245-A67E1B1DBB88 at 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 at voip.com out_uri=sip:9999999
>   999 at voip.com via_cnt==1"....                      
>  
>                       
> #
> U 192.168.0.5:5060 -> 192.168.0.3:5060
>   INVITE sip:9999999999 at 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 at voip.com:5062>;tag=3282942385..To
>   : <sip:9999999999 at voip.com>..Contact:
> <sip:102 at 192.168.0.2:5062>..Call-ID: 
>  
>
29469D19-CDF1-49ED-8245-A67E1B1DBB88 at 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 at voip.com:5062>;tag=3282942385..To: <
>   sip:9999999999 at voip.com>..Call-Id:
> 29469D19-CDF1-49ED-8245-A67E1B1DBB88 at 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 at voip.com:5062>;tag=3282942385..To: 
>   <sip:9999999999 at voip.com>;tag=27378..Call-Id:
> 29469D19-CDF1-49ED-8245-A67E1
>   B1DBB88 at 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 at voip.com:5062>;tag=3282942385..To: 
>   <sip:9999999999 at voip.com>;tag=27378..Call-Id:
> 29469D19-CDF1-49ED-8245-A67E1
>   B1DBB88 at 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 at voip.com SIP/2.0..Via:
> SIP/2.0/UDP 192.168.0.2:5062;r
>  
>
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
> 102 <sip:102 at voi
>   p.com:5062>;tag=3282942385..To:
> <sip:9999999999 at voip.com>..Contact: <sip:10
>   2 at 192.168.0.2:5062>..Call-ID:
> 29469D19-CDF1-49ED-8245-A67E1B1DBB88 at 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 at voip.com SIP/2.0..Via:
> SIP/2.0/UDP 192.168.0.2:5062;r
>  
>
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
> 102 <sip:102 at voi
>   p.com:5062>;tag=3282942385..To:
> <sip:9999999999 at voip.com>..Contact: <sip:10
>   2 at 192.168.0.2:5062>..Call-ID:
> 29469D19-CDF1-49ED-8245-A67E1B1DBB88 at 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 at voip.com SIP/2.0..Via:
> SIP/2.0/UDP 192.168.0.2:5062;r
>  
>
port;branch=z9hG4bKE29503D9D8CF4A479B6D9DDB17C5CFC1..From:
> 102 <sip:102 at voi
>   p.com:5062>;tag=3282942385..To:
> <sip:9999999999 at voip.com>..Contact: <sip:10
>   2 at 192.168.0.2:5062>..Call-ID:
> 29469D19-CDF1-49ED-8245-A67E1B1DBB88 at 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 at voip.com:
>   5062>;tag=3282942385..To:
> <sip:9999999999 at voip.com>;tag=a6a1c5f60faecf035a1
>   ae5b6e96e979a-6e9f..Call-ID:
> 29469D19-CDF1-49ED-8245-A67E1B1DBB88 at 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 at voip.com 
> 
=== message truncated ===

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: log.txt
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050526/f4773f41/attachment.txt>

More information about the sr-users mailing list