Hi,
We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP.
What is the recommended configuration when TCP is used?
Currently, I only have the following:
children=16
listen=udp:<ip>:5060
listen=tcp:<ip>:5060
disable_tcp=no
tcp_connection_lifetime=605 (registration expiry is 600)
Also, is there a difference with UDP regarding NAT handling?
Thanks,
Mickael
Hello,
where are typically those issues with truncated SDP? On the phones?
If you use tcp and have phones behind the nat, it is recommended to not connect if there is no active connection after location lookup -- see core functions for tcp.
Cheers, Daniel
On 04/05/15 13:54, Mickael Marrache wrote:
Hi,
We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP.
What is the recommended configuration when TCP is used?
Currently, I only have the following:
children=16
listen=udp:<ip>:5060
listen=tcp:<ip>:5060
disable_tcp=no
tcp_connection_lifetime=605 (registration expiry is 600)
Also, is there a difference with UDP regarding NAT handling?
Thanks,
Mickael
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
In general, it happens in our network (as more and more Via headers are added).
Sorry, I didn't understand your last sentence. What do you mean by not connect if there is no active connection after location lookup?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, May 04, 2015 11:07 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Recommended configuration for TCP support
Hello,
where are typically those issues with truncated SDP? On the phones?
If you use tcp and have phones behind the nat, it is recommended to not connect if there is no active connection after location lookup -- see core functions for tcp.
Cheers, Daniel
On 04/05/15 13:54, Mickael Marrache wrote:
Hi,
We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP.
What is the recommended configuration when TCP is used?
Currently, I only have the following:
children=16
listen=udp:<ip>:5060
listen=tcp:<ip>:5060
disable_tcp=no
tcp_connection_lifetime=605 (registration expiry is 600)
Also, is there a difference with UDP regarding NAT handling?
Thanks,
Mickael
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
*set_forward_no_connect()* called after lookup() prevents kamailio from making a new connection to a phone if there is no active connection. This is useful when you are trying to call to a UA which kamailio still keeps registration record for, but TCP/TLS connect to this phone is already gone (due to timeout, network problem, etc...).
On 05/05/15 14:54, Mickael Marrache wrote:
In general, it happens in our network (as more and more Via headers are added).
Sorry, I didn't understand your last sentence. What do you mean by not connect if there is no active connection after location lookup?
*From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On Behalf Of *Daniel-Constantin Mierla *Sent:* Monday, May 04, 2015 11:07 PM *To:* Kamailio (SER) - Users Mailing List *Subject:* Re: [SR-Users] Recommended configuration for TCP support
Hello,
where are typically those issues with truncated SDP? On the phones?
If you use tcp and have phones behind the nat, it is recommended to not connect if there is no active connection after location lookup -- see core functions for tcp.
Cheers, Daniel
On 04/05/15 13:54, Mickael Marrache wrote:
Hi, We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP. What is the recommended configuration when TCP is used? Currently, I only have the following: children=16 listen=udp:<ip>:5060 listen=tcp:<ip>:5060 disable_tcp=no tcp_connection_lifetime=605 (registration expiry is 600) Also, is there a difference with UDP regarding NAT handling? Thanks, Mickael _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users-- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany -http://www.kamailioworld.com
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Thanks for your explanation, the problem is that the actual lookup is done by a proxy which is located after our load balancer. Therefore, the TCP connection with the UA should not be visible by the proxy but by the load balancer.
How does that work in such case?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Vitaliy Aleksandrov Sent: Wednesday, May 06, 2015 10:34 AM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Recommended configuration for TCP support
set_forward_no_connect() called after lookup() prevents kamailio from making a new connection to a phone if there is no active connection. This is useful when you are trying to call to a UA which kamailio still keeps registration record for, but TCP/TLS connect to this phone is already gone (due to timeout, network problem, etc...).
On 05/05/15 14:54, Mickael Marrache wrote:
In general, it happens in our network (as more and more Via headers are added).
Sorry, I didn't understand your last sentence. What do you mean by not connect if there is no active connection after location lookup?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, May 04, 2015 11:07 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Recommended configuration for TCP support
Hello,
where are typically those issues with truncated SDP? On the phones?
If you use tcp and have phones behind the nat, it is recommended to not connect if there is no active connection after location lookup -- see core functions for tcp.
Cheers, Daniel
On 04/05/15 13:54, Mickael Marrache wrote:
Hi,
We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP.
What is the recommended configuration when TCP is used?
Currently, I only have the following:
children=16
listen=udp:<ip>:5060
listen=tcp:<ip>:5060
disable_tcp=no
tcp_connection_lifetime=605 (registration expiry is 600)
Also, is there a difference with UDP regarding NAT handling?
Thanks,
Mickael
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi,
I suppose calling set_forward_no_connect() at the LB for a request from the registrar to a user will lead to the result. LB won't try to make an outgoing tcp/tls connection to reach a requested destination and will only forward a request only via existing one.
BR
Thanks for your explanation, the problem is that the actual lookup is done by a proxy which is located after our load balancer. Therefore, the TCP connection with the UA should not be visible by the proxy but by the load balancer.
How does that work in such case?
*From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On Behalf Of *Vitaliy Aleksandrov *Sent:* Wednesday, May 06, 2015 10:34 AM *To:* sr-users@lists.sip-router.org *Subject:* Re: [SR-Users] Recommended configuration for TCP support
*set_forward_no_connect()* called after lookup() prevents kamailio from making a new connection to a phone if there is no active connection. This is useful when you are trying to call to a UA which kamailio still keeps registration record for, but TCP/TLS connect to this phone is already gone (due to timeout, network problem, etc...).
On 05/05/15 14:54, Mickael Marrache wrote:
In general, it happens in our network (as more and more Via headers are added). Sorry, I didn't understand your last sentence. What do you mean by not connect if there is no active connection after location lookup? *From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On Behalf Of *Daniel-Constantin Mierla *Sent:* Monday, May 04, 2015 11:07 PM *To:* Kamailio (SER) - Users Mailing List *Subject:* Re: [SR-Users] Recommended configuration for TCP support Hello, where are typically those issues with truncated SDP? On the phones? If you use tcp and have phones behind the nat, it is recommended to not connect if there is no active connection after location lookup -- see core functions for tcp. Cheers, Daniel On 04/05/15 13:54, Mickael Marrache wrote: Hi, We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP. What is the recommended configuration when TCP is used? Currently, I only have the following: children=16 listen=udp:<ip>:5060 listen=tcp:<ip>:5060 disable_tcp=no tcp_connection_lifetime=605 (registration expiry is 600) Also, is there a difference with UDP regarding NAT handling? Thanks, Mickael _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany -http://www.kamailioworld.com _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
What would happen in this case? If I understand correctly, the proxy will always forward the request but the last hop (before the UAS) will forward the request only if a connection is active?
If the last hop doesn't forward the request because no TCP connection exists, what happens? How the proxy will detect this situation?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Vitaliy Aleksandrov Sent: Friday, May 08, 2015 4:06 PM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Recommended configuration for TCP support
Hi,
I suppose calling set_forward_no_connect() at the LB for a request from the registrar to a user will lead to the result. LB won't try to make an outgoing tcp/tls connection to reach a requested destination and will only forward a request only via existing one.
BR
Thanks for your explanation, the problem is that the actual lookup is done by a proxy which is located after our load balancer. Therefore, the TCP connection with the UA should not be visible by the proxy but by the load balancer.
How does that work in such case?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Vitaliy Aleksandrov Sent: Wednesday, May 06, 2015 10:34 AM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Recommended configuration for TCP support
set_forward_no_connect() called after lookup() prevents kamailio from making a new connection to a phone if there is no active connection. This is useful when you are trying to call to a UA which kamailio still keeps registration record for, but TCP/TLS connect to this phone is already gone (due to timeout, network problem, etc...).
On 05/05/15 14:54, Mickael Marrache wrote:
In general, it happens in our network (as more and more Via headers are added).
Sorry, I didn't understand your last sentence. What do you mean by not connect if there is no active connection after location lookup?
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, May 04, 2015 11:07 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Recommended configuration for TCP support
Hello,
where are typically those issues with truncated SDP? On the phones?
If you use tcp and have phones behind the nat, it is recommended to not connect if there is no active connection after location lookup -- see core functions for tcp.
Cheers, Daniel
On 04/05/15 13:54, Mickael Marrache wrote:
Hi,
We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP.
What is the recommended configuration when TCP is used?
Currently, I only have the following:
children=16
listen=udp:<ip>:5060
listen=tcp:<ip>:5060
disable_tcp=no
tcp_connection_lifetime=605 (registration expiry is 600)
Also, is there a difference with UDP regarding NAT handling?
Thanks,
Mickael
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
What would happen in this case? If I understand correctly, the proxy will always forward the request but the last hop (before the UAS) will forward the request only if a connection is active?
correct.
If the last hop doesn't forward the request because no TCP connection exists, what happens? How the proxy will detect this situation?
It won't find any matching connection and won't try to establish a new one since you asked it to not. So it will just send a reply back to the registrar with an error. After receiving an error registrar in its turn can perform some smart actions like forwarding to a voicemail system.
-
Daniel-Constantin Mierla -
Mickael Marrache -
Vitaliy Aleksandrov