Cisco Gateways

Voice Gateways

IOS gateways

How to add prefix digits to incoming calling numbers through an MGCP gateway

Core Issue

The Cisco CallManager prefix must have an access code (9 for the United States, 0 for Australia) for the Calling Line ID (CLID) on inbound calls.

This way, numbers in the missed or received call logs on each phone have a 9 or 0 prefix for each call. When the user selects Dial, the initial 9 is used to select an outside line, and the remaining digits dial the external party.

This is simple to do in H.323 with a voice translation pattern, which can differentiate based on ISDN call type (to add the national prefix or an access code, plus national prefix) but non-trivial for a Cisco CallManager-controlled Media Gateway Control Protocol (MGCP) gateway.

To configure this functionality for non-MGCP Cisco IOS gateways, perform these steps:

Note: The prefix is 00 for the calling number, so the user does not need to edit the missed call.

1. In global configuration command mode, issue the translation-rule 1 Rule 1 . 00command.

2. Under the dial-peer VoIP, issue the translate-outgoing calling 1 command.

Resolution

This functionality for all Cisco CallManager-controlled skinny and MGCP gateways, including DE-30+ and Catalyst blades, can be configured as shown:

Note: This assumes that extensions do reside in the <None> partition, that the calling party number is nine digits for inbound calls, 0 is the external access code, and 0 is prepended to the area code:

Partition:
 InboundTranslations
Calling search spaces (CSS):
 InboundTranslations contains partition InboundTranslations
Translation Patterns:
 InboundTranslations/1.XXXX
 Partition = InboundTranslations
 CSS = Stations (the name of the Calling Seach Space
 that contains the phones' partition)
 Calling Party Transform Mask = 00XXXXXXXXX
 Discard Digits = PreDot
Gateways
 Gateway A with CSS = InboundTranslations and "Prefix DN" of 1

This configuration does not change the calling party number that is presented to the station for inbound calls (but not station-to-station calls), and it causes the missed calls dial to work without EditDial.

It does this by adding a 1 to the destination pattern of the inbound call so that it is not immediately recognized as a phone extension Distinguished Name (DN) prior to hitting the translation pattern within the Calling Search Space (CSS) of the gateway. It adds the 00 to the calling number with the calling party. Transform Mask then strips the extra 1 from the destination pattern and rings the phone. The extra 1 is only required if you have DNs residing in the <None> partition, which is able to be reached by any CSS and would be a closer match than an XXXX pattern.

If none of the DNs reside in the <None> partition, the translation pattern can be changed to XXXX and the gateway can pass on the DN unchanged to the inbound translations CSS without fear of it matching a real phone. The translation pattern would then not need to modify the called number at all. Only the calling party has a CSS that includes the phones.

How to configure Cisco CallManager Express to make multiple IP phones ring at the same time

VERSION 2

Resolution

You can make multiple IP phones ring at the same time using the overlay ephone-dn feature. It is available with Cisco CallManager Express 3.0 and later.

To resolve the issue, refer to the Overlaid Ephone-dn section of Cisco Unified Communications Manager Express : Configuring Call-Coverage feature.

For more information, refer to Cisco Unified Communcations Manager Express: Overview.

Note: For Cisco CallManager Express versions prior to 3.2.1, ephone-dn overlays disable call waiting. If a phone is using an overlaid ephone-dn on an active call, call waiting is disabled for any incoming calls to any ephone-dn in the overlay set.

For Cisco CallManager Express 3.2.1 and later, call waiting is available for overlaid ephone-dns. Overlaid ephone-dns with call waiting use the c: keyword in the button command and overlaid ephone-dn without call waiting use the o: keyword. To understand the difference in the behavior of overlaid ephone-dns with call waiting and overlaid ephone-dns without call waiting is the same, refer to the Call Waiting section of Cisco Unified CallManager Express: Configuring Call-coverage feature .

Configuring Call Waiting for Communications Manager Express

Call waiting is a feature that is enabled by default on all dual-line ephone-dns.

There are some instances where you may wish to disable Call-Waiting but keep other benifits of a dual-line ephone-dn such as consultative transfer and conferencing.

To disable a directory number from accepting call-waiting requests use the command
no call-waiting beep accept at the ephone-dn.

To make it so a specific phone cannot generate call-waiting beeps to other phones use the command
no call-waiting beep generate at the ephone-dn.

Lastly, Have you ever heard a call waiting beep on your phone, but not been able to get the other person to stop talking long enough for you to tell them you have another call?
Try call-waiting ring at the ephone-dn. This will make your phone ring rather than beep when you get a call waiting beep.

Call waiting does not work on shared dual line ephone-dns

Problem:

Call waiting does not work on a shared dual line ephone-dn.

Detailed Explanation:

We have the following setup:

ephone-dn 1 dual-line

number 1000

ephone 1

mac-address 1111.2222.3333

type 7961

button 1:1

ephone 2

mac-address 1234.1234.1234

type 7961

button 2:1

A call placed to Extension 1000 can be picked up on ephone 1 or ephone 2, placed on hold and then picked up from the other phone. However, if an active call on ephone-dn 1 (say on ephone 1) is placed on hold and another call comes in, ephone 2 is not notified of the call. Only ephone 1 gets a call waiting beep and the caller ID is displayed on ephone 1. In fact, the caller ID may flash for a moment on ephone 2 as well but the call cannot be picked from this ephone.

Reason:

Dual line ephone dns were created to mirror a call waiting feature along with the functionality to natively transfer/conference calls in CME. With the usage of shared lines, it is assumed that channel 2 of the ephone-dn is going to be used for picking up a call at another extension once it is placed on hold. Hence, this channel is reserved for the possibility of such a thing happening due to which a second call coming in at the same time will not ring on ephone 2.

Resolution:

The ephone-dn needs to be converted to an octo-line for the desired functionality to be achieved. This is supported in CME 7.0 +.

How to Create broadcast hunt groups in Communications Manager Express

How to Create broadcast hunt groups in Communications Manager Express

CME supports three types of hunt groups out of the box.

Sequential hunt groups—Ephone DNs always ring in same order.

Peer hunt groups—Ephone DN’s ring in a circular order picking up from the last DN that did not ring.

Longest-idle hunt group—Longest Idle DN gets the next hunt group call.

Some users desire a hunt group that rings on all phones at once. In the full blown CallManager world this is referred to as a “broadcast hunt group”.

To make CallManager Express emulate this broadcast hunting we can use Overlay DNs.

Lets say our help desk has extension 4357( 4357 spells help on a phone touchpad)

Plar to extension 4357 from your fxo ports.

Overlay extension 4357 on to multiple phones

ephone-dn 6 dual
number 4357
huntstop channel
no huntstop

ephone-dn 7 dual
number 4357
huntstop channel
pref 1

ephone 1
button 1o6,7

ephone 2
button 1o6,7

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s