AES: Incorrect UI/Caller Id on third party application.

Doc ID    SOLN328149
Version:    1.0
Status:    Published
Published date:    02 Aug 2018
Author:   
kkanthboppan
 

Details

Application Enablement Services 6.3.3 version.

All versions.

Problem Clarification

Incorrect UI / CallID passed from AES to Unified Agent
Never worked

Yes, it can be duplicated.

Cause

From the CM MSTand the G3traces of AES the Calling number ANI is properly sent to the Application. but the Customer wanted it to be manipulated.


06/18/2018 17:24:43.897:TSAPI:LinkThread01: Received ASAI Message ConnectList
06/18/2018 17:24:43.897:TSAPI:LinkThread01: cap,prim,sao_id             C_EN_REP,C_REQUEST,55685092
06/18/2018 17:24:43.897:TSAPI:LinkThread01: event_name                  C_CONNECTED
06/18/2018 17:24:43.897:TSAPI:LinkThread01: callID                      13150
06/18/2018 17:24:43.897:TSAPI:LinkThread01: callingDev,Party            30213,1
06/18/2018 17:24:43.897:TSAPI:LinkThread01: callingFlags                0x60000
06/18/2018 17:24:43.897:TSAPI:LinkThread01: callingState                0x10
06/18/2018 17:24:43.897:TSAPI:LinkThread01: affectdDev,Party            (null),2
From the g3traces the UCID information

06/18/2018 17:24:43.897:TSAPI:LinkThread01: affectedFlags               0x20000
06/18/2018 17:24:43.897:TSAPI:LinkThread01: affectedState               0x10
06/18/2018 17:24:43.897:TSAPI:LinkThread01: party_id                    2
06/18/2018 17:24:43.897:TSAPI:LinkThread01: cause_value                 CS0/16
06/18/2018 17:24:43.897:TSAPI:LinkThread01: called_num                  07771887369
06/18/2018 17:24:43.897:TSAPI:LinkThread01: calling_num                 30213
06/18/2018 17:24:43.897:TSAPI:LinkThread01: connect_num                 (null)
06/18/2018 17:24:43.897:TSAPI:LinkThread01: called_type[addr_type,numb_plan]     0,1
06/18/2018 17:24:43.897:TSAPI:LinkThread01: calling_type[addr_type,numb_plan]    7,15
06/18/2018 17:24:43.897:TSAPI:LinkThread01: con_type[addr_type,numb_plan]        0,0
06/18/2018 17:24:43.897:TSAPI:LinkThread01: trk[id,gid,direct]          1,3,0x0
06/18/2018 17:24:43.898:TSAPI:LinkThread01: oli: hasInfo?(F)value(0)
06/18/2018 17:24:43.898:TSAPI:LinkThread01: ucid:  8 byte dump of 8 bytes of data:
06/18/2018 17:24:43.898:TSAPI:LinkThread01: ucid:  hex '2710335e 5b27dcc2'
06/18/2018 17:24:43.898:TSAPI:LinkThread01: ucid:  std format: '10000131501529339074'
 

Solution

As per CM engineer this is working as designed and proper Calling information was sent to the application.

Working as designed.


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy