[reSIProcate] Re-INVITE using DUM

[Nash Tsai [TelTel]]

Hi,

 

I happened to be need to modify SipMessage that is needed to be sent, with
InviteSession::provideOffer I cannot do it, also with mDum.makeInviteSession
what is the use of passing third param AppDialogSet?

 

Thanks,

Nash Tsai

 

  _____  

From: Scott Godin [mailto:slgodin at icescape.com] 
Sent: Saturday, September 10, 2005 2:34 AM
To: nash at teltel.com; resiprocate-devel at list.sipfoundry.org
Subject: RE: [reSIProcate] Re-INVITE using DUM

 

You should use InviteSession::provideOffer to send a re-invite - this will
ensure dialogid's are all correct.

 

  _____  

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Nash
Tsai [TelTel]
Sent: Friday, September 09, 2005 2:26 PM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] Re-INVITE using DUM

 

Hi,

 

I used following code to send re-INVITE, however, when the INVITE message is
sent with new dialog ID (from tag and and Call-ID) are different to first
INVITE. I assumed mInviteSessionHandle got from void
onConnected(ClientInviteSessionHandle h, const SipMessage& responseMessage)
can be reuse to provide same dialog ID. Can someone answer me where I have
done wrong?

 

SipMessage& invite = mDum.makeInviteSession(toNameAddr,
&mCallInfo.getConferenceSdp(),
mInviteSessionHandle->getAppDialogSet().get());

mDum.send(invite);

 

Thanks

Nash

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