Balu,
When reading your posting I couldn't think of a scenario that
creates a subscription within an existing dialog (I have a long way to go
trying to learn this stuff). It occured to me that perhaps this section
has been written with the premise that the SUBSCRIBE created the dialog -
which is why the resubscription in response to the 481 is written to
create a new dialog ?. If you are creating a subscription within an
existing dialog perhaps it is sufficient to just generate a new
request(and not a new dialog ?).
- Wayne.
Balu said:
> RFC 3265 section 3.1.4.2 states If a SUBSCRIBE request to refresh
a subscription receives a "481" >response, this indicates that the
subscription has been terminated and that the subscriber did not receive
>notification of this fact.
> In this case, the subscriber should consider the subscription invalid.
If the subscriber wishes to re-subscribe
>to the state, he does so by composing an unrelated initial SUBSCRIBE
request with a freshly-generated Call-ID and a >new, unique "From" tag --
Does this means once a subscribtion for a event is terminated in a dialog,
>resubscribtion for that event cannot be done in the same dialog later
on, if s why can't i resubcribe for that >event in same dialog ( with
different value for id in Event header).
>
>Thanks
>Balu
________________________________________________________________________
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implemento
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
