[reSIProcate] InviteSession and SdpContents (CSTA)

[Steve Robichaud]

What will the big differences be in DumV2 vs Dum ?

Steve

-----Original Message-----
From: Scott Godin
Sent: 08/12/2005 8:04 AM

> Just an update of offline conversations...  There is a consensus that 
> this is something good to support - but since this changes the 
> interfaces so much - the current plan is to implement this capability 
> into DumV2.
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* resiprocate-devel-bounces at list.sipfoundry.org 
> [mailto:resiprocate-devel-bounces at list.sipfoundry.org] *On Behalf Of 
> *Alan Stokes
> *Sent:* Wednesday, December 07, 2005 4:32 AM
> *To:* resiprocate-devel at list.sipfoundry.org
> *Subject:* Re: [reSIProcate] InviteSession and SdpContents (CSTA)
>
>  
>
>     From: "Scott Godin" <slgodin at icescape.com
>     <mailto:slgodin at icescape.com>>
>
>     A while back - it was suggested that we use an abstracted
>     SdpContents class in the InviteSession code to allow app
>     developers to plug in their own SdpContents classes.
>
>      
>     I've been looking into creating a CSTA server with resip/dum -
>     this requires that non-SDP contents are used in the offer/answer.
>      What do people think about changing the InviteSession API's and
>     callbacks to pass around Contents instead of SdpContents?  And
>     maybe a profile setting to indicate if the InviteSession should
>     walk through multipart bodies or not to find SdpContents?
>
> I would be strongly in favour - but then I'm trying to do pretty much 
> the same thing. It seems to me that Contents would work just as well 
> as SdpContents in most places.
>
> What I've done today is a nasty hack - I've derived my custom Contents 
> from SdpContents, but completely overridden the inherited 
> implementation. This means it can be passed in and out of all the 
> relevant resiprocate functions, but when it is serialised / 
> deserialised to the wire it looks the way I want it. This works, but 
> I'm not particularly proud of it. It does demonstrate that lots of 
> things work fine without meaningful SdpContents data. (I'm only using 
> a very simple offer/answer scenario, which probably helps a lot.)
>
> - Alan
>
>------------------------------------------------------------------------
>
>_______________________________________________
>resiprocate-devel mailing list
>resiprocate-devel at list.sipfoundry.org
>https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20051208/4191c50a/attachment.htm>