Re: [reSIProcate] FW: SdpContents::findFirstMatchingCodecs

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

Title: Message

Yes – good find.  I’ll commit a fix for this.

 

Thanks!

 

Scott

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Robert Mansfield
Sent: Friday, March 16, 2007 12:01 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] FW: SdpContents::findFirstMatchingCodecs

 

 

-----Original Message-----
From: Robert Mansfield
Sent: 16 March 2007 15:54
To: 'resiprocate-devel@xxxxxxxxxxxxxxxxxxx'
Subject: SdpContents::findFirstMatchingCodecs

All,

 

Not sure if it's a problem with the stack or my implementation. I upgraded to release 1.1 of resip and the codec operator "==" has changed to incorporate the encoding parameters.

 

As a result and attribute of a=rtpmap:0 PCMU/8000 is not matched to a=rtpmap:0 PCMU/8000/1. I think this should be deemed equivalent.

 

Is it valid to check if either lhs.mEncodingParameters or rhs.mEncodingParameters is empty, and the other equal to Data("1"), the codec matches?

 

Regards,

 

Rob.

 

 

 

============================

Robert Mansfield

Senior Software Engineer

Redwood Technologies Limited

The Redwood Building, Broad Lane, Bracknell, Berkshire, RG12 9GU, U.K.

Registered in England No. 2817863

T +[44] (0)1344 304 344

F +[44] (0)1344 304 345

E rjm@xxxxxxxxxxxxxxx  

W www.redwoodtech.com

=====

 

Email Disclaimer

 

The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the limitations of Redwood Technologies Limited's standard terms and conditions of contract.