Re: [reSIProcate-users] Implementing an X-Dialog-Id: header with DUM
That sounds a little heavy to me although it should work. Wouldn't it
be easier to just store a dialog id to X dialog id mapping in your
application and have one decorator that looks up the x-dialog-id based
on the dialog-id and inserts it?
Scott
On Mon, Oct 6, 2008 at 11:35 AM, Max Bowsher <maxb@xxxxxxxxxxxxx> wrote:
> Hi,
>
> I'd like to add a header, say X-Dialog-Id, containing a unique ID to all
> the SIP messages involved in a particular dialog, so that the progress
> of a dialog through multiple SIP servers under my control can be correlated.
>
> My environment is free of SIP forking, so (IIUC) there is a one-to-one
> relation between Dialogs and DialogSets.
>
> I am using DUM, and am thinking that a way to manage this would be to
> initiate each outgoing InviteSession with a separate UserProfile, which
> would contain a MessageDecorator configured to add the appropriate
> header with its unique value.
>
> Please could someone confirm/deny whether I'm on the right track with
> this approach, or whether there's a better way,
>
>
> Thanks in advance!
>
> Max.
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>