CTI Port always busy

Version 1

    Subject: RE: CTI Port always busy
    Replied by: David Staudt on 27-09-2010 02:29:10 PM
    In addition to being Open for control, a CTI port must also be 'registered' for media.  For TAPI applications, normally the Cisco TSP wave driver provides media transmit/receive functionality - if the wave driver is installed, when you open a CTI port the TSP will automatically register its media using the wave driver.
     
    If media is not registered, the CTI port will not be considered fully 'up' by UCM, giving a busy signal.
     
    The developer guide has some additional discussion and details on CTI media registration.
     
     
    This document was generated from CDN thread

    Created by: Christoph Mueller on 27-09-2010 09:09:02 AM
    Hello all,
     
    I am trying to answer a call on a CTI Port but whenever I call the number of the port, it gives me the busy signal and my TAPI application has no chance to answer the call.
    I open the line with privileges OWNER and MONITOR and media mode AUTOMATED VOICE.
    Same happens when I try to work with TAPI browser.
     
    Would be great to hear any ideas.....maybe the Port is misconfigured. But I do not have access to the Call Manager. And our admin only knows very little about CTI Ports.
     
    Thank you in advance

    Subject: RE: CTI Port always busy
    Replied by: Christoph Mueller on 29-09-2010 08:58:07 AM
    Thank you very much.
    The problem was, that the Cisco Wave Drivers were installed but not functioning properly. On a different machine it works.
     
    But the next problem is, that writing audio to the Cisco wave driver via waveOutWrite only works once, after that, any call to the waveOut-device locks. The same code works fine for playback on the system´s soundcard. Only the Cisco wave driver is making troubles....
     
    Anybody has an idea?
     
     

    Subject: RE: CTI Port always busy
    Replied by: Christoph Mueller on 07-10-2010 08:24:46 AM
    Got it fixed. It seems not possible to do a waveWriteOut in the wave devices callback. Got a second thread now which triggers waveOutWrite when needed.