calledDeviceID changed with 7.1.3.4 upgraded from 7.1.3.3 AES CM

[dclark1111]

This issue appeared once we upgraded CM to 7.1.3.4 from 7.1.3.3. CM was the last to upgrade, AES was done prior with no changes to the function. I have read the release notes to see if there is a change in behavior, but didn't see anything that comes close to what I am seeing. We have a Call Back system and call recording system that use AES. The call back system calls a customer from VDN 12345. Once the agent picks up we see the following event (change numbers around):
Data we see from AES:

Channel 0[55555] Type: CTI_EVENT_AVAYA_TSAPI 8216(57) CSTA_DELIVERED IP:
Channel 0[55555] Msg==>timeReceived=08:56:38.987|eventType=57|eventClass=4|monitorCrossRefId=81|connectionDeviceID=55555|callID=13333|alertingDeviceID=55555|callingDevice=OUTBOUNDCALLERID|calledDevice=12345|callingDeviceID=OUTBOUNDCALLERID|calledDeviceID=12345|lastRedirectedDevice=14444|cause=ecRedirected|trunkGroup=0|trunkMember=1|split=10002|ucid=RANDOMDIGITS|attEventType=128<==


55555 is agent Id
12345 is the call back system vdn

Prior to 7.1.3.4 we saw the calledDeviceID= as the number of the customer the system called back.

I know this is custom to us, but I have no idea where to look to see why there was a change in the CM function or AES function. Or if there is a setting that will change it from reporting vdn to another field.

Looking forward to any ideas you have. I have noticed that there is a patch to 7.1.3.4 to 7.1.3.5. Wondering if its a bug or not.
Thanks for your help!

 

[dclark1111]

I had to open up a case with Avaya on this one, as it appears there was a code change in 7.1.3.4 that carried to 7.1.3.5. Turns out this is a bug in these two releases. Avaya hasn't given an ETA on the fix, but one is coming. We have a PEA and are waiting on the fix to be posted. Thanks for looking!

 

[kyle555]

I had to back out 7.1.3.4 CM. Something about code from CM8 in there being incompatible.

It broke a WFO