Re: [OpenSIPS-Users] rtpproxy timeout notifications
Hi, Flavio! I'm glad to see that things are working better. However, if you still encounter this problem, can you follow the SourceForge bug opened related to this [1]? [1] https://sourceforge.net/tracker/index.php?func=detailaid=3592878group_id=232389atid=1086410# https://sourceforge.net/tracker/index.php?func=detailaid=3592878group_id=232389atid=1086410# Best regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 01/07/2013 12:24 PM, Flavio Goncalves wrote: Hi Razvan, I have fixed an issue were rtpproxy was not being called during reinvites and the customer reduced the use of timeout notifications. The last occurrence of the problem was December 27. There are three possibilities for the problem have disappeared. 1. re-invite handling 2. rtpproxyset handling (I fixed some errors where the set was being set to an invalid value) 3. The user has decreased the use of timeout notifications to a minimum and the occurrence is now less frequent. Still observing the problem. Flavio E. Goncalves 2013/1/7 Răzvan Crainea raz...@opensips.org mailto:raz...@opensips.org Hi, Flavio! Can you tell me what versions of OpenSIPS and RTPProxy are you using? Best regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 01/03/2013 12:31 PM, Flavio Goncalves wrote: Hi Razvan, I'm checking if the problem is not related to re-invites and calling rtpproxy set with an invalid value. Anyway, the logs are below. Dec 20 14:59:28 /sbin/opensips[6978]: ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy [1] Dec 20 14:59:28 /sbin/opensips[6978]: INFO:rtpproxy:timeout_listener_process: RTPProxy buffer: [255] 3066.74196691#0121744.870880408#0121968.1268777973#012949 tel:1268777973%23012949.1984340712#01274 tel:1984340712%2301274.448511458#012860.999375735#0121893.793805873#0122451.492975819#0123796.1055294097#012485.853875076#0122426.1713554641#0122310.1069754522#012555.117610#0123225.315833604#0122922.440360056#012976.780586176#0122899.1149567571#0121 Flavio E. Goncalves CEO - V.Office 2012/12/18 Răzvan Crainea raz...@opensips.org mailto:raz...@opensips.org Hi, Flavio! I've attached a patch for the rtpproxy module, that for every error, it prints the buffer received from the Rtpproxy server. What I want to see is if the message is totally broken, or only some parts of it are malformed. Could you please apply this patch, and paste us the output when the error occurs again? Best regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 12/13/2012 07:01 PM, Flavio Goncalves wrote: I'm having an issue with timeout notification of rtpproxy. Usually sessions are disconnected properly with rtpproxy timeout notification: INFO:do_timeout_notification: notification timeout sent 1715.2112525045 : Success (The dialog hash is presented correctly with period .) However, In some cases (3 to 7 per day in 25000 calls) we got the following message from rtpproxy module. RTP Proxy in this case send the dialog id with a # in the middle. I can't reproduce the problem in the lab. Dec 12 16:42:4 ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy - invalid dialog entry [1727216578#0123634 tel:%5B1727216578%230123634] In this case there is a hash in the middle of the dialog identifier (a str2int function generates this error in the rtpproxy module denying the request and throwing the error message. No errors in OpenSIPS log No errors in rtpproxy log (debug enabled) Any ideas? Flavio E. Goncalves ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] rtpproxy timeout notifications
Hi, Flavio! Can you tell me what versions of OpenSIPS and RTPProxy are you using? Best regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 01/03/2013 12:31 PM, Flavio Goncalves wrote: Hi Razvan, I'm checking if the problem is not related to re-invites and calling rtpproxy set with an invalid value. Anyway, the logs are below. Dec 20 14:59:28 /sbin/opensips[6978]: ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy [1] Dec 20 14:59:28 /sbin/opensips[6978]: INFO:rtpproxy:timeout_listener_process: RTPProxy buffer: [255] 3066.74196691#0121744.870880408#0121968.1268777973#012949.1984340712#01274.448511458#012860.999375735#0121893.793805873#0122451.492975819#0123796.1055294097#012485.853875076#0122426.1713554641#0122310.1069754522#012555.117610#0123225.315833604#0122922.440360056#012976.780586176#0122899.1149567571#0121 Flavio E. Goncalves CEO - V.Office 2012/12/18 Răzvan Crainea raz...@opensips.org mailto:raz...@opensips.org Hi, Flavio! I've attached a patch for the rtpproxy module, that for every error, it prints the buffer received from the Rtpproxy server. What I want to see is if the message is totally broken, or only some parts of it are malformed. Could you please apply this patch, and paste us the output when the error occurs again? Best regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 12/13/2012 07:01 PM, Flavio Goncalves wrote: I'm having an issue with timeout notification of rtpproxy. Usually sessions are disconnected properly with rtpproxy timeout notification: INFO:do_timeout_notification: notification timeout sent 1715.2112525045 : Success (The dialog hash is presented correctly with period .) However, In some cases (3 to 7 per day in 25000 calls) we got the following message from rtpproxy module. RTP Proxy in this case send the dialog id with a # in the middle. I can't reproduce the problem in the lab. Dec 12 16:42:4 ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy - invalid dialog entry [1727216578#0123634 tel:%5B1727216578%230123634] In this case there is a hash in the middle of the dialog identifier (a str2int function generates this error in the rtpproxy module denying the request and throwing the error message. No errors in OpenSIPS log No errors in rtpproxy log (debug enabled) Any ideas? Flavio E. Goncalves ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] rtpproxy timeout notifications
Razavn, I'm using OpenSIPS 1.8.2 from svn and rtpproxy from the opensips repository. Flavio E. Goncalves 2013/1/7 Răzvan Crainea raz...@opensips.org Hi, Flavio! Can you tell me what versions of OpenSIPS and RTPProxy are you using? Best regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 01/03/2013 12:31 PM, Flavio Goncalves wrote: Hi Razvan, I'm checking if the problem is not related to re-invites and calling rtpproxy set with an invalid value. Anyway, the logs are below. Dec 20 14:59:28 /sbin/opensips[6978]: ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy [1] Dec 20 14:59:28 /sbin/opensips[6978]: INFO:rtpproxy:timeout_listener_process: RTPProxy buffer: [255] 3066.74196691#0121744.870880408#0121968.1268777973#012949. 1984340712#01274 .448511458#012860.999375735#0121893.793805873#0122451.492975819#0123796.1055294097#012485.853875076#0122426.1713554641#0122310.1069754522#012555.117610#0123225.315833604#0122922.440360056#012976.780586176#0122899.1149567571#0121 Flavio E. Goncalves CEO - V.Office 2012/12/18 Răzvan Crainea raz...@opensips.org Hi, Flavio! I've attached a patch for the rtpproxy module, that for every error, it prints the buffer received from the Rtpproxy server. What I want to see is if the message is totally broken, or only some parts of it are malformed. Could you please apply this patch, and paste us the output when the error occurs again? Best regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 12/13/2012 07:01 PM, Flavio Goncalves wrote: I'm having an issue with timeout notification of rtpproxy. Usually sessions are disconnected properly with rtpproxy timeout notification: INFO:do_timeout_notification: notification timeout sent 1715.2112525045 : Success (The dialog hash is presented correctly with period .) However, In some cases (3 to 7 per day in 25000 calls) we got the following message from rtpproxy module. RTP Proxy in this case send the dialog id with a # in the middle. I can't reproduce the problem in the lab. Dec 12 16:42:4 ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy - invalid dialog entry [1727216578#0123634 ] In this case there is a hash in the middle of the dialog identifier (a str2int function generates this error in the rtpproxy module denying the request and throwing the error message. No errors in OpenSIPS log No errors in rtpproxy log (debug enabled) Any ideas? Flavio E. Goncalves ___ Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] rtpproxy timeout notifications
Hi Razvan, I have fixed an issue were rtpproxy was not being called during reinvites and the customer reduced the use of timeout notifications. The last occurrence of the problem was December 27. There are three possibilities for the problem have disappeared. 1. re-invite handling 2. rtpproxyset handling (I fixed some errors where the set was being set to an invalid value) 3. The user has decreased the use of timeout notifications to a minimum and the occurrence is now less frequent. Still observing the problem. Flavio E. Goncalves 2013/1/7 Răzvan Crainea raz...@opensips.org Hi, Flavio! Can you tell me what versions of OpenSIPS and RTPProxy are you using? Best regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 01/03/2013 12:31 PM, Flavio Goncalves wrote: Hi Razvan, I'm checking if the problem is not related to re-invites and calling rtpproxy set with an invalid value. Anyway, the logs are below. Dec 20 14:59:28 /sbin/opensips[6978]: ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy [1] Dec 20 14:59:28 /sbin/opensips[6978]: INFO:rtpproxy:timeout_listener_process: RTPProxy buffer: [255] 3066.74196691#0121744.870880408#0121968.1268777973#012949. 1984340712#01274 .448511458#012860.999375735#0121893.793805873#0122451.492975819#0123796.1055294097#012485.853875076#0122426.1713554641#0122310.1069754522#012555.117610#0123225.315833604#0122922.440360056#012976.780586176#0122899.1149567571#0121 Flavio E. Goncalves CEO - V.Office 2012/12/18 Răzvan Crainea raz...@opensips.org Hi, Flavio! I've attached a patch for the rtpproxy module, that for every error, it prints the buffer received from the Rtpproxy server. What I want to see is if the message is totally broken, or only some parts of it are malformed. Could you please apply this patch, and paste us the output when the error occurs again? Best regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 12/13/2012 07:01 PM, Flavio Goncalves wrote: I'm having an issue with timeout notification of rtpproxy. Usually sessions are disconnected properly with rtpproxy timeout notification: INFO:do_timeout_notification: notification timeout sent 1715.2112525045 : Success (The dialog hash is presented correctly with period .) However, In some cases (3 to 7 per day in 25000 calls) we got the following message from rtpproxy module. RTP Proxy in this case send the dialog id with a # in the middle. I can't reproduce the problem in the lab. Dec 12 16:42:4 ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy - invalid dialog entry [1727216578#0123634 ] In this case there is a hash in the middle of the dialog identifier (a str2int function generates this error in the rtpproxy module denying the request and throwing the error message. No errors in OpenSIPS log No errors in rtpproxy log (debug enabled) Any ideas? Flavio E. Goncalves ___ Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] rtpproxy timeout notifications
Hi, Flavio! For RTPProxy, do you mean the RTPProxy repository? Which one, latest stable version, trunk? Best regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 01/07/2013 01:18 PM, Flavio Goncalves wrote: Razavn, I'm using OpenSIPS 1.8.2 from svn and rtpproxy from the opensips repository. Flavio E. Goncalves 2013/1/7 Răzvan Crainea raz...@opensips.org mailto:raz...@opensips.org Hi, Flavio! Can you tell me what versions of OpenSIPS and RTPProxy are you using? Best regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 01/03/2013 12:31 PM, Flavio Goncalves wrote: Hi Razvan, I'm checking if the problem is not related to re-invites and calling rtpproxy set with an invalid value. Anyway, the logs are below. Dec 20 14:59:28 /sbin/opensips[6978]: ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy [1] Dec 20 14:59:28 /sbin/opensips[6978]: INFO:rtpproxy:timeout_listener_process: RTPProxy buffer: [255] 3066.74196691#0121744.870880408#0121968.1268777973#012949 tel:1268777973%23012949.1984340712#01274 tel:1984340712%2301274.448511458#012860.999375735#0121893.793805873#0122451.492975819#0123796.1055294097#012485.853875076#0122426.1713554641#0122310.1069754522#012555.117610#0123225.315833604#0122922.440360056#012976.780586176#0122899.1149567571#0121 Flavio E. Goncalves CEO - V.Office 2012/12/18 Răzvan Crainea raz...@opensips.org mailto:raz...@opensips.org Hi, Flavio! I've attached a patch for the rtpproxy module, that for every error, it prints the buffer received from the Rtpproxy server. What I want to see is if the message is totally broken, or only some parts of it are malformed. Could you please apply this patch, and paste us the output when the error occurs again? Best regards, Razvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 12/13/2012 07:01 PM, Flavio Goncalves wrote: I'm having an issue with timeout notification of rtpproxy. Usually sessions are disconnected properly with rtpproxy timeout notification: INFO:do_timeout_notification: notification timeout sent 1715.2112525045 : Success (The dialog hash is presented correctly with period .) However, In some cases (3 to 7 per day in 25000 calls) we got the following message from rtpproxy module. RTP Proxy in this case send the dialog id with a # in the middle. I can't reproduce the problem in the lab. Dec 12 16:42:4 ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy - invalid dialog entry [1727216578#0123634 tel:%5B1727216578%230123634] In this case there is a hash in the middle of the dialog identifier (a str2int function generates this error in the rtpproxy module denying the request and throwing the error message. No errors in OpenSIPS log No errors in rtpproxy log (debug enabled) Any ideas? Flavio E. Goncalves ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org mailto:Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] rtpproxy timeout notifications
Hi Razvan, I'm checking if the problem is not related to re-invites and calling rtpproxy set with an invalid value. Anyway, the logs are below. Dec 20 14:59:28 /sbin/opensips[6978]: ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy [1] Dec 20 14:59:28 /sbin/opensips[6978]: INFO:rtpproxy:timeout_listener_process: RTPProxy buffer: [255] 3066.74196691#0121744.870880408#0121968.1268777973#012949.1984340712#01274.448511458#012860.999375735#0121893.793805873#0122451.492975819#0123796.1055294097#012485.853875076#0122426.1713554641#0122310.1069754522#012555.117610#0123225.315833604#0122922.440360056#012976.780586176#0122899.1149567571#0121 Flavio E. Goncalves CEO - V.Office 2012/12/18 Răzvan Crainea raz...@opensips.org Hi, Flavio! I've attached a patch for the rtpproxy module, that for every error, it prints the buffer received from the Rtpproxy server. What I want to see is if the message is totally broken, or only some parts of it are malformed. Could you please apply this patch, and paste us the output when the error occurs again? Best regards, Razvan Crainea OpenSIPS Core Developerhttp://www.opensips-solutions.com On 12/13/2012 07:01 PM, Flavio Goncalves wrote: I'm having an issue with timeout notification of rtpproxy. Usually sessions are disconnected properly with rtpproxy timeout notification: INFO:do_timeout_notification: notification timeout sent 1715.2112525045 : Success (The dialog hash is presented correctly with period .) However, In some cases (3 to 7 per day in 25000 calls) we got the following message from rtpproxy module. RTP Proxy in this case send the dialog id with a # in the middle. I can't reproduce the problem in the lab. Dec 12 16:42:4 ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy - invalid dialog entry [1727216578#0123634] In this case there is a hash in the middle of the dialog identifier (a str2int function generates this error in the rtpproxy module denying the request and throwing the error message. No errors in OpenSIPS log No errors in rtpproxy log (debug enabled) Any ideas? Flavio E. Goncalves ___ Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] rtpproxy timeout notifications
Hi, Flavio!
I've attached a patch for the rtpproxy module, that for every error, it
prints the buffer received from the Rtpproxy server. What I want to see
is if the message is totally broken, or only some parts of it are
malformed. Could you please apply this patch, and paste us the output
when the error occurs again?
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 12/13/2012 07:01 PM, Flavio Goncalves wrote:
I'm having an issue with timeout notification of rtpproxy.
Usually sessions are disconnected properly with rtpproxy timeout
notification:
INFO:do_timeout_notification: notification timeout sent
1715.2112525045 : Success (The dialog hash is presented correctly with
period .)
However, In some cases (3 to 7 per day in 25000 calls) we got the
following message from rtpproxy module. RTP Proxy in this case send
the dialog id with a # in the middle. I can't reproduce the problem in
the lab.
Dec 12 16:42:4 ERROR:rtpproxy:timeout_listener_process: Wrong formated
message received from rtpproxy - invalid dialog entry [1727216578#0123634]
In this case there is a hash in the middle of the dialog identifier (a
str2int function generates this error in the rtpproxy module denying
the request and throwing the error message.
No errors in OpenSIPS log
No errors in rtpproxy log (debug enabled)
Any ideas?
Flavio E. Goncalves
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Index: modules/rtpproxy/timeout_process.c
===
--- modules/rtpproxy/timeout_process.c (revision 9424)
+++ modules/rtpproxy/timeout_process.c (working copy)
@@ -327,6 +327,7 @@
if(p == NULL) {
LM_ERR(Wrong formated message received from rtpproxy [%.*s]\n,
dlg_id.len, dlg_id.s);
+ LM_INFO(RTPProxy buffer: [%d] %.*s\n, len, len, buffer);
break;
}
id.s = dlg_id.s;
@@ -334,6 +335,7 @@
if(str2int(id, h_entry) 0) {
LM_ERR(Wrong formated message received from rtpproxy - invalid
dialog entry [%.*s]\n, id.len, id.s);
+ LM_INFO(RTPProxy buffer: [%d] %.*s\n, len, len, buffer);
break;
}
id.s = ++p;
@@ -344,6 +346,7 @@
if(str2int(id, h_id) 0) {
LM_ERR(Wrong formated message received from rtpproxy - invalid
dialog id [%.*s]\n, id.len, id.s);
+ LM_INFO(RTPProxy buffer: [%d] %.*s\n, len, len, buffer);
break;
}
LM_DBG(hentry = %u, h_id = %u\n, h_entry, h_id);
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] rtpproxy timeout notifications
I'm having an issue with timeout notification of rtpproxy. Usually sessions are disconnected properly with rtpproxy timeout notification: INFO:do_timeout_notification: notification timeout sent 1715.2112525045 : Success (The dialog hash is presented correctly with period .) However, In some cases (3 to 7 per day in 25000 calls) we got the following message from rtpproxy module. RTP Proxy in this case send the dialog id with a # in the middle. I can't reproduce the problem in the lab. Dec 12 16:42:4 ERROR:rtpproxy:timeout_listener_process: Wrong formated message received from rtpproxy - invalid dialog entry [1727216578#0123634] In this case there is a hash in the middle of the dialog identifier (a str2int function generates this error in the rtpproxy module denying the request and throwing the error message. No errors in OpenSIPS log No errors in rtpproxy log (debug enabled) Any ideas? Flavio E. Goncalves ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTPProxy timeout notifications
Hello Razvan! Now it's working, thank you. But I want to tell you that -W key in rtpproxy and Opensips doesn't work. When -W timer expires rtpproxy notifies about it Opensips but last one cannot drop call because there is no information about callee and caller contacts in dialog. -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Razvan Crainea Sent: Monday, January 03, 2011 7:25 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] RTPProxy timeout notifications Hello Denis, The problem you are dealing with is that you are using a TCP socket to receive timeout notifications from RTPProxy. When a timeout notification is received through TCP, the nathelper module searches for the sender in the rtpproxies specified in rtpproxy_sock module parameter. It cannot find it in that list, so it ignores the notification. Because you are using a UNIX socket to communicate with RTPProxy, then you should also use a UNIX socket to receive timeout notifications from it. Note that I posted today a bug fix for this behavior. You can watch the thread at: http://lists.rtpproxy.org/pipermail/devel/2011-January/thread.html Regards, Razvan On 12/28/2010 04:52 PM, Denis Putyato wrote: Hello Bogdan RTP Proxy is working but timeout notification does not. There is error /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu Sent: Tuesday, December 28, 2010 5:49 PM To: OpenSIPS users mailling list; Razvan Crainea Subject: Re: [OpenSIPS-Users] RTPProxy timeout notifications Hi Denis, Denis Putyato wrote: Hello Bogdan! 1) There is no patch in official release of Opensips 1.6.4 which I can download from web site (source tar). There is a patch only in SVN version of Opensips 1.6.4 Hmm..that's a packaging bug :(I will take care of this. 2) The patch which I can use from SVN version I can apply only to rtpproxy from git. If I use rtpproxy from web site I cannot apply patch to it (there are some errors during process of patch). I will ask Razvan (the author of this work) to see if the patch can be ported to official rtpproxy release too (not as coding, but as functionality). In my case I use rtpproxy from git with applied patch from SVN version of Opensips (when I start rtpproxy I use such command /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60. As I understand without patch -W doesn`t work) and official release of Openspis 1.6.4 which I downloaded from web site (not from SVN) And this works ? Regards, Bogdan -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu Sent: Tuesday, December 28, 2010 1:31 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] RTPProxy timeout notifications Hi Denis, Silly question, but have you applied to the official RTPproxy the patches that comes with the nathelper module ? Regards, Bogdan Denis Putyato wrote: Hello! During tests of new feature in rtpproxy I received such problem: “Dec 27 11:42:42 opensips /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring” And log for rtpproxy “Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session 6fe1-00bf-8e08-8065-0002a405c...@172.31.255.250, tag 6f008e65a4;1 requested, type strong Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session on a port 64922 created, tag 6f008e65a4;1 Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: setting timeout handler Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: pre-filling caller's address with 3.3.3.3:23066 Dec 28 07:43:37 opensips /usr/local/opensips1.6.4/sbin/opensips[28196]: ERROR:nathelper:force_rtp_proxy: Unable to parse body Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: pre-filling callee's address with 2.2.2.2:18408 Dec 28 07:43:39 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:process_rtp: session timeout Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTP stats: 1449 in from callee, 421 in from caller, 1870 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTCP stats: 7 in from callee, 2 in from caller, 9 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: session on ports 64922/4 is cleaned up Dec 28 07:44
Re: [OpenSIPS-Users] RTPProxy timeout notifications
Hello Denis, The problem you are dealing with is that you are using a TCP socket to receive timeout notifications from RTPProxy. When a timeout notification is received through TCP, the nathelper module searches for the sender in the rtpproxies specified in rtpproxy_sock module parameter. It cannot find it in that list, so it ignores the notification. Because you are using a UNIX socket to communicate with RTPProxy, then you should also use a UNIX socket to receive timeout notifications from it. Note that I posted today a bug fix for this behavior. You can watch the thread at: http://lists.rtpproxy.org/pipermail/devel/2011-January/thread.html Regards, Razvan On 12/28/2010 04:52 PM, Denis Putyato wrote: Hello Bogdan RTP Proxy is working but timeout notification does not. There is error /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu Sent: Tuesday, December 28, 2010 5:49 PM To: OpenSIPS users mailling list; Razvan Crainea Subject: Re: [OpenSIPS-Users] RTPProxy timeout notifications Hi Denis, Denis Putyato wrote: Hello Bogdan! 1) There is no patch in official release of Opensips 1.6.4 which I can download from web site (source tar). There is a patch only in SVN version of Opensips 1.6.4 Hmm..that's a packaging bug :(I will take care of this. 2) The patch which I can use from SVN version I can apply only to rtpproxy from git. If I use rtpproxy from web site I cannot apply patch to it (there are some errors during process of patch). I will ask Razvan (the author of this work) to see if the patch can be ported to official rtpproxy release too (not as coding, but as functionality). In my case I use rtpproxy from git with applied patch from SVN version of Opensips (when I start rtpproxy I use such command /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60. As I understand without patch -W doesn`t work) and official release of Openspis 1.6.4 which I downloaded from web site (not from SVN) And this works ? Regards, Bogdan -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu Sent: Tuesday, December 28, 2010 1:31 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] RTPProxy timeout notifications Hi Denis, Silly question, but have you applied to the official RTPproxy the patches that comes with the nathelper module ? Regards, Bogdan Denis Putyato wrote: Hello! During tests of new feature in rtpproxy I received such problem: “Dec 27 11:42:42 opensips /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring” And log for rtpproxy “Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session 6fe1-00bf-8e08-8065-0002a405c...@172.31.255.250, tag 6f008e65a4;1 requested, type strong Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session on a port 64922 created, tag 6f008e65a4;1 Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: setting timeout handler Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: pre-filling caller's address with 3.3.3.3:23066 Dec 28 07:43:37 opensips /usr/local/opensips1.6.4/sbin/opensips[28196]: ERROR:nathelper:force_rtp_proxy: Unable to parse body Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: pre-filling callee's address with 2.2.2.2:18408 Dec 28 07:43:39 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:process_rtp: session timeout Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTP stats: 1449 in from callee, 421 in from caller, 1870 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTCP stats: 7 in from callee, 2 in from caller, 9 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: session on ports 64922/4 is cleaned up Dec 28 07:44:07 opensips rtpproxy[28223]: ERR:do_timeout_notification: failed to send timeout notification: Broken pipe” Opensips 1.6.4 Latest rtpproxy from git with patch for RTPProxy timeout notifications The start string of rtpproxy: /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60 Opensips.cfg: … … modparam(nathelper, rtpproxy_sock, /var/run/rtpproxy.sock) modparam(nathelper, rtpp_notify_socket, tcp:1.1.1.1:2) … … rtpproxy_offer(con); …. rtpproxy_answer(con); … During voice session everything fine (bidirectional voice flow). Then I emulate
Re: [OpenSIPS-Users] RTPProxy timeout notifications
Hi Denis, Silly question, but have you applied to the official RTPproxy the patches that comes with the nathelper module ? Regards, Bogdan Denis Putyato wrote: Hello! During tests of new feature in rtpproxy I received such problem: “Dec 27 11:42:42 opensips /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring” And log for rtpproxy “Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session 6fe1-00bf-8e08-8065-0002a405c...@172.31.255.250, tag 6f008e65a4;1 requested, type strong Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session on a port 64922 created, tag 6f008e65a4;1 Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: setting timeout handler Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: pre-filling caller's address with 3.3.3.3:23066 Dec 28 07:43:37 opensips /usr/local/opensips1.6.4/sbin/opensips[28196]: ERROR:nathelper:force_rtp_proxy: Unable to parse body Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: pre-filling callee's address with 2.2.2.2:18408 Dec 28 07:43:39 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:process_rtp: session timeout Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTP stats: 1449 in from callee, 421 in from caller, 1870 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTCP stats: 7 in from callee, 2 in from caller, 9 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: session on ports 64922/4 is cleaned up Dec 28 07:44:07 opensips rtpproxy[28223]: ERR:do_timeout_notification: failed to send timeout notification: Broken pipe” Opensips 1.6.4 Latest rtpproxy from git with patch for RTPProxy timeout notifications The start string of rtpproxy: /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60 Opensips.cfg: … … modparam(nathelper, rtpproxy_sock, /var/run/rtpproxy.sock) modparam(nathelper, rtpp_notify_socket, tcp:1.1.1.1:2) … … rtpproxy_offer(con); …. rtpproxy_answer(con); … During voice session everything fine (bidirectional voice flow). Then I emulate LAN problem and after 20 s expire I received such message. Call is still active. Thank you for any help. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Event - expo, conf, social, bootcamp 2 - 4 February 2011, ITExpo, Miami, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTPProxy timeout notifications
Hello Bogdan! 1) There is no patch in official release of Opensips 1.6.4 which I can download from web site (source tar). There is a patch only in SVN version of Opensips 1.6.4 2) The patch which I can use from SVN version I can apply only to rtpproxy from git. If I use rtpproxy from web site I cannot apply patch to it (there are some errors during process of patch). In my case I use rtpproxy from git with applied patch from SVN version of Opensips (when I start rtpproxy I use such command /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60. As I understand without patch -W doesn`t work) and official release of Openspis 1.6.4 which I downloaded from web site (not from SVN) -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu Sent: Tuesday, December 28, 2010 1:31 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] RTPProxy timeout notifications Hi Denis, Silly question, but have you applied to the official RTPproxy the patches that comes with the nathelper module ? Regards, Bogdan Denis Putyato wrote: Hello! During tests of new feature in rtpproxy I received such problem: “Dec 27 11:42:42 opensips /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring” And log for rtpproxy “Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session 6fe1-00bf-8e08-8065-0002a405c...@172.31.255.250, tag 6f008e65a4;1 requested, type strong Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session on a port 64922 created, tag 6f008e65a4;1 Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: setting timeout handler Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: pre-filling caller's address with 3.3.3.3:23066 Dec 28 07:43:37 opensips /usr/local/opensips1.6.4/sbin/opensips[28196]: ERROR:nathelper:force_rtp_proxy: Unable to parse body Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: pre-filling callee's address with 2.2.2.2:18408 Dec 28 07:43:39 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:process_rtp: session timeout Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTP stats: 1449 in from callee, 421 in from caller, 1870 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTCP stats: 7 in from callee, 2 in from caller, 9 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: session on ports 64922/4 is cleaned up Dec 28 07:44:07 opensips rtpproxy[28223]: ERR:do_timeout_notification: failed to send timeout notification: Broken pipe” Opensips 1.6.4 Latest rtpproxy from git with patch for RTPProxy timeout notifications The start string of rtpproxy: /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60 Opensips.cfg: … … modparam(nathelper, rtpproxy_sock, /var/run/rtpproxy.sock) modparam(nathelper, rtpp_notify_socket, tcp:1.1.1.1:2) … … rtpproxy_offer(con); …. rtpproxy_answer(con); … During voice session everything fine (bidirectional voice flow). Then I emulate LAN problem and after 20 s expire I received such message. Call is still active. Thank you for any help. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Event - expo, conf, social, bootcamp 2 - 4 February 2011, ITExpo, Miami, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTPProxy timeout notifications
Hi Denis, Denis Putyato wrote: Hello Bogdan! 1) There is no patch in official release of Opensips 1.6.4 which I can download from web site (source tar). There is a patch only in SVN version of Opensips 1.6.4 Hmm..that's a packaging bug :(I will take care of this. 2) The patch which I can use from SVN version I can apply only to rtpproxy from git. If I use rtpproxy from web site I cannot apply patch to it (there are some errors during process of patch). I will ask Razvan (the author of this work) to see if the patch can be ported to official rtpproxy release too (not as coding, but as functionality). In my case I use rtpproxy from git with applied patch from SVN version of Opensips (when I start rtpproxy I use such command /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60. As I understand without patch -W doesn`t work) and official release of Openspis 1.6.4 which I downloaded from web site (not from SVN) And this works ? Regards, Bogdan -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu Sent: Tuesday, December 28, 2010 1:31 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] RTPProxy timeout notifications Hi Denis, Silly question, but have you applied to the official RTPproxy the patches that comes with the nathelper module ? Regards, Bogdan Denis Putyato wrote: Hello! During tests of new feature in rtpproxy I received such problem: “Dec 27 11:42:42 opensips /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring” And log for rtpproxy “Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session 6fe1-00bf-8e08-8065-0002a405c...@172.31.255.250, tag 6f008e65a4;1 requested, type strong Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session on a port 64922 created, tag 6f008e65a4;1 Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: setting timeout handler Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: pre-filling caller's address with 3.3.3.3:23066 Dec 28 07:43:37 opensips /usr/local/opensips1.6.4/sbin/opensips[28196]: ERROR:nathelper:force_rtp_proxy: Unable to parse body Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: pre-filling callee's address with 2.2.2.2:18408 Dec 28 07:43:39 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:process_rtp: session timeout Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTP stats: 1449 in from callee, 421 in from caller, 1870 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTCP stats: 7 in from callee, 2 in from caller, 9 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: session on ports 64922/4 is cleaned up Dec 28 07:44:07 opensips rtpproxy[28223]: ERR:do_timeout_notification: failed to send timeout notification: Broken pipe” Opensips 1.6.4 Latest rtpproxy from git with patch for RTPProxy timeout notifications The start string of rtpproxy: /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60 Opensips.cfg: … … modparam(nathelper, rtpproxy_sock, /var/run/rtpproxy.sock) modparam(nathelper, rtpp_notify_socket, tcp:1.1.1.1:2) … … rtpproxy_offer(con); …. rtpproxy_answer(con); … During voice session everything fine (bidirectional voice flow). Then I emulate LAN problem and after 20 s expire I received such message. Call is still active. Thank you for any help. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Event - expo, conf, social, bootcamp 2 - 4 February 2011, ITExpo, Miami, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] RTPProxy timeout notifications
Hello Bogdan RTP Proxy is working but timeout notification does not. There is error /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu Sent: Tuesday, December 28, 2010 5:49 PM To: OpenSIPS users mailling list; Razvan Crainea Subject: Re: [OpenSIPS-Users] RTPProxy timeout notifications Hi Denis, Denis Putyato wrote: Hello Bogdan! 1) There is no patch in official release of Opensips 1.6.4 which I can download from web site (source tar). There is a patch only in SVN version of Opensips 1.6.4 Hmm..that's a packaging bug :(I will take care of this. 2) The patch which I can use from SVN version I can apply only to rtpproxy from git. If I use rtpproxy from web site I cannot apply patch to it (there are some errors during process of patch). I will ask Razvan (the author of this work) to see if the patch can be ported to official rtpproxy release too (not as coding, but as functionality). In my case I use rtpproxy from git with applied patch from SVN version of Opensips (when I start rtpproxy I use such command /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60. As I understand without patch -W doesn`t work) and official release of Openspis 1.6.4 which I downloaded from web site (not from SVN) And this works ? Regards, Bogdan -Original Message- From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu Sent: Tuesday, December 28, 2010 1:31 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] RTPProxy timeout notifications Hi Denis, Silly question, but have you applied to the official RTPproxy the patches that comes with the nathelper module ? Regards, Bogdan Denis Putyato wrote: Hello! During tests of new feature in rtpproxy I received such problem: “Dec 27 11:42:42 opensips /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring” And log for rtpproxy “Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session 6fe1-00bf-8e08-8065-0002a405c...@172.31.255.250, tag 6f008e65a4;1 requested, type strong Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session on a port 64922 created, tag 6f008e65a4;1 Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: setting timeout handler Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: pre-filling caller's address with 3.3.3.3:23066 Dec 28 07:43:37 opensips /usr/local/opensips1.6.4/sbin/opensips[28196]: ERROR:nathelper:force_rtp_proxy: Unable to parse body Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: pre-filling callee's address with 2.2.2.2:18408 Dec 28 07:43:39 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:process_rtp: session timeout Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTP stats: 1449 in from callee, 421 in from caller, 1870 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTCP stats: 7 in from callee, 2 in from caller, 9 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: session on ports 64922/4 is cleaned up Dec 28 07:44:07 opensips rtpproxy[28223]: ERR:do_timeout_notification: failed to send timeout notification: Broken pipe” Opensips 1.6.4 Latest rtpproxy from git with patch for RTPProxy timeout notifications The start string of rtpproxy: /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60 Opensips.cfg: … … modparam(nathelper, rtpproxy_sock, /var/run/rtpproxy.sock) modparam(nathelper, rtpp_notify_socket, tcp:1.1.1.1:2) … … rtpproxy_offer(con); …. rtpproxy_answer(con); … During voice session everything fine (bidirectional voice flow). Then I emulate LAN problem and after 20 s expire I received such message. Call is still active. Thank you for any help. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Bogdan-Andrei Iancu OpenSIPS Event - expo, conf, social, bootcamp 2 - 4 February 2011, ITExpo, Miami, USA www.voice-system.ro ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin
[OpenSIPS-Users] RTPProxy timeout notifications
Hello! During tests of new feature in rtpproxy I received such problem: “Dec 27 11:42:42 opensips /usr/local/opensips1.6.4/sbin/opensips[26496]: DBG:nathelper:timeout_listener_process: unknown rtpproxy – ignoring” And log for rtpproxy “Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session 6fe1-00bf-8e08-8065-0002a405c...@172.31.255.250, tag 6f008e65a4;1 requested, type strong Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: new session on a port 64922 created, tag 6f008e65a4;1 Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: setting timeout handler Dec 28 07:43:37 opensips rtpproxy[28223]: INFO:handle_command: pre-filling caller's address with 3.3.3.3:23066 Dec 28 07:43:37 opensips /usr/local/opensips1.6.4/sbin/opensips[28196]: ERROR:nathelper:force_rtp_proxy: Unable to parse body Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:43:38 opensips rtpproxy[28223]: INFO:handle_command: pre-filling callee's address with 2.2.2.2:18408 Dec 28 07:43:39 opensips rtpproxy[28223]: INFO:handle_command: lookup on ports 64922/4, session timer restarted Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:process_rtp: session timeout Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTP stats: 1449 in from callee, 421 in from caller, 1870 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: RTCP stats: 7 in from callee, 2 in from caller, 9 relayed, 0 dropped Dec 28 07:44:07 opensips rtpproxy[28223]: INFO:remove_session: session on ports 64922/4 is cleaned up Dec 28 07:44:07 opensips rtpproxy[28223]: ERR:do_timeout_notification: failed to send timeout notification: Broken pipe” Opensips 1.6.4 Latest rtpproxy from git with patch for RTPProxy timeout notifications The start string of rtpproxy: /usr/local/rtpproxy/bin/rtpproxy -l 1.1.1.1 -s unix:/var/run/rtpproxy.sock -F -i -n tcp:1.1.1.1:2 -T 20 -W 60 Opensips.cfg: … … modparam(nathelper, rtpproxy_sock, /var/run/rtpproxy.sock) modparam(nathelper, rtpp_notify_socket, tcp:1.1.1.1:2) … … rtpproxy_offer(con); …. rtpproxy_answer(con); … During voice session everything fine (bidirectional voice flow). Then I emulate LAN problem and after 20 s expire I received such message. Call is still active. Thank you for any help. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
