CUCM 8.6 TSP issue

Hi,
I've trouble making the TSP connection to a CUM 8.6 cluster.
I am using windows 7 64 Bit PC and installed the "CiscoTSPx64.exe" as a fresh, did a reboot and configured the required paramenters (CTI Server/Username PWD).
When I use dialer.exe, I don't see Cisco line available. When I go to install the WAVE driver, I don't see WAVE folder created. I searched for OEMSETUP.INF, couldn't find it anywhere.
I put the TSP client in trace mode which generated the output mentioned below. I am sure my username/pwd is correct as I can login to CUCMUSER webpage from the same PC.
I've tried installing TSP plugin from following CUCM versions:
CUCM version: 8.6.2.22900-9
CUCM Version: 8.6.2.20000-2
When I install 32 bit TSP client, I do see WAVE folder created but when I try to install it, it throws an error saying this application is not supported on 64bit OS.
++++++++++++++++++++++++++++++++++++++++++++++++++++
16:13:32.730 HDR|10/22/2012 CiscoTSP001.tsp,Special
16:13:32.730 |   ProviderOpenRequest::qbeTraceOut seq# =0x00000005
16:13:32.731 |   ProviderOpenRequest::qbeTraceOut {{0x00000104, 0x00000000}, 0xFFFFDDDD, 0x000D0001, 0x00000003, 0x00000020, 0x0000006C, 0x00000080}
16:13:32.731 |   ProviderOpenRequest::qbeTraceOut
        ProviderName             : {0x0000008C, 18, CiscoTSP 8.6(2.7) }
        LoginUserID              : {0x000000B0, 10, 5, 2, katr }
        ApplicationID            : {0x000000EA, 25, CiscoTSP001-172.20.40.26 }
        QBEClientVersion         : {0x0000009E, 18, CiscoTSP 8.6(2.7) }
        ProviderEventFilter = {0x000000DA, 16, 4} :
            {bDeviceRegistered: 0xFFFFFFFF, bDeviceUnRegistered: 0xFFFFFFFF, bDirectoryChangeNotify: 0xFFFFFFFF, bDeviceConfigChangedNotify: 0xFFFFFFFF}
        WantServerHeartbeat     : 0x0000001E
        CMAssignedApplicationID : 0x00000000
        PluginName              : {0x00000103, 9, CiscoTSP }
        bLightWeightProviderOpen: 0x00000000
        SingleSignOnTicket      : {0x00000000, 0, }
        AuthenticationType      : 0
        bOldDeviceLineFetch     : 0x00000000
