Thanks Razvan.
I'm still trying to troubleshoot this problem, i've seen that in the opensips
logs, when i place a call, there are the following error messeges:
Apr 15 21:21:31 sip-lab /usr/local/opensips110/sbin/opensips[14226]:
INFO:core:probe_max_sock_buff: using snd buffer of 255 kb
Apr 15 21:21:31 sip-lab /usr/local/opensips110/sbin/opensips[14226]:
INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket
Apr 15 21:21:32 sip-lab /usr/local/opensips110/sbin/opensips[14225]:
ERROR:nathelper:msg_send: tcp_send failed
Apr 15 21:21:32 sip-lab /usr/local/opensips110/sbin/opensips[14225]:
ERROR:nathelper:nh_timer: sip msg_send failed!
Apr 15 21:21:41 sip-lab /usr/local/opensips110/sbin/opensips[14226]:
ERROR:core:tcp_blocking_connect: timeout 10 s elapsed from 10 s
Apr 15 21:21:41 sip-lab /usr/local/opensips110/sbin/opensips[14226]:
ERROR:core:tcpconn_connect: tcp_blocking_connect failed
Apr 15 21:21:41 sip-lab /usr/local/opensips110/sbin/opensips[14226]:
ERROR:core:tcp_send: connect failed
Apr 15 21:21:41 sip-lab /usr/local/opensips110/sbin/opensips[14226]:
ERROR:tm:msg_send: tcp_send failed
Apr 15 21:21:41 sip-lab /usr/local/opensips110/sbin/opensips[14226]:
ERROR:tm:t_forward_nonack: sending request failed
Apr 15 21:21:41 sip-lab /usr/local/opensips110/sbin/opensips[14226]:
ERROR:rtpproxy:force_rtp_proxy: Unable to parse body
Apr 15 21:21:41 sip-lab /usr/local/opensips110/sbin/opensips[14226]: incoming
reply
Apr 15 21:21:41 sip-lab /usr/local/opensips110/sbin/opensips[14226]:
ERROR:rtpproxy:force_rtp_proxy: Unable to parse body
Apr 15 21:21:41 sip-lab /usr/local/opensips110/sbin/opensips[14226]: incoming
reply
Apr 15 21:21:42 sip-lab /usr/local/opensips110/sbin/opensips[14225]:
ERROR:nathelper:msg_send: tcp_send failed
Apr 15 21:21:42 sip-lab /usr/local/opensips110/sbin/opensips[14225]:
ERROR:nathelper:nh_timer: sip msg_send failed!
I didn't reply before because i was serching in the forum but i didn'n find any
helpfull topic.
Do you still think that is a network issue? Do those error logs have a meaning?
If you see, form the call placing to the incoming replay there are 10 secs.
Thanks a lot,
Leo.
Il Lunedì 14 Aprile 2014 10:26, Razvan Crainea-3 [via OpenSIPS (Open SIP
Server)] <ml-node+s1449251n7590723...@n2.nabble.com> ha scritto:
Hi, Leo!
This doesn't seem to be related to OpenSIPS. My suggestion is to trace
this at the network layer and check if and why the TCP/TLS connection is
taking 15-20 seconds.
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 04/14/2014 01:17 AM, leo wrote:
> Hello:
>
> I'm using opensips 1.10 in a simple single domain scenario.
> The UA are normally NATted.
> The problem i'm having is that the call establishment using UDP is 1 or 2
> sec while when i use TCP or TLS the call is taking 15-20 sec.
> Is this normal? How could i have the same performance for TCP/TLS like with
> UDP?
> Thanks a lot.
>
> Leo.
>
>
>
> --
> View this message in context:
> http://opensips-open-sip-server.1449251.n2.nabble.com/UDP-vs-TCP-TLS-tp7590719.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
________________________________
If you reply to this email, your message will be added to the discussion
below:http://opensips-open-sip-server.1449251.n2.nabble.com/UDP-vs-TCP-TLS-tp7590719p7590723.html
To unsubscribe from UDP vs TCP/TLS, click here.
NAML
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/UDP-vs-TCP-TLS-tp7590719p7590757.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
