TX1310 and Cisco Touch 12"

[JensLantermann]

Hello everybody,

we have installed the CUCM 8.5.1-10000 and have added the latest Device Pack.

Now the CUCM knows the TX1310. Everything is configured and looks good, the TX1310 ist registered at the CUCM.

But the Cisco Touch is all the time in the status "Establishing Connection" to the codec.

We are using the latest Telepresence Software 1.9.2!

Has anybody any idea what is wrong?

Thanks a lot!!!

[David Orzelek]

If the Touch panel continues to show the following:

 Attempting to connect with system. Please wait a moment"
 
 
Touch Panel Stuck in "Establishing Connection"

 Please attempt to Factory reset the codec
 
 

CLI command:

admin: utils system factory reset

[David Orzelek]

Also please be aware that per the Data Sheet for the TX 1310:

http://www.cisco.com/en/US/prod/collateral/ps7060/ps8329/ps8330/ps10340/data_sheet_c78-712079.html

Product compatibility

Cisco TelePresence TX1310 65: • Cisco Unified Communications Manager 8.5.2 & 8.6.2 or later • Cisco TelePresence Multipoint Switch 1.8 or later • Cisco TelePresence Manager 1.8 or later

CUCM 8.5.1 is not supported for this platform.

It will have to be 8.5.2 or preferred 8.6.2 or later

[JensLantermann]

Why is this not supported? The latest devicepack and the admin guide tells 8.5.X is supported.

But we have done a n upgrade to the latest version. Same problem!!!!

Who has any idea?

[David Orzelek · Accepted solution]

Have you tried the factory reset via CLI yet ?

CLI command:

admin: utils system factory reset

If so what are the results ?

Note The TX1310-65 may ship with Release 1.9.0 installed. In that case, you must upgrade to Release 1.9.0.1 at the time of installation.

•CUCM Release 8.5.1

Note If the TX1310-65 is installed at a site that includes TX9x00 systems, Cisco recommends CUCM Release 8.6(2a)SU2 for the TX1310-65.

[Leonardo Freitas]

Hello Guys,

We are facing the same problem with CTS/TX 1300-47.

The touch pad stay freezed at "Establishing Connection”   attempting to connect with the system. Please wait a moment.".

We did factory reset as well as downgrade to 1.8.4 without success.

According to the document "Cisco TelePresence Touch 12 System Alerts and Meeting Messages" this occurs when connection to Unified Infrastructure Manager (UIM) is not established and the recommended action is "Wait for connection before using the system".

Well, we are waiting for hours without success.

Any news?

Thanks a lot...

[Marius Nedregaard]

Hi Leonardo.

Please make sure that you have installed the correct COP(for your product), that you have chosen correct software-build in the unit configuration, that you have a supported CUCM version for touch and that you have the current device package installed.

Thanks

//Marius

[Leonardo Freitas]

Hi Marius,

Thaks for your reply.

See answers:

Please make sure that you have installed the correct COP(for your product):

COP's installed and tested:

cmterm-CTS.1-8-0-55R-K9.P2.cop

cmterm-CTS.1-8-4-13R-K9.P2.cop

cmterm-CTS.1-9-2-19R-K9.P2.cop

That you have chosen correct software-build in the unit configuration:

Like said before:

CTS.1-8-0-55R-K9.P2

CTS.1-8-4-13R-K9.P2

CTS.1-9-2-19R-K9.P2

Remember that the P2 version is indicated when using the touch 12. If this isn't installed, the touch 12 doesn't boot properly. Stops at mark 5 into boot process.

That you have a supported CUCM version for touch:

According to Cisco touch 12 guide, the release 8.5.1 which we are using is compatible.

That you have the current device package installed:

OK for this.

Thanks a lot,

Best regards,

[Paula Talamo]

Jens and Leonardo,

• For both of your systems, is the Touch 12 completing all 7 checks on startup and then getting the message?  If so, please open a TAC case so the logs can be reviewed and further troublshooting done.  As David indicated, a factory reset may remedy this but Leonardo indicates in his case, it did not.

• Regarding CUCM 8.5.1 - please reference the 1.9 Software Version Compatibility document as it lists the additional items to be aware of when choosing that version.

• Leonardo - a clarification to what you stated above:

Remember that the P2 version is indicated when using the touch 12. If this isn't installed, the touch 12 doesn't boot properly. Stops at mark 5 into boot process.

You are correct for the systems that use the P2 image (e.g. CTS500-32, TX1310-65, TX1310-65, TX9000, TX9200). The main difference once the software install moved to using COP files and the Touch 12 was introduced is the importance to remove the file extension from the filename (.SPA or .sbn) configured for the device profile in CUCM.  Some CTS endpoints use the P1 version of software (CTS500, CTS1000, CTS1300, CTS3000, CTS3010, CTS3200, CTS3210) and P1 will be in the firmware/COP filename.  Further details about the COP files and Touch 12 are here .

- Paula

[JensLantermann]

The issue was solved, with the upgrade to version 1.9.0.1 as first step.

Jens

[Leonardo Freitas]

JensLantermann escreveu:
The issue was solved, with the upgrade to version 1.9.0.1 as first step.
Jens

I did the same that Jens related and works for me. This version (1.9.0.1) contains some kind of "magic" .

Thanks Jens and all other guys for assistance.

Best wishes

Leonardo

[David Orzelek]

Jens

What code were you running prior to 1.9.0.1 ?

I beleive you stated 1.9.2

Also what CUCM version are you using with CTS 1.9.0.1 ?

Regards

[JensLantermann]

The facory version was 1.9.0

1. We have tried it with a direct upgrade to 1.9.2. It works for codec, but fails to the Cisco Touch.

2. Facory Reset (back to 1.9.0)

3. Upgrade to version 1.9.0.1. It works for codec and for the Cisco Touch.

3. Upgrade to version 1.9.2. Now it works for codec and for the Cisco Touch.

This was really a horrible error.

[vkozevnikovas]

Hello everyone!

Almost every installation i have got the same issue.

Now we have 1.9.3 latest version, system got 1.9.0 factory version.

The most of the times we are waiting for CUCM to be ready for us, so i am usually set ctstype to TX9... and do camera alignment and so on.

If i do not connect tuch panel till get upgrade from the CUCM, it will help to avoid issue with touh panel? Or i still need to do factory reset?

[vkozevnikovas]

After factory reset, Touch Panel connected to the system.

We got another error message, Not Registered. Had to reboot CUCM, after that all was working fine.

We are missing directories on touchpanel, any idea how to puch them from CUCM to each system?