[SR-Users] kamailio sending 408 request time out

[Daniel-Constantin Mierla]

On 13/06/15 15:26, Priyaranjan Nayak wrote:
> Hi All,
>
> I am using  kamailio-4.2.5 for testing setup. After starting the
> kamailio I am getting below message
> /usr/local/sbin/kamailio -f /usr/local/etc/kamailio/kamailio.cfg -N 20
> -m 512 -M 8
> /usr/local/sbin/kamailio -f /usr/local/etc/kamailio/kamailio.cfg -E
> loading modules under config path: /usr/local/lib64/kamailio/modules/
>  0(24471) WARNING: <core> [socket_info.c:1392]: fix_hostname(): could
> not rev. resolve 192.168.1.118
>  0(24471) WARNING: <core> [socket_info.c:1392]: fix_hostname(): could
> not rev. resolve 192.168.1.118
> Listening on
>              udp: 192.168.1.118:4060 <http://192.168.1.118:4060>
>              tcp: 192.168.1.118:4060 <http://192.168.1.118:4060>
> Aliases:
>
>  0(24471) INFO: <core> [tcp_main.c:4748]: init_tcp(): using epoll_lt
> as the io watch method (auto detected)
>  0(24473) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to
> import bind_ob
>  0(24473) INFO: rr [rr_mod.c:160]: mod_init(): outbound module not
> available
>  0(24473) INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size
> 1024
>  0(24473) INFO: <core> [udp_server.c:175]: probe_max_receive_buffer():
> SO_RCVBUF is initially 212992
>  0(24473) INFO: <core> [udp_server.c:225]: probe_max_receive_buffer():
> SO_RCVBUF is finally 425984
>  8(24481) INFO: ctl [io_listener.c:225]: io_listen_loop():
> io_listen_loop:  using epoll_lt io watch method (config)
>
> Once I sent the request to kamailio server, I am not getting 408
> request time out from kamailio  and  getting below log
>
> 12(24485) ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error
> reading: Connection reset by peer (104)
> 12(24485) ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR:
> tcp_read_req: error reading
>  9(24482) ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error
> reading: Connection reset by peer (104)
>  9(24482) ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR:
> tcp_read_req: error reading
> 12(24485) ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error
> reading: Connection reset by peer (104)
> 12(24485) ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR:
> tcp_read_req: error reading
> 10(24483) ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error
> reading: Connection reset by peer (104)
> 10(24483) ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR:
> tcp_read_req: error reading
> 13(24486) ERROR: <core> [tcp_main.c:4162]: handle_tcpconn_ev():
> connect 192.168.1.114:61945 <http://192.168.1.114:61945> failed
> 13(24486) ERROR: <core> [tcp_main.c:4162]: handle_tcpconn_ev():
> connect 192.168.1.114:19129 <http://192.168.1.114:19129> failed
> 13(24486) ERROR: <core> [tcp_main.c:4162]: handle_tcpconn_ev():
> connect 192.168.1.114:6050 <http://192.168.1.114:6050> failed
>
> Could you please give me any idea how to resolve this issue ?
>
you should provide the network trace with the sip traffic for better
understanding of what happens. The logs are pretty clear, though --
kamailio couldn't connect to the destination.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com

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