Hello,

We analyzed out logs and found that for few calls we are getting trunk id in place of agent station id with connectionAlerting(CallControlConnectionEvent event) override function.
We are calling event.getConnection().getAddress().getName().

Can you please suggest what could be the reason? Is there any setting we need to do at Avaya CM end?

Thanks & Regards,
Umesh

So you are querying for a party's name in the call and sometimes you get agent information back (is that the party placing the call)? and sometimes you get a trunk identifier?

What is the full call flow?
What analysis have you done?
What release are you working with (CM, AES, JTAPI)?
Have you looked at the TSAPI trace logs on AES for insight related to the two different results?

Troubleshooting questions are best asked via support tickets and not in the forums. Minimal troubleshooting support is provided to registered level members in the program. Through the forums we can provide suggestions on how to proceed but no troubleshooting assistance due to the overall complexity in doing so.

Thanks John for reply.
- Around out of 6000 calls, for 100 calls we received trunk id in place of agent device id with connectionAlerting event, when querying event.getConnection().getAddress().getName().
-AES Version is 8.1.1 and JTAPI version is 8.0.1
- Customer call comes to IVR via trunk and after IVR flow it reaches to agent through ACD.
-We asked AES trace from customer.

We posted in forum if anyone found this kind of issue is past.

Regards,
Umesh