Looks like my ladder flow is distorted ..resending.
GW CVP
F1 <--------------REFER
F2 ----------->202 Accepted
F3 -----------> Notify (Trying)
F4 <------------200 Ok (Notify)
F5 ----------->Notify(Ringing)
F6 <------------200 Ok(Notify)
Approx. after 58 seconds.
F7 <-----------Subscribe (Event: REFER)
F8 -------------> 503 Service Unavailable.
After this multiple update messages every 2 hour and then BYE after
11 hours.
F9 <---------------BYE
F10 -------------->200 OK. (BYE)
Thanks,Ashish Rawat
On Monday, 20 April 2015 6:00 PM, ashish rawat
<ashish_rawat1...@yahoo.co.in> wrote:
Hello All,
I am troubleshooting an issue here where the following flow of events is
leading to hung call licenses in CVP. Can anyone point out anything out of
specs here? Do you think stpes F7 and F8 constitute a valid transaction to
extend REFER subscription and convey final status of the REFEREED Event? As per
my reading of RFC 3515 that seems to be valid.
GW
CVP F1 <--------------REFERF2
----------->202AcceptedF3
----------->Notify (Trying)F4
<------------200Ok (Notify)F5
----------->Notify(Ringing)F6
<------------200Ok(Notify) Approx. after 58 seconds
REFER subscription is extended as expected coz of expires timer of 60 seconds
in the initial REFER.
F7 <-----------Subscribe(Event:
REFER)F8 -------------> 503 Service Unavailable.
Afterthis multiple update messages every 2 hour and then BYE after 11 hours.F9
<---------------BYEF10
-------------->200 OK. (BYE)
Thanks,Ashish Rawat
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
