Messages to and fro T-server

Voice & Telephony
1

Hi Guys,

Do you know how do we find if there are any gaps in Messaging between T-Server and AES ? We are having a few issues where we see no messaging from switch for a few secs, we came to know when we analysed a few conn ids which were default routed.

But I wanted to how do we know if thats happening again, say for a particular time. Do we have any key words to grep and check all messages were proper. Here below is the messaging from T-server logs. how do we read them ?

@12:03:33.0718 [<<] 08 00 00 27 08 02 82 22 62 96 1C 1F 91 A1 1C 02 01 02 02 01 95 40 14 08 02 81 9C 10 02 37 D9 70 06 80 2A 2A 2A 2A 2A 96 47 01 8C

@12:05:06.9567 [>>] 08 00 00 24 08 02 50 B6 64 96 1C 1C 91 A1 19 02 01 03 02 01 8C 40 11 96 49 06 81 36 34 35 34 B9 49 06 83 31 35 31 35 B5

Cheers
Karthik

2

You should use the Avaya Asai protocol reference guide.

Fra

1 Like
3

The first message is a report about an “invalid number”, whereas the second is a Status Query of a DN.

1 Like
4

Thanks buddy, I have download a few docs from avaya.

By the way, which digit did you use for identifying the type of facility invoke ?

5

Hi Karthik,

Can you post your further steps in your trouble shooting, as we too are experiencing the same problem…

Thanks
Chandra

1 Like
6

For the first message, 0x62 is the message type, 0x9c is the cause value; for the second message, 0x64 is the message type, 0x81 the domain type.

Fra

1 Like
7

Hi Fra,

Thanks. and I did go through some ASAI protocol and code guide. Learning day by day :slight_smile:

And Chandra,

The issue was identified to be a switch side issue. CLAN for AES server is connected to is running on older Firmware , this should be upgraded and can cause some CTI connectivity issues if the firmware remains on older versions.

I would suggest you to check the firmware and make sure you have the right and latest version.

Cheers
KArthik

8

Hi Karthik and fra,

Thanks for the information. I will look in this direction.

Thanks,
Chandra

9

Hi,

Please check the clan firmware version if it is 21 or below, possible suggestion would be to upgrade it to 24 which has fix for this issue, and latest version is 26.

am not an expert, but just a beginner to Genesys, but i thought i could share what i have come across, i hope this would be useful.

Cheers
Karthik