Hi Martin,
I made a fix for this problem - please update from cvs. It will be great
if you could test it to see if the problem is fixed or if no side
effects pop up.
regards,
bogdan
Bogdan-Andrei Iancu wrote:
Hi Martin,
thanks for report - indeed, it seams to be a problem - I was able to
reproduce the scenario. I will start working on it, but it will be
better if you also open a new bug report on the tracker.
Thanks and regards,
bogdan
Martin Koenig wrote:
Hello all,
in the given scenario, a CANCEL-message is t_relay()-ed to the next
hop user
agent in transport UDP, and the target agent does not to it. However,
openser is not re-transmitting the cancel message:
#
U 2006/05/30 10:35:14.928141 USERAGENT-A:5060 -> OPENSER:5060
CANCEL sip:[EMAIL PROTECTED]:5060;user=phone SIP/2.0.
Via: SIP/2.0/UDP
USERAGENT-A:5060;branch=z9hG4bK-b42132959a0eaae2d4f43ba197d4c249;rport=5060.
From: <sip:[EMAIL PROTECTED]>;tag=1548336820.
To: <sip:[EMAIL PROTECTED];user=phone>.
Call-ID: [EMAIL PROTECTED]
CSeq: 2 CANCEL.
Max-Forwards: 68.
Contact: <sip:[EMAIL PROTECTED]:5060;transport=udp>.
Content-Length: 0.
.
#
U 2006/05/30 10:35:14.928806 OPENSER:5060 -> USERAGENT-B:5060
CANCEL sip:[EMAIL PROTECTED]:5060;user=phone SIP/2.0.
Via: SIP/2.0/UDP OPENSER;branch=z9hG4bK5ef1.bea7a8f6.0.
Via: SIP/2.0/UDP
USERAGENT-A:5060;branch=z9hG4bK-b42132959a0eaae2d4f43ba197d4c249;rport=5060.
From: <sip:[EMAIL PROTECTED]>;tag=1548336820.
To: <sip:[EMAIL PROTECTED];user=phone>.
Call-ID: [EMAIL PROTECTED]
CSeq: 2 CANCEL.
Max-Forwards: 67.
Contact: <sip:[EMAIL PROTECTED]:5060;transport=udp>.
Content-Length: 0.
.
#
U 2006/05/30 10:35:14.928835 OPENSER:5060 -> PROXY-B:5060
SIP/2.0 200 canceling.
Via: SIP/2.0/UDP
USERAGENT:5060;branch=z9hG4bK-b42132959a0eaae2d4f43ba197d4c249;rport=5060.
From: <sip:[EMAIL PROTECTED]>;tag=1548336820.
To:
<sip:[EMAIL PROTECTED];user=phone>;tag=54438713ac33febc84bf508cca
f41100-cfc5.
Call-ID: [EMAIL PROTECTED]
CSeq: 2 CANCEL.
Content-Length: 0.
.
The second cancel is the only cancel ever that openser will send out. I
believe it should start re-transmission of the cancel message after
500ms,
then 1000ms etc. Is this a known issue?
Best regards,
Martin
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
