Grandstream Networks, Inc.
Table of Contents OVERVIEW ..................................................................................................................... 4 MANAGING OUTBOUND ROUTE ................................................................................. 5 Using Source Caller ID Filter ................................................................................................................... 5 Using Privilege Level .......................................................................................
Table of Figures Figure 1: Create an Outbound Route ............................................................................................................ 5 Figure 2: Enable Filter on Source Caller ID .................................................................................................. 6 Figure 3: Privilege Level for Outbound Rule ................................................................................................. 7 Figure 4: Extension Permission on UCM6XXX ..................
OVERVIEW This document presents instructions to manage outbound and inbound routes on the UCM6XXX. Firstly, we will introduce how to use source caller ID filter and privilege level to control outbound calls. UCM6XXX series support two ways to define source caller ID filter: • Selecting allowed extensions The permission and privilege settings are used to control the outbound calls generated from extension, IVR, DISA, and inbound route so that the UCM6XXX can securely handle the calls as desired.
MANAGING OUTBOUND ROUTE There are two methods to manage the outbound route, Privilege Level and Source Caller ID Filter. When creating/editing an outbound rule under Web UI Extension/Trunk Outbound Routes, users shall see "Privilege Level" option and “Enable Filter on Source Caller” options as shown in the following figure.
Figure 2: Enable Filter on Source Caller ID After “Enable Filter on Source Caller ID” option is enabled, “Privilege Level” option is automatically disabled (turned into grey) and more options will show up for user to configure the filter. There are two ways to configure the source caller ID: 1. Select extensions/extension groups Select extensions/extension groups from “Available Extensions/Extension Groups” to “Selected Extensions/Extension Groups”.
For example, if “Custom Dynamic Route” is configured as “_xxxx”, only extensions of 4 digits can use this outbound rule to make outbound calls. If both of the above options are configured, they will take effect at the same time. Therefore, the extension making the outbound call will either need to be an extension in the selected list or match the pattern defined in “Custom Dynamic Route” option.
Note: • • Setting “Privilege Level” to “Disable” will lead to the outbound route unavailable unless “Enable Filter on Source Caller ID” option is enabled to control outbound permission. Basically, selecting “Disable” means to disable the outbound rule and thus no outbound call can be placed through this outbound rule.
The extension needs to be assigned with higher or equal level permission compared to the outbound route's privilege level in order to make outbound calls using that route. When making an outbound call via a route from an UCM6XXX extension, the UCM6XXX will compare the extension's permission level with the outbound route's privilege level. If the extension's permission level is higher than or equal to the outbound route's privilege level, the call will be allowed to go through.
DISA Permission When creating/editing a DISA under Web UI Call Features DISA, users shall see " "Permission" options with 4 levels in the drop-down list. Figure 6: DISA Permission To allow calls routed to this DISA to use trunk to dial external numbers, the administrator should select a proper level for “Permission” option. Once a DISA is created, users can configure the inbound route destination as "DISA" or IVR key event as "DISA".
In this case, pattern XXXX will match any numbers that dialed. However, for number 1234, since it is declared explicitly, UCM6XXX will select Outbound Route 2 to place the call. • Note: For UCM6XXX pattern matching mechanism, specific matching always has higher priority than global matching. Case 3: Matching first Character Outbound Route 1 has matching pattern ‘_X.’ Outbound Route 2 has matching pattern ‘_0X.
Figure 7: Create an Inbound Route This "Privilege Level" option applies to the inbound rule only when "Default Destination" is set to “External Number” or "by DID".
OUTBOUND CALLER ID/DOD CONFIGURATION On UCM6XXX web GUI, there are 4 places that allow users to configure the Caller ID to be displayed on the callee’s LCD. We could name them as: • • • • Trunk Caller ID Trunk DOD Extension Caller ID Global Outbound Caller ID In this section, we will introduce the configuration of each of them and their priority. Trunk Caller ID When editing a SIP peer trunk, users shall see “Keep Trunk CID”, “Caller ID” and “CallerID Name” options.
Example of how DOD is used: Company ABC has a SIP trunk. This SIP trunk has 4 DIDs associated to it. The main number of the office is routed to an auto attendant. The other three numbers are direct lines to specific users of the company. At the moment when a user makes an outbound call their caller ID shows up as the main office number. This poses a problem as the CEO would like their calls to come from their direct line. This can be accomplished by configuring DOD for the CEO’s extension.
Figure 10: Edit DOD Extension Caller ID When creating/editing an extension, users shall see options “CallerID Number”, “First Name” and “Last Name”. Figure 11: Extension Caller ID “First Name” and “Last Name” together define caller ID name.
Global Outbound Caller ID On UCM6XXX Web UI PBX Settings General Settings page, users shall see “Global Outbound CID” and “Global Outbound CID Name” options: Figure 12: Global Outbound CID “Global Outbound CID” and “Global Outbound CID Name” will be used as call ID and call ID name of an outbound call if following conditions are satisfied: • “Keep Trunk CID” of the trunk is disabled • DOD of the trunk is not configured • The extension initiating the outbound call doesn’t have caller ID number and
Outbound Caller ID Priority • If trunk caller ID is configured and “Keep Trunk CID” is enabled, then trunk CID is of the highest priority. “Caller ID” and “CallerID Name” of the trunk will override caller ID configured in DOD, extension and global settings. • If “Keep Trunk CID” is disabled, the priority of the other three caller id configuration is as following: 1. DOD has the highest priority 2. Extension CID has the second priority 3.
MANAGING INBOUND ROUTE DID Pattern Configuration When creating/editing an inbound rule under Web UI Extension/Trunk Inbound Routes, users shall see "Pattern" option. User could use the following characters to define the DID pattern: • X: Any Digit from 0-9. • Z: Any Digit from 1-9. • N: Any Digit from 2-9. • ".": Wildcard. Match one or more characters. • "!": Wildcard. Match zero or more characters immediately. All patterns will be prefixed with “_”.
1. The field Pattern defines the allowed pattern of the dialed number 2. The field CallerID Pattern defines the allowed pattern of the caller number Only if both patterns are matched, the inbound call can successfully go through. To illustrate it more clearly, here is an example. Assuming a peer trunk is configured between two UCM6XXX. 1. An extension 10000 on UCM6XXX-A wants to call an extension 5000 on UCM6XXX-B. 2.
There are two modes available for uses to select: To-header and Request-line. Select “To-header” to use To header in SIP message as the destination ID; select “Request-line” to use Requestline header in SIP message as the destination ID. Figure 15: Edit SIP Trunk – DID Mode Prepend Trunk Name to Caller ID for Inbound Call When creating/editing an inbound rule, user shall see “Prepend Trunk Name” option.
Figure 16: Edit Inbound Rule – Prepend Trunk Name Prepend User Defined Name to Caller ID for Inbound Call When creating/editing an inbound rule, user shall see “Prepend User Defined Name” option. If this option is enabled, UCM6XXX will prepend the name defined by user to the caller ID name for all incoming calls through this inbound rule. Therefore, the caller ID name displayed on the called extension will be the name plus the caller ID.
Figure 18: Edit Inbound Rule – Alert-info Users can set “Alert-info” option in Inbound Route to “Custom” and specify “Custom Alert-Info” as “External” for instance, and the phones can be configured to use a specific ringtone if matching rule is set to “External”. If the call is coming through the trunk, the phone will ring using specified ringtone and user will know the call is external, otherwise, the phone will ring using default ringtone letting the user know that the call is Internal.
Multiple Mode In the UCM6XXX, the user can configure inbound route to enable multiple mode to switch between different destinations. The inbound multiple mode can be enabled under Inbound Route settings. Figure 20: Edit Inbound Rule – Multiple Mode When Multiple Mode is enabled for the inbound route, the user can configure a “Default Destination” and a “Mode 1” destination for this route. By default, the call coming into this inbound route will be routed to the default destination.
