Digit manipulation – best practices

When doing digit manipulation, first decide whether you want to do it at route pattern level or route group level. Route group level is recommended for following reasons.

 a. The end user will see the manipulated digits if you do digit manipulation at the route-pattern level. If you do it at route group level, the end user will not see that on his phone.

b. IF you do it at route pattern level, CDR will log the digits including the manipulated ones. So its recommended to do it at the route group level.

c. Any digit manipulation you do at route group level completely overrides the setting at route pattern level.

Connected party Name/Number presentation

When caller A calls caller B, caller B sees caller ID as caller A's name and number. This can be controlled using the Calling number/name presentation parameter in translation pattern or route pattern. At the gateway level, you can control the Calling party number  but not the Calling party name.

When caller A calls caller B, once the call gets connected, caller A may see caller B's number /name on his phone. This is called Connected party presentation. This can be restricted at the translation pattern, route pattern level. For outbound dialing, connected party presentation works only on internal calls and QSIG trunks.

For Internal calls, you need to use a translation pattern. When A calls B and B is forwarded to C, A will see C's name and number on his phone. This can be restricted by setting a translation pattern for B, so that when A calls B, it matches the translation pattern first. On the translation pattern, you can set the connected party name and number setting to restricted.

Connected Line ID and Connected Name Presentation for incoming calls apply only for QSIG gateways. The gateway has no settings for Name Presentation.

Calling party name / number presentation

You can set this parameter either at Route pattern level or Gateway level. Gateway level overrides Route pattern level. The operation of Calling name and Calling number is independent.

If you set it to Default, it passes calling name/number as such. (presentation bit is 0081)

If you set it to Allowed, it sets the presentation bit (debug isdn q931) to 0081

If you set it to Restricted, it sets the presentation bit to 00a1.

Name display shows up in debug isdn q931 output as "Display i = name".

Best practices for Ext mask, Calling transform mask etc

Choose either route pattern or route group to set External Ph number mask, Calling party transform mask and prefix digits. (not both). Any time you set a calling transform mask or prefix digit at the route group level, every other setting at route pattern is overridden.

If you set Rgroup setting to Default, it will honor settings at route pattern level. (except in cases where you set a calling transform mask or Prefix digits at route group level).

If you set Rgroup setting to On, it will override settings at route pattern level.

If you set Rgroup setting to Off, it will override settings at route pattern level. Calling party ext mask will not be used.

For MGCP gateways, if Caller ID DN is set at gateway level, it will override settings at route list level. If Caller ID DN is not set at gateway level, it will default back to Service parameter settings.

Caller ID presentation in Translation patterns

Caller ID presentation in Route patterns over ride CallerID presentation in Translation patterns

Caller ID / Caller Name display

This was tested over an ICT.

Caller ID screening only screens the number, not name.

If name is configured on the phone (Display – Internal Caller ID) and caller ID is screened, the destination will see the caller id as “Display Name – Unknown number”

If name is not configured on the phone and caller ID is screened, the destination will see the caller id as “Private”

MGCP – Strip Trailing #

Trailing# works only with the @ pattern.

Other discard digits like PreDot, PreAt etc works fine with any pattern, ex: 9.1[2-9]XX[2-9]XXXXXX

In CCM 4.1, you don’t need to define any discard digit rules to remove trailing#. CCM considers trailing # as interdigit timeout and to match the route pattern, but does not forward the # to the gateway.

Using # in route patterns

# is a valid character in Route patterns. If a route pattern contains # as an intermediate digit, call manager will not consider that to be a digit termination.

MGCP will pass the #(both trailing# and the # in between) to the gateway.

H323 will pass the # in between the numbers to the gateway, but sending the trailing # depends on the Service Parameter “Strip # sign from Called Party Number”.

Translation pattern

When PLAR is set up, you have to add the translation pattern into a Partition and CSS.

1. To set up plar, create an empty translation pattern. Put it in a partition / CSS

2. Set the PLAR CSS to phones.

3. Put called party transform mask in translation pattern to the desired destination number

Caller ID Presentation

Available at Route pattern, Gateway as well as service parameter level.

Options available are Default, Restricted and Allowed.

FInd out what Default means.

Allowed – Caller id is allowed

Restrictede – Caller id is blocked.

International Dial plan

Download the file and install it on Publisher and then on all subscribers.
Restart CCM service to reflect changes.

NANP, UKNP

Partitions and CSS

*** Partitions can contain – , space
*** The max number of partitions that can be entered in a system depends on how many characters are there in each partition name. You can have for ex: 2 character partitions up to 170. or if using 15 characters you can have up to 32 partitions.

*** max character limit in an individual CSS = limited to 512 (half of 1024, because a combined CSS clause contains device and line CSS)
*** max number of partitions in a CSS depends on individual partition names.
*** max length of combined CSS clause (inclusive of device and line partition) = 1024.

External Phone number mask

If you set EXt. phone number mask at the line level, the header bar on ip phone will be set to the same number. If phones extension is 1631 and you set the mask to 817542XXXX, the header bar will display 8175421631.

Route-Lists (Calling Party Info)

If the RL is set to Default, it would follow whatever is set at the RP level.

If the RL is set to ON, it would override whatever is set at RP level.

If the RL is set to OFF, it would override external phone number mask settings and hence would use the DN of the line.

If the Calling Party Transform Mask is set at RL level, it overrides the settings at RP.

If the Caller ID DN is set at gateway level (H323) it overrides the settings at RL and RP level.

If the Caller ID DN is set at gateway level (MGCP) it overrides settings at RL and RP level. If Caller ID Dn is not set at gateway level (MGCP) but it is set at service parameter level, it uses the mask used at service parameter level.

