> > Because a non call-stateful (non dialog-stateful) > > proxy does not record-route, it will not observe > > subsequent requests on the dialog. > > Thus the RFC does not really apply to > > transaction-stateful proxies which are > > not also acting call-stateful > > A transactionstateful proxy can also record-route > if it wants to be in the path of all transaction, > it is not that only callstateful proxy should do. > > As we know that a transactionstateful proxy > maintains only a state for a transaction but > does not maintain any callstate. > > If this is the case how a transactionstateful > proxy handles the session timer when it does/doesn't > record-route or it is only applicable to call > stateful proxies ?
A proxy which does not remain within the dialog path (e.g. record-route) does not observe refreshes. Thus it does not really know when the session expired. A proxy which remains within the dialog MAY release call related resources as mentioned within section 8.3. If the proxy has no call (dialog) resources to release, change, or log upon the release of the session, I have no idea why a proxy would start an expiration timer based upon RFC 4028. _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
