DevLink uses a Windows Dynamic Link Library (DLL) file called DEVLINK.DLL. This file is installed by default into "Program Files/Avaya/IP Office/DEV Link" directory. Programs using this interface simply need to link to this library and use it's functions.
· Any application that uses the DevLink DLL should include it in the application installation script. As the DLL is not a COM component, no registration is necessary. The DLL does not require any registry settings or supporting files.
· When developing an application that uses the DLL, the DevLink header file (devlink.h) and appropriate library file (devlink.lib or devlinkomf.lib) should be copied to the same directory as the project source files. The devlink.lib library file contains export symbols in COFF format which can be used with projects written in Visual C++. The devlinkomf.lib library file contains export symbols in OMF format for other linkers.
· To support a legacy application with DevLink3, this original DLL must be replaced with the appropriate 32-bit or 64-bit DLL from the DevLink3 SDK.
The DEVLINK.DLL files can be used in any language that supports Dynamic Link Libraries (DLLs), e.g. Microsoft Visual C++ or Borland Delphi.
DevLink allows developers to request call-backs, which are generated when significant events occur. For the real-time event stream, this occurs at various stages throughout a call's lifetime. Both telephony calls and data calls are included in the events generated.
Please note that all application call-backs are made on a thread which DevLink creates. As a result, consideration must be given by programmers to ensure that all functions called from within a call-back are thread-safe.
