From k at isvyaz.ru Sat Mar 14 08:33:58 2009 From: k at isvyaz.ru (=?windows-1251?B?yu7t8fLg7fLo7Q==?=) Date: Sat, 14 Mar 2009 20:33:58 +0500 Subject: [RTPproxy Users] converting RTPProxy 1.2 .rtp pcap files to wav (or mp3) - solution Message-ID: <182894674.20090314203358@isvyaz.ru> Hello! I tried to find a solution to convert rtp files to wav for version rtpproxy < 1.2. I'm read scary stories about the creation rtpproxy-module fpr sems :) Fortunately, since version 1.2 came the parameter -P allows you to record rtp-traffic in a pcap. Here is my decision to convert this to wav, using rtpbreak (http://xenion.reactive-search.com/?page_id=7), sox and lame (for mp3). Tested with debian etch. First, the conversion of each channel in the raw: rtpbreak -W -r longfilename_of_rtpproxy_record.a.rtp rtpbreak -W -r longfilename_of_rtpproxy_record.a.rtp Then mix in the format wavpcm stereo: sox --combine merge -r 8k -A rtp.0.0.raw -r 8k -A rtp.1.0.raw -t wavpcm -s out.wav and, finally, converting to mp3: lame out.wav out.mp3 Thank you :-) Shpinev Konstantin, http://callibry.net From sobomax at sippysoft.com Sat Mar 14 09:26:02 2009 From: sobomax at sippysoft.com (Maxim Sobolev) Date: Sat, 14 Mar 2009 09:26:02 -0700 Subject: [RTPproxy Users] converting RTPProxy 1.2 .rtp pcap files to wav (or mp3) - solution In-Reply-To: <182894674.20090314203358@isvyaz.ru> References: <182894674.20090314203358@isvyaz.ru> Message-ID: <49BBDA9A.4040808@sippysoft.com> Konstantin, Thank you very much for sharing this with us. I have added this recipe to the FAQ. ?????????? wrote: > Hello! > > I tried to find a solution to convert rtp files to wav for version > rtpproxy < 1.2. I'm read scary stories about the creation > rtpproxy-module fpr sems :) > > Fortunately, since version 1.2 came the parameter -P allows you to record rtp-traffic in a pcap. > Here is my decision to convert this to wav, using rtpbreak (http://xenion.reactive-search.com/?page_id=7), sox and lame (for mp3). Tested with debian etch. > > First, the conversion of each channel in the raw: > > rtpbreak -W -r longfilename_of_rtpproxy_record.a.rtp > rtpbreak -W -r longfilename_of_rtpproxy_record.a.rtp > > Then mix in the format wavpcm stereo: > > sox --combine merge -r 8k -A rtp.0.0.raw -r 8k -A rtp.1.0.raw -t wavpcm -s out.wav > > and, finally, converting to mp3: > > lame out.wav out.mp3 > > Thank you :-) Regards, -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts T/F: +1-646-651-1110 Web: http://www.sippysoft.com MSN: sales at sippysoft.com Skype: SippySoft From R.Voermans at global-e.nl Wed Mar 25 13:49:10 2009 From: R.Voermans at global-e.nl (Ronald Voermans) Date: Wed, 25 Mar 2009 21:49:10 +0100 Subject: [RTPproxy Users] Problem with next_gw and rtpproxy Message-ID: Dear Kamailio users, I have a problem with using rtpproxy and the next_gw function: when the first gateway is for whatever reason unavailable, the next gateway is selected. I use rtpproxy for all calls, so when the next gateway is selected, the force_rtp_proxy function is called again. I use this function with the following parameters: faroc. Next to that, rtpproxy is running in bridged mode, so the function also has the additional parameters I or E. When the first gateway is available, everything goes ok. However when the next gateway is selected, there are some errors in the SDP-message: v=0. o=- 104514515 104514515 IN IP4 10.254.254.110.254.254.1. s=-. c=IN IP4 10.254.254.110.254.254.1. t=0 0. m=audio 5397453976 RTP/AVP 18 0 8 100 101. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:100 NSE/8000. a=fmtp:100 192-193. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=ptime:20. a=sendrecv. a=nortpproxy:yes. a=nortpproxy:yes. As you can see, the 'o' and 'c' line are wrong. It is not an option to disable the function force_rtp_proxy again, because the other gateway can be on the external interface instead of the internal (so there is a change in I or E when calling force_rtp_proxy again). I tried to use the function unforce_rtp_proxy in my failure_route, but this also didn't change anything. Thanks for your time and help! Regards, Ronald Voermans From osas at voipembedded.com Wed Mar 25 14:13:49 2009 From: osas at voipembedded.com (Ovidiu Sas) Date: Wed, 25 Mar 2009 17:13:49 -0400 Subject: [RTPproxy Users] Problem with next_gw and rtpproxy In-Reply-To: References: Message-ID: <6f497e130903251413hf0a8442s253eaa36aafba4b@mail.gmail.com> This is a kamailio question. You need to perform force_rtp_proxy in a branch route, so it will not affect the original message. Next time when you call next_gateway you will need to force_rtp_proxy in a branch route again and everything should work properly. Regards, Ovidiu Sas On Wed, Mar 25, 2009 at 4:49 PM, Ronald Voermans wrote: > Dear Kamailio users, > > I have a problem with using rtpproxy and the next_gw function: when the first gateway is for whatever reason unavailable, the next gateway is selected. I use rtpproxy for all calls, so when the next gateway is selected, the force_rtp_proxy function is called again. > > I use this function with the following parameters: faroc. Next to that, rtpproxy is running in bridged mode, so the function also has the additional parameters I or E. > > When the first gateway is available, everything goes ok. However when the next gateway is selected, there are some errors in the SDP-message: > > > v=0. > o=- 104514515 104514515 IN IP4 10.254.254.110.254.254.1. > s=-. > c=IN IP4 10.254.254.110.254.254.1. > t=0 0. > m=audio 5397453976 RTP/AVP 18 0 8 100 101. > a=rtpmap:18 G729/8000. > a=fmtp:18 annexb=no > a=rtpmap:0 PCMU/8000. > a=rtpmap:8 PCMA/8000. > a=rtpmap:100 NSE/8000. > a=fmtp:100 192-193. > a=rtpmap:101 telephone-event/8000. > a=fmtp:101 0-15. > a=ptime:20. > a=sendrecv. > a=nortpproxy:yes. > a=nortpproxy:yes. > > > As you can see, the 'o' and 'c' line are wrong. It is not an option to disable the function force_rtp_proxy again, because the other gateway can be on the external interface instead of the internal (so there is a change in I or E when calling force_rtp_proxy again). I tried to use the function unforce_rtp_proxy in my failure_route, but this also didn't change anything. > > Thanks for your time and help! > > Regards, > Ronald Voermans > _______________________________________________ > Users mailing list > Users at rtpproxy.org > http://lists.rtpproxy.org/mailman/listinfo/users > From R.Voermans at global-e.nl Thu Mar 26 01:02:28 2009 From: R.Voermans at global-e.nl (Ronald Voermans) Date: Thu, 26 Mar 2009 09:02:28 +0100 Subject: [RTPproxy Users] Problem with next_gw and rtpproxy In-Reply-To: <6f497e130903251413hf0a8442s253eaa36aafba4b@mail.gmail.com> References: <6f497e130903251413hf0a8442s253eaa36aafba4b@mail.gmail.com> Message-ID: <1EBF014F0B26AF42B43FBC1BB5974F76B122EB83@gi-glogil-ex1.gilze.global-e.nl> Ovidiu, Thank you for your answer, and sorry if this is not the right list. One more (and last) question about it: Will an 'append_branch()' in the failure_route suffice for this to work? Here's my failure_route: failure_route[1] { route(21); if(!next_gw()) { xlog("L_ERR", "Failed to select next PSTN gateway - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); route(10); exit; } # Set Flag 30 to prevent adding multiple CLI-headers setflag(30); t_on_failure("1"); route(12); } route[12] calls the force_rtp_proxy function. If i add append_branch() before route(12) in the failure_route, will this work? Thanks again, Ronald -----Oorspronkelijk bericht----- Van: users-bounces at rtpproxy.org [mailto:users-bounces at rtpproxy.org] Namens Ovidiu Sas Verzonden: woensdag 25 maart 2009 22:14 Aan: RTPproxy Users Onderwerp: Re: [RTPproxy Users] Problem with next_gw and rtpproxy This is a kamailio question. You need to perform force_rtp_proxy in a branch route, so it will not affect the original message. Next time when you call next_gateway you will need to force_rtp_proxy in a branch route again and everything should work properly. Regards, Ovidiu Sas On Wed, Mar 25, 2009 at 4:49 PM, Ronald Voermans wrote: > Dear Kamailio users, > > I have a problem with using rtpproxy and the next_gw function: when the first gateway is for whatever reason unavailable, the next gateway is selected. I use rtpproxy for all calls, so when the next gateway is selected, the force_rtp_proxy function is called again. > > I use this function with the following parameters: faroc. Next to that, rtpproxy is running in bridged mode, so the function also has the additional parameters I or E. > > When the first gateway is available, everything goes ok. However when the next gateway is selected, there are some errors in the SDP-message: > > > v=0. > o=- 104514515 104514515 IN IP4 10.254.254.110.254.254.1. > s=-. > c=IN IP4 10.254.254.110.254.254.1. > t=0 0. > m=audio 5397453976 RTP/AVP 18 0 8 100 101. > a=rtpmap:18 G729/8000. > a=fmtp:18 annexb=no > a=rtpmap:0 PCMU/8000. > a=rtpmap:8 PCMA/8000. > a=rtpmap:100 NSE/8000. > a=fmtp:100 192-193. > a=rtpmap:101 telephone-event/8000. > a=fmtp:101 0-15. > a=ptime:20. > a=sendrecv. > a=nortpproxy:yes. > a=nortpproxy:yes. > > > As you can see, the 'o' and 'c' line are wrong. It is not an option to disable the function force_rtp_proxy again, because the other gateway can be on the external interface instead of the internal (so there is a change in I or E when calling force_rtp_proxy again). I tried to use the function unforce_rtp_proxy in my failure_route, but this also didn't change anything. > > Thanks for your time and help! > > Regards, > Ronald Voermans > _______________________________________________ > Users mailing list > Users at rtpproxy.org > http://lists.rtpproxy.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users at rtpproxy.org http://lists.rtpproxy.org/mailman/listinfo/users From osas at voipembedded.com Thu Mar 26 02:27:36 2009 From: osas at voipembedded.com (Ovidiu Sas) Date: Thu, 26 Mar 2009 05:27:36 -0400 Subject: [RTPproxy Users] Problem with next_gw and rtpproxy In-Reply-To: <1EBF014F0B26AF42B43FBC1BB5974F76B122EB83@gi-glogil-ex1.gilze.global-e.nl> References: <6f497e130903251413hf0a8442s253eaa36aafba4b@mail.gmail.com> <1EBF014F0B26AF42B43FBC1BB5974F76B122EB83@gi-glogil-ex1.gilze.global-e.nl> Message-ID: <6f497e130903260227t280210d1g957822806fb4e0a5@mail.gmail.com> You need to use ranch_route instead of route: http://www.kamailio.net/dokuwiki/doku.php/core-cookbook:1.5.x#branch_route And you need to call branch_route after next_gw. With lcr you don't need to call append_branch. Regards, Ovidiu Sas On Thu, Mar 26, 2009 at 4:02 AM, Ronald Voermans wrote: > Ovidiu, > > Thank you for your answer, and sorry if this is not the right list. > > One more (and last) question about it: > Will an 'append_branch()' in the failure_route suffice for this to work? > > Here's my failure_route: > > failure_route[1] > { > ? ? ? ?route(21); > ? ? ? ?if(!next_gw()) > ? ? ? ?{ > ? ? ? ? ? ? ? ?xlog("L_ERR", "Failed to select next PSTN gateway - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); > ? ? ? ? ? ? ? ?route(10); > ? ? ? ? ? ? ? ?exit; > ? ? ? ?} > ? ? ? ?# Set Flag 30 to prevent adding multiple CLI-headers > ? ? ? ?setflag(30); > ? ? ? ?t_on_failure("1"); > ? ? ? ?route(12); > } > > route[12] calls the force_rtp_proxy function. > > If i add append_branch() before route(12) in the failure_route, will this work? > > Thanks again, > > Ronald > -----Oorspronkelijk bericht----- > Van: users-bounces at rtpproxy.org [mailto:users-bounces at rtpproxy.org] Namens Ovidiu Sas > Verzonden: woensdag 25 maart 2009 22:14 > Aan: RTPproxy Users > Onderwerp: Re: [RTPproxy Users] Problem with next_gw and rtpproxy > > This is a kamailio question. ?You need to perform force_rtp_proxy in a > branch route, so it will not affect the original message. ?Next time > when you call next_gateway you will need to force_rtp_proxy in a > branch route again and everything should work properly. > > Regards, > Ovidiu Sas > > On Wed, Mar 25, 2009 at 4:49 PM, Ronald Voermans wrote: >> Dear Kamailio users, >> >> I have a problem with using rtpproxy and the next_gw function: when the first gateway is for whatever reason unavailable, the next gateway is selected. I use rtpproxy for all calls, so when the next gateway is selected, the force_rtp_proxy function is called again. >> >> I use this function with the following parameters: faroc. Next to that, rtpproxy is running in bridged mode, so the function also has the additional parameters I or E. >> >> When the first gateway is available, everything goes ok. However when the next gateway is selected, there are some errors in the SDP-message: >> >> >> v=0. >> o=- 104514515 104514515 IN IP4 10.254.254.110.254.254.1. >> s=-. >> c=IN IP4 10.254.254.110.254.254.1. >> t=0 0. >> m=audio 5397453976 RTP/AVP 18 0 8 100 101. >> a=rtpmap:18 G729/8000. >> a=fmtp:18 annexb=no >> a=rtpmap:0 PCMU/8000. >> a=rtpmap:8 PCMA/8000. >> a=rtpmap:100 NSE/8000. >> a=fmtp:100 192-193. >> a=rtpmap:101 telephone-event/8000. >> a=fmtp:101 0-15. >> a=ptime:20. >> a=sendrecv. >> a=nortpproxy:yes. >> a=nortpproxy:yes. >> >> >> As you can see, the 'o' and 'c' line are wrong. It is not an option to disable the function force_rtp_proxy again, because the other gateway can be on the external interface instead of the internal (so there is a change in I or E when calling force_rtp_proxy again). I tried to use the function unforce_rtp_proxy in my failure_route, but this also didn't change anything. >> >> Thanks for your time and help! >> >> Regards, >> Ronald Voermans >> _______________________________________________ >> Users mailing list >> Users at rtpproxy.org >> http://lists.rtpproxy.org/mailman/listinfo/users >> > _______________________________________________ > Users mailing list > Users at rtpproxy.org > http://lists.rtpproxy.org/mailman/listinfo/users > > _______________________________________________ > Users mailing list > Users at rtpproxy.org > http://lists.rtpproxy.org/mailman/listinfo/users > From ndlgroup1 at gmail.com Tue Mar 31 03:41:59 2009 From: ndlgroup1 at gmail.com (oso che bol) Date: Tue, 31 Mar 2009 17:41:59 +0700 Subject: [RTPproxy Users] RTPProxy always hang after some running hours In-Reply-To: <7d0336790903310328i287b27c8l8c3131a0153dc739@mail.gmail.com> References: <7d0336790903310328i287b27c8l8c3131a0153dc739@mail.gmail.com> Message-ID: <7d0336790903310341l22926679m6caa090d2b6d23a7@mail.gmail.com> FYI: On Tue, Mar 31, 2009 at 5:28 PM, oso che bol wrote: > Dear All, > After some running hours, I checked back if RTPPROXY is run or not, It's > always NO run. > > My command to run rtpproxy is: > rtpproxy -s udp:174.132.X.Y:7890 -f -u root -l 174.132.X.Y & > Opensips is running on another box. > My questions: > - How can we trace the reasons why rtpproxy disconnect? > - How we could trace the information fo Call go through RTPProxy? > - Do rtpproxy allow anonymous user or not root user of opensips? > Thanks and Regards, > -LN > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.rtpproxy.org/pipermail/users/attachments/20090331/1db2577f/attachment.html From sobomax at sippysoft.com Tue Mar 31 04:17:42 2009 From: sobomax at sippysoft.com (Maxim Sobolev) Date: Tue, 31 Mar 2009 04:17:42 -0700 Subject: [RTPproxy Users] RTPProxy always hang after some running hours In-Reply-To: <7d0336790903310341l22926679m6caa090d2b6d23a7@mail.gmail.com> References: <7d0336790903310328i287b27c8l8c3131a0153dc739@mail.gmail.com> <7d0336790903310341l22926679m6caa090d2b6d23a7@mail.gmail.com> Message-ID: <49D1FBD6.4010205@sippysoft.com> oso che bol wrote: > FYI: > > On Tue, Mar 31, 2009 at 5:28 PM, oso che bol > wrote: > > Dear All, > > After some running hours, I checked back if RTPPROXY is run or not, > It's always NO run. > > My command to run rtpproxy is: > rtpproxy -s udp:174.132.X.Y:7890 -f -u root -l 174.132.X.Y & > Opensips is running on another box. > My questions: > - How can we trace the reasons why rtpproxy disconnect? > - How we could trace the information fo Call go through RTPProxy? > - Do rtpproxy allow anonymous user or not root user of opensips? 1. Which version of the RTPproxy is that? 2. You can try to debug by starting it in foreground (flag -f) and redirecting stdout/stderr to the file, i.e.: rtpproxy -f ...your options... > /tmp/rtpproxy.log 2>&1 Regards, -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts T/F: +1-646-651-1110 Web: http://www.sippysoft.com MSN: sales at sippysoft.com Skype: SippySoft From ndlgroup1 at gmail.com Tue Mar 31 04:33:36 2009 From: ndlgroup1 at gmail.com (oso che bol) Date: Tue, 31 Mar 2009 18:33:36 +0700 Subject: [RTPproxy Users] RTPProxy always hang after some running hours In-Reply-To: <49D1FBD6.4010205@sippysoft.com> References: <7d0336790903310328i287b27c8l8c3131a0153dc739@mail.gmail.com> <7d0336790903310341l22926679m6caa090d2b6d23a7@mail.gmail.com> <49D1FBD6.4010205@sippysoft.com> Message-ID: <7d0336790903310433k7337d8bdh7ba03913f8b5044f@mail.gmail.com> Dear MakSym, RTPPROXY ver 1.2 Do you mean, we will run start rtpproxy by command: rtpproxy -f -s udp:174.132.X.Y:7890 -u root -l 174.132.X.Y > /tmp/rtpproxy.log 2>&1 & Thanks, -LN On Tue, Mar 31, 2009 at 6:17 PM, Maxim Sobolev wrote: > oso che bol wrote: > >> FYI: >> >> On Tue, Mar 31, 2009 at 5:28 PM, oso che bol > ndlgroup1 at gmail.com>> wrote: >> >> Dear All, >> >> After some running hours, I checked back if RTPPROXY is run or not, >> It's always NO run. >> >> My command to run rtpproxy is: >> rtpproxy -s udp:174.132.X.Y:7890 -f -u root -l 174.132.X.Y & >> Opensips is running on another box. >> My questions: >> - How can we trace the reasons why rtpproxy disconnect? >> - How we could trace the information fo Call go through RTPProxy? >> - Do rtpproxy allow anonymous user or not root user of opensips? >> > > 1. Which version of the RTPproxy is that? > > 2. You can try to debug by starting it in foreground (flag -f) and > redirecting stdout/stderr to the file, i.e.: > > rtpproxy -f ...your options... > /tmp/rtpproxy.log 2>&1 > > Regards, > -- > Maksym Sobolyev > Sippy Software, Inc. > Internet Telephony (VoIP) Experts > T/F: +1-646-651-1110 > Web: http://www.sippysoft.com > MSN: sales at sippysoft.com > Skype: SippySoft > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.rtpproxy.org/pipermail/users/attachments/20090331/a3103c64/attachment.html From ndlgroup1 at gmail.com Tue Mar 31 05:33:39 2009 From: ndlgroup1 at gmail.com (oso che bol) Date: Tue, 31 Mar 2009 19:33:39 +0700 Subject: [RTPproxy Users] RTPProxy always hang after some running hours In-Reply-To: <7d0336790903310433k7337d8bdh7ba03913f8b5044f@mail.gmail.com> References: <7d0336790903310328i287b27c8l8c3131a0153dc739@mail.gmail.com> <7d0336790903310341l22926679m6caa090d2b6d23a7@mail.gmail.com> <49D1FBD6.4010205@sippysoft.com> <7d0336790903310433k7337d8bdh7ba03913f8b5044f@mail.gmail.com> Message-ID: <7d0336790903310533h3875ad29l5672a5056dfea2ce@mail.gmail.com> Dear Maxim, btw, i run rtpproxy on centos 5.2 and compile from source. Thanks, -LN On Tue, Mar 31, 2009 at 6:33 PM, oso che bol wrote: > Dear MakSym, > > RTPPROXY ver 1.2 > > Do you mean, we will run start rtpproxy by command: > > rtpproxy -f -s udp:174.132.X.Y:7890 -u root -l 174.132.X.Y > > /tmp/rtpproxy.log 2>&1 & > > Thanks, > > -LN > > On Tue, Mar 31, 2009 at 6:17 PM, Maxim Sobolev wrote: > >> oso che bol wrote: >> >>> FYI: >>> >>> On Tue, Mar 31, 2009 at 5:28 PM, oso che bol >> ndlgroup1 at gmail.com>> wrote: >>> >>> Dear All, >>> >>> After some running hours, I checked back if RTPPROXY is run or not, >>> It's always NO run. >>> >>> My command to run rtpproxy is: >>> rtpproxy -s udp:174.132.X.Y:7890 -f -u root -l 174.132.X.Y & >>> Opensips is running on another box. >>> My questions: >>> - How can we trace the reasons why rtpproxy disconnect? >>> - How we could trace the information fo Call go through RTPProxy? >>> - Do rtpproxy allow anonymous user or not root user of opensips? >>> >> >> 1. Which version of the RTPproxy is that? >> >> 2. You can try to debug by starting it in foreground (flag -f) and >> redirecting stdout/stderr to the file, i.e.: >> >> rtpproxy -f ...your options... > /tmp/rtpproxy.log 2>&1 >> >> Regards, >> -- >> Maksym Sobolyev >> Sippy Software, Inc. >> Internet Telephony (VoIP) Experts >> T/F: +1-646-651-1110 >> Web: http://www.sippysoft.com >> MSN: sales at sippysoft.com >> Skype: SippySoft >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.rtpproxy.org/pipermail/users/attachments/20090331/0cc544a2/attachment.html From ndlgroup1 at gmail.com Tue Mar 31 03:28:50 2009 From: ndlgroup1 at gmail.com (oso che bol) Date: Tue, 31 Mar 2009 10:28:50 -0000 Subject: [RTPproxy Users] RTPProxy always hang after some running hours Message-ID: <7d0336790903310328i287b27c8l8c3131a0153dc739@mail.gmail.com> Dear All, After some running hours, I checked back if RTPPROXY is run or not, It's always NO run. My command to run rtpproxy is: rtpproxy -s udp:174.132.X.Y:7890 -f -u root -l 174.132.X.Y & Opensips is running on another box. My questions: - How can we trace the reasons why rtpproxy disconnect? - How we could trace the information fo Call go through RTPProxy? - Do rtpproxy allow anonymous user or not root user of opensips? Thanks and Regards, -LN -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.rtpproxy.org/pipermail/users/attachments/20090331/c1a7343d/attachment.html