[reSIProcate] Resiprocate asserts due to ClientNonInvite

[Rashmi Keshava Iyengar]

 Hi,

   I'm using resiprocate version 0.9.0-5019 and have an application on top
to register two user agents (on the same target).
   The application acts as both a UAC and a UAS and they all share a single
DUM.

   I get the following assertion failure when one of the UAs tries to make a
call to a remote entity.
   I have verified that both the UAs were successfully registered with the
SIP server prior to the attempt to make a call.

   Though I have provided very little(?) information here I would like to
know what are the possible scenarios in resiprocate when the
   transaction state machine is moved to ClientNonInvite (ref:
TransactionState.hxx - line 175) ?

   What does a ClientNonInvite state stand for? Does it happen when there is
already an
   existing invite for the concerned client?

   TransactionState.cxx:433: void
resip::TransactionState::processClientNonInvite(resip::TransactionMessage*):
Assertion `!isInvite(msg)' failed.

   Any pointers would be helpful!

Thanks,
Rashmi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060208/897b0148/attachment.htm>