Manipulating Calls On Callmanager Express

I have gathered in this article configuration examples of how to modify call properties on the Cisco Callmanager Express.

Clid Network-number Command

The clid network-number modifies the Caller ID number that is sent on the network. To try it, we first make a call from x5002 to x4002:clid-network-number-2016-03-29 04_02_43

Then, in the outbound matched dial peer, we add clid network-number instruction:

clid-network-number-2016-03-29 04_04_03

We verify with “show dialplan number 4002”

clid-network-number-2016-03-29 04_05_35

or with “show run | s dial-peer voice 4000”

clid-network-number-2016-06-07 16_30_20

or with “show dial-peer voice 4000”

clid-network-number-2016-06-07 16_30_28

And we dial once again:

clid-network-number-2016-03-29 04_06_13

Notice that the calling party number is presented to the called party as 3025555002 instead of 5002.

Clid restrict command

“Clid restrict” command on the Callmanager Express restricts the appearance of the calling number in the outbound dial peer:

clid-restrict-2016-03-29 04_08_46

I applied “clid restrict” to the outbound dial peer. To test it, I made a call from x5002 to x4002. Notice that the caller ID is “private” on the called party phone:

clid-restrict-2016-03-29 04_10_08

To verify that “clid restrict” has been applied, do “show dialplan number”:

clid-restrict--2016-03-29 04_19_28

Clid strip command

We remove the previous “Clid restrict” and set “clid strip”.

clid-strip--2016-03-29 04_16_14

We verify it with “show dialplan number”:

clid-strip--2016-03-29 04_16_54

We dial. Only the caller name is displayed on the PSTN phone

clid-strip--2016-03-29 04_17_24

By the way: in general, to verify which Caller ID restriction will be applied when dialing a given number, we use the following command:

show dialplan number

Clid strip name command

This command strips only the line name.

Let us see the line name on Mongi phone, with “show ephone-dn 1” (because it is a softphone registered to the CUCME)

clid-network-number-2016-06-07 16_31_34

The normal appearance is as follows:

clid-network-number-2016-06-07 16_35_44

Under the same outbound dial peer, we configure clid strip name

clid-network-number-2016-06-07 16_34_57

And we dial again. The caller ID name is stripped:

clid-network-number-2016-06-07 16_36_26

Clid strip and clid strip name, together

The impact of clid strip and clid strip name under the same outbound dial peer gives the following output:

clid-network-number-2016-06-07 16_41_01

Clid commands: personal thoughts

In their CVOICE Quick Reference Sheets, Sauer and Wallace mention that Clid command are used to present -or to hide- Caller ID information in Q.931 messages, in ISDN networks. As you can see in my experiments, the effect of Clid commands works well on an Ethernet network.

Dialplan-pattern Example

The dialplan-pattern command works for both inbound call legs and outbound call legs on the Cisco Callmanager Express.

This command is useful when:

  • we have a direct mapping between DID numbers and internal phone DNs
  • the last digits of each DID number equals to the phone DN. For example: DID 5126935002 -> internal phone x5002.

The dialplan-pattern command is available only for SCCP IP phones registered to a CUCME router. For inbound call legs, the command allows to translate a called DID number into a shorter number that matches the ephone-dn.

For outbound call legs, the same command translates the short calling number -which is the internal company number- to a full DID number.
Here is the lab setting in which we are going to test it:

dialplan-pattern-example--2016-04-02 14_22_25

First, we remove all the voice translation rules and voice translation patterns.

Then the configuration of the dialplan-pattern command is done at the Telephony-service level

dialplan-pattern-example--2016-04-02 14_07_23

The dialplan-pattern command generates a POTS dial peer for each internal 4-digit extension.

dialplan-pattern-example--2016-04-02 14_14_51

You can’t see the configuration of these auto-generated dial peers.

dialplan-pattern-example--2016-04-02 14_23_40

Effect on inbound call legs

A call from PSTN to 5126935002 is matched at Mongi router to an inbound dial peer, then the auto-generated dial peer is selected as the outbound matched dial peer.

dialplan-pattern-example--2016-04-02 14_26_49
The PSTN call came on the Mongi router. The called number was translated by dialplan-pattern command from 5126935002 to 5002
dialplan-pattern-example--2016-04-02 14_27_01
The Local PSTN phone dialed 5126935002

Effect on outbound call legs

Let’s call from an internal extension x5001 to the local PSTN number 512477551. The calling number got translated from x5001 to 5126935001:

dialplan-pattern-example--2016-04-02 14_30_44
An outbound call from Mongi phone x5001 to Bicycle shop Local PSTN number.
dialplan-pattern-example--2016-04-02 14_31_01
A call is received at the PSTN phone from 5126935001, which is a DID number owned by Mongi shop.

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *