This is a quick note to the list in case there is someone interested in taking on this clean up effort. The SDP handling in SdpBody is a bit of a mess that I am to blame for at least originally and it has not gotten better. There are two major problems with SdpBody. It does not keep media sets (m lines) separate or distinct and it mixes body contruction/parsing with codec negotiation.
I think SdpBody should be thrown out and redone. SdpBody should only contain utilities to parse an SDP body and to construct one. SDP contains structured data that should be pulled out into structures or classes and then the codec negotiation operations should be done on the structured data and then for the SDP offer a new SdpBody should be constructed from the negotiation calculations and operations. There are now a set of utilities to contain the SDP data in the recently created sipXSdpLib. SdpBody should parse and create an Sdp with SdpMediaLines. Then we can create an SDP negotiator class or methods to operate on the Sdp class. I would be happy to discuss the requirement and solution details with volunteer(s) for this effort. Cheers, Dan SIPez LLC SIP VoIP, IM and Presence Consulting http://www.sipez.com tel: +1 (617) 273-4000 _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
