[reSIProcate] Not using Dum but Stack Apis for the Cancel Message

[Asheesh Joshi]

You must use DUM for managing dialogues. Infact that is the only way you can
manage dialogues in resiprocate.

-Asheesh 

-----Original Message-----
From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of sumit
Sent: Thursday, September 29, 2005 4:26 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] Not using Dum but Stack Apis for the Cancel Message

Hi All

I am facing a problem when I am trying to create the Cancel message by using
the stack APIs rather than DUM .
Problem: Always I am receiving a 481 message with the error being INFO |
20050928-154930.502 |  |  | RESIP:TRANSACTION | 0 | 1079976608 |
TransactionState.cxx:304 | No matching INVITE for incoming (from TU) CANCEL
to uac

I frame the Cancel Message in the following manner

                   DeprecatedDialog dlog(mContact);
                    auto_ptr<SipMessage>
cancel(dlog.makeCancel(*backupInvite) );
                    mStack.send(*cancel);

where backupInvite is obtained from
             
                   backupInvite=Helper::makeInvite( target, mContact,
mContact);
                   backupInvite->setContents(sdp);

Has anyone come across a similar problem?The problem on analysing I feel is
the sip transaction id not matching.

Regards
Sumit


_______________________________________________
resiprocate-devel mailing list
resiprocate-devel at list.sipfoundry.org
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel