[reSIProcate] Finding the correct DialogID to get the InviteSession
Kovar, William (Bill)
bkovar at avaya.com
Wed May 10 10:07:32 CDT 2006
Jason,
I thought about persisting the InviteSessionHandle but I wasn't sure it
pointed to only ONE dialogId.
Is there a 1:1 relationship between InviteSessionHandle -> DialogId?
I need to find the right call in the UA and the right end of the call to
move it correctly.
Bill Kovar
_____
From: jason.fischl at gmail.com [mailto:jason.fischl at gmail.com] On Behalf
Of Jason Fischl
Sent: Wednesday, May 10, 2006 10:52 AM
To: Kovar, William (Bill)
Cc: resiprocate-devel
Subject: Re: [reSIProcate] Finding the correct DialogID to get the
InviteSession
Can you not store the InviteSessionHandle instead? That way you won't
need to call findInviteSession at all. You can just store a map from
refid -> InviteSessionHandle.
On 5/9/06, Kovar, William (Bill) <bkovar at avaya.com> wrote:
I'm building a multiple UA server that receives 3rd party
commands that contain a Uri and refid.
A top layer maps Uri->UA to find the UA. But I can't seem to
figure out what to persist in my UA to find the correct dialog to act
on. My UA may have multiple active sessions.
If I map inside the UA as such:
std::map<unsigned long refid, DialogId> the_map;
and then add to the map
the_map[refid] = ish->getAppDialog()->getDialogID();
and then do:
mdum->findInviteSession(DialogId);
Compiler complains about no appropriate copy constructor on
resip::DialogId.
Should I modify class DialogId to have a copy constructor or is
there another way around this? Or does the DialogUsageManager have some
goodies for me to use to find the correct session inside one UA.
Any alternatives to findInviteSession() ??
Any suggestions??
Bill Kovar
bkovar at avaya.com
_______________________________________________
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/20060510/c3577ead/attachment.htm>
More information about the resiprocate-devel
mailing list