reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] cancel Client INVITE does not stop retransmitting

Ok great - I'll commit this change to SVN next week, if there are no objections.  : )

On Thu, Apr 2, 2009 at 5:22 PM, fuliang yuan <fuliangyuan@xxxxxxxxx> wrote:
Scott,

Yes, the problem is fixed with your recommendation.
 TimerB is triggered to terminate the transaction after 16 seconds.

Thanks a lot!

Frank


On Thu, Apr 2, 2009 at 3:21 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
Frank,

Can you try modifying the bolded line of code below from TransactionState::processClientInvite (line 963 on SVN head) and let me know if the re-transmissions stop?

   else if (isTimer(msg))
   {
      /* Handle Transaction Timers , Retransmission Timers which were set and Handle
         Cancellation of Timers for Re-transmissions here */

      TimerMessage* timer = dynamic_cast<TimerMessage*>(msg);
      StackLog (<< "timer fired: " << *timer);
      
      switch (timer->getType())
      {
         case Timer::TimerA:
            if (mState == Calling && !mIsAbandoned)   // <------- MODIFIED CODE HERE
            {
               unsigned long d = timer->getDuration()*2;
               // TimerA is supposed to double with each retransmit RFC3261 17.1.1          

               mController.mTimers.add(Timer::TimerA, mId, d);
               InfoLog (<< "Retransmitting INVITE: " << mMsgToRetransmit->brief());
               sendToWire(mMsgToRetransmit, true);
            }
            delete msg;
            break;

Thanks,
Scott


On Thu, Apr 2, 2009 at 2:42 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
I can't find anything explicit in the RFC for direction on this one.  I suppose though that it makes sense to stop re-transmitting the INVITE.  I'll look into this further.

Scott


On Thu, Apr 2, 2009 at 1:03 PM, fuliang yuan <fuliangyuan@xxxxxxxxx> wrote:
Scott,

CancelClientInvite transaction msg dose not cause resip stack to send out CANCEL msg, but mark the transaction as bing abandoned. It should stop retransmitting INVITE msg.

My question is why resip stack keep retransmitting the canceled INVITE msg.

Thanks

Frank


On Thu, Apr 2, 2009 at 11:09 AM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
A cancel cannot be sent out unless a 100 trying or provisional response has been received.  From section 9.1 of RFC3261:

"If no provisional response has been received, the CANCEL request MUST NOT be sent; rather, the client MUST wait for the arrival of a provisional response before sending the request."

Scott

On Thu, Apr 2, 2009 at 11:48 AM, fuliang yuan <fuliangyuan@xxxxxxxxx> wrote:
Hi,

The resiprocate version is 1.4.1.
The call scenarios is  to send INVITE and send cancelClientInvite to stop retransmiting INVITE after 200 ms. There is no response from server.

But it did not stop it.

Here is the log:
STACK | 20090402-102959.127 | testClient | RESIP:TRANSACTION | 3086866656 | Tran
sactionState.cxx:354 | Found matching transaction for CancelClientInviteTransact
ion: 5b66074fd95b973f -> tid=5b66074fd95b973f [ ClientInvite/Calling unreliable
target=[ V4 0.0.0.0:0 UNKNOWN_TRANSPORT target domain=unspecified mFlowKey=0 ]]^
M
STACK | 20090402-102959.127 | testClient | RESIP:TRANSACTION | 3086866656 | Tran
sactionState.cxx:799 | TransactionState::processClientInvite: CancelClientInvite
Transaction: 5b66074fd95b973f tid=5b66074fd95b973f [ ClientInvite/Calling unreli
able target=[ V4 0.0.0.0:0 UNKNOWN_TRANSPORT target domain=unspecified mFlowKey=
0 ]]^M

STACK | 20090402-102959.728 | testClient | RESIP:TRANSACTION | 3086866656 | Tran
sactionState.cxx:354 | Found matching transaction for Timer: Timer A 500 -> tid=
5b66074fd95b973f [ ClientInvite/Calling unreliable target=[ V4 0.0.0.0:0 UNKNOWN
_TRANSPORT target domain=unspecified mFlowKey=0 ]]^M
STACK | 20090402-102959.728 | testClient | RESIP:TRANSACTION | 3086866656 | Tran
sactionState.cxx:799 | TransactionState::processClientInvite: Timer: Timer A 500
 tid=5b66074fd95b973f [ ClientInvite/Calling unreliable target=[ V4 0.0.0.0:0 UN
KNOWN_TRANSPORT target domain=unspecified mFlowKey=0 ]]^M
STACK | 20090402-102959.728 | testClient | RESIP:TRANSACTION | 3086866656 | Tran
sactionState.cxx:951 | timer fired: TimerMessage TransactionId[5b66074fd95b973f]
  Type[Timer A] duration[500]^M
DEBUG | 20090402-102959.728 | testClient | RESIP:TRANSACTION | 3086866656 | Time
rQueue.cxx:85 | Adding timer: Timer A tid=5b66074fd95b973f ms=1000^M
INFO | 20090402-102959.728 | testClient | RESIP:TRANSACTION | 3086866656 | Trans
actionState.cxx:962 | Retransmitting INVITE: SipReq:  INVITE 5557771234@xxxxxxxx
3.90 tid=5b66074fd95b973f cseq=INVITE contact=yffulf@xxxxxxxxxxxxxxxxxxxxxxxxxxx
m:5080 / 1 from(tu)^M
.............................................................

Regards,

Frank


_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/