Export (0) Print
Expand All
Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

LINECALLFEATURE2

Windows Mobile 6.5
A version of this page is also available for
4/8/2010

These bit-flag constants describe the supplemental features available for conferencing, transferring, and parking calls.

The following table shows the LINECALLFEATURE2 constants.

Value Description

LINECALLFEATURE2_NOHOLDCONFERENCE = 0x00000001

If this bit is on, a "no hold conference" can be created by using the LINECALLPARAMFLAGS_NOHOLDCONFERENCE option with lineSetupConference. The LINECALLFEATURE_SETUPCONF bit will also be on in the dwCallFeatures member in the LINECALLSTATUS structure.

LINECALLFEATURE2_ONESTEPTRANSFER = 0x00000002

If this bit is on, "one step transfer" can be created by using the LINECALLPARAMFLAGS_ONESTEPTRANSFER option with lineSetupTransfer. The LINECALLFEATURE_SETUPTRANSFER bit will also be on in the dwCallFeatures member.

LINECALLFEATURE2_TRANSFERCONF = 0x00000080

If this bit is on, the lineCompleteTransfer function can be used to resolve the transfer as a three-way conference. The LINECALLFEATURE_COMPLETETRANSF bit will also be on in the dwCallFeatures member.

LINECALLFEATURE2_TRANSFERNORM = 0x00000040

If this bit is on, the lineCompleteTransfer function can be used to resolve the transfer as a normal transfer. The LINECALLFEATURE_COMPLETETRANSF bit will also be on in the dwCallFeatures member.

Aa918493.note(en-us,MSDN.10).gifNote:
If neither TRANSFERNORM nor TRANSFERCONF is specified in the dwCallFeature2 member in LINECALLSTATUS but LINECALLFEATURE_COMPLETETRANSF is specified, then it is possible that either will work, but the service provider has not specified which.

These constants are for TAPI version 2.0 and later.

Headertapi.h
Windows Embedded CEWindows CE 3.0 and later
Windows MobileWindows Mobile Version 5.0 and later

Community Additions

Show:
© 2015 Microsoft