[reSIProcate] RFC 4661 support

Scott Godin sgodin at sipspectrum.com
Fri Jan 18 13:39:07 CST 2013


For the XML body itself:
You should use OctetContents for a generic XML body.  Take a look in
resip/stack/test for many examples of how to do various things in stack. In
particular testPidf.cxx and substitute Pidf class with OctetContents.   The
dum directory also has a test subdir for DUM specific things.

repro is a proxy, so it's not the right place for this.

DUM is the appropriate place for generating or server SUBSCRIPTION dialogs.
 Check out:http://www.resiprocate.org/DUM_Creating_New_Client_Subscriptions
You can add the message body after calling dum.makeSubscription and before
calling send.

Scott

On Fri, Jan 18, 2013 at 2:27 PM, resip stack <resipdev at gmail.com> wrote:

> Hello Scott,
>
> thanks for the reply.
>
> I am looking towards adding a XML body using the
> resip::stack::contents.cxx file on the outbound SUBSCRIBE request.
>
> Can I directly use the contents.cxx or use DUM to add this content.
>
> Do you have any suggestios on how I can do this using DUM or repro? Any
> example or pointers would be helpful.
>
> Thanks
>
>
> On Fri, Jan 18, 2013 at 5:40 AM, Scott Godin <sgodin at sipspectrum.com>wrote:
>
>> The question is really too general.  Are you looking for client side
>> support or server side?  Either-way - the events sent out for
>> a particular subscription server written using resip/dum are in the control
>> of the application.  All the server/application would need to do is access
>> the filter XML body from the SUBSCRIBE message, then honour the filter
>> requirements when sending out notifications.  For client side, all you
>> really need to do is attach the filter XML body to the outbound SUBSCRIBE
>> request.
>>
>> Scott Godin
>> SIP Spectrum, Inc.
>> www.sipspectrum.com
>>
>> On Thu, Jan 17, 2013 at 11:08 PM, resip stack <resipdev at gmail.com> wrote:
>>
>>> Does anybody have any idea how to support filter mechanisms using resip
>>> stack?
>>>
>>>
>>>
>>> _______________________________________________
>>> resiprocate-devel mailing list
>>> resiprocate-devel at resiprocate.org
>>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20130118/329e940a/attachment.htm>


More information about the resiprocate-devel mailing list