[OpenSIPS-Users] UAC's CANCEL into siptrace
Jeff Pyle
jpyle at fidelityvoice.com
Sun Oct 25 03:31:10 CET 2009
Hi Iñaki,
Don't you ever sleep?
Come to think of it, I've used trace_dialog() on a 1.5 proxy with no problem
in the siptrace capture. Maybe this is a new 1.6 problem?
I call trace_dialog() after the initial INVITE. It wouldn't normally get
called on anything other than an initial INVITE, including a CANCEL. It
would definitely get called before the CANCEL in terms of the transactional
or dialog terms, however.
My CANCEL processing is very basic, from the default config I believe:
# CANCEL processing
if (is_method("CANCEL")) {
if (t_check_trans())
t_relay();
exit;
}
- Jeff
On 10/24/09 10:25 PM, "Iñaki Baz Castillo" <ibc at aliax.net> wrote:
> El Domingo, 25 de Octubre de 2009, Jeff Pyle escribió:
>> Am I likely handling CANCELs incorrectly in the
>> loose_route() portion?
>
> CANCEL is not an in-dialog request. Instead, it's a hop-by-hop request, this
> is: UAC generates it, the proxy takes it and generates a new one for each
> current branch (if there is parallel forking).
>
> About siptrace, I remember that it doesn't capture some ACK's, but I don't
> remember issues with CANCEL. Be sure you call trace_dialog() before tha CANCEL
> handling.
>
More information about the Users
mailing list