Hi,

We frequently run into the situation where a call is simultaneously CANCEL'd by the caller and answered (2xx) by the callee. This results in the caller not sending an e2e ACK, since it CANCEL'd the branch. It results in retransmission of the 200 OK, since the proxy can't CANCEL the branch anymore.

It leaves the dialog in state 3

#define DLG_STATE_CONFIRMED_NA 3 /*!< confirmed dialog without a ACK yet */ (dlg_hash.h)

for up to 'dialog_timeout' time.

Is there a straightforward hack for this situation? Does changing the dialog timeout AVP have any effect after the relay of the initial INVITE (and thus invocation of the registered dialog init TM callback)?

More generally, I was wondering if there has been any thought given to the idea of separate timeout modparams for confirmed-nonACKed state, as well as early state perhaps.

Thanks,

-- Alex