| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
|
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_Application_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: 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: You should use InviteSession::provideOffer
to send a re-invite – this will ensure dialogid’s are all correct. From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Nash Tsai [TelTel] 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 |