Author Message
Karthik.Ageer
Joined: Jul 4, 2017
Messages: 11
Offline
Hi Team,

When trying to logging into an avay"a Agent on a extension which is not registered to CM Using our pegacall (CTI tool), we are getting the error "TSAPIPlatformException - There is already an Agent logged on at the station" . We are expecting an error message something like Extension is not currently loggedin. Can you please confirm if this is a Avaya bug and can it be fixed ?

Thanks,
Karthik
MartinFlynn
Joined: Nov 30, 2009
Messages: 1922
Online
It looks like Communication Manager uses the same error (GENERIC_OPERATION (1)) for the two cases. It is just a limitation of the system.

Martin
Karthik.Ageer
Joined: Jul 4, 2017
Messages: 11
Offline
Is there an option to change the error Message, so that enduser understands what is wrong with the login attempt.

Thanks,
Karthik
MartinFlynn
Joined: Nov 30, 2009
Messages: 1922
Online
It is possible for you to catch the exception and generate your own message. Unfortunately, JTAPI seems to hide the error cause generated by TSAPI. This means that it can be difficult to report the exact reason for a failure so that may be of limited value.

In this case, it is possible to check that there are no agents already logged into a station before attempting to login. Have a look at AvayaCallCenterUserAgent.agentLogin() in the AgentView sample application for an example of this.

Martin
Go to:   
Mobile view