[OpenSIPS-Users] Route selection based on SDP codecs

[John Quick]

Jeff,

Thanks. No, I was not aware of the new functions in textops. However, it has given me the incentive to
upgrade my test server to version 1.6 so I can try them... and all the other interesting new features.

The upgrade required many changes in my opensips.cfg file - more than I expected:
auth_radius to aaa_radius and auth_aaa
uri_db merged with uri - check_to/from
Mods to Permissions/Group - allow_trusted, is_user_in etc

At last it is now running (with no errors or segfaults). Next, to see if it behaves correctly when
handling a SIP request. No doubt it will be worth the effort - thanks to all those who contribute to
this project.

I'll keep you updated if the codec tests work.

John

> -----Original Message-----
> From: Jeff Pyle [mailto:jpyle at fidelityvoice.com]
> Sent: 02 November 2009 16:22
> To: John.Quick at smartvox.co.uk; OpenSIPS users mailling list
> Subject: Re: [OpenSIPS-Users] Route selection based on SDP codecs
> 
> John,
> 
> That's a great idea...  Regarding (a), have you looked the codec_* functions
> available in 1.6's textops?  The codec_exists() function will return back
> true if a particular codec is available in the existing SDP.  Perhaps this
> functionality could be extended to return an AVP to give the numerical
> priority of the codec as well.
> 
> 
> 
> - Jeff
> 
> 
> 
> 
> On 11/2/09 11:06 AM, "John Quick" <John.Quick at smartvox.co.uk> wrote:
> 
> > If a call is has G.729 set as the preferred codec in the SDP, I want to send
> > it to an Asterisk server
> > with transcoding capabilities. If the preferred codec is G.711 I will send it
> > directly to the media
> > server, gateway or other destination.
> >
> > I can use TEXTOPS to search for entries like this in the SDP:
> > m=audio 10004 RTP/AVP 18
> > a=rtpmap:18 G729/8000
> >
> > (a) Is there a better way than using regular expression searches of the
> > message body?
> > (b) How certain is it that G.729 will always use 18 to identify it in the SDP?
> >
> > Many thanks.
> >
> > John Quick
> > Systems Consultant
> > Smartvox Limited