11 Nov
2010
11 Nov
'10
6:42 p.m.
Hi All,
I'm still getting these errors and I'm struggling to resolve the
problem. I think I'm missing an append_branch or something simple in
my config, a little guiedance will be appriciated.
The error:
Nov 11 10:23:26 sip-router1 /usr/local/sbin/kamailio[23739]: ERROR: tm
[t_fwd.c:1379]: ERROR: t_forward_nonack: no branches for forwarding
Nov 11 10:23:26 sip-router1 /usr/local/sbin/kamailio[23739]: ERROR: tm
[tm.c:1300]: ERROR: w_t_relay_to: t_relay_to failed
The sip graph causing the error:
http://pastebin.com/VHhQ1sJY
My config:
http://pastebin.com/BYn4g5ur
Do I need to have a mechanism to deal with a 486 form the carrier?
Thanks.
JR
--
JR Richardson
Engineering for the Masses
11 Nov
11 Nov
6:52 p.m.
1. One problem may be that you are calling route[RELAY] from your
failure route and using sl_send_reply(). The route[RELAY] is still
being invoked in a failure route execution context, even if you have
managed to contextually invoke another route, or subroutine if you will.
Stateless replies (sl_reply_error()) cannot be sent from within a
failure route.
2. Yes. throw an append_branch() into your failure route.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street NE
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
6:54 p.m.
On 11/11/2010 11:52 AM, Alex Balashov wrote:
2. Yes. throw an append_branch() into your failure
route.
To expand on this; the proxy can't just arbitrarily t_relay() again
after it has received a final negative reply. That's not what proxies
do. The only way it can happen is if a proxy uses its forking
capability, as described by the standard, to create a new branch to
another destination. Only then would it be justified in keeping the
final negative reply on the first branch opaque from the customer and
pursuing other options.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street NE
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
5127
days inactive
5127
days old
2 comments
2 participants
participants (2)
-
Alex Balashov -
JR Richardson