Archive for the ‘Route Plan’ Category

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

Posted: June 14, 2006 by sankar in Route Patterns

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

Posted: June 14, 2006 by sankar in Route Patterns

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".

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

Posted: April 29, 2006 by sankar in Route Plan

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

Caller ID / Caller Name display

Posted: April 29, 2006 by sankar in Route Plan

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 #

Posted: April 21, 2006 by cciestudy in MGCP, Route Patterns

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.