Step 1 Designate primary phone numbers
Enterprise Voice integrates voice with other messaging media, such that when an incoming call arrives at the server, the server maps the number to the users SIP-URI and then forks the call to all the client endpoints associated with that SIP-URI. This process, known as reverse number lookup, requires that each user be associated with a primary phone number.
A Primary Phone Number must be:
-
Globally unique or, in the case of internal extensions, unique in the enterprise.
-
Owned by and routable in the enterprise. Personal numbers should not be used.
Enterprise users may have two or more telephone numbers listed for them in Active Directory. All the telephone numbers associated with a particular user can be viewed or changed on the property sheet for that user in the Active Directory Users and Computers snap-in.
The Telephone number text box on the General tab of the User Properties dialog box should contain the users main work number. This number will usually be designated as the user's Primary Phone Number.
Certain users may have exceptional requirements (for example, an executive who wants all incoming calls routed through an administrative assistant), but such exceptions should be limited only to those where the need is clear and critical.
Once a primary number is chosen, it must be:
-
Normalized to E.164 format
-
Copied to the Active Directory msRTCSIP-line attribute
.gif) Note: |
|---|
|
Coexisting with Remote Call Control. Remote call control is the ability to use Office Communicator to monitor and control a desktop PBX phone. Control is routed through the server, which acts as a gateway to the PBX. Remote call control first became available with Live Communications Server 2005 with SP1 and Communicator 1.0. Communications Server 2007 and Communicator 2007 together continue to provide remote call control to users who are not enabled for Enterprise Voice.
If you have enabled remote call control in your organization, you know that remote call control also uses the msRTCSIP-line attribute to designate the primary phone number for users. If your organization will have some users enabled for Enterprise Voice and others, perhaps most, still connected to a PBX, you may be concerned about whether Enterprise Voice and remote call control can coexist.
|
There are two methods for populating the msRTCSIP-line attribute:
-
Advanced settings in the Office Communications Server snap-in for the Active Directory Users and Computers management console.
-
MIIS (Microsoft Identity Integration Server) or WMI (Windows Management Instrumentation) scripts. MIIS is recommended for this purpose.
Where many phone numbers must be processed, a script is the obvious choice. Depending on how your organization represents telephone numbers in Active Directory, the script may have to normalize primary phone numbers to E.164 format before copying them to the msRTCSIP-line attribute.
-
If your organization maintains all telephone numbers in Active Directory in a single format, and if that format is E.164, then your script only needs to write each Primary Telephone Number to the msRTCSIP-line attribute.
-
If your organization maintains all telephone numbers in Active Directory in a single format, but that format is not E.164, then your script should define an appropriate normalization rule to convert Primary Telephone Numbers from their existing format to E.164 before writing them to the msRTCSIP-line attribute.
-
If your organization does not enforce a standard format for telephone numbers in Active Directory, then your script should define appropriate normalization rules to convert Primary Phone Numbers from their various formats to E.164 compliance before writing the Primary Telephone Numbers to the msRTCSIP-line attribute.
Your script will also have to insert the prefix Tel: before each primary number before writing it to the msRTCSIP-line attribute.
The expected format of the number specified in this attribute is:
-
Tel:+14255550100;ext=50100.
-
Tel:5550100 (for unique enterprise wide extensions)
| Important: |
|---|
|
The normalization performed by ABS does not replace or otherwise eliminate the need to normalize each user's primary phone number in Active Directory because ABS does not have access to Active Directory and therefore cannot copy primary numbers to the msRTCSIP-line attribute.
|