[asterisk-dev] What's an AOR?

[Olle E. Johansson]

22 maj 2013 kl. 20:18 skrev Mark Michelson <mmichelson at digium.com>:

> On 05/22/2013 09:44 AM, Olle E. Johansson wrote:
>> I notice that chan_pjsip use "aor" as a replacement for peer/user - an account.
> 
> This is not correct. The replacement for peer/user is the type "endpoint". The term "endpoint" is generic enough that it can refer to any sort of logical SIP device with which Asterisk will be communicating.
> 
> An endpoint may be configured to have any number of aors associated with it. In turn, each aor may have multiple contacts bound to it. This allows a hierarchical structure that decouples endpoints from locations.
The AOR according to RFC 3261 is the number - the business card address - that is the primary handle to reach someone.
Whatever structure you have in the configuration - it's still the dialplan extension.

So how do you handle this forking in the PBX and then in the SIP channel? Have you modified the PBX?

> 
>> 
>> In SIP an AOR is the address that resolves into destinations - your registered phones - when you initiate a dialog. It's also the address you register to in order to add a new device.
>> 
>> In Asterisk the AOR you place a call to is the extension in the dialplan. It resolves into a SIP account and then to the registred devices.
>> 
>> So in fact we have two AOR's - the one you call to and the one you register to. In Asterisk they're different.
> 
> Just a quick interjection here. They don't *have* to be different.
But we do recommend them to be different. Always. Having extension "200" with the SIp account "200" is a bad concept and should not be a recommendation, ever.

> 
>> 
>> I would prefer that the AOR stays as a name for the extension, what you dial to, and that we separate that from what we register to. That's just an account.
>> 
>> Calling one AOR - the business card style address in SIP - could resolve into many sip devices.
>> 
>> I think using AOR for the registration account will confuse many, since you can't call it without an extension in the dialplan.
>> 
>> From over ten years of teaching this stuff, I think it's important that we have proper names for things.
> 
> I think the name "aor" is proper for what it actually is. It is simply a named entity to which contacts may be bound. An aor may be shared by multiple endpoints, or an endpoint may have multiple associated aors. There is also nothing that restricts you from having an endpoint, an aor, and the extension used to call the endpoint share the same name.
I agree that it's one role of the aor in the SIP standard - to accept bindings of contacts. But it's one part, and since we separated the two parts into two different namespaces - the dialplan and sip channel objects - I would prefer that the AOR term is not used for the latter, but for the former.

/O
> 
>> In the rest of the world this is just "SIP accounts". Let's call them that.
>> 
>> Or follow my old suggestion - to have "devices", "services" and "trunks" as account types.
>> 
>> /O
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> 
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-dev
> 
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>  http://lists.digium.com/mailman/listinfo/asterisk-dev