[reSIProcate] Re-INVITE using DUM

[Nash Tsai [TelTel]]

Hi Scott,

 

Thanks for answering, and I went ahead to modify DUM's code, now, I can send
re-INVITE with modified SipMessage ok now but I got a new problem, when I am
already in a dialog session with a party (A), and if I send new INVITE to
another party (B) then send re-INVITE to existing party and before 200 come
back from B if I tried to send another re-INVITE to A, the DUM will
automatically send a BYE when trying to send re-INVITE, please see diagram
below, and my question is "is this appropriate behavior of DUM", any reason
that it send a BYE automatically?  

 

 

 

ME                                       A
B

|                                            |         INVITE

|---------------------------------------------------------------------------
--------->|

|              (re)INVITE               |

|------------------------------------------->|

|                   200                    |

|<------------------------------------------ |

|                                                    180
|

|<--------------------------------------------------------------------------
----------|

|          (re)INVITE (Intended)   |

|------------------------------------------>|

|     (But) BYE (send by DUM)

|-------------------------------------------|

 


Thanks,

Nash Tsai

 

 

  _____  

From: Scott Godin [mailto:slgodin at icescape.com] 
Sent: Tuesday, September 13, 2005 8:49 PM
To: nash at teltel.com; resiprocate-devel at list.sipfoundry.org
Subject: RE: [reSIProcate] Re-INVITE using DUM

 

There currently is no easy way to do what you want without customizing the
dum code.  There is a setOutgoingMessageInterceptor on the DUM in SVN head,
that could be used for this.

 

As far as AppDialogSets, check out:
http://warsaw.sjc.purplecomm.com/wiki/index.php?title=DUM_Associating_Applic
ation_Data_with_DialogSets_and_Dialogs

 

Basically you pass an AppDialogSet in so that you can associate application
data to the new InviteSession.

 

Scott

 

  _____  

From: Nash Tsai [TelTel] [mailto:nash.teltel at gmail.com] 
Sent: Monday, September 12, 2005 11:56 PM
To: Scott Godin; resiprocate-devel at list.sipfoundry.org
Subject: RE: [reSIProcate] Re-INVITE using DUM

 

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/20050914/ba125013/attachment.htm>