Hello,
o Jim Burke [04/03/09 00:58]:
Hi All,
I am using call-timer app and found that it does not forward any
CANCEL messages to the 'B' leg of the call. Based on the debug and
wireshark, SEMS replied to the CANCEL on the 'A' leg with a 200 Ok.
It then sets the timer to 0 and waits for the 200 OK with SDP from the
'B' leg and then will send a BYE to the 'B' leg.
I would have expected SEMS while working in B2B mode to forward the
CANCEL to the 'B' leg of the call and stop the terminating phone from
ringing. Does anyone else have some thoughts on how SEMS should
handle this scenario?
that it what it is supposed to do. Note that the CANCEL can actually not
be forwarded verbatim (like later in-dialog requests), but on the
terminating side the dialog is ended - if is for example is already
established, it must be terminated with BYE.
In your log I find this line strange:
Apr 2 14:01:37 sip01 sems[32016]: ERROR: [b6e63ba0] cancel
(trans_layer.cpp:616): Trying to cancel a non-INVITE request (we
SHOULD NOT do that)
Dialog layer has found the INVITE transaction (so it calls cancel(), in
AmSipDialog::cancel()), but transaction layer (trans_layer.cpp in
sipctrl) thinks it's not an INVITE transaction, so it refuses... maybe
the full log and the SIP dump would give more insight.
Regards
Stefan
--
Stefan Sayer
VoIP Services
[email protected]
www.iptego.com
IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
