[SR-Users] 477 Unfortunately error on sending to next hop occurred

Daniel-Constantin Mierla miconda at gmail.com
Fri Aug 23 20:46:18 CEST 2013


Hello,

On 8/23/13 8:33 PM, Steve Davies wrote:
>
> On 23 August 2013 19:42, Daniel-Constantin Mierla <miconda at gmail.com 
> <mailto:miconda at gmail.com>> wrote:
>
>     Can you try the new patch attached?
>
>     I overlooked that the code where to skip sending the reply was in
>     between some #ifdef ... #else ... #endif and I did it only for the
>     #else branch, but actually the #ifdef was enabled by compile.
>
>     You have to apply the patch on clean sources.
>
>
> Hi,
>
> I now get the -4, thanks!
>
>  > Aug 23 20:25:22 ubuntu /usr/local/sbin/kamailio[5645]: NOTICE: 
> <script>: SLD: in RELAY, t_relay returned -4 err.rcode is <null> t_r_c 
> is 100 sent = 0
>
> FWIW, I had an sl_reply_error() after the t_relay and it decided to 
> send back a 500.
>
> Which probably doesn't matter for me since I will go on and try my 
> alternate routing.
>
> But is there a way to get hold of that "-477", and get the 
> sl_reply_error to use the 477 ?

Not at this moment, but can be eventually added as t_reply_error(), as 
there is an internal variable holding that code.

Btw, after using t_relay() in this case, is better to use 
send_reply(...) instead of sl_send_reply(...), to clean the transaction 
gracefully in case the appropriate structure was created.

Cheers,
Daniel

>
> Thanks,
> Steve
>
>
>
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: ERROR: tm 
> [../../forward.h:196]: msg_send(): msg_send: ERROR: udp_send failed
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: DEBUG: tm 
> [t_fwd.c:1369]: t_send_branch(): t_send_branch: send to 
> 41.221.230.60:5060 <http://41.221.230.60:5060> (1) failed
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: ERROR: tm 
> [t_fwd.c:1387]: t_send_branch(): ERROR: t_send_branch: sending request 
> on branch 0 failed
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: DEBUG: tm 
> [t_funcs.c:357]: t_relay_to(): ERROR:tm:t_relay_to:  t_forward_nonack 
> returned error
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: DEBUG: tm 
> [t_funcs.c:365]: t_relay_to(): not generating immediate reply for 
> error -477
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: ERROR: *** 
> cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=562 a=26 n=xlog
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: DEBUG: tm 
> [t_lookup.c:1100]: t_check_msg(): DEBUG: t_check_msg: msg id=5 global 
> id=5 T start=0xb2f7ef18
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: DEBUG: tm 
> [t_lookup.c:1172]: t_check_msg(): DEBUG: t_check_msg: T already found!
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: DEBUG: tmx 
> [t_var.c:467]: pv_get_tm_reply_code(): reply code is <100>
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: NOTICE: 
> <script>: SLD: in RELAY, t_relay returned -4 err.rcode is <null> t_r_c 
> is 100 sent = 0
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: ERROR: *** 
> cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=566 a=16 n=if
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: ERROR: *** 
> cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=564 a=24 
> n=sl_reply_error
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: DEBUG: <core> 
> [msg_translator.c:206]: check_via_address(): 
> check_via_address(172.16.230.1, 172.16.230.1, 0)
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: ERROR: sl 
> [sl_funcs.c:371]: sl_reply_error(): ERROR: sl_reply_error used: I'm 
> terribly sorry, server error occurr
> ed (1/SL)
> Aug 23 20:25:44 ubuntu /usr/local/sbin/kamailio[5646]: ERROR: *** 
> cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=566 a=2 n=exit
>
>

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20130823/02f2ad4a/attachment-0001.html>


More information about the sr-users mailing list