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
wrote:
> Hello,
>
> the problem is in failure route where you don't filter out can
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 see
>> 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
On 11/04/2010 04:01 PM, JR Richardson wrote:
Hi All,
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 lo
El Thu, 4 Nov 2010 15:01:43 -0500
JR Richardson escribió:
> Hi All,
>
> 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
>
> After going blind sta
