lineDevSpecific
The lineDevSpecific
function enables service providers to provide access to features not offered by
other TAPI functions. The meaning of the extensions are device specific, and
taking advantage of these extensions requires the application to be fully aware
of them.
LONG lineDevSpecific(
HLINE hLine, |
|
DWORD dwAddressID, |
|
HCALL hCall, |
|
LPVOID lpParams, |
|
DWORD dwSize |
|
); |
|
Parameters
hLine
A handle to a
line device. This parameter is required.
dwAddressID
An address ID
on the given line device.
hCall
A handle to a
call. This parameter is optional, but if it is specified, the call it
represents must belong to the hLine line device. The call state of hCall
is device specific.
lpParams
A pointer to
a memory area used to hold a parameter block. The format of this parameter
block is device specific and its contents are passed by TAPI to or from the
service provider.
dwSize
The size in bytes
of the parameter block area.
Return Values
Returns a
positive request ID if the function will be completed asynchronously, or a
negative error number if an error has occurred. The dwParam2 parameter
of the corresponding LINE_REPLY
LINEERR_INVALADDRESSID,
LINEERR_OPERATIONUNAVAIL, LINEERR_INVALCALLHANDLE, LINEERR_OPERATIONFAILED,
LINEERR_INVALLINEHANDLE, LINEERR_RESOURCEUNAVAIL, LINEERR_INVALPOINTER,
LINEERR_UNINITIALIZED, LINEERR_NOMEM.
Additional
return values are device specific.
Remarks
This
operation is part of the Extended Telephony services. It provides access to a
device-specific feature without defining its meaning. This operation is only
available if the application has successfully negotiated a device-specific
extension version.
This function
provides a generic parameter profile. The interpretation of the parameter
structure is device specific. Whether dwAddressID and/or hCall
are expected to be valid is device-specific. If specified, they must belong to hLine.
Indications and replies sent back the application that are device specific
should use the LINE_DEVSPECIFIC
A service
provider can provide access to device-specific functions by defining parameters
for use with this function. Applications that want to make use of these
device-specific extensions should consult the device-specific (in this case,
vendor-specific) documentation that describes what extensions are defined. An
application that relies on these device-specific extensions will typically not
be able to work with other service provider environments.
See Also