|Sonus Documentation Portal|
Use the AoR Group profile object to group together sets of Address of Record (AoR) values to be used in Application Layer call forking. With this feature, the SBC receives a single initial INVITE for a target and creates multiple initial INVITEs with different call-Ids to different targets. These additional targets are associated with the received target through configuration. An AoR Group Profile is associated with a VOIP Subscriber profile. When the VOIP Subscriber is the target of a call, the contents of the AoR Group Profile are used in forking calls to multiple subscriber devices (AoRs).
On the SBC main screen navigate to All > Profiles > Aor Group Profile
The Aor Group Profile window opens showing a list of any configured AoR Group Profiles.
To create a new AoR Group Profile click New Aor Group Profile on the Aor Group Profile List window. The Create New Aor Group Profile window is displayed.
The parameters and their descriptions are given below:
|Name||Up to 23 characters||Specifies the name to assign to the profile.|
|Aor Data List||Up to 1500 characters||
Specifies up to 10 AoRs for call forking.
You have the option to include two timer values within an AoR:
The delayBeforeRingTimer (default: 0) - Specifies a duration in milliseconds (0 to 300000) to delay forking to the destination. If not provisioned or zero, the SBC does not delay forking to the destination. This is applied per AoR. A forking call to this AoR is initiated only if final (2xx or 3xx) response is not received from any other AoR until the specified time. It is applied separately if there are multiple forked calls for the same AoR.
The answerTooSoonTimer (default 0) - Specifies a duration in milliseconds (0 to 300000) used by the SBC to terminate a call if it receives an answer before the specified time. This is applied per AoR. A final answer received before the specified time causes the call to be terminated with BYE. Other forked calls to other AoRs stay intact. It is applied separately if there are multiple forked calls for the same AoR.
You must begin the AoR entry with a URI type. The basic syntax for specifying an AoR:
Inclusion of the timer values is optional, but if included, the order and syntax must be maintained such as in the following examples of valid AoRs:
Separate complete AoRs with a comma and do not include spaces.
Note: For standard routing cases, the "user=phone" parameter is used.
|Preferred Identity||Up to 1500 characters||
Specifies the preferred identity for the AoR group.
|Aor Dialog Attribute||n/a||
Specifies the user part that is used for the active early dialog selection behavior.
The options are:
|Wait for Answer||0 to 300000 milliseconds||
Specifies a single time period value in milliseconds for all AoRs to which the ingress call is forked. Any non-2xx final answer (3xx responses) is delayed until the configured time expires, as follows:
The default value is 0.
Note: Currently, the timer should only be configured up to 120 seconds.
Make the necessary entries and click Save.