NEC NEAX 2400 with Serial MCI Integration Guide for Cisco Unity 3.0
Remapping Extension Numbers

Table Of Contents

Remapping Extension Numbers

The Remapping Feature

Setting Up Cisco Unity to Remap Extension Numbers

Syntax and Examples


Remapping Extension Numbers


The Remapping Feature

The extension remapping feature lets you convert the calling numbers and forwarding numbers of calls that Cisco Unity handles to the extensions of your choice. This feature is useful, for example, when the phone system cannot map multiple extension numbers on a subscriber's phone to a single Inbox.

Remapping can change one or both of the following extension numbers in a call:

Calling number (the number from which a call originates). For example, Cisco Unity changes the calling number of calls that the phone system sends it so that the caller ID appears to be a different extension than the one that actually placed the call.

Forwarding number (the number that a call is going to). For example, unanswered calls to all line extensions on a single phone can be forwarded to the Inbox of a single subscriber; or unanswered calls to phones not assigned to subscribers can be forwarded to the Inbox of a supervisor.

Setting Up Cisco Unity to Remap Extension Numbers

This section includes a procedure for enabling the remapping feature. There are also examples of extension remapping syntax.

By performing the procedure, you can create multiple files in either or both of two directories:

In the Calling directory, one or more .exm files remap caller ID numbers.

In the Forwarding directory, one or more .exm files remap numbers that Cisco Unity provides with calls it forwards.

Creating remapping instructions in an .exm file in a directory remaps only the type of extension number that the directory is named for. For example, if you want to remap only the extensions that Cisco Unity provides with calls it forwards, you must enter the instructions in an .exm file in the Forwarding directory; the Calling directory needs no file in this case.

In each directory, you can have several .exm files with different file names but the same .exm extension to help organize the remapping information (for example, Ports_1-12.exm and Ports_13-24.exm). Cisco Unity reads all files that have the .exm extension in these directories.

To remap extension numbers


Step 1 On the Cisco Unity server, browse to the CommServer\IntLib\ExtensionMapping directory. In this directory is the file Sample.txt and two more directories: Calling and Forwarding.

Step 2 To remap calling numbers, go to the Calling directory.

Step 3 Using a text editor, create (or open) an .exm file in one directory.

For a sample file, see the file Sample.txt in the CommServer\IntLib\ExtensionMapping directory. To create a section for indicating which voice messaging ports will be monitored for remapping calls, enter [Range] and press Return.

An .exm file can have only one [Range] section.

Step 4 Enter ports= followed by the numbers of the voice messaging ports separated by commas. Ranges are designated by a hyphen (-) without spaces. To monitor all voice messaging ports, enter ports=* on this line. Then press Return.

For example, you might enter:

ports=1,2,5-34,10

Step 5 To create a section for the remapping rules, press Return, enter [Number Mappings], and then press Return.

An .exm file can have only one [Number Mappings] section.

Step 6 Using the wildcards and examples in the following "Syntax and Examples" section, enter one remapping rule on the line. Then press Return. The rule format is:

<original number>, <new number>

The rules cannot include spaces between digits. However, the numbers must be separated by a comma and a single space. Wildcard characters cannot appear at the beginning of a number.

Step 7 For all remaining rules, repeat Step 6.

Step 8 Save and close the .exm file.

Step 9 To remap forwarding numbers, go to the directory CommServer\IntLib\ExtensionMapping\Forwarding.

Step 10 Perform Steps 3 through 8.

Step 11 For extension remapping to take effect, restart the Cisco Unity software. For more information, see Appendix A, "Exiting and Starting the Cisco Unity Software and Server."


Syntax and Examples

Table B-1 lists the wildcard characters you can use in the .exm files.

Table B-1 Wildcard Characters

Wildcard
Result

*

Matches zero or more digits.

?

Matches exactly one digit. Use ? as a placeholder for a single digit.


Table B-2 gives examples for the syntax and results of rules in the .exm files.

Table B-2 Syntax Examples

Rule
Original Number
New Number

2189, 1189

3189, 1189

4189, 1189

2189

3189

4189

1189

1189

1189

2???, 1???

2189

2291

1189

1291

3???, 1???

3189

3291

1189

1291

8???, 61???

8000

8765

61000

61765

123*, 44*

12300

12385

4400

4485


Cisco Unity executes rules in the order they appear in the .exm file. For example, the .exm file might contain the following rules:

1234, 1189
3189, 1189
4189, 1189
123?, 8891

The extension 1234 would be remapped to 1189 while extensions 1233 and 1235 would be remapped to 8891, because the rule mapping 1234 appears earlier.

An .exm file might contain the following:

[Range]
ports=1,2,5-34,10

[Number Mappings]
2189, 1189
3189, 1189
4189, 1189
8???, 9???