16:13:32.734 |   ProviderOpenResponse::qbeTraceIn seq# =0x00000005 result =0x00000000
16:13:32.734 |   ProviderOpenResponse::qbeTraceIn {{0x0000008B, 0x00000000}, 0xFFFFDDDD, 0x000D0001, 0x00000004, 0x00000020, 0x00000034, 0x0000003F}
16:13:32.734 |   ProviderOpenResponse::qbeTraceIn
        Result          : 0x00000000
        ProviderInfo    : {0x00000054, 14, 8.6.2.20000-2 }
        ClientHeartbeat : 30
        ServerHeartbeat : 30
        PluginVersion   : {0x00000062, 10, 8.6.2.2-0 }
        PluginLocation : {0x0000006C, 39,
http://10.1.10.10/plugins/CiscoTSP.exe
        dwProviderId    : 117440522
        bisFIPSEnabled : 0x00000000
16:13:42.886 |   ProviderOpenCompletedEvent::qbeTraceIn {{0x00000091, 0x00000000}, 0xFFFFDDDD, 0x000D0001, 0x0000007E, 0x00000020, 0x00000048, 0x00000032}
16:13:42.887 |   ProviderOpenCompletedEvent::qbeTraceIn
        Reason           : 0x8CCC0075
        SequenceNumber   : 5
        ProviderInfo     : {0x00000068, 14, 8.6.2.20000-2 }
        ClientHeartbeat : 0
        ServerHeartbeat : 0
        Description      : {0x00000076, 33, Directory login failed - timeout }
        bMonitorCallPark : 0
        ProviderId       : 117440522
        DSCPForCTI2Apps : 0x00000000
        bEnableIpv6      : 0x00000000
        unicodeUserID    : {0x00000098, 2, 1, 2, }
        daysPswdToExp    : 4294967295
        totalDevices : 775040566
16:13:42.887 |   CQBEHelperBase::ProviderOpen() *ERROR* Provider open failed. result=-1932787595
16:13:42.887 |   ProviderClosedEvent::Trace
        dummyHeader.dwLen =28
        dummyHeader.dwType =0
        dwMagicCookie =0xFFFFDDDD
        dwProtocolVersion =0x000D0001
        dwPDUNumber =155
        dwHeaderSize =32
        dwFixedSize =4
        dwVariableSize =0
16:13:42.887 |   ProviderClosedEvent::Trace
16:13:32.730 HDR|10/22/2012 CiscoTSP001.tsp,Special
16:13:32.730 |   ProviderOpenRequest::qbeTraceOut seq# =0x00000005
16:13:32.731 |   ProviderOpenRequest::qbeTraceOut {{0x00000104, 0x00000000}, 0xFFFFDDDD, 0x000D0001, 0x00000003, 0x00000020, 0x0000006C, 0x00000080}
16:13:32.731 |   ProviderOpenRequest::qbeTraceOut
        ProviderName             : {0x0000008C, 18, CiscoTSP 8.6(2.7) }
        LoginUserID              : {0x000000B0, 10, 5, 2, katr }
        ApplicationID            : {0x000000EA, 25, CiscoTSP001-172.20.40.26 }
        QBEClientVersion         : {0x0000009E, 18, CiscoTSP 8.6(2.7) }
        ProviderEventFilter = {0x000000DA, 16, 4} :
            {bDeviceRegistered: 0xFFFFFFFF, bDeviceUnRegistered: 0xFFFFFFFF, bDirectoryChangeNotify: 0xFFFFFFFF, bDeviceConfigChangedNotify: 0xFFFFFFFF}
        WantServerHeartbeat     : 0x0000001E
        CMAssignedApplicationID : 0x00000000
        PluginName              : {0x00000103, 9, CiscoTSP }
        bLightWeightProviderOpen: 0x00000000
        SingleSignOnTicket      : {0x00000000, 0, }
        AuthenticationType      : 0
        bOldDeviceLineFetch     : 0x00000000
16:13:32.734 |   ProviderOpenResponse::qbeTraceIn seq# =0x00000005 result =0x00000000
16:13:32.734 |   ProviderOpenResponse::qbeTraceIn {{0x0000008B, 0x00000000}, 0xFFFFDDDD, 0x000D0001, 0x00000004, 0x00000020, 0x00000034, 0x0000003F}
16:13:32.734 |   ProviderOpenResponse::qbeTraceIn
        Result          : 0x00000000
        ProviderInfo    : {0x00000054, 14, 8.6.2.20000-2 }
        ClientHeartbeat : 30
        ServerHeartbeat : 30
        PluginVersion   : {0x00000062, 10, 8.6.2.2-0 }
        PluginLocation : {0x0000006C, 39, http://10.1.10.10/plugins/CiscoTSP.exe }
        dwProviderId    : 117440522
        bisFIPSEnabled : 0x00000000
16:13:42.886 |   ProviderOpenCompletedEvent::qbeTraceIn {{0x00000091, 0x00000000}, 0xFFFFDDDD, 0x000D0001, 0x0000007E, 0x00000020, 0x00000048, 0x00000032}
16:13:42.887 |   ProviderOpenCompletedEvent::qbeTraceIn
        Reason           : 0x8CCC0075
        SequenceNumber   : 5
        ProviderInfo     : {0x00000068, 14, 8.6.2.20000-2 }
        ClientHeartbeat : 0
        ServerHeartbeat : 0
        Description      : {0x00000076, 33, Directory login failed - timeout }
        bMonitorCallPark : 0
        ProviderId       : 117440522
        DSCPForCTI2Apps : 0x00000000
        bEnableIpv6      : 0x00000000
        unicodeUserID    : {0x00000098, 2, 1, 2, }
        daysPswdToExp    : 4294967295
        totalDevices : 775040566
16:13:42.887 |   CQBEHelperBase::ProviderOpen() *ERROR* Provider open failed. result=-1932787595
16:13:42.887 |   ProviderClosedEvent::Trace
        dummyHeader.dwLen =28
        dummyHeader.dwType =0
        dwMagicCookie =0xFFFFDDDD
        dwProtocolVersion =0x000D0001
        dwPDUNumber =155
        dwHeaderSize =32
        dwFixedSize =4
        dwVariableSize =0
16:13:42.887 |   ProviderClosedEvent::Trace
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Any help on this will be greatly appreciated.
thanks,
Kapil

Hi Zane,
We are using Microsoft AD as LDAP Server. We engaged Microsoft support who ran a utility on one of the domain controller and confirmed that LDAP authentication on port 3268 is successful.
TAC engineer later pointed out that we may be hitting the following BUG and advised an upgrade:
Bug ID: CSCts99665
CTI Authentication failure + OutOfMemoryError:
Curerrently waiting for an opportunity to ugprade our CUCM cluster.
thanks,
Kapil

Similar Messages

CUCM Subscriber back-up issue

Quick question :
I have an SFTP server, which I managed to configure on CUCM PUB fot the back-up purpose.
While doing the back-up, it manage to back-up PUB but back-up to SUB is failing, I could see that the sftp server IP address is pingable through PUB but not through SUB( they both are located at different DC with different IP ranges).
Not sure, if that is the reason SUB is not able to back-up...... ? or, if SFTP is reachable via PUB, SUB should also be backed up.
I can see replication is working fine in the cluster and both PUB and SUB can talk to each other.
Any advise??

Thanks Chris, I am waiting for required routing to be done.
Once that is finished, i will test it again and confirm if that resolved the issue.... :-)

CUCM Cluster "Partition Unalligned" Issue Resolution by PCD (Prime Collaboration Deployment)

Dear all,
I will test soon (asap i got bootable 9.1.2 software) to solve "partition unalligned" issue with CUCM Cluster version 9.1.2.11900-12.
In my opinion, we can solve this issue with PCD as migrate unalligned cluster to a new cluster with same version.
Do anybody test it before?
What is your opinions?
Best Regards,
Mesut

Hi Aman,
As i found out, correct answer should be "migration to 9.x unsupported by CPD" for CUCM version 9.X.
But just imagine, you have 8 servers in a cluster at version 10.X with Partition Unalligned issue. Is PCD not a good alternative to DRS to solve this issue while migrating to a new cluster with PCD?
Best Regards,
Mesut

CUCM - Webex Callback DTMF issue

Hi!
Im having some trouble with webex conferences. When i use the "Callback" feature, i recieve the call but when it asks to accept it, i press the digits and nothing. its lik a DTMF-relay problem but only fails with the Webex callback feature.
Any Ideas??

Hi Juan,
Did you tried from another device?
You can also take that option off, in the admin side you can disable this feature...
see image...
Thanks

TSP TAPI Driver and CUCM 10.X

Hi all
I use: Cisco CP-6921 phone, CUCM 10.X, TSP TAPI driver
I have installed a connector and TSP TAPI driver to make and receive calls from my PC. My problem is that when i receive calls and if i do not pick up the phone after two rings the connector drops the call...but my CISCO CP-6921 is still ringing because the caller is still calling.
I'm not sure that the problem is caused by the connector configuration or the configuration for my line in CUCM. For outgoing calls all is working fine. In the connector setting there is not anything about call tries. I will appreciate your help for resolve his issue.
Thank you

Hi Mohsin,
You can not take a backup from 7.x and restore on 10.x version. The backup can be restored on similar version of cucm only. You can use the Prime Collaboration Deployment ( PCD ) tool to upgrade and migrate your existing 7.x cucm cluster to new 10.x cluster on BE6K.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/pcdadmin/10_0_1/CUCM_BK_U9C58CB1_00_pcd-administration-guide-1001/CUCM_BK_U9C58CB1_00_ucmap-administration-guide_chapter_011.html
You can refer the upgrade guide for cucm 10.x for additional details.
HTH
Manish

ITL Issue with CUCM 8.6(2a)SU3

Hi, We have a cluster of 6 nodes pub, 2 standalone ccm, 2 (ccm+tftp) and 1MoH server.
when we move a phone from one device pool to another, the phone displays "Registration Rejected:Security Error"
I tried deleting the ITL files on the phones but still no luck. with 'show itl' command, we see that the 'System Administrator Security Token' and the 'TFTP' function ITL Record parameters twice with two different certificates in all the nodes.
On another working cluster, the ITL Records of System Administrator Security Token' and the 'TFTP' function can be seen only once.
any idea why this difference? The change in CUCM happened before this issue was that we changed the DSCP enterprise parameter and reset all the phones and restarted the CCM service on all the 4 nodes.

I would start by restarting the TVS and TFTP services on the servers within the cluster.
Thanks,
Tony
Please rate helpful posts!

VCS X8.5.1 SIP TLS to CUCM 8.6.2

I'm having problems enabling TLS on my SIP trunk from the VCS to CUCM.
The SIP trunk shows active on the VCS, but I can't make calls from VCS to CUCM or from CUCM to VCS.
Before configuring TLS, I was able to make these calls.
With TLS enabled, the VCS search for calls from VCS to CUCM show the call rejected and give the reason "Forbidden"
Calls from CUCM to VCS get fast busy and I do not see anything in the search history on the VCS.
I've restarted the trunk and call manager service on the CUCM servers, but no change.
I'm not really sure where to go from here.
I followed the following guide for configuring the SIP trunk. http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-5/Cisco-VCS-SIP-Trunk-to-Unified-CM-Deployment-Guide-CUCM-8-9-10-and-X8-5.pdf
Any help is appreciated.
Thanks,
Joe

I have again checked these and identical to what I set up, We have a multiple TX9000's on the CUCM in Secure mode working perfect and can make Encrypted calls to the TPS server via a TPS TCP Trunk.
but any calls to the VCS just fail on a VCS To CUCM Trunk using TLS with a fast busy signal. and the VCS doesn't even show a search history for it.
In the eyes of the VCS and the CUCM there is no Issues with the TLS SIP Trunk it seems to be working, but It seems SIP TLS packets don't even leave the CUCM. I have tried almost every resource known, and thought it was me just having some random issue until I saw Josef post the same issue.
Tomorrow I will check the X.509 names on the CUCM SIP Security Profile as this is the only thing I can think of that might cause the SIP trunk to be OK up but not route correctly maybe?

Cisco Jabber for Mac 9.2.1: slow to register with CUCM

Hi,
We have this specific problem on our Jabber for Mac 9.2.1 client only: the client takes 60 to 70 seconds to connect to CUCM (running 8.6.2) when it starts.
After Jabber registers with CUCM, there is no issue, it's just very slow to register.
Anybody getting the same behaviour? We have no such issue on previous versions of Jabber for Mac version 8 or Jabber for Windows version 9.
Thanks,
Fabrice

For those interested, I have the answer to my own question: if one of your configured DNS servers is not responding, Jabber 9.2.1 will delay registration to the phone services. This behaviour is seen only in this specifc version of Jabber, hopefully it will be fixed in the next release. Watch out if one of your DNS server goes offilne.
Fabrice

SIP trunk incoming and outgoing calls issue

Hi Everyone,
We recently installad a SIP trunk and terminated on CUBE and CUCM but we have issues on incoming and outgoing calls, When someone dial in from outside he keeps listening the dailing ring even after we pick up the phone and at the end the callers time exipres and call gets disconnected.
For Dailing out, the dialed number rings and caller hear the dailing ring as well but if someone pick the phone it apprears that call is connected but no audio in it, dead air.
Our call flow is as
IP Phones => CUCM --->SIPTRUNK--->CUBE=>SIPTRUNK=>SP
I have attached the config for CUBE and debug ccsip messages output for both incoming and outgoing calls.
Please if some help in sorting out this issue, Thanks in Advance
Tasneem

Inbound call>>>>
The reason you are experiencing this is that your CUBE is requesting PRACK and your provider is not responding to it..
Here we have your cube sending 180 ringing with "Require 100rel"..This was sent several times and your ITSP didnt respond probably because they do not support 100rel...(It is Huwaei after all, they do what they like)
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.205.20.50:5060;branch=z9hG4bKkpw18wp35hfw2c23h51ww6a8aT19871
From: ;tag=sbc080552fph4hp-CC-25
To: ;tag=256F3440-12C
Date: Thu, 16 Jan 2014 13:31:34 GMT
Call-ID: isbc6818c4kfhaa4ca1k5f8k1awsh52f1ccw@SoftX3000
CSeq: 1 INVITE
Require: 100rel
RSeq: 2507
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: "TEST STC" ;party=called;screen=yes;privacy=off
Contact:
Record-Route:
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Content-Length: 0
AFter the CUBE didnt get any response, it then replied with Gateway Timeout...
Jan 16 13:31:54.550: //31880/5A4406E48184/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 504 Gateway Timeout
Via: SIP/2.0/UDP 10.205.20.50:5060;branch=z9hG4bKkpw18wp35hfw2c23h51ww6a8aT19871
From: ;tag=sbc080552fph4hp-CC-25
To: ;tag=256F3440-12C
Call-ID: isbc6818c4kfhaa4ca1k5f8k1awsh52f1ccw@SoftX3000
CSeq: 1 INVITE
Reason: Q.850;cause=102
Content-Length: 0
I suggest you disable this parameter..and test again
voice service voip
sip
rel1xx disable
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Why don't my 2007.1 XML service export files work in 2007.1.1?

Why don't my 2007.1 XML service export files work in 2007.1.1?
Due to changes to the XML export file format in version 2007.1.1, XML service export files from version 2007.1 are not usable in version 2007.1.1.

Hi Alexander,
Just a nit-pick, I'm sure you already know this, but the phone looks for "/spa303.cfg" not "spa303.cfg"
Let's simplify your issue, forget that you have CUCM running.
CUCM is not an issue unless you have CDP running on the swich connected to the SPA303 and the SPA303 is requesting files on the wrong VLAN.
CUCM is not an issue unless the responding DHCP server is pointing the SPA303 to the wrong TFTP server.
Try this:
a. Factory reset your phone [else it will not look for /spa$PSN.cfg]
b. What DHCP server responds to your SPA303 when it boots up? Is it the DHCP server you're expecting, or didn't a rogue DHCP server "jump" in and make an OFFER pointing the SPA phone to the wrong place?
c. Look at the DHCP OFFER OPTIONS from the server, is OPTION 66 *exactly* what you're expecting?
d. Now look at the ARP request that the SPA303 performs, is it ARPing the correct provisioning server?
Here's what you should see assuming your phone gets no response from a TFTP server:
1. The SPA303 will now look 4 times for the following files at 3-second intervals:
SEP1CDF0F2F14F2.cnf.xml
/spa303.cfg
2. The SPA303 will now look 8 times for the following files at 3-second intervals:
XMLDefault303.cnf.xml [repeat 8 times]
/spa303.cfg
3. The SPA303 will now look 20 times for the following file at 3-second intervals:
/spa303.cfg
4. The SPA303 will now look 33 times for the following file at 3-second intervals:
/Cisco/SPA303/1cdf0f2f14f2.cfg [33 retries for this file]
5. The SPA303 will now look 33 times for the following file at 3-second intervals:
/spa303.cfg
Up to now, about 6 minutes have elapsed since the phone was connected to the network and powered up.
6. Wait for about 54 minutes
7. Repeat steps 4 and 5 until a file is found [click Wireshark image for high-resolution version]
Regards,
Patrick----
Use this reference document to locate SPA phone resources

Agent is unable to login

Hello,
We have issue with agent logging in.
Trying to integrate our UCCE (Staging) with seibel with CTI server. We have installed the connector verified through the config .... all is intact as par the recommended guidelines of seibel vendor.
As well as Services are also active from UCCE end. Agent instrument is also participating in the Jtapi application user.
When attempted to login with the CTI tool , we are getting error : " Error: Login could not be performed- Possible cause are invalid instrument; Media termination Problem or other CM issue." .
Verified through the procmon : enclosed the snapshot...
not sure if i need to upgrage the CUCM to overcome this issue.
Any thoughts would be appreciated.
CUCM : 8.5.1.1000
Agent CTI toolkit: 8.5.7
Cheers,

hi,
there is a makecall utility comes with JTAPI when you install it on your machine for integration.
its located under,
C:\Program Files\JTAPITools\makecall (probably on your PG server)
use that utility to verify your JTAPI is working correctly.
go to command promp
move to that folderc (CD C:\Program Files\JTAPITools\makecall)
and run
java makecall <origin> <login> <password> <delay> <origin extension> <destination Extension>
exmaple
java makecall 192.168.50.5 pg1user pg1user 1000 23006 25000
where
192.168.50.5 is CUCM
pg1user, pg1user is username and password
1000 is delay in millisecond
23006 is the extension monitored by jtapi
and 25000 is extension i am trying to call
if this works then you JTAPI is working correct, you may possibly look at sieble.
if doesnt , then please try to reasociate/reset device.
regards
Chintan

New CUMA 7.x can't web access ?

Hi friends ;
new CUMA installation for MCS7845-I2 server. Just follow the instruction installation step. Right after finish the installation some how not able web access to CUMA server. the web links is http://10.10.10.1:7080/adminportal . Suspect that w/s issue, but other w/s not able access too. Those w/s can access cucm, cup unity no issue. What could be wrong ? Pls advice.
rgds
tan

Check to see if Cisco Tomcat is running:
utils service list
Michael
http://htluo.blogspot.com

%VOICE_IEC-3-GW: H323: Internal Error (Socket error): IEC=1.1.186.5.7.5 Error

Can anyone help me with this error. I would like to know what this error means. From what i can see its a call disconnect but it a fault or maybe a call restriction?
%VOICE_IEC-3-GW: H323: Internal Error (Socket error): IEC=1.1.186.5.7.5 on callID 6732 GUID=4DD81BA230AA11E385F070CA9BB22E20.

I could reproduce something in the lab which causes the same error codes:
287674: Oct 14 14:20:30.840: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xFA49
Channel ID i = 0xA98388
Exclusive, Channel 8
287675: Oct 14 14:20:36.840: %VOICE_IEC-3-GW: H323: Internal Error (Socket error): IEC=1.1.186.5.7.5 on callID 272232 GUID=D9FEA303340111E38068001DA10435C0
287676: Oct 14 14:20:36.848: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0xFA49
Cause i = 0x80A6 - Network out of order
This happens in my case if an interface has the H.323 bind whose IP address is not reachable from the CUCM (loopback interface, routing issue?).
No TCP connection can be established between gateway and CUCM.
A good debug choice on the gateway is "debug ip tcp transaction"
Here my example:
287691: Oct 14 14:21:58.222: TCP: Random local port generated 27825, network 1
287692: Oct 14 14:21:58.222: TCB4B0EED38 bound to 10.0.0.1.27825 <--- IS THIS THE INTERFACE YOU WANT FOR SIGNALLING??
287693: Oct 14 14:21:58.222: Reserved port 27825 in Transport Port Agent for TCP IP type 1
287694: Oct 14 14:21:58.222: TCP: sending SYN, seq 227953095, ack 0
287695: Oct 14 14:21:58.226: TCP0: Connection to 10.45.0.50:1720, advertising MSS 1460
287696: Oct 14 14:21:58.226: TCP0: state was CLOSED -> SYNSENT [27825 -> 10.45.0.50(1720)]
287697: Oct 14 14:21:58.226: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xFB49
Channel ID i = 0xA98389
Exclusive, Channel 9
287698: Oct 14 14:22:00.226: 10.0.0.1:27825 <---> 10.45.0.50:1720 congestion window changes
287699: Oct 14 14:22:00.226: cwnd from 1460 to 1460, ssthresh from 65535 to 2920
287700: Oct 14 14:22:00.226: TCP0: timeout #1 - timeout is 4000 ms, seq 227953095
287701: Oct 14 14:22:00.226: TCP: (27825) -> 10.45.0.50(1720)
287702: Oct 14 14:22:02.634: TCB4B0A7300 setting property TCP_TOS (11) 498A5BD8
287703: Oct 14 14:22:02.838: TCP0: ACK timeout timer expired <--- NO ACK RECEIVED FROM CUCM
Check on the CUCM with CLI "utils network capture host ip " if packets from the gateway actually arrive at CUCM. If they do maybe the way back is not possible.
Try to telnet the CUCM to port 1720 from the gateway signalling interface.
If you don't get an "open" you have a network issue (routing, firewall, ACL...)
Bad example:
router#telnet 10.45.0.50 1720 /source-interface lo10
Trying 10.45.0.50, 1720 ...
% Connection timed out; remote host not responding
Good example:
router#telnet 10.45.0.50 1720 /source-interface fas0/0
Trying 10.45.0.50, 1720 ... Open
hope that helps
Martin

Jabber goes offline when enabling capabilities assignment

Hi
Is anyone facing this issue :
Jabber goes offline for all users when enabling capabilities assignment for a new user in CUCM ?
to resolve this we have to go into CUPS and restart the XCP router service or authentication service for the jabber client to reconnect ...
any suggestions \ ideas welcome.... thanks

Hi Araf,
We never had any similar issues to this one. By your description since all users go offline I dont think that this is Jabber issue at all. I suggest you should probably open a TAC case against CUCM to address your issue.
Regards,
Marko

CAD login failed - The password specied is Invalid

Uccx version 8.0.2
CUCM Version 8.0
Issue: For the past couple of weeks i have noticed that when new users are added to CUCM via LDAP, new users can login ok on EM but when logging to CAD get "The password specied is Invalid"
I have reset the Cisco Desktop Sync Service and the Cisco Desktop LDAP Monitor Service no Joy.. I have also rest the Directory services on Desk top administrator still no joy ... i have rebooted both uccx servers no joy either. This only happens to new users
Any help will greatly be apprciated

Hi Chakshu,
Thanks for pointing me in the right direction... I did a trace and found the following ( see below).. restarted the LDAP server and it fixed it . Thanks a million
<Can't contact LDAP server>
2014-08-09 18:34:54:704 DEBUG [0x85ac4ba0] LdapClientLogger.h[104] LC0001: An exception occurred in <establishConnection(Calabrio LDAP, )> while establishing connection -- com.spanlink.util.connection.SplkConnectException: LDAP bind error.
2014-08-09 18:34:54:704 WARN [0x85ac4ba0] LC0001 establishConnection: Error occurred while performing an LDAP operation.
2014-08-09 18:34:54:705 DEBUG [0x85ac4ba0] ConnectionManager.cpp[702] attemptToConnectToAllHosts: Caught <com.spanlink.util.connection.SplkConnectException: LDAP bind error.> which is ignored.

CUCM 8.6 TSP issue

Similar Messages

Maybe you are looking for