|
Short Code Programming for SCN
|
With Small Community Networking enabled, the IP Offices 'learn' each others extension numbers and route calls appropriately. However the same does not apply to dialing other numbers meant for a remote IP Office. To allow these to be routed correctly across the SCN trunk links, short codes can be used.
Scenario
We want a short code on System A which will correctly route any 3000 range number to System B. This will allow System B group numbers to be dialed from System A. To achieve the above scenario, we will add a new system short code. By using a system short code it becomes available to all users.
| 1. | Receive the configuration from System A. |
| 2. | Click Short code to display a list of existing system short codes. |
| 3. | Right-click on the displayed list and select New. |
| 4. | Enter the short code settings as follows: |
| • | Short Code: 3XXX
This will match any four-digit number beginning with 3. |
| • | Telephone Number: .
The . indicates that the short code should output the digits as dialed. |
| • | Line Group ID: 3000
This should match the Outgoing Group ID given to the IP Office SCN line connected to System B. |
| 6. | If the only change made to the configuration was this short code, load the new configuration using merge, otherwise load the configuration and reboot. |
| 7. | A similar system short code can be added to System B's configuration to route 2XXX dialing to System A. |
© 2009 AVAYA
15-601011 Issue 23.p.-
07:07, 30 October 2009
(scn_scn_short_codes.htm)
Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing
by Avaya before they become applicable to any particular order or contract. The company reserves the right to
make alterations or amendments at its own discretion. The publication of information in this document does not
imply freedom from patent or any other protective rights of Avaya or others.
All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other
trademarks are the property of their respective owners.
Last Modified: 29/04/2009
|