< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] adding non-sdp contents to outbound invites using DumFeature


Thanks.  Another issue with manipulating the contents of the message is that
authentication headers compute hashes based on the contents in some
instances.  The auth headers are added in DUM before the features and before
the decorators.  Using a messagedecorator seems like it would be difficult
to recomputed the auth header since the message is decorated at the stack
level.  

My current hack is to:

* make findDialogSet public in DialogUsageManager
* add a getClientAuthManager to DUM
* add a getAppDialogSet to DialogSet
* use all of the above in my feature to get the dialogset and my specific
contents, add the contents to the outbound invite and finally re-add auth
headers using the ClientAuthManager.

Maybe adding non-sdp should be added to makeInviteSession?  If that's not a
good idea then doing something like passing the userprofile into the
feature's process( ) function, or similar, would be helpful.  Thoughts?

Thanks,

-justin

-----Original Message-----
From: slgodin@xxxxxxxxx [mailto:slgodin@xxxxxxxxx] On Behalf Of Scott Godin
Sent: Wednesday, August 26, 2009 9:27 PM
To: Justin Matthews
Cc: resiprocate-devel
Subject: Re: [reSIProcate] adding non-sdp contents to outbound invites using
DumFeature

You could use a unique user profile per call.  You would set a unique
outbound decorator per call that would encapsulate the specific body
you want to the add to the messages.  This avoids the mapping
complications.

Scott

On Wed, Aug 26, 2009 at 2:46 PM, Justin Matthews<jmatthewsr@xxxxxxxxx>
wrote:
> Hi,
>
>
>
> I am trying to add contents in addition to the normal SDP of an outbound
> invite.  Using a DUM feature I want to store the contents pointer of this
> new content in the appdialogset so that the contents can be looked up and
> applied to the message.  The problem is trying to get the appdialogset
from
> the sipmessage sent to the feature without having an actual Dialog. Is
there
> a better way to do this?  I?ve looked at messagedecorator and possibly
> storing a map of dialogsetid?s to contents in my feature object, but the
> messagedecorator has the rollback mechanism which seems like wasted cycles
> and increased complexity and the map requires removing the entries once
the
> outbound call is finished.
>
>
>
> Any ideas?
>
>
>
> Thanks,
>
>
>
> -justin
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>