| C# | Visual Basic | Visual C++ |
public byte[] DeviceSpecific( byte[] inputData, TapiAddress address, TapiCall call, int outputDataSize )
Public Function DeviceSpecific ( _ inputData As Byte(), _ address As TapiAddress, _ call As TapiCall, _ outputDataSize As Integer _ ) As Byte()
public: array<unsigned char>^ DeviceSpecific( array<unsigned char>^ inputData, TapiAddress^ address, TapiCall^ call, int outputDataSize )
- inputData (array< Byte >[]()[])
- A byte array that contains input data.
- address (TapiAddress)
- An address on the line (if required for the specific function). Set to null reference (Nothing in Visual Basic) if not required.
- call (TapiCall)
- A call on the line (if required for the specific function). Set to null reference (Nothing in Visual Basic) if not required.
- outputDataSize (Int32)
- Size of output data, in bytes. Set to zero if specific function does not return any data.
Many TSPs provide functionality specific to the telephony system using device specific extensions. DeviceSpecific method allows the application to access device specific functions implemented by the TSP. Please refer to the TAPI documentation for your telephony hardware to find out about device specific functionality supported by the telephony service provider.
The application has to negotiate a version of the extension supported by the line device using NegotiateDeviceSpecificExtensionVersion(UInt32, UInt32) before opening the line in order to use DeviceSpecific method.
| This method should be used when input or output data have variable length. Make sure to specify outputDataLength large enough to hold all output data. Use DeviceSpecific(Object, TapiAddress, TapiCall, Type) when device specific function has fixed size structures as input and output data. Please feel free to contact us and we will gladly help with more complex scenarios. |
| Exception | Condition |
|---|---|
| TapiException | DeviceSpecific failed because of Telephony API (TAPI) error. |
Assembly: Traysoft.AddTapi (Module: Traysoft.AddTapi)