Hello, you need a transcoder in the middle. OpenSER does only signaling, so it is not able to transcode. Asterisk, for example, does. Cheers, Daniel On 02/15/07 10:57, tusker keg wrote: _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

Hi, rtpproxy and mediaproxy do media-relaying and OpenSER does SIP routing. Both have nothing to do with codecs, which are negotiated end-to-end. So yes, OpenSER and rtpproxy/mediaproxy do support G729 in a sense that they allow UACs to communicate with G729. If you want to transcode between codecs (e.g. G711 <-> G729), you need - as Daniel already said - a transcoder like Asterisk. Andreas raviprakash sunkara wrote: This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of confidence. Thank you for your cooperation. _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

Hi, we would be very interested! :-) I think it's a great idea but...what do you mean with "very simple" ?! Stefano Atle Samuelsen ha scritto: _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

Hello Atle, On 02/15/07 13:04, Atle Samuelsen wrote: could you upload the patches to the tracker? It sounds very useful in some scenarios. We will have a look and make sure that the patch for nathelper gets very well integrated in existing code. Here is the link to the tracker: http://sourceforge.net/tracker/?atid=743022&group_id=139143&func=br…

Thanks, Daniel >So alittle status on the code: >The code was written for SER trunc about half a year ago. The nathelper >part is written by me, who does'nt do C very much, so that part is very >flacky. but as a proof of concept it works. >There is a need of a function as decribed above that can check what >codecs the UA supports. > > >- Atle > >* Stefano Capitanio &lt;s.capitanio(a)caspur.it&gt; [070215 11:52]: > >>Hi, >> >>we would be very interested! :-) >>I think it's a great idea but...what do you mean with "very simple" ?! >> >>Stefano >> >>Atle Samuelsen ha scritto: >> >>>Hi Guys, >>> >>>Just qurious.. How intrested are you guys in a very simple transcoder, >>>wich is based on rtpproxy ? - Atle >>> >>>* Andreas Granig &lt;andreas.granig(a)inode.info&gt; [070215 11:09]: >>> >>>>Hi, >>>> >>>>rtpproxy and mediaproxy do media-relaying and OpenSER does SIP routing. Both have nothing to do with codecs, which are >>>>negotiated end-to-end. So yes, OpenSER and rtpproxy/mediaproxy do support G729 in a sense that they allow UACs to >>>>communicate with G729. If you want to transcode between codecs (e.g. G711 <-> G729), you need - as Daniel already said - >>>>a transcoder like Asterisk. >>>> >>>>Andreas >>>> >>>>raviprakash sunkara wrote: >>>> >>>>>Hello Daniel , >>>>>I'm Also Having the Same doubt on g729 Codec, >>>>>I'm using RTPproxy with Nathelper , >>>>>OpenSER and RTP proxy does media signaling when the Call is Established, >>>>>My main question is >>>>>Is RTP proxy support the G729, with OpenSER, >>>>>With out using the Transcoder ( Asterisk ) How can OpenSER signals the G729 Codec. >>>>>On 2/15/07, *Daniel-Constantin Mierla * &lt;daniel(a)voice-system.ro <mailto:daniel@voice-system.ro>> wrote: >>>>> Hello, >>>>> you need a transcoder in the middle. OpenSER does only signaling, so it >>>>> is not able to transcode. Asterisk, for example, does. >>>>> Cheers, >>>>> Daniel >>>>> On 02/15/07 10:57, tusker keg wrote: >>>>> > Howdy >>>>> > >>>>> > I have a situation I hope you guys will help me out with >>>>> > >>>>> > I am receiving call from a VOIP peer (SIP Call) and the peer can >>>>> > only send them as G711. >>>>> > I need to redirect to call to another voip peer over the wan and due >>>>> > to bandwidth considerations I need to translate the codec to g729. >>>>> > >>>>> > Any ideas on how to do this, >>>>> > >>>>> > Sample config file will be help >>>>> > >>>>> > Regards >>>>> > >>>>> > ./Tusker >>>>> > >>>>> > _______________________________________________ >>>>> > Users mailing list >>>>> > Users(a)openser.org <mailto:Users@openser.org> >>>>> > http://openser.org/cgi-bin/mailman/listinfo/users >>>>> > >>>>> _______________________________________________ >>>>> Users mailing list >>>>> Users(a)openser.org <mailto:Users@openser.org> >>>>> http://openser.org/cgi-bin/mailman/listinfo/users >>>>>-- >>>>>Thanks and Regards >>>>>Ravi Prakash Sunkara &gt;&gt;&gt;&gt;&gt;ravi.sunkara(a)hyperion-tech.com <mailto:ravi.sunkara@hyperion-tech.com> >>>>>M:+91 9985077535 >>>>>www.hyperion-tech.com <http://www.hyperion-tech.com> >>>>>Client and Parent company :- www.august-networks.com <http://www.august-networks.com> >>>>>------------------------------------------------------------------------ >>>>>_______________________________________________ >>>>>Users mailing list &gt;&gt;&gt;&gt;&gt;Users(a)openser.org >>>>>http://openser.org/cgi-bin/mailman/listinfo/users >>>>> >>>>This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice >>>>of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not >>>>copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of >>>>confidence. Thank you for your cooperation. >>>> >>>>_______________________________________________ >>>>Users mailing list &gt;&gt;&gt;&gt;Users(a)openser.org >>>>http://openser.org/cgi-bin/mailman/listinfo/users >>>> >>>_______________________________________________ >>>Users mailing list &gt;&gt;&gt;Users(a)openser.org >>>http://openser.org/cgi-bin/mailman/listinfo/users >>> >>_______________________________________________ >>Users mailing list &gt;&gt;Users(a)openser.org >>http://openser.org/cgi-bin/mailman/listinfo/users >> > >_______________________________________________ >Users mailing list &gt;Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users >

I think the best is to get integrated in the trunk. We hate maintaining patches, because are very time consuming. If it is a very useful feature or complies with standards it is no reason to keep it as patch. We go for configuration options to enable/disable features. It is more easier to have it in the trunk as it gets updated all the time when something internally changes.

I am not the maintainer of nathelper module in ser, so I cannot get it there, but with openser is easier, and here we can help. If you want to release the code for public, we are willing to adopt it in openser.