Welcome to the Cisco TelePresence Developer forum! This forum is for integrators and developers only. The topics should be around device integration and development of solutions with Cisco TelePresence equipment only. This is NOT a product support channel. If you have support related questions please contact your local Cisco representative. Topics not following the above rules may be removed  from the forum. Topics that drift off into flame wars or go way off topic may also be removed without further notice.

« Back to AMX Control

RE: TC_COMM_dr1_0_0.jar comm drop

Combination View Flat View Tree View
Threads [ Previous | Next ]
RE: TC_COMM_dr1_0_0.jar comm drop
c60 c40 amx module
Answer
9/10/12 10:24 PM
Prior to the migration of Tandberg's Developer's Forum over to Cisco's Developer Network, I had posted a request for help regarding the inabliity of the AMX C series module recognizing that the codec has been power cycled and there by dumping all comm port configurations thrown to it by the module when it first initializes after the AMX controller is rebooted. Unfortunatley, the migration over the CDN has lost my posting on this issue, so I'm unable to see if there has been any further developments on this issue.
 
This is arrises whenever the IT department at the client's site decides they want to reboot the Tandberg C series codec after the control system has booted up. And until the control system is either rebooted or the REINIT command is sent to the module, the module stops transmitting any commands to the device port, thereby breaking all control of the device. Unfortunately, I am only able to control the codec over RS-232 as the AMX controller is not vetted to sit on the US government's network.
 
Has there been any headway made on this issue? I am still encountering control system faliures due to this issue, and am working on writting code to work around this issue. If this issue has been resolved or has a work around that I would not have to create, I would welcome either of these.
 
Thank you for your help in resolving this issue.
 
John B.
 
PS - We are experiencing this issue in an installation that includes some 120+ C series Tandberg codecs and a similiar amount of AMX NI-4100's. Any support to resolve this systemic issue would be apprecaited.
Flag

 The forum is moderated by R&D and our aim is to answer your questions as soon as possible. If we cannot resolve your issues immediately we will try to give you feedback indicating when you may expect an answer.

Note that in no circumstances are we able or even allowed to give any promises regarding new products, firmware updates, new features, release dates etc. before they are officially released.

If your question is for a specific product please include both the device type (e.g. Codec C60 or Codec 3000 MXP) and software version (e.g. TC 2.1 or F8.0) for us to be able to answer as accurate as possible.