[reSIProcate] Finding the correct DialogID to get the InviteSession

[Kovar, William (Bill)]

Assuming that persisting DialogId is not going to work....
 
Is there some way to get the InviteSession if I have a CallId??
 
Bill Kovar
ECAD R&D - IC Advocate and Workflow
Avaya Inc.
(732) 852-2609
bkovar at avaya.com
 

  _____  

From: Scott Godin [mailto:slgodin at icescape.com] 
Sent: Wednesday, May 10, 2006 9:33 AM
To: Kovar, William (Bill); resiprocate-devel
Subject: RE: [reSIProcate] Finding the correct DialogID to get the
InviteSession



Why are passing the DialogId class itself to the findInviteSession call?
Did you mean something like:  mdum->findInviteSession(the_map[refid])?

 

What line is giving you the compiler error?

 

Scott

 

  _____  

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of
Kovar, William (Bill)
Sent: Tuesday, May 09, 2006 6:27 PM
To: resiprocate-devel
Subject: [reSIProcate] Finding the correct DialogID to get the
InviteSession

 

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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060510/d77f496a/attachment.htm>