McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 317

↗ View in doc context
page
317
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::326

Return Values Returns zero if the request succeeds or a negative number if an error occurs. Possible return values follow: PHONEERR_INVALAPPNAME PHONEERR_OPERATIONFAILED PHONEERR_INIFILECORRUPT PHONEERR_INVALPOINTER PHONEERR_REINIT PHONEERR_NOMEM PHONEERR_INVALPARAM phoneNegotiateAPIVersion Use the phoneNegotiateAPIVersion function to negotiate the API version number to be used with the specified phone device. It returns the extension identifier that the phone device supports, or zeros if no extensions are provided. Function Details LONG WINAPI phoneNegotiateAPIVersion( HPHONEAPP hPhoneApp, DWORD dwDeviceID, DWORD dwAPILowVersion, DWORD dwAPIHighVersion, LPDWORD lpdwAPIVersion, LPPHONEEXTENSIONID lpExtensionID ); Parameters hPhoneApp The handle to the application registration with TAPI. dwDeviceID The phone device to be queried. dwAPILowVersion The least recent API version with which the application is compliant. The high-order word represents the major version number, and the low-order word represents the minor version number. dwAPIHighVersion The most recent API version with which the application is compliant. The high-order word represents the major version number, and the low-order word represents the minor version number. lpdwAPIVersion A pointer to a DWORD in which the API version number that was negotiated will be returned. If negotiation succeeds, this number ranges from dwAPILowVersion to dwAPIHighVersion. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 285 Basic TAPI Implementation phoneNegotiateAPIVersion

Page 317 content