We've recently migrated from a DLG based CTI-Link with Genesys TServer to TSAPI. Since migrating to TSAPI, the value Genesys is receiving for ANI on calls when the remote party number is restricted (blocked caller ID) is odd.
On DLG, Genesys would receive an empty data string ("") for ANI when it was blocked. On TSAPI the ANI value is an odd string starting with “T”, followed by a 3 to 5 numeric digits, and then ending with “#1”.
See below example excerpt from Genesys TServer log:
callingDevice
{
deviceID 'T13715#1'
deviceIDType explicitPublicUnknown
deviceIDStatus idProvided
}
And then shortly after we see it as an attribute ‘Other DN’ and then ‘ANI’.
AttributeOtherDN 'T13715#1'
.
.
AttributeANI 'T13715#1'
Any thoughts?
Genesys Framework 8.1 T-Server for Avaya TSAPI
Avaya AES 6.3
Avaya CM 6.2
On DLG, Genesys would receive an empty data string ("") for ANI when it was blocked. On TSAPI the ANI value is an odd string starting with “T”, followed by a 3 to 5 numeric digits, and then ending with “#1”.
See below example excerpt from Genesys TServer log:
callingDevice
{
deviceID 'T13715#1'
deviceIDType explicitPublicUnknown
deviceIDStatus idProvided
}
And then shortly after we see it as an attribute ‘Other DN’ and then ‘ANI’.
AttributeOtherDN 'T13715#1'
.
.
AttributeANI 'T13715#1'
Any thoughts?
Genesys Framework 8.1 T-Server for Avaya TSAPI
Avaya AES 6.3
Avaya CM 6.2
Comment