Emergin
Upgrading Existing Nortel and SpectraLink Installations for Extension Mapping
Description:
The extension-mapping feature allows OAI Open Application Interface - Manufacturer specific protocol. (SpectraLink/Avaya), CAT (Nortel Companion) and VMTP Vocera Mail Transfer Protocol - Designed by Emergin, this protocol communicates with the Vocera system software, which controls the wireless Vocera communications badges. This uses the Emergin "Carrier Extension Mapping" to assign users an ID and a numeric extension to these devices. (See www.vocera.com for more information) (Vocera) carriers to maintain a mapping of extensions to protocol specific identifiers without the need for creating user profiles.
OAI, CAT and Vocera carriers can map phone extensions into identifiers required by the protocol:
- OAI requires a port identifier
- CAT requires a WTN
- Vocera requires an alphanumeric name
An extension map editor has been added to the properties for each of these carriers to allow entries to be added, edited and deleted.
Reason for change:
OAI and CAT installations have been using user profiles to map each extension to another identifier. The user profiles have been created with numeric extension numbers as their names, and Alarm Messenger has been configured to extract users from input. The creation of these users requires customers to purchase additional user licenses and has added additional configuration steps for the integrator.
How to Upgrade Existing Installations:
OAI Installation:
Existing installations have:
· User profiles with extension numbers as their profile names. Each user profile contains a single device, which is configured with an extension and a port identifier.
· Alarm Messenger has been configured to extract users from input.
This build recognizes OAI devices and automatically converts the database for use with extension mapping.
Upgrade steps:
1. Make a backup of the server and alarm messenger database.
2. Upgrade to the 102903 build.
Option 1: No changes to Alarm Messenger, keep the user profiles.
This option requires no configuration changes. The devices inside the user profiles are converted to work with extension mapping automatically during the upgrade. Double-check the upgrade by viewing the extension map in the OAI carrier:
1. Open the Administrator to the Carriers tab.
2. Double-click the OAI carrier and switch to the 'OAI Settings' tab.
3. Click the 'Extension;' button.
4. Review each extension and port for correctness.
5. Each extension should have a user icon beside it, indicating the device is owned by a user profile.
6. Review the Ring Types for each extension for correctness.
Everything should work as before. When users are paged, their PINs are mapped to port identifiers automatically.
Option 2: Change Alarm Messenger to extract PIN/carrier, remove user profiles.
This option requires changes on Alarm Messenger and the removal of the user profiles. It's more work, but much cleaner.
1. Change Alarm Messenger to use extract PIN from input instead of extract user from input for each alert.
2. Open the Administrator to the User's tab.
3. For each user profile that is named for an extension:
a. Make a note of the user profile name (the Extension) and the PIN number (port identifier) of its device.
b. Delete the user profile.
4. Change to the Carriers tab.
5. Double-click the OAI carrier and switch to the 'OAI Settings' tab.
6. Click the 'Extension' button.
7. For each extension from step 3:
a. Click the button
b. Enter the Extension
c. Click the button and use the controls to set the Port. Click OK.
d. Select the Ring Type.
e. Click OK.
Setup is completed. When these extensions are extracted from Alarm Messenger and sent to this carrier, they are mapped to port identifiers automatically.
CAT Installation:
Existing installations have:
· User profiles with extension numbers as their profile name. Each user profile contains a device with the PIN number corresponding to the handset's WTN. Extension information is not currently stored in the device settings.
· Alarm Messenger has been configured to extract users from input.
Upgrade steps:
1. Make a backup of the server and alarm messenger database.
2. Upgrade to the 102903 build.
Option 1: No changes to Alarm Messenger, keep the user profiles.
This option requires the least amount of work and doesn't change Alarm Messenger.
1. Open the Administrator to the User's tab.
2. For each user profile that is named for an extension:
a. Edit the device. Make a note of the number displayed in the 'Extension' field. This is the WTN that we'll need in step d).
b. Click the 'Edit' button.
c. Enter the extension in the 'Extension' field.
d. Enter the WTN in the 'WTN' field.
e. Click OK.
f. Repeat for each user.
Setup is completed. When messages are sent to these users, their PINs are mapped to WTNs automatically.
Option 2: Change Alarm Messenger to extract PIN/carrier, remove user profiles.
This option requires changes on Alarm Messenger and the removal of the user profiles. It's more work, but much cleaner.
1. Change Alarm Messenger to use extract PIN from input instead of extract user from input for each alert.
2. Open the Administrator to the User's tab.
3. For each user profile that is named for an extension:
a. Make a note of the user profile name (the Extension) and the PIN number (WTN) of its device.
b. Delete the user profile.
4. Change to the Carriers tab.
5. Double-click the CAT carrier and switch to the 'Nortel Settings' tab.
6. Click the 'Extension Map&ldots;" button.
7. For each extension:
a. Click the 'Add&ldots;' button
b. Enter the Extension and WTN.
c. Click OK.
Setup is completed. When these extensions are extracted from Alarm Messenger and sent to this carrier, they are mapped to WTNs automatically.