[Serusers] Cancel an Invite on ser 0.9.3

Toni Barata toni-r-barata at ptinovacao.pt
Fri Jul 1 17:55:13 CEST 2005


Hi again,

 

Same issue on the release 0.9.3.

 

Regards,

Toni

 

________________________________

From: serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org] On
Behalf Of Toni Barata
Sent: sexta-feira, 1 de Julho de 2005 15:55
To: serusers at lists.iptel.org
Subject: [Serusers] Cancel an Invite on ser 0.8.14

 

Hi All,

 

Can someone checks why, in the situation of a client that cancels a call
before the destination send a "180 ringing" to the proxy, that causes
some troble to the proxy because it is not forwarding the cancel to the
destination.

 

See the following 2 examples :

 

In this situation the cancel works fine:

 

651.327850 10.112.128.220 -> 10.112.128.247 SIP/SDP Request: INVITE
sip:testef03 at teste.pt, with session description

651.328725 10.112.128.247 -> 10.112.128.220 SIP Status: 100 trying --
your call is important to us

651.328778 10.112.128.247 -> 10.112.128.187 SIP/SDP Request: INVITE
sip:testef03 at 10.112.128.187:7678, with session description

651.576892 10.112.128.187 -> 10.112.128.247 SIP Status: 180 Ringing

651.577005 10.112.128.247 -> 10.112.128.220 SIP Status: 180 Ringing

651.722172 10.112.128.220 -> 10.112.128.247 SIP Request: CANCEL
sip:testef03 at teste.pt

651.723047 10.112.128.247 -> 10.112.128.187 SIP Request: CANCEL
sip:testef03 at 10.112.128.187:7678

651.723084 10.112.128.247 -> 10.112.128.220 SIP Status: 200 cancelling

651.723622 10.112.128.247 -> 10.112.128.220 SIP Status: 487 Request
cancelled

651.724792 10.112.128.220 -> 10.112.128.247 SIP Request: ACK
sip:testef03 at teste.pt

651.899824 10.112.128.187 -> 10.112.128.247 SIP Status: 200 OK

651.900593 10.112.128.187 -> 10.112.128.247 SIP Status: 487 Request
Terminated

651.900666 10.112.128.247 -> 10.112.128.187 SIP Request: ACK
sip:testef03 at 10.112.128.187:7678

 

In this one, the cancel never reaches the destination client, so it
keeps ringing...

 

657.866834 10.112.128.220 -> 10.112.128.247 SIP/SDP Request: INVITE
sip:testef03 at teste.pt, with session description

657.867667 10.112.128.247 -> 10.112.128.220 SIP Status: 100 trying --
your call is important to us

657.867720 10.112.128.247 -> 10.112.128.187 SIP/SDP Request: INVITE
sip:testef03 at 10.112.128.187:7678, with session description

658.068940 10.112.128.247 -> 10.112.128.187 SIP/SDP Request: INVITE
sip:testef03 at 10.112.128.187:7678, with session description

658.083368 10.112.128.220 -> 10.112.128.247 SIP Request: CANCEL
sip:testef03 at teste.pt

658.084201 10.112.128.247 -> 10.112.128.220 SIP Status: 200 ok -- no
more pending branches

658.084948 10.112.128.247 -> 10.112.128.220 SIP Status: 487 Request
cancelled

658.085933 10.112.128.220 -> 10.112.128.247 SIP Request: ACK
sip:testef03 at teste.pt

658.228348 10.112.128.187 -> 10.112.128.247 SIP Status: 180 Ringing

658.232010 10.112.128.187 -> 10.112.128.247 SIP Status: 180 Ringing

 

Thanks,

Toni

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050701/6b5d0a30/attachment.htm>


More information about the sr-users mailing list