Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Initial configuration. Connection timeout.

Greetings,

I have an existing CM v8.0.3 and have completed all the steps from Cisco Jabber Voice for Android Release 9.1.4 Administration Guide.  I installed the 9.1.1v1 COP file on the CM, created a new Cisco Dual Mode for Android device and installed Jabber v9.1.4 on a Samsung Galaxy S4 Active running v4.2.2 and also a Samsung Galaxy S2 I777 running 4.1.2.  Both devices attempt to connect.  In the logs on the phone, I see

TFTP Download=Complete,

UCM Registration Initialzing,

UCM Registration Disconnected,

UCM Registration Initialized,

UCM Registration Connected,

UCM Registration Disconnected. 

I also saw UCM Registration Single Reg - voip, a few times.  On the phone when attempting to verify after 20 or so seconds, I get Connection timed out.  I do see the IP address of the phone show up in the CM under the device but it is unregistered.  There is a firewall between the voice and data network, but it is wide open.  I even created wifi for the voice network and placed the device on that network and updated the preset wifi networks on the device configuration page so as to eliminate the firewall, but that didn't change anything.  When I change networks, the IP address of the device changes in the CM device list so it is getting the connection for a bit. 

I'm at a loss for where to go next.  Anyone have any ideas?  I have attached the send logs.

Everyone's tags (2)
2 REPLIES
Cisco Employee

Initial configuration. Connection timeout.

Hi russell

I see from the logs about the time out...

12-10 19:56:47.868 D/libpsipcc(17006): SIPCC-SIP_TCP_MSG: sip_tcp_read_socket: CUCM closed TCP connection.
12-10 19:56:47.868 E/libpsipcc(17006): SIP : sip_tcp_read_socket : socket error=2
12-10 19:56:47.868 D/libpsipcc(17006): SIPCC-SIP_TCP_MSG: sip_tcp_createconnfailed_to_spi: Active server going down due to CM_CLOSED_TCP. ip_addr:192.168.52.32

It seems you have not restarted the CUCM node/Nodes after installing the cop file.

Please make sure that

-You install the file on all node on CUCM cluster

-Reload the nodes after installing the cop file

Tapan

New Member

Actually, the CallManager had

Actually, the CallManager had been restarted many times with no success.  We pretty much gave up on trying to get this to work.

1106
Views
0
Helpful
2
Replies