If you use statefull forwarding (t_relay), then CANCEL is handled hop-by-hop. Thus openser's tm module should process the incoming CANCEL and generate an outgoing CANCEL.

Try this in your config:

if ( is_method("CANCEL") && !t_check_trans() ) { # CANCEL without matching INVITE transaction, ignore # may happen if the INVITE is slower than the CANCEL # ignore the CANCEL, as the client will retransmit it, # and maybe next time # the INVITE transaction is already created xlog("L_WARN","$ci CANCEL without matching transaction ... ignore and discard.\n"); exit; }

if ( is_method("CANCEL") ) { # CANCEL with matching INVITE transaction, just # t_relay xlog("L_INFO","$ci CANCEL with matching transaction ... t_relay.\n"); t_relay(); exit; }

regards klaus

Andreas M. wrote:

Hello, i have following setup:

Cisco AS5300 -- Openser --- Client

Now if there is an incoming call from the CiscoGW to the client and is canceled, but the "cancel" message does not arrive at the client (because any reason), the phone doesn´t stop ringing.

Cisco --- OSER --- Client Cancel -> <- Canceling Cancel ->

thats it. It seems that no one is missing any OK or ACKS!

It happens only sometimes, but who is responsible to handle this behavior ? The Cisco Gateway or the Proxy ?

Using OSER 1.0.1

regards, Andreas M.

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users