The subscription, to an AOR, should give info about registrations for 
that AOR. In principle it can give information about other AORs too.

The only place I know of that uses that is 3gpp/ims. In IMS, a 
subscription to the reg event package for an AOR gives you status on 
that AOR and all "associated" AORs. (E.g. the ones that show up in 
P-Associated-URI.)

        Thanks,
        Paul

On 10/22/2010 2:04 AM, Hazzy wrote:
> 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)"<dwor...@avaya.com>
> To: Hazzy<hazzy...@yahoo.co.in>; "Sip-implementors@lists.cs.columbia.edu"
> <Sip-implementors@lists.cs.columbia.edu>
> Sent: Wed, 20 October, 2010 7:18:53 PM
> Subject: RE: [Sip-implementors] basic clarification regarding RFC3680
>
> ________________________________________
> From: sip-implementors-boun...@lists.cs.columbia.edu
> [sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Hazzy
> [hazzy...@yahoo.co.in]
>
> 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:x...@abcd.com) 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
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to