Appendix: Remapping Extension Numbers
Changing the Number of Installed Ports
Syntax and Examples
Table
Table
Wildcard | Result |
*Matches zero or more digits.
? | Matches exactly one digit. Use ? as a placeholder for a single digit. |
Table
Table | Syntax Examples |
| |
|
|
|
|
Rule |
| Original Number | New Number |
|
|
|
|
2189, 1189 |
| 2189 | 1189 |
3189, 1189 |
| 3189 | 1189 |
4189, 1189 |
| 4189 | 1189 |
|
|
|
|
2???, 1??? |
| 2189 | 1189 |
|
| 2291 | 1291 |
|
|
|
|
3???, 1??? |
| 3189 | 1189 |
|
| 3291 | 1291 |
|
|
|
|
8???, 61??? |
| 8000 | 61000 |
|
| 8765 | 61765 |
|
|
|
|
123*, 44* |
| 12300 | 4400 |
|
| 12385 | 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]
[Number Mappings] 2189, 1189 3189, 1189 4189, 1189 8???, 9???
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
| 33 |
| |
|
|