That fixed it, thanks Daniel,
I can't beleive I missed that, it is in the example config too. I
guess I need to RTM a bit more.
Have a great weekend.
JR
On Fri, Nov 5, 2010 at 11:36 AM, Daniel-Constantin Mierla
<miconda(a)gmail.com> wrote:
Hello,
the problem is in failure route where you don't filter out canceled
transaction and try to re-route even the caller canceled the call.
Add at the top of your failure route:
if (t_is_canceled()) {
exit;
}
Cheers,
Daniel
On 11/5/10 4:48 PM, JR Richardson wrote:
I'm seeing random errors in my Kamailio 3.0.2 log:
ERROR: tm [tm.c:1300]: ERROR: w_t_relay_to: t_relay_to failed
ERROR: tm [t_fwd.c:1379]: ERROR: t_forward_nonack: no branches for
forwarding
Are you sure those are the only errors in the log?
I've gotten that before when getting bogus or missing 'Via' headers
from
bandwidth.com in the 487s.
Here is a pastebin of the conversation, what is interesting is line 29
through 32.
http://pastebin.com/QcaAeqjN
For some reason Kamailio is sending 2 additional 487's without a
response. I believe this is why I am getting the log errors. I
played around with "modparam("tm", "cancel_b_method", 2)"
but have the
same results.
Here is a pastebin of my kamailio.cfg:
http://pastebin.com/Tn3humr0
Any suggestions on where to put some logging statements and what to
look for would be helpful.
Thanks.
JR
--
Daniel-Constantin Mierla
http://www.asipto.com
--
JR Richardson
Engineering for the Masses