When not using our user provisioning API, AORs can be processed on dynamic basis.
When a request is initially made for an AOR within a configured authority (either through REGISTER or a request which requests the resource), a HTTP callback is made for the AOR's configurating.
The response - as with every other platform API call - can include a monitor Link header for the platform to monitor for changes, and will create a component within the runtime host that requests it. The component will remain valid for the lifetime of the HTTP resource, and any changes in configuration will result in the changes being applied to the component.
<aor user="theo" authority="voip.co.uk"> <storage id="xxx"/> </aor>