Re: [reSIProcate] help about RFC4916
On Wed, Sep 28, 2011 at 9:03 AM, kiand@xxxxxxxxx <kiand@xxxxxxxxx> wrote:
> Hi,
>
>
>
> I need to add support for RFC 4916 specification in Resiprocate, in order to
> change Connected Identity in a Third Party Call Control scenario.
>
> I would like to know which could be the best place to add the “from-change”
> option tag in “Supported” header (maybe the MasterProfile?) and where to
> handle incoming/outgoing UPDATE messages for Connected Identity.
>
>
>
> Regards,
>
> Andrea
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
Hi,
I think the current standard way of adding a new supported option tag
is using MasterProfile::addSupportedOptionTag, like:
// Note: you can pass a custom char* to Token
mpMasterProfile->addSupportedOptionTag(Token(Symbols::Replaces));
Regarding the UPDATE, the default InviteSessionHandler does have
support for handling the UPDATE method (and InviteSession also
supports sending outgoing UPDATEs), but it looks like it is mainly
tied to offer/answer negotiation. I do not think it is possible to
send an UPDATE with no SDP offer using InviteSession and I don't think
it is possible to be notified (using InviteSessionHandler) of incoming
UPDATE requests that do not contain an SDP offer...
Those APIs would need to be added to (probably) InviteSession and
InviteSessionHandler. I also think they would be useful :)
Regards,
Francis