Author Message
balakrishnankasilingam
Joined: Jul 26, 2006
Messages: 0
Offline
After establishing an ASAI connection to AES, ie link up, there is a RESTART message from AES. In reply I send a RESTART ACKNOWLEDGE. If I send any ASAI packet after this, there is no response from AES. I tried sending a layer 3 heartbeat. No response from AES. I also tried sending a "register event notification", for which also I do not get any response.

The bytes exchanged
01 00 00 02 01 01 connection request from client
02 0a 00 00 connection accepted from AES
08 00 00 19 08 02 00 00 46 79 01 87 96 1b 05 84 3a 54 0a b9 1b 01 83 1b 01 82 1b 01 81 ASAI data : RESTART packet from AES
08 00 00 0C 08 02 80 00 4e 79 01 87 96 1b 01 83 ASAI data: RESTART ACKNOWLEDGEMENT from client.
08 00 00 13 08 02 80 00 4e 79 01 87 96 1b 05 84 3a 54 0a b9 1b 01 83 layer 3 heartbeat from client
no response from AES

What is the version IE 1b 05 84 3a 54 0a b9 in the RESTART mean?
The protocol reference document doesn't seem to document the last 4 bytes. I think that the layer 3 heartbeat is not being responded to because the RESTART process has not completed properly. I am unable to get a response for 'Event Notification request' or 'value query association' too.





JoelEzell
Joined: Nov 15, 2013
Messages: 780
Offline
Hello,

The DLG service is currently not supported on these forums. Please consider using the "Request Technical Support" link instead. Sorry for the inconvenience.

Joel
balakrishnankasilingam
Joined: Jul 26, 2006
Messages: 0
Offline
The issue has been resolved. It happens to be a configuration issue. The configuration change had to be done in Communication Manager. When I
created cti-link in CM, I had set its Type to ADJ-IP. Setting this to ASAI-IP got the problem resolved.
Now we get response from AES to a L3 heartbeat request, Event notification request etc from our client.
JoelEzell
Joined: Nov 15, 2013
Messages: 780
Offline
Great news, I'm happy to hear that! Thanks for posting this information for others that may have a similar issue. Sorry we weren't able to be more help to you.
Go to:   
Mobile view