Hi,
the trace is quite complex. looks like UA2 receives the cancel and
terminates the call (487 reply for INVITE and 200 ok for cancel).
But for some reasons, the UA1 is keep sending cancel even after 200 ok
was received.
at some point the invite transaction is deleted from the proxy and the
CANCEL retransmission doesn't hit any INVITE transaction anymore, which
leads to the CANCEL looping on the proxy.
regards,
bogdan
unplug wrote:
When UA1 makes a call to UA2, both ringing. Then UA1
cancels the
call, a strange log message (from ngrep) will be got below. After
that UA2 will ring 3 times itself. You can see in line 718, there is
a cancel method. After that, there are many Record-Route, Via in the
sip CANCEL method (line 763, line 1578 and many). Does anyone know
what the problem is?
http://meerkat.no-ip.com/openser/cancel.log
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users