Telephony

[This is preliminary documentation and subject to change.]

The following guidelines relate to providing consistent, up-to-date support for telephony on Microsoft® Windows®:

• Use TAPI for telephony. (Required)
• Use the Assisted Telephony interface in telephony-enabled applications. (Required)
• Implement the full TAPI interface in telephony-centric applications. (Required)
• Apply dialing properties to numbers in telephony-centric applications. (Required)
• Allow a user to select the calling device in telephony-centric applications. (Required)
• Share serial devices properly in telephony-centric applications. (Required)
• Explicitly link to a TAPI32 Library if using TAPI 2.x. (Required)
• Gracefully downgrade to work with TAPI 1.4 from TAPI 2.x. (Required)
• Use TAPI 2.1 remote service provider for client-server telephony. (Recommended)
• Use TAPI 2.1 client-management functions for client-server telephony. (Recommended)
• Use TAPI 2.1 for telephony as soon as it becomes available. (Best Practice)
• Use the dialing properties current location settings in telephony-enabled applications. (Best Practice)
• Use the canonical/international form for the number dialed in telephony-enabled applications. (Best Practice)
• Provide separate fields with defaults for phone number entry. (Best Practice)
• Handle the LINE_CREATE message properly in telephony-centric applications. (Best Practice)
• Handle _REINIT messages properly in telephony-centric applications. (Best Practice)