SIP URI Number Translation provides a mechanism to map names to directory numbers. This bridges the gap between telephony calls established between two directory numbers and SIP-type calls established between user account names.
The 3300 ICP Administrator uses the URI/Number Translation form and imports the .csv file of Active Directory (AD) URI/Number entries into the 3300 ICP database (see Programming below).
If URI/Number Translation is enabled for the SIP Peer, outbound SIP calls perform a check on the dialed digits for a match. If a match is found, the number is translated into a URI and appropriate SIP headers are created using the name. If a match is not found, the call proceeds normally according to the current SIP functionality, using dialed digits to form the URI.
Likewise, all inbound SIP calls with URI/Number Translation enabled, perform a check on a received user URI for a match. If a match is found, then the URI is translated to the associated number and sent to 3300 ICP call control. If a match is not found, the call proceeds normally according to the current SIP functionality.
For Release 7.1, only one Live Communication Server (LCS) can be connected to the 3300 ICP.
Only 3300 ICPs directly connected via a SIP link to an LCS require this translation.
This translation functionality only applies to calls going to/from the 3300 ICP to/from the LCS.
If there are more than two 3300 ICPs connected to the LCS, URI/Number translation needs to be enabled on both 3300 ICPs.
The .csv file of all PC-to-Phone users on the LCS is required. If the .csv file contains more than 1000 URI/Number pairs, only the first 1000 are imported.
The .csv file is not shared with other 3300 ICP's.
Active Directory allows the SIP URI field to be 454 character long, and the telephone number to be 66 digits. The URI/Number Translation form limits the SIP URI to 256 characters, and the maximum digits to 30 (maximum E.164 number).
The URI appears first followed by the extension number. Also, the beginning of the .csv file must contain the View name, View id, and the 3300 ICP software load number. In order to create the .csv file in the proper format, it is recommended that an entry be added in the URI/Number Translation form and be exported to a .csv file. Then, the customer data can be added to this file.
The .csv file entries are in the following format: "URI", "directoryNumber", CR/LF (carriage return/line feed)
An example of a .csv file format is shown here:
URI/Number Translation,vid1.65,7.1.2.2
0,1,
URI,User Number,
AdamMair@nhl.com,30888,
AdamsKevyn@nhl.com,3270,
AebischerDavid@nhl.com,3577,
AfanasenkovDmitry@nhl.com,3165,
WhitneyRyan@nhl.com,3566,
WiemerJason@nhl.com,3291,
WilliamsJason@nhl.com,3297,
WilliamsJustin@nhl.com,3370,
To import data from the .csv file into the 3300 ICP (new installation):
Obtain the .csv file containing the Office Communicator's URIs and routable telephone numbers.
Create a template .csv file.
In the URI/Number Translation form add a dummy entry and then press Export. This creates a .csv file with the view name, view id, and 3300 ICP software load and the dummy entry.
Copy the data from the Office Communicator .csv file into this template .csv file.
Import the .csv file into the 3300 ICP using the URI/Number Translation form
Remove any existing entries in the URI/Number Translation form by pressing the Delete button.
Press Import and then enter the name of the .csv file or use Browse to find the file.
Press Next to validate the data. You could receive warning messages (see notes below).
Press Import to import the file.
Notes:
If the file contains more than 1000 URI/User Number entries, a warning window appears. Only the first 1000 entries are imported.
Entries in the URI/Number Translation form must be unique. There can be only one occurrence of a URI and one occurrence of a number in the table. Multiple URI's assigned to a single number or multiple numbers associated to a single URI are not allowed. You can use the Search capability in this form to search for a URI.
If there are duplicate entries, open the .csv file and make the corrections. Re-import the data by repeating Step 4 above.
When there are updates or changes to the PC-to-Phone users in the AD, these changes can be made in the .csv file and then be imported again. The following procedure is recommended:
Export the current data in the URI/Number Translation form into a backup .csv file.
Use Microsoft Excel to compare the backup .csv file with the new .csv file (with updates from the AD) and resolve any conflicts.
Delete any existing entries in the URI/Number Translation form by using Range Programming Delete.
Import the new .csv file, following step 4 in the above procedure.
