If your AE Server is R4.2 then a protocol version of 4.2 should be fine, assuming your SDK is also R4.2. If you are using an earlier SDK then it (i.e. the SDK not the AE Server) will reject the setProtocol request.

Although you can use an earlier version of the DMCC-SDK with a later version of AE Server (i.e. R4.1 SDK with a R4.2 AE Server), you cannot run a later version of the DMCC-SDK with an earlier version of AE Server. You will get the errror response noted below.

Yes, both endpoints should be able to register. Are the two endpoints registering as the same extension or different extensions? If they are registering as the same extension, only the first registration will have a talk path.

See the getButtonInformation request in PhysicalDeviceServices. Also see ButtonIDConstants for a list of common button IDs. If a lamp has a button associated with it, the lampID and the buttonID should be the same.

Vijay,

Is this just a cut-and-paste error? In your other thread you gave the CM IP address as 113.132.193.202 (not 204).

See my reply in the other thread.

The 2001 error code indicates that you have some kind of network access problem. Can you ping the CM IP address from the AE Server? They seem to be on the same network, so the ping should succeed. If you can ping successfully, then check the AE Server Administration web-pages again. Go to "CTI OAM Administration" -> "Administration" -> "Network Configuration" -> "Local IP". Ensure that, for the "Switch Connectivity" field, you have selected the correct ethernet interface for the 113.132.193.x subnet.

Vijay,

As Nick and John have already mentioned, port 4722 is used for secure socket layer connections, using TLS. If you do not require a secure socket for your application, connect to port 4721 instead. Note, however, that port 4721 is disabled by default.
To enable port 4721, you must use a browser to log onto the AES OAM web-pages. Go to "CTI OAM Administration" -> "Administration" -> "Network Configuration" -> "Ports". About half-way down the form, under "DMCC Server Ports", enable port 4721 and click "Apply Changes".
Finally, you need to restart the DMCC service. From the OAM web-pages, Go to "Maintenance" => "Service Controller" and check the "DMCC Service" box. Click the "Restart Service "button.
ONce the DMCC service has restarted, youshould be able to connect your appplication to port 4721.

The 2001 error code indicates that you have some kind of network access problem. Can you ping the CM IP address from the AE Server? They seem to be on the same private network, so the ping should succeed. If you can ping successfully, then check the AE Server Administration web-pages again. Go to "CTI OAM Administration" -> "Administration" -> "Network Configuration" -> "Local IP". Ensure that, for the "Switch Connectivity" field, you have selected the correct ethernet interface for the 172.16.2.x subnet.

Check that port 4721 on the AE server is enabled (by default, it is disabled). You can check this from the AE Server Administration web-pages. Logon and then go to "CTI OAM Administration" -> "Administration" -> "Network Configuration" -> "Ports". Look under "DMCC Server Ports". If port 4721 is disabled, you need to enable it and then restart the DMCC service, using the "Maintenance" -> "Service Controller" page..

The latest version of Communicationn Manager is R4.0. There is also a Beta version of R5.0 availaable, if you are part of the beta release program.

As Nick states in the other thread, the latest version of Applications Enablement Server is R4.0, with R4.1 in Beta.