If translation-patterns are set at the gateway, it overrides everything else.

————-Order of Operation for MGCP————–
Line
Route-pattern
Route-List
Service parameter (Caller ID)
CCM Gateway settings (Caller ID DN)
Actual gateway (translation patterns)
PSTN or PBX.

————-Order of Operation for H323————–
Line
Route-pattern
Route-List
CCM Gateway setting (Caller ID DN)
Actual gateway (translation patterns)
PSTN or PBX.

Prefix digits – Route Lists

Prefix digits at RL level overides prefix digits at RP level.

If a Caller ID DN is specified either in service parameter or gateway level, prefix digits set at RP or RL level

Route Filter Summary

See attached picture below . Click on it to enlarge!  

Router Filter Lab

Created an ICT between CM 333 and Cm40
IP communicator on CM 40 has extension 2142626000
Remaining hard phones are registered to CM 333 (1XXX range)

————————–

Test 1: AREA-CODE is the 3 digit area code for long distance calls.

AREA-CODE == 214 —-> dials ip communicator if you dial a 1 followed by 214 followed by 7 digits

Test 2: LOCAL-AREA-CODE is the 3 digit area code for 10 digit local calls.

LOCAL-AREA-CODE == 214 —–> dials ip communicator if you dial 214 followed by 7 digits

Test 3 : AREA-CODE == 214 and LOCAL-AREA-CODE == 214 —> This condition does not exist (As soon as you dial a 1, you get busy tone)

Test 4: AREA-CODE == 214 OR LOCAL-AREA-CODE == 214 —-> This will match either 1214 or just 214.

Test 5: INTERNATIONAL-OPERATOR = EXISTS —> IF you dial 9.010 If you dial 9.011 it matches 9.@ because “01” is international access and it waits for the international number (country code/areacode/number) to be dialed and then routes out.

Test 7: INTERNATIONAL-DIRECTDIAL = EXISTS –> If you dial 9.011, it matches 9.@ because the last “1” is international direct dial and it waits for international number (country code/area code/ number) to be dialed and routes out.

Router Filters

Router filters work only when @ is used.
Router filter tags change depending up on Numbering plan

Router filter tag descriptions:

* Difference between AREA-CODE and LOCAL-AREA-CODE. If you dial a 10 digit local number then you should useLOCAL-AREA-CODE. If you dial a long distance number (11 digits) you should use AREA-CODE

*COUNTRY-CODE – can be 1, 2 or 3 digits represents country code of a international number.

*END-OF-DIALING – # is end of dialing character for International dialing. This is represented by END-OF-DIALING.

* INTERNATIONAL-ACCESS – 2 digit access code that specifies international dialing. Calls that originate in the US, use 01 as the code. (first 2 digits of the code 011)

* INTERNATIONAL_DIRECT_DIAL – 1 digit code that identifies a direct dialed international call. Calls that originate in the US use 1 for this code. (last digit of the code 011)

* INTERNATIONAL-OPERATOR – 1 digit code that identifies operated assisted international call. This code specifies 0 for calls that originate in the US.

911/411/611/211

When route pattern is 9.@ and you dial 9.911/9.611/9.411/9.211 it immediately matches 911/611/411/211 and routes the call.

Urgent Priority Flag

This seems to be working only with 911/611 type calls.

Route Groups

*** If you are adding an MGCP gateway in a route group that uses QSIG, you can only add other MGCP gateways that are also QSIG enabled. Once you add a gateway (with QSIG) in a route-group, all other non-QSIG gateways are not listed.

*** Same applies vice versa (if you add a non-qsig MGCP gateway, all other qsig MGCP gateways are not listed

*** When a QSIG MGCP gateway is added to a route group, the route group configuration page shows the Route-group type as QSIG. (If the gateway is NON-QSIG, it shows the Route-group type as Non-QSIG)

*** H323 / H225 type gateways cannot be added to a Route group which already has a QSIG type MGCP gateway.

How to Load balance outbound calls

** This works only at the Route group level and is applicable only to the first route group in the route list

** At the route-group config page, set the order of selection for each device to 1.

** Change service parameter (Cisco Callmanager)

“Reorder Route List ” to True. (Default is False)

** If its set to True, CM uses Round Robin load balancing for the first route-group in the route-list

** If its set to False, CM uses linear distribution for those devices in the first route-group/route-list with the same device selection order.

Understanding Route-Lists

*** Add a route-list
*** Enter a name
*** Select one route-group at a time.

*** Settings on Route-List
a. Use Calling party’s external phone number mask – On/ Off / Default.

i. If you use Default, what ever is configured at RP or Line is used.
ii. Off disables CLID.
iii. On indicates that calling party, full external number is used for CLID.

(Order of priority is , RL, RP, Line)

b. Calling Party Transform mask – Over rides what is set at Route pattern level/ Line level
c.

External phone number mask at Line level

If you set EXt. phone number mask at the line level, the header bar on ip phone will be set to the same number. If phones extension is 1631 and you set the mask to 817542XXXX, the header bar will display 8175421631.

Caller ID Translations

Refer to : Route-List / Route-group/ Route-patterns:

 If the RL is set to Default, it would follow whatever is set at the RP level.

If the RL is set to ON, it would override whatever is set at RP level.

If the RL is set to OFF, it would override external phone number mask settings and hence would use the DN of the line.

If the Calling Party Transform Mask is set at RL level, it overrides the settings at RP.

If the Caller ID DN is set at gateway level, it overrides the settings at RL and RP level.

If translation-patterns are set at the gateway, it overrides everything else