Some background information on the important files in the Diva SDKdssdk.dll is the core of the Diva SDK and is also the DLL used for the C/C++ API so this must always be present on any system using the Diva SDK. divasdk.dll - this is the 'Component' APIs, used in Visual Basic and VB.NET applications, it should be in \system32 and registered with Windows - you can use the divaregistercomponent.bat to do this. divaserver.dll - this is the .NET managed interface so generally used with C#.NET applications and again uses dssdk.dll as a base and should be in \System32. Note that many developers use the Component API with C#. You can move the DLLs to other directories if required but as DLLs use the Windows execution path it is recommended to only have them in one location on the system running the application. Using SDK with HMPTwo additional files are used when using the Diva SDK with HMP.divaload.dll is the link between the SDK and HMP so it is recommended that it is always in the same directory as dssdk.dll. dssdk.xml is the configuration file for using the SDK with HMP and it is recommended that it is always in the same directory as dssdk.dll. dssdk.xml should have both the number of channels and the local IP address configured as per the examples in the manual. Systems without this usually work ok but we have seen odd behaviour on system that don't have this minimum information so it is strongly recommended that all systems have these elements configured. And of course if you are not using the default SIP you should enter H323 as the protocol. e.g:
<DivaAPIConfiguration> <Device> <NetworkInterface>192.168.1.50</NetworkInterface> <Channels>10</Channels> <SignalingProtocol>SIP</SignalingProtocol> </Device></DivaAPIConfiguration>
The dlls (and consequently the xml file) follow the usual Windows search path so I would recommend you only have one copy of these files and always keep them in \system32.