Re: [reSIProcate-users] Timeout for INVITE - 200 OK

[Jorge Bustamante <jbustamante@xxxxxxxxxxxxx>]

Thanks Scott, this was exactly what I was looking for :-).

Regards,

Jorge Bustamante

On Thu, May 22, 2014 at 7:43 AM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:

Yes there is a timeout.  It is essentially 32 seconds.  RFC3261 discussed all the timers involved here.  There is a DUM callback InviteSession handler that notifies you of this.

      /// default behaviour is to send a BYE to end the dialog

      virtual void onAckNotReceived(InviteSessionHandle);

From RFC3261:

   When the "Completed" state is entered, timer H MUST be set to fire in
   64*T1 seconds for all transports.  Timer H determines when the server
   transaction abandons retransmitting the response.  Its value is
   chosen to equal Timer B, the amount of time a client transaction will
   continue to retry sending a request.  If timer G fires, the response
   is passed to the transport layer once more for retransmission, and
   timer G is set to fire in MIN(2*T1, T2) seconds.  From then on, when
   timer G fires, the response is passed to the transport again for
   transmission, and timer G is reset with a value that doubles, unless
   that value exceeds T2, in which case it is reset with the value of
   T2.  This is identical to the retransmit behavior for requests in the
   "Trying" state of the non-INVITE client transaction.  Furthermore,
   while in the "Completed" state, if a request retransmission is
   received, the server SHOULD pass the response to the transport for
   retransmission.

   If an ACK is received while the server transaction is in the
   "Completed" state, the server transaction MUST transition to the
   "Confirmed" state.  As Timer G is ignored in this state, any
   retransmissions of the response will cease.

   If timer H fires while in the "Completed" state, it implies that the
   ACK was never received.  In this case, the server transaction MUST
   transition to the "Terminated" state, and MUST indicate to the TU
   that a transaction failure has occurred.

Scott

On Wed, May 21, 2014 at 4:30 PM, Jorge Bustamante <jbustamante@xxxxxxxxxxxxx> wrote:

Hi,

I was wondering if there is a timeout set within resiprocate for giving up sending 200 OK response for a received INVITE without getting the corresponding ACK... I assume there should be such a timeout, so... do you know how much is it? can (should?) it be changed to some other value? and more importantly, do you know if there is some callback that my application could attach to so it gets notified when this happens?

Regards,
Jorge Bustamante

See why you should attend BroadSoft Connections 2014

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.

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

See why you should attend BroadSoft Connections 2014

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.