400 likes | 721 Views
Exchange 2010 Unified Messaging. The Exchange 2010 Unified Messaging has the following goals:Review of Exchange Server 2010 Unified Messaging fundamentalsOverview of Exchange Server 2010 Unified Messaging migrationExchange Server 2010 Unified Messaging administration. Ideal audience for this
E N D
1. Exchange Deployment Planning Services Key Message
The goal of this presentation is to provide the audience with a basic understanding of Exchange 2010 Unified MessagingKey Message
The goal of this presentation is to provide the audience with a basic understanding of Exchange 2010 Unified Messaging
2. Exchange 2010 Unified Messaging Slide Objective: To explain the overall goals of the Exchange 2010 Unified Messaging
Instructor Notes:
This module will cover ExchangeSlide Objective: To explain the overall goals of the Exchange 2010 Unified Messaging
Instructor Notes:
This module will cover Exchange
3. Exchange 2010 Unified Messaging Slide Objective: To show the ideal audience for this module.
Instructor Notes:
This is the recommended audience for the module. Do not be overly concerned if the group does not match the ideal audience. During your time onsite you can have conversations with different resources to get questions answered.
Slide Objective: To show the ideal audience for this module.
Instructor Notes:
This is the recommended audience for the module. Do not be overly concerned if the group does not match the ideal audience. During your time onsite you can have conversations with different resources to get questions answered.
4. Exchange 2010 Unified Messaging Slide Objective: To show the audience what to focus on during the module.
Instructor Notes:
Slide Objective: To show the audience what to focus on during the module.
Instructor Notes:
5. Agenda Background
Architecture
How Microsoft® Exchange UM is used at Microsoft
Exchange 2010 UM
Migration
Features
Questions Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes:
6. ArchitectureIn the Enterprise, Same Architecture as Exchange Server 2007 UM protocols
SIP/RTP to gateway/PBX
LDAP to the directory
MAPI/RPC to mailboxes
Can place UM servers distant from PBXs
Support scale out and server consolidation Slide Objective:
Instructor Notes:
Exchange UM architecture for enterprise deployments has not changed significantly in Exchange 2010.
UM uses VoIP protocols to communicate its signaling and media: SIP/(TCP or TLS) and (RTP or SRTP)/UDP. These protocols work well even when network latency is high (500 ms round trip) and packet loss is significant (up to 3%): this means that UM can be placed at considerable distance (hundreds or even thousands of miles) from the PBX or IP PBX.
UM’s scale-out architecture (multiple UM servers can handle calls for a given UM Dial Plan) combines well with its support for server consolidation (any UM Server can belong to multiple Dial Plans). UM can successfully be deployed in centralized and decentralized topologies.Slide Objective:
Instructor Notes:
Exchange UM architecture for enterprise deployments has not changed significantly in Exchange 2010.
UM uses VoIP protocols to communicate its signaling and media: SIP/(TCP or TLS) and (RTP or SRTP)/UDP. These protocols work well even when network latency is high (500 ms round trip) and packet loss is significant (up to 3%): this means that UM can be placed at considerable distance (hundreds or even thousands of miles) from the PBX or IP PBX.
UM’s scale-out architecture (multiple UM servers can handle calls for a given UM Dial Plan) combines well with its support for server consolidation (any UM Server can belong to multiple Dial Plans). UM can successfully be deployed in centralized and decentralized topologies.
7. Exchange 2010 UM Architecture Slide Objective:
Instructor Notes:
OCS Front EndSlide Objective:
Instructor Notes:
OCS Front End
8. PBX On-premise, UM hosted Mid-to-large companies own PBXs, but may want Exchange and UM to be hosted
Public network between PBX and UM Slide Objective:
Instructor Notes:
This solution requires using Session Border Controller (SBCs).Slide Objective:
Instructor Notes:
This solution requires using Session Border Controller (SBCs).
9. Exchange UM in MicrosoftStatistics from U.S. Corporate Dial Plans UM mainly used for call answering
About 2 in 3 of these are “missed calls”
Slide Objective:
Instructor Notes:
In a typical week for Microsoft’s US corporate Dial Plans, the four UM servers handle over a quarter of a million telephone calls. These can be divided into (a) call answering, where the called user did not answer and the call went to “voice mail” (i.e., UM), (b) Automated Attendant, where the caller tries to identify and contact a user by name or number, and (c) Outlook Voice Access, where UM-enabled users (subscribers) log in over the phone to check voice mail, e-mail, calendar, etc. Note that the number of calls for purposes of call answering is nearly 70 times more than the number of Outlook Voice Access calls.Slide Objective:
Instructor Notes:
In a typical week for Microsoft’s US corporate Dial Plans, the four UM servers handle over a quarter of a million telephone calls. These can be divided into (a) call answering, where the called user did not answer and the call went to “voice mail” (i.e., UM), (b) Automated Attendant, where the caller tries to identify and contact a user by name or number, and (c) Outlook Voice Access, where UM-enabled users (subscribers) log in over the phone to check voice mail, e-mail, calendar, etc. Note that the number of calls for purposes of call answering is nearly 70 times more than the number of Outlook Voice Access calls.
10. Migration from Exchange Server 2007 Principles governing migration of UM-enabled mailboxes to Exchange 2010
How it works
Known limitations and issues Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes:
11. Migration from Exchange Server 2007 UM 2010 requires mailbox, transport 2010 Slide Objective:
Instructor Notes:
When migrating to Exchange 2010 UM from Exchange Server 2007 UM, the underlying principle is that UM 2010 will not work directly against an Exchange Server 2007 mailbox. If a UM 2010 server finds itself handling a call for a user whose mailbox is Exchange Server 2007, it will immediately try to hand off the call to a UM 2007 server in the same Dial Plan. Therefore, customers must retain at least one UM 2007 server in any Dial Plan in which users have Exchange Server 2007 mailboxes.
IP gateways should be reconfigured to send calls only to UM 2010 servers: these will redirect, if necessary, to UM 2007 servers. (Redirection does not work from UM 2007 to 2010.) UM 2007 servers must be at SP2 (or later). UM-enabled users do not need to be reconfigured unless they are in an OCS (SIP) Dial Plan. In this case, a new Dial Plan must be created, and UM servers (2010 and, if necessary, 2007) must be configured to handle calls for the new Dial Plan. UM-enabled users who use OCS for enterprise voice must then be UM-disabled in the old UM Dial Plan and re-enabled in the new UM Dial Plan.Slide Objective:
Instructor Notes:
When migrating to Exchange 2010 UM from Exchange Server 2007 UM, the underlying principle is that UM 2010 will not work directly against an Exchange Server 2007 mailbox. If a UM 2010 server finds itself handling a call for a user whose mailbox is Exchange Server 2007, it will immediately try to hand off the call to a UM 2007 server in the same Dial Plan. Therefore, customers must retain at least one UM 2007 server in any Dial Plan in which users have Exchange Server 2007 mailboxes.
IP gateways should be reconfigured to send calls only to UM 2010 servers: these will redirect, if necessary, to UM 2007 servers. (Redirection does not work from UM 2007 to 2010.) UM 2007 servers must be at SP2 (or later). UM-enabled users do not need to be reconfigured unless they are in an OCS (SIP) Dial Plan. In this case, a new Dial Plan must be created, and UM servers (2010 and, if necessary, 2007) must be configured to handle calls for the new Dial Plan. UM-enabled users who use OCS for enterprise voice must then be UM-disabled in the old UM Dial Plan and re-enabled in the new UM Dial Plan.
12. Migration from Exchange Server 2007Principles Governing Migration Require upgrade to Exchange Server 2007 SP2
UM 2010 servers can only access Exchange 2010 UM-enabled mailboxes
Exchange Server 2007 UM-enabled mailboxes must be accessed by UM 2007 SP2
Access means:
Call answering (leaving voice messages)
Outlook Voice Access (for subscribers) Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes:
13. Migration from Exchange Server 2007Known Limitations and Issues Must keep at least one UM 2007 SP2 server in the Dial Plan until all UM-enabled 2007 mailboxes have been migrated
Can keep the same Dial Plan and pilot number if gateway sends calls to UM 2010
Should administer with 2010 management tools Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes:
14. Administrative ChangesRoles UM now uses Exchange RBAC
Three UM administrative roles, as shipped
UM administrator
Administer any and all UM functionality
UM recipient administrator
Provision UM mailbox, PIN reset, clear lockout
UM prompt administrator
Update Dial Plan and/or Auto Attendant prompts
Custom roles may be created Slide Objective:
Instructor Notes:
Many enterprises wish to separate voice mail-style administration from e-mail administration (often because different people will perform the respective tasks). UM now supplies three administrative roles out of the box and more can be created.Slide Objective:
Instructor Notes:
Many enterprises wish to separate voice mail-style administration from e-mail administration (often because different people will perform the respective tasks). UM now supplies three administrative roles out of the box and more can be created.
15. Fax SupportChanges Exchange Server 2007 UM supported inbound fax
Delivered to users’ mailboxes
No specialized routing software
No outbound fax
UM customers mostly used other fax products
Exchange 2010 UM will not create fax messages
Partner Fax Servers for Exchange 2010 integration
UM can hand fax calls off to partner solution
UM configuration slightly extended (for partner URI)
Partner connections are authenticated by Exchange (sender ID, receive connector, TLS
Slide Objective:
Instructor Notes:
UM 2010 will not create fax messages. In the beta, it is not possible to use UM as a front end to fax message creation, so customers who have been using it for one-number fax will find this does not work. By the time Exchange 2010 is released, we plan to support fax creation with partner products. UM will hand off calls in which fax tone is detected to configured partner solutions (on-premise or hosted), which will create the fax messages.Slide Objective:
Instructor Notes:
UM 2010 will not create fax messages. In the beta, it is not possible to use UM as a front end to fax message creation, so customers who have been using it for one-number fax will find this does not work. By the time Exchange 2010 is released, we plan to support fax creation with partner products. UM will hand off calls in which fax tone is detected to configured partner solutions (on-premise or hosted), which will create the fax messages.
16. International Support Each UM language pack to contain:
Prerecorded prompts
Text-to-speech (now using Microsoft engine)
Speech recognition (command/control, names) Slide Objective:
Instructor Notes:
List of Language Packs
http://technet.microsoft.com/en-us/library/bb124728.aspx
Slide Objective:
Instructor Notes:
List of Language Packs
http://technet.microsoft.com/en-us/library/bb124728.aspx
17. Codec Support MP3 (codec and file format) is now the default for recording voice messages
Socializes more easily with non-Windows and non-Windows Mobile mail clients Slide Objective:
Instructor Notes:
MP3 is now the default recording codec for new UM Dial Plans (existing Dial Plans can be configured to use it, if required).Slide Objective:
Instructor Notes:
MP3 is now the default recording codec for new UM Dial Plans (existing Dial Plans can be configured to use it, if required).
18. Caller ID Lookup Improvements Failure to resolve caller ID to a name is a major source of complaint by end users
Numbering plan split across UM Dial Plans
Added EquivalentDialPlanPhoneContexts on DP
FQDN of other DPs in same numbering plan
Many non UM-enabled users have more than one phone number
msRTCSIP-Line is not multi-valued
Added UMCallingLineIds to User object
See http://technet.microsoft.com/en-us/library/dd351203.aspx for details Slide Objective:
Instructor Notes:
UM does not always resolve calling line ID to an AD DS user or personal contact. There can be many reasons for this.
In UM 2010, the strategy for calling line ID resolution has been extended in several ways. Where extension numbers in multiple UM Dial Plans form a consistent numbering plan, each Dial Plan can be configured to “know” about the other Dial Plans that share the common numbering plan. UM will then try to resolve the calling line ID in any of the Dial Plans (not just that of the called party, as previously). UM in Exchange Server 2007 will use the msRTCSIP-Line AD DS attribute to try to look up calling line ID. However, this attribute is only present when OCS has been installed, and is single valued. In UM 2010, UM will also try to resolve against the (new) UMCallingLineIDs attribute on the User object. This is multi-valued, and does not depend on the user being UM- or UC-enabled.Slide Objective:
Instructor Notes:
UM does not always resolve calling line ID to an AD DS user or personal contact. There can be many reasons for this.
In UM 2010, the strategy for calling line ID resolution has been extended in several ways. Where extension numbers in multiple UM Dial Plans form a consistent numbering plan, each Dial Plan can be configured to “know” about the other Dial Plans that share the common numbering plan. UM will then try to resolve the calling line ID in any of the Dial Plans (not just that of the called party, as previously). UM in Exchange Server 2007 will use the msRTCSIP-Line AD DS attribute to try to look up calling line ID. However, this attribute is only present when OCS has been installed, and is single valued. In UM 2010, UM will also try to resolve against the (new) UMCallingLineIDs attribute on the User object. This is multi-valued, and does not depend on the user being UM- or UC-enabled.
19. Call Answering RulesFormerly Known As Personal Auto Attendant Call answer is UM’s most frequent scenario
Play greeting, take message
Users wanted more control
e.g., special greetings by contact, time of day
Call answering rules
Condition: if it evaluates to true, then run…
Greeting and menu: collect caller's choice of…
Action: transfer, "Find me" or leave message Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes:
20. Message Waiting Indicator Changes to MWI Support Exchange Server 2007 UM did not support MWI
Third-party solutions required
Exchange 2010 UM supports MWI natively
Configure through UM Mailbox Policy
ON by default
No new roles
Highly scalable
MWI via SMS
Requires mail gateway Slide Objective:
Instructor Notes:
MWI is supported natively by Exchange 2010 Unified Messaging (previously, partner solutions were required). No new Exchange roles are required. Properties on the UM Mailbox Policy (true/false) and UM IP Gateway (true/false) objects control the behavior. The UM server will send SIP NOTIFY messages through any gateway in the Dial Plan configured for use. If the user has set up text messaging, they can configure message waiting notifications via SMS. Slide Objective:
Instructor Notes:
MWI is supported natively by Exchange 2010 Unified Messaging (previously, partner solutions were required). No new Exchange roles are required. Properties on the UM Mailbox Policy (true/false) and UM IP Gateway (true/false) objects control the behavior. The UM server will send SIP NOTIFY messages through any gateway in the Dial Plan configured for use. If the user has set up text messaging, they can configure message waiting notifications via SMS.
21. Voice Mail Preview: 1 of 3Quickly Triage Voice Messages Speech recognition applied to voice mail
Searchable
Beginning of preview shown in SMS MWI Slide Objective:
Instructor Notes:
Voice mail Preview can provide an embedded text version of the voice message, when it is delivered. The goal is to allow the recipient to understand the significance of the message without necessarily having to listen to it. However, the speech recognition is usually less than completely correct, so this feature is not intended to support dictation or transcription.
The preview text is automatically searchable. The beginning of the preview will be provided in SMS MWI, if the user has enabled this kind of notification. Outlook “14” will provide some significant additional UI features when presenting Voice Mail Preview. For example, clicking on the text will set the audio playback position.Slide Objective:
Instructor Notes:
Voice mail Preview can provide an embedded text version of the voice message, when it is delivered. The goal is to allow the recipient to understand the significance of the message without necessarily having to listen to it. However, the speech recognition is usually less than completely correct, so this feature is not intended to support dictation or transcription.
The preview text is automatically searchable. The beginning of the preview will be provided in SMS MWI, if the user has enabled this kind of notification. Outlook “14” will provide some significant additional UI features when presenting Voice Mail Preview. For example, clicking on the text will set the audio playback position.
22. Voice Mail Preview: 2 of 3Details RTM includes U.S. English, French (France) and Italian
SP1 adds English (Canada), Polish, Portuguese (Portugal), Spanish (Spain)
Accuracy is not 100%
Average ~75% for en-US, less for other languages
"Your mileage may vary“
Controlled by UM mailbox policy
Uses Dial Plan default language Slide Objective:
Instructor Notes: Slide Objective:
Instructor Notes:
23. Voice Mail Preview: 3 of 3Transcription = Intensive Calculation CPU-intensive: affects UM scalability
Throttled: UM will skip transcription if too busy
Estimate ~1 VM/min/core as throughput Slide Objective:
Instructor Notes:
Speech recognition for voice mail Preview uses much more CPU than UM consumes for other uses of speech recognition (command and control, names). UM will skip the creation of a voice mail preview if it would delay the delivery of the message too much. So, if resources are insufficient, many voice messages will be delivered without a preview.Slide Objective:
Instructor Notes:
Speech recognition for voice mail Preview uses much more CPU than UM consumes for other uses of speech recognition (command and control, names). UM will skip the creation of a voice mail preview if it would delay the delivery of the message too much. So, if resources are insufficient, many voice messages will be delivered without a preview.
24. Protected Voice Mail: 1 of 3UM Observes Voice Mail Privacy Conventions Exchange Server 2007 UM doesn’t have private voice mail
Deployment blocker for some customers
Some voice messages are sensitive
Caller may have marked the message private
Some users receive nothing but sensitive voice mails
Treat voice mail as special case of e-mail
E-mail can already be protected
IRM
UM will use the same approach Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes:
25. Protected Voice Mail: 2 of 3 Controlled by UM mailbox policy
Requires AD DS RMS
Private: protect if sender marks message private
All: protect all messages (don't ask sender)
Always uses Do Not Forward permissions
RequireProtectedPlayOnPhone property
Blocks use of multimedia: no voice data on client
Slide Objective:
Instructor Notes:
The RequireProtectedPlayOnPhone flag was added to meet requirements from customers who did not want decrypted audio to be present (even transiently) on user’s PCs. Outlook Voice Access will allow playback of protected voice messages. If this, or play-on-phone is used, the decrypted audio is only present briefly on the UM server.Slide Objective:
Instructor Notes:
The RequireProtectedPlayOnPhone flag was added to meet requirements from customers who did not want decrypted audio to be present (even transiently) on user’s PCs. Outlook Voice Access will allow playback of protected voice messages. If this, or play-on-phone is used, the decrypted audio is only present briefly on the UM server.
26. Protected Voice Mail: 3 of 3 Requires rights management-aware client interface that also supports Exchange UM
Outlook Voice Access (Exchange UM TUI/VUI)
Outlook Web App (Exchange 2010)
Outlook 2010
Does not work:
Outlook 2007
Windows Mobile 6.1
Windows Mobile 6.5 Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes:
27. Improvements in SP1 UM reporting
The reports for Call Statistics and User Call Logs found in the Exchange Management Console are displayed in the Exchange Control Panel
UM management in the Exchange Control Panel
You can use ECP to manage UM components in a cross-premises environment
Cross-Forest UM-enabled mailbox migration
You can use the New-MoveRequest cmdlet with the Mailbox Replication Service (MRS) to move a UM-enabled mailbox within a local forest and multiple forests in an enterprise
28. Improvements in SP1 Outlook Voice Access improvements
Outlook Voice Access users can log on to their Exchange 2010 mailbox and choose the order to listen to unread voice mail messages, from the oldest message first or the newest message first
Caller Name Display support
Support for enhanced caller ID resolution for displaying names for voice mails from unresolved numbers using Caller Name Display (CND)
Test-ExchangeUMCallFlow cmdlet
Use to test UM connectivity and call flow
29. Improvements in SP1 New UM Dial Plan wizard
An additional page has been added to the New UM Dial Plan wizard that allows you to add a UM server to the dial plan
Lync Server 2010 Support
Migrating SIP URI dial plans and Message Waiting Indicator (MWI) notifications in a cross-premises environment has been added
Secondary UM dial plan support
You can add a secondary UM dial plan for a UM-enabled user
30. Improvements in SP1 UM language packs added
New UM language packs are now available. In addition, the Spanish (Spain) (es-ES) UM language pack available for Exchange 2010 SP1 now includes Voice Mail Preview, a feature that wasn’t available in the Exchange 2010 RTM release of that language pack
Unified Communications Managed API/speech platform improvements
UM server relies on UCMA for its underlying SIP signaling and speech processing
UM auto attendant update
UM auto attendant will play only the holiday greeting on a holiday
31. Improvements in SP1 Call answering rules improvements
In RTM, Call Answering Rules required a caller to explicitly select an option. If they don’t, UM times out after 10 seconds, and then prompts again for input.
In SP1, the timeout value is now 5 seconds, and the caller is prompted with "To leave a voice message, press the pound key or wait for the tone." If the caller doesn't press a key, UM prompts the caller to record a voice mail message instead of waiting for them to press a key
32. Improvements in SP1 Call answering rules improvements
In RTM, when a caller greeted by a call answering rule selects the voice mail option, a UM server first plays the called party's voice mail greeting before prompting the caller with the instruction to leave a voice message. This can be confusing if the user has created custom greetings
In SP1, the voice mail greeting is skipped if the caller has chosen to leave a voice message via a call answering rule that's configured
33. Improvements in SP1 Call answering rules improvements
In SP1, a missed call notification won't be left for a user if the inbound call reaches the called party using the Find Me feature, if a call transfer succeeds, or if a voice message is successfully left for the user
34. End of Exchange 2010 Unified Messaging
35. For More Information Exchange Server Tech Centerhttp://technet.microsoft.com/en-us/exchange/default.aspx
Planning serviceshttp://technet.microsoft.com/en-us/library/cc261834.aspx
Microsoft IT Showcase Webcasts http://www.microsoft.com/howmicrosoftdoesitwebcasts
Microsoft TechNet http://www.microsoft.com/technet/itshowcase
37. Caller ID ResolutionThe Big Picture Black: same as UM 2007
Blue: improved from UM 2007
Red: new in UM 2010 Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes:
38. Customer Research and Feedback Exchange UM is used most for creating call-answered voice messages
Outlook Voice Access is very valuable to mobile workers, but they are often in the minority
Requests for:
Built-in MWI support
Speech recognition (not just in English)
Outbound fax support
Support split messaging/telephony administration model
Better audio support for non-Windows clients
Private voice mail option
Better caller ID resolution
Slide Objective:
Instructor Notes:
Observations on and requests from the wider Exchange UM customer base are broadly in line with the Microsoft’s own figures. Most UM call-minutes are spent taking messages because the user didn’t answer their phone. Outlook Voice Access is valued highly by mobile users who are away from their desk or from the office, especially if they don’t have smart phones. However, this is often a minority of the workforce (albeit an important and often vocal minority).Slide Objective:
Instructor Notes:
Observations on and requests from the wider Exchange UM customer base are broadly in line with the Microsoft’s own figures. Most UM call-minutes are spent taking messages because the user didn’t answer their phone. Outlook Voice Access is valued highly by mobile users who are away from their desk or from the office, especially if they don’t have smart phones. However, this is often a minority of the workforce (albeit an important and often vocal minority).
39. Migration from Exchange Server 2007How It Works Call answering scenario Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes:
40. Caller ID Lookup Improvements: 2/2 Extension of CLID to E.164 was inflexible
InternationalNumberFormat single-valued
Added NumberingPlanFormats on DP
One or more patterns to extend N-digit to E.164
Lookup did not use unindexed AD DS attributes
telephoneNumber, homePhone, mobile
UM can now generate suffix search fields
AllowHeuristicADCallingLineIDResolution on DP
Bottom line: caller ID lookup is now better! Slide Objective:
Instructor Notes:
Previously, when UM needed to extend a number received to compare with an E.164 value, it used the InternationalNumberFormat property as a template. However, this rather overloads the property, which in any event is single-valued, and there are scenarios in which this is too restrictive. The new NumberingPlanFormats property on the Dial Plan is multi-values, and specifically designed for the purpose of number extension.
AD DS contains a number of user attributes (e.g. telephoneNumber) that seem natural choices for calling line ID resolution. However, in the past UM has not used them, because they are not indexed and have no well-defined syntax. In UM 2010, UM will generate its own search indexes on telephoneNumber, homePhone and mobile fields in AD DS if the new AllowHeuristicADCallingLineIDResolution property is true (as it is by default).Slide Objective:
Instructor Notes:
Previously, when UM needed to extend a number received to compare with an E.164 value, it used the InternationalNumberFormat property as a template. However, this rather overloads the property, which in any event is single-valued, and there are scenarios in which this is too restrictive. The new NumberingPlanFormats property on the Dial Plan is multi-values, and specifically designed for the purpose of number extension.
AD DS contains a number of user attributes (e.g. telephoneNumber) that seem natural choices for calling line ID resolution. However, in the past UM has not used them, because they are not indexed and have no well-defined syntax. In UM 2010, UM will generate its own search indexes on telephoneNumber, homePhone and mobile fields in AD DS if the new AllowHeuristicADCallingLineIDResolution property is true (as it is by default).
41. Caller ID ResolutionAD DS Lookup On Telephone Number Standard AD DS phone attributes are not indexed (unsuitable perf for direct query)
UM copies reversed phone numbers to DTMF map attribute (allows suffix search)
Numbers searched (if present):
telephoneNumber, otherTelephone
homePhone, otherHomePhone
mobile, otherMobile
facsimileTelephoneNumber, otherFacsimileTelephoneNumber
Controlled by AllowHeuristicADCallingLineIDResolution property on UM Dial Plan (true | false) Slide Objective:
Instructor Notes:
Slide Objective:
Instructor Notes: