Basically a SUBSCRIBE message To/From header should have a AOR for which the
user(subscriber) wants to subscribe. Based on this subscription,registrar
(notifier) will notify about the registration events i.e.
lets say contact/s associated with the subscribed AOR in registrar
expired,shorten,refreshed,registered etc. Notify will be sent to the subscriber
with this info. Please confirm if my understanding is correct here.
1. The RFC 3680 states that a single NOTIFY can have details of multiple
registrations (AOR). lets say user(subscriber) 'A' is subscribed for only 1
AOR. is it possible that he can received Nofity that can have details for
multiple AOR's ?? If so,what should be the subscriber behavior..it should
ignore
the AOR's for which it hasn't subscriber ?
Re
Regards,
Hazzy.
________________________________
From: "Worley, Dale R (Dale)" <[email protected]>
To: Hazzy <[email protected]>; "[email protected]"
<[email protected]>
Sent: Wed, 20 October, 2010 7:18:53 PM
Subject: RE: [Sip-implementors] basic clarification regarding RFC3680
________________________________________
From: [email protected]
[[email protected]] On Behalf Of Hazzy
[[email protected]]
As per RFC3680,UE once registered, it cansubscribe for registration events and
get the notifications for registrations.
I need to clarify, how the registration and subscription are associated i.e.
Lets say User 'A' registers its aor i.e. SIP URI (sip:[email protected]) and
contact 'X' with the registrar.
_______________________________________________
*Any* element can subscribe for the registration events for *any* AOR (provided
the notifier allows the subscription to be created).
The registration and the subscription are *not associated* with each other
(other than that the subscription will report the existence of the
registration).
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
