"Vivek Gupta" <[EMAIL PROTECTED]> asks:
> For a Non-Invite server transaction, we fire 'timer J' once we have
> received the final response from the TU and on 'timer J' expiry that
> transaction is terminated.
>
> What should be the behavior if one sees no response from the TU? When
> that transaction can be terminated and how?
That's a pretty odd situation: non-INVITE transactions aren't supposed to
wait for user interaction.
For instance, RFC 3265 says
3.1.6.1. Initial SUBSCRIBE Transaction Processing
In no case should a SUBSCRIBE transaction extend for any longer than
the time necessary for automated processing. In particular,
notifiers MUST NOT wait for a user response before returning a final
response to a SUBSCRIBE request.
This requirement is imposed primarily to prevent the non-INVITE
transaction timeout timer F (see [1]) from firing during the
SUBSCRIBE transaction, since interaction with a user would often
exceed 64*T1 seconds.
The remote UA will tear down its client transaction once its Timer F fires,
at least.
frank
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
