ARM

The external applications menu lets operators directly access the Routing Manager (ARM) for managing the dial plan and call routing rules of multi-site, multi-vendor enterprise VoIP networks. The ARM enables centralized control of all session routing decisions. Through the ARM’s graphical user interface, network administrators can design and modify their voice network topologies and call routing policies from a single location, resulting in significant time and cost savings. Time-consuming tasks such as adding a new PSTN or SIP trunk interconnection, adding a new branch office or modifying individual users’ calling privileges can be carried out simply and rapidly.

To enable a direct connection to the ARM:
1. Open the OVOC Server tab (System > Configuration > OVOC Server) as shown in the following figure, and then click the ARM option.

ARM Configuration

2. In the field 'ARM Server FQDN / IP' under the General section, enter the FQDN (host name) or IP address of the ARM server to connect to. You can obtain these from your enterprise's network administrator if necessary.
3. Note that parameters 'ARM Status', 'ARM Version' and 'Unique Identifier' are provisional placeholders. They will be automatically reconfigured with true values after connection with the ARM is established.
4. Under the ARM Single Sign On section, you can optionally configure direct sign-on to the ARM. Admin and Operator types can configure this SSO connection. Note that the feature applies only to ARM versions that support it. The logic is identical to the logic of a regular sign-on.
5. Under the OVOC-ARM Communication section, you can select the Secure Communication option for HTTPS secured communications between OVOC-ARM. Specify an ARM operator and their password to allow communication from OVOC to ARM. If an OVOC-ARM connection has already been established, you can opt to configure the 'Change ARM Password' parameter value.
6. Under the ARM-OVOC Communication section, specify a valid OVOC operator. This operator must be a 'System' operator (see Adding a 'System' Operator) with a security level of 'Operator'. This operator will then be defined in the ARM to be used by the ARM with REST communication toward the OVOC.
7. Click Submit.
8. In any OVOC page, click the external applications menu icon displayed on the right side of the title bar.
If your browser is configured to block pop-ups, a message will appear indicating 'Pop-ups were blocked on this page' (or similar). In this case, set your browser to allow pop-ups.
ARM status as well as the statuses of other applications can be viewed in the menu. The example in the preceding figure indicates that the network is not managed by the ARM (Not Connected) and that there is an alarm in the ARM-managed network whose severity is Critical. If the color code had been green, the indication would have been that the network is managed by the ARM and that there are no alarms in the ARM-managed network.
9. In the external applications menu that opens, click the Routing Manager link.
10. View if you configured SSO the ARM's main screen which opens in a new browser tab. If you didn't configure SSO, you'll be prompted to log in.