When migrating to the Meraki MC platform, If number porting has been requested to transfer existing DIDs to an MC Dashboard organisation, the current PBX where the DIDs terminate for incoming calls may need to have call forwarding configured to new temporary DIDs while the porting process is completed. In addition, PBX users may want to enable 4-6 digit Meraki MC extension dialing from their current PBX.
You can configure the route of a call from Cisco CallManager to Cisco Meraki MC DIDs.
In this example, the placement of a call to the Cisco Meraki MC DID (415) 523-9268 occurs after the call forwarding configuration is complete. The incoming call routes to a computer telephony integration (CTI) route point, which is then routed to the Cisco Meraki MC DID via configured carrier SIP trunks. The CTI route point is configured to forward all calls to (415) 523-9268. The call then arrives via PSTN at the customer’s carrier infrastructure is routed to the Cisco Meraki MC endpoint configured with the (415) 523-9268 DID via the Cisco Meraki cloud platform.
Complete these steps to configure call forwarding to Cisco Meraki MC DIDs
Open Cisco CallManager Administration.
Choose Device > CTI Route Point.
Click the Add a New CTI Route Point link, and then enter the extension equal to the Direct Inward Dial (DID) number that you want other people to call - in this case 4155239268.
Use this information to enter the settings for each MC phone:
Device Name—A unique identifier for this device. Enter between 1 and 15 characters, which includes alphanumeric characters, dots, dashes, or underscores.
Description—A descriptive name for the CTI route point eg. “Cisco Meraki - 4155239268”.
Device Pool—Specifies the collection of properties for this device, which includes Cisco CallManager Group, Date/Time Group, Region, and Calling Search Space for autoregistration. Select the name of a Device Pool from the drop-down menu.
Click Insert. This action refreshes the page to display the information that you entered for the new CTI route point. The list on the left side of the page displays an icon that you can click to begin to add lines to the route point.
Click Line 1 on the left side of the page, and then enter this setting:
Forward All—Enter the voice mail pilot number for port 1 to indicate the directory number to which all calls forward.
The second method of forwarding calls to a Cisco Meraki MC DID is via call forwarding features to located directly on the existing Cisco handset.
There are two types of call forwarding features to choose from depending on what your CUCM administration has allowed:
When call forwarding is enabled for any line other than the primary line, your phone does not provide you with confirmation that calls are being forwarded. Instead, you must confirm your settings in the User Options web pages.
1. Log in to your User Options web pages.
2. Access your call forwarding settings.
Setting up and cancelling Call Forward All from a Cisco handset towards a Cisco Meraki MC endpoint DID (4155239268 for this example):
1. To set Call Forward All, press CFwdALL or Forward All and enter the target MC phone number 4155239268.
2. To cancel Call Forward All, press CFwdALL or Forward All.
To verify that Call Forward All is enabled on your primary line, look for the Call Forward icon above your primary phone number and the Call Forward target number in the status line.
It is possible to forward calls to MC DIDs from existing trunks and DIDs by configuring a Mitel 3300 MCD PBX to forward calls directly to the new MC DIDs via the public carrier. Please note that this will result in an additional call leg.
Set up a Call Forward Profile:
Program a button on the phone:
The most cost efficient and simple way to forward calls on a Shoretel VOIP system requires an administrator configuring a route point with call forwarding to a Meraki MC phone DID. Route points are preferable to Shoretel extensions due to the fact that no licensing is required. The route point is hosted on the customer incumbent Shoretel Director server typically hosted at headquarters. The following steps outline how such a route point can be configured within the Shoretel Director.
To begin configuring route points, click the Route Points link under Call Control in the navigation frame.
Click Add New to begin configuring a new route point.
The following parameters on the route point parameters page will need to be configured to forward inbound calls to a Cisco Meraki DID:
Extension: This is the extension number of the route point on the Shoretel system. This must be a unique extension number on the Shoretel system. If the user was previously assigned a device and user license with an extension, this extension will need to either be changed or deleted before the route point is created.
DID: A single DID number can be assigned to the route point. This will need to match the DID that was previously configured on the user’s Device and User extension.
User Group: User groups are how the Shoretel PBX assigns permissions to outbound trunks. A user group with appropriate call permissions will need to be selected. Eg. If the Meraki MC DID requires a long distance or international call to be made from the Shoretel system, then a user group with access to a trunk capable of long distance or international calls will need to be assigned.
Route Point Server: This is typically the Shoretel Director server in a single site configuration.
Make Number Private: If the route point is configured with this parameter, the route point extension will be hidden in the Shoretel directory. This is an optional field.
Schedule: Schedules can be configured for the On-Hours, Holiday, and Custom modes that automatically change the call handling of the Meraki MC route point. If no schedules are specified, the system uses On-Hours mode. This is an optional field.
Call Handling Call Forward: Calls can be forwarded to a Meraki MC endpoint under certain conditions. Typically, the “Always” condition will need to be selected which forwards calls to the number specified in the Always Destination parameter immediately when a call is received.
To allow CUCM phones to dial MC 4-6 digit extensions, a CUCM administrator can configure outbound digit manipulation in order to prepend the first 4-6 digits of the MC DID to the dialed extension number. For increased convenience, the MC administrator should consider choosing sequential DIDs (Eg. (415) 886-3600, (415) 886-3601 etc.) when initially purchasing DIDs which will require only one customer destination pattern. For each non-sequential MC DID, an additional destination pattern will be required. Number manipulation can be achieved by employing the prefix configuration option to append digits to the dialed number. This IOS command is configured under dial-peer configuration mode.
In the example below, when a CUCM user dials an MC four digit extension beginning with 36 and ending in any digit, calls will be routed via the CUCM PSTN gateway (located at port 1/0:20).
SF(config)#dial-peer voice 36 pots SF(config-dial-peer)#destination-pattern 36..% SF(config-dial-peer)#prefix 415886 SF(config-dial-peer)#port 1/0:20
When a user dials the extension 3658 on their CUCM handset, the first six digits of the MC DID are prepended before being sent to the PSTN. The PSTN gateway will then receive the digits 4158863658. Note that if a provider is expecting full E164 formatted numbers, a country code may also need to be specified in front of the prefix.