On Mon, 2009-12-14 at 17:43 +0530, Dushyant Dhalia wrote:
> 1. Does the proxy server have to start a timer for receipt of NOTIFY?
No, because the proxy need not be stateful (beyond a single
request/response transaction). The UAs are responsible for keeping
track of the subscription state.
Dale
> As suggested by Sumit and Pandurangan, if i maintain SUBSCRIBE dialog for
> the timer sent in Expires header of 200 OK (which at times might be as large
> as one week in IMS) then i would be wasting my resources at PROXY server
> unnecessarily which is my concern.
I agree that it is waste of re
Paul Kyzivat wrote:
Pandurangan R S wrote:
In such a case UAC and NOTIFIER would
destroy then SUBSCRIBE
dialog quietly.
NOTIFIER will destroy the dialog as per RFC3265.
But how/why did the UAC destroy subscribe dialog? I think it has to
wait for
Pandurangan R S wrote:
>> In such a case UAC and NOTIFIER would destroy then SUBSCRIBE
>> dialog quietly.
>
> NOTIFIER will destroy the dialog as per RFC3265.
> But how/why did the UAC destroy subscribe dialog? I think it has to
> wait for the NOTIFY.
>
>> Now my questions are -
>> 1. Does the
Hi Dushyant ,
If Notifier timeouts then how come UAC know about this, UAC must be in
neutral state of subcribe dialog and running some re-subcription
timer.
When that expires uac sends a re-subscribe,now if this RE-SUBSCRIBE
gets 481 then you can remove usage at proxy.
note: still to remove hangi
> In such a case UAC and NOTIFIER would destroy then SUBSCRIBE
> dialog quietly.
NOTIFIER will destroy the dialog as per RFC3265.
But how/why did the UAC destroy subscribe dialog? I think it has to
wait for the NOTIFY.
> Now my questions are -
> 1. Does the proxy server have to start a timer for
The scenario
is as follows -
1. UAC sends SUBSCRIBE.
2. Proxy forwards SUBSCRIBE to the NOTIFIER.
3. NOTIFIER sends 200 (OK) which is received by the UAC.
4. NOTIFIER sends NOTIFY which is lost, retransmissions are also lost.
As per RFCs 3265 and 5057 subscribe usage should be destroyed in su
