WFO ACR - no such TLink error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • gavinchan
    Aspiring Member
    • Mar 2012
    • 1

    WFO ACR - no such TLink error

    I am installing v11.0-2patch110014. ACR on windows 2008 R2 64bit.

    Always get the following error:
    Link to CTI on 10.0.8.83 reporting error: no such TLINK
    Link to CTI on 10.0.8.83 reporting error: Not available
    Recorder fatal error: Main CTI feed

    since I tested my old ACR 10.1 without any problem using the conference mode recording. so I believe the AES and CM are set up properly.

    any suggestion?
    or what should I input in the AES TSAPI Server(s) and AES TSAPI Switch Names(s) parameters. since the wording for these 2 parameters are actually different from 10.1.
    10.1 askes you to input the TLink directly, while v11.0 doesn't not.

    thanks!
    Gavin
  • cpage
    Aspiring Member
    • Nov 2012
    • 2

    #2
    AES TSAPI Server = IP of the AES
    AES TSAPI Switch Name = CLAN or Proc-R

    do you have the TSAPI tool installed on the server? have you tested it to see if you can get a CTI Link connection?

    Comment

    • hussam
      Aspiring Member
      • May 2012
      • 1

      #3
      WFO ACR - no such TLink error

      Hi All,

      did you fix this issue, since it happend with me after installing WFO 11.

      any help please.

      Comment

      • wawior
        Hot Shot
        • May 2011
        • 19

        #4
        Hi,

        I faced this issue as well.
        Solutions are:
        -AES TSAPI Server = IP of the AES
        -AES TSAPI Switch Name = name of CLAN/Procr that was set in AES. In other words this is second name in TLINK - between 1st and 2nd hash ("#")
        -TLINK should be Encrypted = secured. So in TLINK there should be CSTA-S

        I hope it will help.


        Brgs
        Michal

        Comment

        • pmulya
          Hot Shot
          .
          • Oct 2010
          • 23

          #5
          The way ACR identifies TLink is changed in ACR 11 comapred to version 10. In ACR 11 we only need to mention AES IP and switch connection name configured in AES. ACR will then query AES to find out the appropriate TLINK to be used. It will only use the TLink if the link shows up on AES.

          Comment

          • faveror
            Member
            .
            • Jul 2018
            • 3

            #6
            erro fatal

            What does that mistake mean? wfo 10.1

            0x7f: 0x3f

            Comment

            Loading