Hello,
On 9/15/11 4:02 PM, Timo Klecker wrote:
Hi Daniel,
I managed to get a log with debug 4 from one call. I had to take out all
IP-Addresses and Usernames, hope you can use it.
the log confirmed what I expected:
Sep 15 15:32:33 vux896 /sbin/kamailio[31594]: DEBUG: siptrace
10:27
An: Timo Klecker; kamailio users
Betreff: Re: [SR-Users] CANCEL is not processed in onsend_route
Hello,
On 9/15/11 4:02 PM, Timo Klecker wrote:
Hi Daniel,
I managed to get a log with debug 4 from one call. I had to take out
all IP-Addresses and Usernames, hope you can use it.
the log
on the trace-flag, as you suggested.
Greetings
Timo
-Ursprüngliche Nachricht-
Von: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Gesendet: Freitag, 23. September 2011 10:27
An: Timo Klecker; kamailio users
Betreff: Re: [SR-Users] CANCEL is not processed in onsend_route
Hello,
On 9/15
. September 2011 11:20
An: sr-users@lists.sip-router.org
Betreff: Re: [SR-Users] CANCEL is not processed in onsend_route
I have no idea how siptrace works, but: When using tm module, the
CANCEL is
not forwarded but absorbed by tm module, and then tm module creates a
new
CANCEL based
Betreff: Re: [SR-Users] CANCEL is not processed in onsend_route
I have no idea how siptrace works, but: When using tm module, the CANCEL is
not forwarded but absorbed by tm module, and then tm module creates a new
CANCEL based on the previous sent INVITE.
That may be the reason why on_send route
-router.org
Betreff: Re: [SR-Users] CANCEL is not processed in onsend_route
I have no idea how siptrace works, but: When using tm module, the CANCEL is
not forwarded but absorbed by tm module, and then tm module creates a new
CANCEL based on the previous sent INVITE.
That may be the reason why
Hello all,
I want to log the incoming and outgoing CANCEL on my Kamailio. I tried with
a call of sip_trace in the default route
setflag(22);
if (method == CANCEL) {
sip_trace();
if (t_check_trans()) {
t_relay();
I have no idea how siptrace works, but: When using tm module, the CANCEL
is not forwarded but absorbed by tm module, and then tm module creates a
new CANCEL based on the previous sent INVITE.
That may be the reason why on_send route is not activated.
klaus
Am 06.09.2011 10:24, schrieb Timo
