![]() ![]() A translation pattern matches the dialed digits in a similar manner to the matching of a route pattern. To prevent call-routing loops, CUCM passes digits through translation patterns for only ten iterations.įigure 12-11 illustrates the operation of a translation pattern. Eventually, the call is routed or blocked. The new pattern may match another translation pattern where digit transformation can occur once again. The resulting pattern is then re-analyzed by the system. Translation patterns use route-pattern style matching and transformation-mask digit manipulations. ■ Extension mapping from a public to private network ■ Hotlines with a need for private line automatic ringdown (PLAR) functionality (security phones in elevators or on a college campus) ■ Security desks and operator desks (abbreviated dialing) Additional examples where translation patterns can be used are as follows: In these situations, a uniform dialing plan can be created and translation patterns applied to accommodate the unique office codes at each location. The translation pattern can prefix a 9 and a 1 to all incoming PSTN calls.ĭigit manipulation and translation patterns are used frequently in cross-geographical distributed systems where, for instance, the office codes are not the same at all locations. The caller ID from the PSTN may include only 10 digits while the system requires 11 digits prefixed with an access code of 9 to properly route outgoing calls. Translation patterns are useful to manipulate the caller ID of incoming PSTN calls to allow the users to quickly return phone calls using the redial and missed-calls functionality. ![]() The translation pattern can also be used to block certain patterns. ![]() Note: This can only block unwanted calls based on DNIS information and not on the ANI information.įor more information, refer to Route Pattern Configuration.CUCM uses translation patterns to manipulate digits before routing a call. In this case, the "knob" that is used to block the call is the Route or Block this pattern option. To do this, the DNIS or called number can be specified in a route pattern, then applied to the gateway. To block calls in the same manner at the Cisco CallManager level, use translation patterns. Note: This method of blocking calls can only be accomplished based on the DNIS information (called party number) and not on the ANI (calling party number) information. This sends the call nowhere, and the calling party receives a reorder tone. Give the x-lation pattern a CSS that has access to NOTHING. Then, the gateway in Cisco CallManager must be configured to have a Content Services Switch (CSS) with access to this x-lation pattern first, based on the x-lation pattern partition. This is accomplished through translation patterns in the Cisco CallManager configuration.Īn x-lation pattern in Cisco CallManager must be created to match the inbound DNIS information (called party number). ![]() If a Media Gateway Control Protocol (MGCP) gateway (controlled by Cisco CallManager) is used, the only way to block unwanted calls is based on the DNIS information. If an H.323 gateway is used, incoming calls can be blocked based on ANI and DNIS information through translation rules on the gateway configuration.įor more information on how to block incoming calls with an H.323 gateway, refer to How to block incoming calls based on calling number and called number information with a Cisco IOS H.323 gateway. Then, make sure to consider any limitations of the gateway being used. To determine the appropriate procedure, first determine whether it is desirable to block unwanted calls based on Automatic Number Identifier (ANI), or Dialed Number Identification Service (DNIS) information, or both. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |