Version: 1.0
Status: Draft: 05/01/03
Contact: Roney E. Boyd

PURPOSE

The VCCS Call Manager Route Pattern Guidelines pertain strictly to the creation of the basic route pattern requirements that will maintain commonality between the various Call Manager Clusters within VCCS. These Guidelines do not attempt to address Partitions or Call Search Spaces creation or usages since the creation and usages of Partitions and Call Search Spaces depend entirely on how the individual locations restricts or administers phone usages, but is discussed here to remind the reader that Partition and Call Search Spaces definitions can be define after the Route Patterns have been created.

The VCCS Call Manager Route Pattern Guidelines addresses the creation of route patterns for VoIP in state calling only and does not address the creation of other route patterns that the college may deem necessary for their location.

This guideline is applicable to Call Managers implemented at the System Office, Colleges and VCC Utility.

The Guidelines assume that the reader of this document has a Call Manger that is at the software version level 3.2.2c or above. This is the version where support for Call Manager to Call Manager calling using the Gatekeeper was first introduced. The version allows the use of the Gatekeeper instead of having to create an inter-cluster trunk to communicate with another Call Manager.

GUIDELINE

The Guideline is divided into the following sections:

Screen shots of the various sections are provided as an example of how the final panel will appear once all the definitions are in place.

The Gatekeeper definitions use the IP Address of the Gatekeeper as the required name field on the Gatekeeper Definition panel. The actual Gatekeeper device is located at one of the VCC Utility host sites. The Terminal Type selection on the Gatekeeper Definition panel is Gateway. Within the Description field key in VCCS VoIP Network Gatekeeper. The Device Pool should be specified as the Default unless your site has selected to use a different region size (ulaw protocol) for your IP Phones. This Guideline recommends using the Default.

The screen shot below shows the recommended definitions to be used for the Gatekeeper section:

The second half of the Gatekeeper Definition panel is for Anonymous Calls Device. Check the box to turn Anonymous Calls on. This setting eliminates the need to configure a separate H.323 device (inter-cluster trunk) in the local Cisco Call Manager cluster for each remote Cisco Call Manager or H.323 gateway that it can call over the VoIP WAN.  For Calling Party Selection, select Originator. For Presentation Bit, select Allowed. For Num Digits, select 4. This field processes incoming calls and indicates the number of digits starting from the last digit of the called number used to route calls coming into the H.323 device. Check the box for Sig Digits. Significant digits represent the number of final digits retained on inbound calls and must be used in conjunction with Num Digits.

The screen shot below shows the recommended definitions to be used for the Anonymous Device section:

 There is no need to change any of the other fields in the Gateway and Anonymous Device sections. Please do an insert/update for the changes to take affect.

The next panel that has to be created or modified is the Router filter panel. Key in the name 7-digit-dialing and select DOES-NOT-EXIST for Local-Area-Code. These are the only changes that are required for the Route Filters panel.

The screen shot below shows the recommended definitions to be used for the Route Filter Device:

Please do an insert/update for the changes to take affect.

In-state route patterns can now be created. There are several options for creating in-state route patterns. One options is to create a route pattern for each area code for the state of Virginia.  For example, you would enter route patterns 8.804XXXXXXX, 8.540XXXXXXX, 8.703XXXXXXX, etc. Another example is a single route pattern 8.XXXXXXXXXX. While the latter example is simplistic it is not consistent with how the route patterns (VoIP dial peer statements) are defined in the college 3640-Gateway Devices. The recommendation in this Guideline is to create a route pattern for each area code. The recommendation is based on the way matching is done for route patterns. Having the area code specified allows for greater future expansion if and when VCCS collaborate with another state(s) for VoIP service.

The screen shot below shows the recommended definitions to be used for the Route Patterns:

The process will need to be repeated for each individual area code. The number 8 in front of the route pattern is used as a translation pattern that the caller never dials. The number 8 is an information number to inform the Call Manager how to handle the routing of the call. The PreDot selection for Discard Digits under the Called Party Transformations sections informs the Call Manager that the digits after the Dot are the only digits to route for the call. After entering all the required information for a route pattern, an insert/update must be performed for the Call Manager to recognize the change.

Route Pattern 8.814225XXXX is used for VCCS VoIP audio conference.  Please note that if a caller attempts to dial this special route pattern outside of the VCCS VoIP network they will receive unexpected results.

The screen shot below shows the recommended definitions to be used for the VoIP Audio Conference Route Pattern:

An insert/update must be performed for the changes to take affect.

For each route pattern that is preceded by the number "8" a translation pattern will have to be created to ensure the initial number (8) is not a required digit to be dialed by the caller.

The screen shot below shows the recommended definitions to be used for the Translation Pattern Pattern:

An insert/update must be performed for the changes to take affect. Also, there is a special translation pattern required for a Call Manager that uses the Gatekeeper to call other Call managers. The special translation pattern will ensure that the last four (4) digits (extension number) of the called number will be used.  Place the ten (10) digit number that represent the area code, exchange number and station for your IP Phones in the translation pattern field.  In the case of the System Office that pattern is 804819XXXX.  Set the Called Party Transform Masks to XXXX in the Called Party Transformations section.

The screen shot below shows the recommended definitions to be used for the special Translation Pattern:

An insert/update must be performed for the changes to take affect.

The above Guidelines will ensure commonality between all the Call Manager sites within the Virginia Community College System and allow for future expansion to communicate with other Voice over IP sites.

Return to Guideline Page