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: <urischeme>:<user>@<domain>;<delayBeforeRingTimer>;<answerTooSoonTimer>;user=phone 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: - sip:bob@example.com;10000;2000;user=phone
- sip:bob@example.com;0;2000
- sip:bob@example.com
- sip:bob@example.com;0;0;user=phone
Separate complete AoRs with a comma and do not include spaces. Note: For standard routing cases, the "user=phone" parameter is used. |