hi ,
>>>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 doesnot maintain any callstate.
If this is the case how a transactionstateful proxy handles the session timer
when it does/doesnt record-route or it is only applicable to call stateful
proxies ?
need clarification in this regard .....
Any solutions/comments appreciated
Thanks in advance
--JayaKrishna
Brett Tate <[EMAIL PROTECTED]> wrote:
> Section 8.3 of RFC 4028 says that proxy
> may free any resources associated with the
> call on session expiry.
>
> I want more clarification on what we should
> do on a session expiry when proxy is behaving
> as transactionstateful.
>
> The behavior in RFC 4028 tells more of proxy
> that is behaving as callstateful.
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.
---------------------------------
Too much spam in your inbox? Yahoo! Mail gives you the best spam protection
for FREE!
http://in.mail.yahoo.com
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
