Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Avaya CT Client Error on CLS

Avaya CT Client Error on CLS

Avaya CT Client Error on CLS

Need some help here...

Anti-virus was just upgraded and since then, I am not receiving any recordings.  

I get the following error on the Avaya CT client on the CLS Server:

CAPI - Connect Failed - Status is - 2

Has anybody seen this?

Thanks in advance,


RE: Avaya CT Client Error on CLS

Try temporarily disabling firewall and restart system.  Can you connect to Avaya CT with TS Spy or Admin? Think it's a networking issue, check your tslib file has the correct ip address and port.

RE: Avaya CT Client Error on CLS

Its not an error connecting to the T-Server.  Its an error indicating that the Driver connect connect to the CAPI (Call Server).  Call Server runs on port 2050 for 8.x or 62050 in Perform.  You should check your firewall to see if you are blocking any localhost ports and allow everything for localhost.

RE: Avaya CT Client Error on CLS

Thanks for you help!

I called NICE and they informed me that the issue was actually related to SQL server--incorrect password caused the ODBC driver to fail.  After running a CLS wizzard, the problem was fixed.


RE: Avaya CT Client Error on CLS

On my NICE CLS, I am getting a CTI Failure - monitoring a device has ended lucent ts switch (1406)

has anyone seen this?  what causes this?

RE: Avaya CT Client Error on CLS

if you go to c:\nicecti\integration there will be a failed devices text file open that and it will show you what extension has failed check it on switch to see if it still exists if not remove it from devices file.

The error comes when the nice driver fails to monitor it it tries to monitor it 4 times and if unsuccesful then goes onto next extension. you will have to reboot once you have removed device

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close