[cisco-voip] CUCM 6.0.1. - CiscoTSP 6.0 Error

Jason Burns burns.jason at gmail.com
Mon Sep 1 08:25:58 EDT 2008


Hensley,

You may want to make sure you're using the GC port 3268 in your CUCM LDAP
integration as per the SRND and then restart CTIManager.

If that doesn't take care of it, then it's to the traces as Wes suggested.

On Thu, Aug 28, 2008 at 4:43 PM, Wes Sisk <wsisk at cisco.com> wrote:

> Hi Hensley,
>
> In that case the next step of investigation is the CTI SDI/SDL traces.  TSP
> sends ProviderOpen over CTIQBE (TCP:2748) to CTIManager process.  CTIManager
> process should process that ProviderOpen request and authenticate the user.
>  Use RTMT to get the CTIManager SDI and SDL traces and see what those show
> after the client attempts ProviderOpen.
>
>
> Regards,
> Wes
>
> Webmaster - hensleys.de wrote:
>
>> Hi Wes,
>>
>> thx for yor answer .. forgot to mention that i already searched cisco,
>> google and vo-ip lists / boards and did everything mentioned there and like
>> you said in your answer.
>>
>> CUCM is AD (2003) integratet and users can login to ccmuser with their AD
>> credentials.
>>
>> Also users are in group "CCMEnduser Administration" and "allow CTI".
>> Phones have "allow control from CTI" enabled, lines have "allow control from
>> CTI" enabled. Still the line won't show up when i try to use "dialer" or
>> something like that.
>>
>> To cut out firewall problems i placed one test pc in our voice vlan and
>> tried ... still same error. :( I changed the user / pwd in TSP config to
>> some that does not exist to check if i get a new error but still the same
>> messages appear in logs.
>>
>> regards _Hensley_
>>
>> Wes Sisk schrieb:
>>
>>> "Directory login failed - timeout"
>>>
>>>
>>> Looks like directory authentication is failing.  Is this using AD/LDAP
>>> authentication?  Make sure the user can login.  I believe all user passwords
>>> were reset during the upgrade.
>>>
>>> Also recall that CM6.x changes some user behavior for CTI.  Users must be
>>> added to specific groups too enable features such as:
>>> allow CTI control of devices
>>> allow access to ccmuser
>>>
>>> setup those.  make sure the user can authentication to http://<cm_server>/ccmuser
>>> and then see what happens with TSP.
>>>
>>> Regards,
>>> Wes
>>>
>>> Webmaster - hensleys.de wrote:
>>>
>>>> Hi @all ...
>>>>
>>>> we just migrated from CCM 3.3(4) to CUCM 6.0.1.1000-37 and are now
>>>> facing 1 issue.
>>>>
>>>> Systems: CUCM 6.0.1.1000-37 (appliance) / IPCC Express 5.0 (enhanced)
>>>> Phones: mostly 7960 (100), some 7911 and 7912
>>>>
>>>> CiscoTSP 6.0(0.7) does not work. The old version 3.3 with CCM 3.3 worked
>>>> fine. CTIManager on CUCM is working fine and IPCC runs without problems ...
>>>> agents can control their phones.
>>>>
>>>> Detailed logs bring up these messages:
>>>> ---snip---
>>>> 08/27/2008 17:31:34.745 CiscoTSP001.tsp|
>>>> ProviderOpenCompletedEvent::Trace
>>>>       ProviderInfo = 6.0.1.1000-37
>>>>         Description = Directory login failed - timeout
>>>>         bMonitorCallParkDNs = 0
>>>>         dwProviderId = 16780775
>>>>         dwDSCPForCTI2Apps = 0|<LVL::Special><MASK::0200>
>>>> 08/27/2008 17:31:34.745 CiscoTSP001.tsp|
>>>> ProviderOpenCompletedEvent::qbeTrace
>>>>        dwReason =0x8CCC0075
>>>>        dwSequnceNumber     =1
>>>>        ProviderInfo        ={0x0000004C, 14, 6.0.1.1000-37 }
>>>>        dwClientHeartbeat   =0
>>>>        dwServerHeartbeat   =0
>>>>        Description         ={0x0000005A, 33, Directory login failed -
>>>> timeout }
>>>>        bMonitorCallParkDNs =0
>>>>        dwProviderId        =16780775
>>>>        dwDSCPForCTI2Apps    =0x00000000|<LVL::Special><MASK::0200>
>>>> ---snip---
>>>>
>>>> ---snip---
>>>> 08/27/2008 17:31:34.745 CiscoTSP001.tsp| CQBEHelperBase::ProviderOpen()
>>>> *ERROR* Provider open failed. result=-1932787595|<LVL::Error><MASK::0001>
>>>> 08/27/2008 17:31:34.745 CiscoTSP001.tsp|
>>>> TSPI_lineNegotiateTSPIVersion()
>>>>        TSPI_lineNegotiateTSPIVersion returns = 0x00000000
>>>>        TSPI return version = 0x00020001|<LVL::Special><MASK::0400>
>>>> 08/27/2008 17:31:34.745 CiscoTSP001.tsp|   TSPI_providerEnumDevices()
>>>>        dwPermanentProviderID = 0x0000000A
>>>>        hProvider = 0x00FD51D8
>>>>        lpfnLineCreateProc = 0x73367C05
>>>>        lpfnPhoneCreateProc = 0x7336FEC1|<LVL::Special><MASK::0400>
>>>> 08/27/2008 17:31:34.745 CiscoTSP001.tsp|   TSPI_providerEnumDevices()
>>>>        TSPI_providerEnumDevices returns = 0x00000000
>>>>        dwNumLines = 0
>>>>        dwNumPhones = 0|<LVL::Special><MASK::0400>
>>>> 08/27/2008 17:31:34.745 CiscoTSP001.tsp|   TSPI_providerInit()
>>>>        dwTSPIVersion = 0x00020001
>>>>        dwPermanentProviderID = 0x0000000A
>>>>        lpfnCompletionProc = 0x73375DFE|<LVL::Special><MASK::0400>
>>>> 08/27/2008 17:31:34.745 CiscoTSP001.tsp|   TSPI_providerInit()
>>>>        TSPI_providerInit returns = 0x00000000
>>>>        dwLineDeviceIDBase = 0x00000008
>>>>        dwPhoneDeviceIDBase = 0x00000000
>>>>        dwNumLines = 0
>>>>        dwNumPhones = 0
>>>>        lpdwTSPIOptions = 0x00FD51E4|<LVL::Special><MASK::0400>
>>>> 08/27/2008 17:31:41.335 CiscoTSP001.tsp|   TSPI_providerShutdown() After
>>>> GlobalTSP->TSPI_providerShutdown()|<LVL::Special><MASK::0400>
>>>> 08/27/2008 17:31:41.335 CiscoTSP001.tsp|   ProviderCloseRequest::Trace
>>>> :dwSequenceNumber = 0x00000002|<LVL::Special><MASK::0200>
>>>> 08/27/2008 17:31:41.335 CiscoTSP001.tsp|   ProviderCloseRequest::Trace
>>>>        dummyHeader.dwLen =28
>>>>        dummyHeader.dwType =0
>>>>        dwMagicCookie =0xFFFFDDDD
>>>>        dwProtocolVersion =0x00090000
>>>>        dwPDUNumber =9
>>>>        dwHeaderSize =32
>>>>        dwFixedSize =4
>>>>        dwVariableSize =0|<LVL::Special><MASK::0200>
>>>> 08/27/2008 17:31:41.335 CiscoTSP001.tsp|   SendMessage() *ERROR* send()
>>>> failed with error 10038.|<LVL::Error><MASK::0001>
>>>> 08/27/2008 17:31:41.335 CiscoTSP001.tsp| CCtiInterface::ctiDisconnect()
>>>> *ERROR* Could not send ProviderCloseRequest. error=|<LVL::Error><MASK::0001>
>>>> ---snip---
>>>>
>>>> Can someone point me in the right direction?
>>>>
>>>> Thanks in advance!
>>>>
>>>> regards _Hensley_
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>
>>>
>>>  _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080901/dc97c9c1/attachment.html>


More information about the cisco-voip mailing list