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: [email protected] [mailto:[email protected]] 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:22222 -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: [email protected] > [mailto:[email protected]] 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 [email protected], 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/46666, 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/46666, 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/46666 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:22222 -T 20 -W 60 >> >> Opensips.cfg: >> >> … >> >> … >> >> modparam("nathelper", "rtpproxy_sock", "/var/run/rtpproxy.sock") >> >> modparam("nathelper", "rtpp_notify_socket", "tcp:1.1.1.1:22222") >> >> … >> >> … >> >> 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 >> [email protected] >> 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 [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
