Hi,
>From my point of view, Sesion Timers are only useful for call statefull
>proxies because this ones have resources reserved for all running sessions. If
>a session ends due to an end-point crash, the proxy will keep reserving
>resources forever. That is why a timer is required.
In the case of a transaction statefull proxy, the resources are reserved only
for the duration of a transaction, which is usually around 30 seconds.
Moreover, how can a transaction statefull proxy be aware of Session Timers if
they usually have a higher value than the duration of a common transaction?
Hope it helps,
Samuel.
Unclassified.
>>> Jaya krishna <[EMAIL PROTECTED]> 08/04/05 07:04AM >>>
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
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors