Table Of Contents

Route Pattern/Hunt Pilot Configuration

Finding a Route Pattern/Hunt Pilot

Adding a Route Pattern/Hunt Pilot

Updating a Route Pattern/Hunt Pilot

Copying a Route Pattern/Hunt Pilot

Deleting a Route Pattern/Hunt Pilot

Route Pattern/Hunt Pilot Configuration Settings

Route Pattern/Hunt Pilot Configuration

---

A route pattern/hunt pilot comprises a string of digits (an address) and a set of associated digit manipulations that can be assigned to a route list or a gateway. Route patterns and hunt pilots provide flexibility in network design. They work in conjunction with route filters and route lists to direct calls to specific devices and to include, exclude, or modify specific digit patterns.

Refer to "Understanding Route Plans" in Cisco CallManager System Guide for more detailed route pattern/hunt pilot information.

Use the following topics to add, update, copy, or delete a route pattern/hunt pilot:

•Finding a Route Pattern/Hunt Pilot

•Adding a Route Pattern/Hunt Pilot

•Updating a Route Pattern/Hunt Pilot

•Copying a Route Pattern/Hunt Pilot

•Deleting a Route Pattern/Hunt Pilot

•Route Pattern/Hunt Pilot Configuration Settings

Finding a Route Pattern/Hunt Pilot

Because you might have several route patterns/hunt pilots in your network, Cisco CallManager lets you use specific criteria to locate specific route patterns/hunt pilots. To locate route patterns/hunt pilots, use the following procedure.

---

Note During your work in a browser session, Cisco CallManager Administration retains your route pattern/hunt pilot search preferences. If you navigate to other menu items and return to this menu item, Cisco CallManager Administration retains your route pattern/hunt pilot search preferences until you modify your search or close the browser.

---

Procedure

---

Step 1 Choose Route Plan > Route Pattern/Hunt Pilot.

The Find and List Route Patterns/Hunt Pilots window displays. Use the two drop-down selection boxes to search for a route pattern.

Step 2 From the first Find Route Patterns/hunt Pilots where drop-down selection box, choose Pattern, Description, or Partition.

---

Note The criterion that you choose in this drop-down list box specifies how the list of route patterns/hunt pilots that your search generates will be sorted. For example, if you choose Description, the Description column will display as the left column of the results list.

---

Step 3 From the second Find Route Patterns/Hunt Pilots where drop-down list box, choose one of the following criteria:

•begins with

•contains

•ends with

•is exactly

•is not empty

•is empty

Step 4 Specify the appropriate search text, if applicable, and click Find. You can also specify how many items per page to display.

---

Note To find all route patterns/hunt pilots that are registered in the database, click Find without entering any search text.

---

A list of discovered route patterns/hunt pilots displays by

•Route pattern/hunt pilot icon

•Route pattern/hunt pilot

•Partition

•Description

•Route Filter

•Gateway/Route List

---

Note You can delete multiple route patterns/hunt pilots from the Find and List Route Patterns/Hunt Pilots window by checking the check boxes next to the appropriate route patterns/hunt pilots and clicking Delete Selected. You can delete all route patterns/hunt pilots in the window by checking the check box in the matching records title bar and clicking Delete Selected.

---

Step 5 Click the route pattern/hunt pilot from the list of records that matches your search criteria.

The window displays the route pattern/hunt pilot that you choose.

---

Related Topics

•Adding a Route Pattern/Hunt Pilot

•Updating a Route Pattern/Hunt Pilot

•Copying a Route Pattern/Hunt Pilot

•Deleting a Route Pattern/Hunt Pilot

•Route Pattern/Hunt Pilot Configuration Settings

Adding a Route Pattern/Hunt Pilot

This section describes how to add a route pattern/hunt pilot.

Before You Begin

Ensure that the following items are configured in Cisco CallManager:

•Gateway

•Route list

•Partition (unless you are using <None>)

•Route filter (unless you are using <None>)

---

Timesaver Assigning 8XXX to a gateway routes all directory numbers 8000 to 8999 out the gateway. Similarly, 82XX routes directory numbers 8200 to 8299. See the "Special Characters and Settings" section in the Cisco CallManager System Guide for more information about wildcards.

---

Procedure

---

Step 1 Choose Route Plan > Route Pattern/Hunt Pilot.

Step 2 Click Add a New Route Pattern/Hunt Pilot.

Step 3 Enter the appropriate settings as described in Table 21-1.

Step 4 Click Insert.

---

Note After you click Insert and the window refreshes, an (Edit) link appears in the window next to the Gateway or Route/Hunt List field. This link takes you to the Gateway Configuration or Route List Configuration window for reference, depending on whether the Gateway or Route/Hunt List field contains a gateway or a route/hunt list, so you can see the route group(s) and/or line group(s) that are included in that route/hunt list, if route group(s) or line group(s) were specified. If not, you see devices.

---

---

Related Topics

•Finding a Route Pattern/Hunt Pilot

•Route Pattern Wildcards and Special Characters, Cisco CallManager System Guide

•Adding a Route Filter, page 17-4

•Updating a Route Pattern/Hunt Pilot

•Copying a Route Pattern/Hunt Pilot

•Deleting a Route Pattern/Hunt Pilot

•Route Pattern/Hunt Pilot Configuration Settings

•Understanding Route Plans, Cisco CallManager System Guide

Updating a Route Pattern/Hunt Pilot

This section describes how to update a route pattern/hunt pilot.

Procedure

---

Step 1 Choose Route Plan > Route Pattern/Hunt Pilot.

Step 2 Locate the route pattern/hunt pilot that you want to update. See the "Finding a Route Pattern/Hunt Pilot" section.

---

Note If you change the gateway or route/hunt list, you must click Update prior to selecting the Edit link. Otherwise, you get linked to the previous gateway or route/hunt list.

---

Step 3 Update the appropriate settings as described in the "Route Pattern/Hunt Pilot Configuration Settings" section.

Step 4 Click Update.

The updated route pattern/hunt pilot displays.

---

Related Topics

•Finding a Route Pattern/Hunt Pilot

•Route Pattern Wildcards and Special Characters, Cisco CallManager System Guide

•Adding a Route Filter, page 17-4

•Adding a Route Pattern/Hunt Pilot

•Copying a Route Pattern/Hunt Pilot

•Deleting a Route Pattern/Hunt Pilot

•Route Pattern/Hunt Pilot Configuration Settings

•Understanding Route Plans, Cisco CallManager System Guide

Copying a Route Pattern/Hunt Pilot

This section describes how to copy a route pattern.

Procedure

---

Step 1 Choose Route Plan > Route Pattern/Hunt Pilot.

Step 2 Locate the route pattern/hunt pilot that you want to copy. See the "Finding a Route Pattern/Hunt Pilot" section.

Step 3 Check the check box next to the route pattern/hunt pilot that you want to copy.

Step 4 Click the Copy icon of that route pattern/hunt pilot.

The window displays the copy of the route pattern/hunt pilot.

Step 5 Update the appropriate settings as described in Table 21-1.

Step 6 To add the new route pattern/hunt pilot, click Insert.

---

Note After you click Insert and the window refreshes, an (Edit) link appears in the window next to the Gateway or Route/Hunt List field. This link takes you to the Gateway Configuration or Route/Hunt List Configuration window for reference, depending on whether the Gateway or Route/Hunt List field contains a gateway or a route/hunt list, so you can see the route group(s) and/or line group(s) that are included in that route/hunt list, if route group(s) or line group(s) were specified. If not, you see devices.

---

---

Tip You can also copy a route pattern/hunt pilot by locating and displaying the route pattern/hunt pilot that you want to copy and clicking Copy. Then, follow the instructions in Step 5 and Step 6.

---

---

Related Topics

•Finding a Route Pattern/Hunt Pilot

•Route Pattern Wildcards and Special Characters, Cisco CallManager System Guide

•Adding a Route Filter, page 17-4

•Adding a Route Pattern/Hunt Pilot

•Updating a Route Pattern/Hunt Pilot

•Deleting a Route Pattern/Hunt Pilot

•Route Pattern/Hunt Pilot Configuration Settings

•Understanding Route Plans, Cisco CallManager System Guide

Deleting a Route Pattern/Hunt Pilot

This section describes how to delete a route pattern/hunt pilot.

Procedure

---

Step 1 Choose Route Plan > Route Pattern/Hunt Pilot.

Step 2 Locate the route pattern/hunt pilot that you want to delete. See the "Finding a Route Pattern/Hunt Pilot" section.

Step 3 Check the check box of the route pattern/hunt pilot that you want to delete and click Delete Selected.

A message that displays states that you cannot undo this action.

Step 4 To delete the route pattern, click OK or to cancel the deletion, click Cancel.

---

Tip You can also delete a route pattern/hunt pilot by locating and displaying the route pattern/hunt pilot that you want to delete and clicking Delete.

---

---

Related Topics

•Finding a Route Pattern/Hunt Pilot

•Route Pattern Wildcards and Special Characters, Cisco CallManager System Guide

•Adding a Route Filter, page 17-4

•Adding a Route Pattern/Hunt Pilot

•Updating a Route Pattern/Hunt Pilot

•Copying a Route Pattern/Hunt Pilot

•Route Pattern/Hunt Pilot Configuration Settings

•Understanding Route Plans, Cisco CallManager System Guide

Route Pattern/Hunt Pilot Configuration Settings

Table 21-1 describes the available fields in the Route Pattern/Hunt Pilot Configuration window.

Table 21-1 Route Pattern/Hunt Pilot Configuration Settings 

Field	Description
Pattern Definition
Route Pattern/Hunt Pilot	Enter the route pattern/hunt pilot, including numbers and wildcards (do not use spaces); for example, for NANP, enter 9.@ for typical local access, or 8XXX for a typical private network numbering plan. Note Ensure that the directory route pattern/hunt pilot, which uses the chosen partition, route filter, and numbering plan combination, is unique. Check the route pattern/hunt pilot, translation pattern, directory number, call park number, call pickup number, message waiting on/off, or meet me number if you receive an error that indicates duplicate entries. You can also check the route plan report. •See the "Route Pattern Wildcards and Special Characters" section in the Cisco CallManager System Guide for more information about wildcards.
Partition	If you want to use a partition to restrict access to the route pattern/hunt pilot, choose the desired partition from the drop-down list box. If you do not want to restrict access to the route pattern/hunt pilot, choose <None> for the partition. See the "Partition Configuration" section for more information on how to use partitions. If more than 250 partitions exist, the ellipsis button (...) displays next to the drop-down list box. Click the ... button to display the Select Partition window. Enter a partial partition name in the List items where Name contains field. Click the desired partition name in the list of partitions that displays in the Select item to use box and click OK. Note To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters. Note Make sure that the combination of route pattern/hunt pilot, route filter, and partition is unique within the Cisco CallManager cluster.
Description	Enter a description of the route pattern/hunt pilot.
Numbering Plan	Choose a numbering plan.
Route Filter	If your route pattern/hunt pilot includes the @ wildcard, you may choose a route filter. The optional act of choosing a route filter restricts certain number patterns. The route filters that display depend on the numbering plan that you choose from the Numbering Plan drop-down list box. If more than 250 route filters exist, the ellipsis button (...) displays next to the drop-down list box. Click the ... button to display the Select Route Filters window. Enter a partial route filter name in the List items where Name contains field. Click the desired route filter name in the list of route filters that displays in the Select item to use box and click OK. Note To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters.
MLPP Precedence	Choose an MLPP precedence setting for this route pattern/hunt pilot from the drop-down list box: •Flash Override—Highest precedence setting (level 0) for MLPP calls. •Flash—Second-highest precedence setting (level 1) for MLPP calls. •Immediate—Third-highest precedence setting (level 2) for MLPP calls. •Priority—Fourth-highest precedence setting (level 3) for MLPP calls. •Routine—Lowest precedence setting (level 4) for MLPP calls. •Default—Does not override the incoming precedence level but rather lets it pass unchanged. Note Refer to the "Precedence" section in the "Multilevel Precedence and Preemption" chapter of the Cisco CallManager Features and Services Guide for more information.
Gateway or Route/Hunt List	Choose the gateway or route/hunt list for which you are adding a route pattern/hunt pilot. Note If at least one port of the defined gateway that is included in a route group does not exist, or has an assigned DN, this drop-down list box does not include that gateway. When a gateway is chosen in the drop-down list box, Cisco CallManager uses all the ports in the gateway to route/block this route pattern/hunt pilot. This action does not apply for MGCP gateways.
Route Option	The Route Option designation indicates whether you want this route pattern/hunt pilot to be used for routing calls (such as 9.@ or 8[2-9]XX) or for blocking calls. Choose the Route this pattern or Block this pattern radio button. If you choose the Block this pattern radio button, you must choose the reason for which you want this route pattern/hunt pilot to block calls. Choose a value from the drop-down list box: •No Error •Unallocated Number •Call Rejected •Number Changed •Invalid Number Format •Precedence Level Exceeded
Provide Outside Dial Tone	Check the check box if appropriate.
Allow Overlap Sending	Check the check box if appropriate.
Urgent Priority	Check the check box if appropriate.
Calling Party Transformations
Use Calling Party's External Phone Number Mask	Check the check box if you want the full, external phone number to be used for calling line identification (CLID) on outgoing calls. You may also configure an External Phone Number Mask on all phone devices. Note The calling party transformation settings that are assigned to the route groups in a route/hunt list override any calling party transformation settings that are assigned to a route pattern/hunt pilot that is associated with that route/hunt list.
Calling Party Transform Mask	Enter a transformation mask value. Valid entries for the NANP include the digits 0 through 9, the wildcard character X, the characters * and #, and blank. If this field is blank and the preceding field is not checked, no calling party transformation takes place. See the "Calling Party Number Transformations Settings" section in the Cisco CallManager System Guide for more information.
Prefix Digits (Outgoing Calls)	Enter prefix digits in the Prefix Digits (Outgoing Calls) field. Valid entries for the NANP include the digits 0 through 9, #, *, and blank. Note The appended prefix digit does not affect which directory numbers route to the assigned device.
Calling Line ID Presentation	Cisco CallManager uses calling line ID presentation (CLIP/CLIR) as a supplementary service to allow or restrict the originating caller's phone number on a call-by-call basis. Choose whether you want the Cisco CallManager to allow or restrict the display of the calling party's phone number on the called party's phone display for this route pattern. Choose Default if you do not want to change calling line ID presentation. Choose Allowed if you want Cisco CallManager to allow the display of the calling number. Choose Restricted if you want Cisco CallManager to block the display of the calling number. For more information about this field, see Table 14-6 in the "Calling Party Number Transformations Settings" section in the Cisco CallManager System Guide.
Calling Name Presentation	Cisco CallManager uses calling name presentation (CNIP/CNIR) as a supplementary service to allow or restrict the originating caller's name on a call-by-call basis. Choose whether you want the Cisco CallManager to allow or restrict the display of the calling party's name on the called party's phone display for this route pattern. Choose Default if you do not want to change calling name presentation. Choose Allowed if you want Cisco CallManager to display the calling name information. Choose Restricted if you want Cisco CallManager to block the display of the calling name information. For more information about this field, see Table 14-6 in the "Calling Party Number Transformations Settings" section in the Cisco CallManager System Guide.
Connected Party Transformations
Connected Line ID Presentation	Cisco CallManager uses connected line ID presentation (COLP/COLR) as a supplementary service to allow or restrict the called party's phone number on a call-by-call basis. Choose whether you want Cisco CallManager to allow or restrict the display of the connected party's phone number on the calling party's phone display for this route pattern. Choose Default if you do not want to change the connected line ID presentation. Choose Allowed if you want to display the connected party's phone number. Choose Restricted if you want Cisco CallManager to block the display of the connected party's phone number. For more information about this field, see Table 14-9 in the "Connected Party Presentation and Restriction Settings" section in the Cisco CallManager System Guide.
Connected Name Presentation	Cisco CallManager uses connected name presentation (CONP/CONR) as a supplementary service to allow or restrict the called party's name on a call-by-call basis. Choose whether you want Cisco CallManager to allow or restrict the display of the connected party's name on the calling party's phone display for this route pattern. Choose Default if you do not want to change the connected name presentation. Choose Allowed if you want to display the connected party's name. Choose Restricted if you want Cisco CallManager to block the display of the connected party's name. For more information about this field, see Table 14-9 in the "Connected Party Presentation and Restriction Settings" section in the Cisco CallManager System Guide.
Called Party Transformations
Discard Digits	From the Discard Digits drop-down list box, choose the discard digits instructions that you want to associate with this route pattern. The discard digits that display depend on the numbering plan that you choose from the Numbering Plan drop-down list box. See the "Discard Digits Instructions" section in the Cisco CallManager System Guide more information on discard instructions for the North American Numbering Plan. Note The called party transformation settings that are assigned to the route groups in a route/hunt list override any called party transformation settings that are assigned to a route pattern/hunt pilot that is associated with that route/hunt list.
Called Party Transform Mask	Enter a transformation mask value. Valid entries for the NANP include the digits 0 through 9, the wildcard character X, the characters * and #, and blank. If the field is blank, no transformation takes place. Cisco CallManager sends the dialed digits exactly as dialed.
Prefix Digits (Outgoing Calls)	Enter prefix digits in the Prefix Digits (Outgoing Calls) field. Valid entries for the NANP include the digits 0 through 9, #, *, and blank. Note The appended prefix digit does not affect which directory numbers route to the assigned device.
ISDN Network-Specific Facilities Information Element
Carrier Identification Code	Enter the appropriate carrier identification code (0, 3, or 4 digits) in the Carrier Identification Code field. Carrier identification codes allow customers to reach the services of interexchange carriers. The following list shows examples of commonly used carrier identification codes: •ATT—0288 •Sprint—0333 •WorldCom/MCI—0222 For a complete list of NANP carrier identification codes, go to http://www.nanpa.com/.
Network Service Protocol	From the Network Service Protocol drop-down list box, choose the PRI protocol that matches the protocol of the terminating gateway.
Network Service	Choose the appropriate network service. The values vary depending on the network service protocol that you choose from the Network Service Protocol field.
Service Parameter Name	This field displays the service parameter name that is associated with the chosen network service. If no service parameter exists for the network service, the field displays <Not Exist>.
Service Parameter Value	Enter the appropriate service parameter value. Valid entries include the digits 0 through 9. If a service parameter does not exist for the network service, Cisco CallManager Administration disables this field.

Related Topics

•Finding a Route Pattern/Hunt Pilot

•Adding a Route Pattern/Hunt Pilot

•Updating a Route Pattern/Hunt Pilot

•Copying a Route Pattern/Hunt Pilot

•Deleting a Route Pattern/Hunt Pilot