This document was generated from CDN thread
Created by: Kari Teffeau on 21-12-2011 10:42:39 PM
First question:
The c90 allows you to do 3 multi-site calls, why are there 4 participant blanks in the example touch panel file - just curious (my client asked and I had no answer).
Second question:
I recently had a situation where the 1st participant state was listed as "dialing" even after the "disconnect all" command was issued several times. When we tried to place new calls, they always showed up as the 2nd participant. Finally rebooted the codec and all participant states reported "disconnected" correctly - new calls started with 1st participant again. Got a report that sometimes calls will get stuck in the codec and you have to reboot it (this seems to match what I witnessed). Has anyone else experienced this?
I definitely wanted to check to ensure I'm using the right versions of everything together and that this isn't code related (i.e. is it something I can program around). I'm using the module TANDBERG_TC_v1_3_1_dr1_0_0. My codec has TC4.1.0.
Thanks for any help/advice you can spare -
Subject: RE: Call state getting stuck
Replied by: David Bruun-Lie on 22-12-2011 02:47:47 PM
Hi,
the codec can do 3 + 1 calls (3 video + 1 audio only), thus 4 slots.
We are aware that sometimes a call may get stuck in the current module - and needs a resync of the call state. This is something we are looking into.
Merry Christmas and Regards,
David
Subject: RE: Call state getting stuck
Replied by: Kari Teffeau on 20-03-2012 03:10:59 PM
ugh...this happened again - we're experiencing more crazy.
--------------------
Client had a government caller that could not receive calls - only make outgoing calls.
Gov't calls client in morning - everything is fine. They hang up.
After lunch, gov't calls again, client is hitting "answer" button, but nothing happens.
The touch panel is indicating they're "connected" but they are not. Client reports that directories are not populating even when they hit the "corporate/local" button.
I had them reboot the codec. They're able to receive the call - they provided no more details.
A couple days later the client called indicating that the camera wouldn't show up on the screen.
--------------------
Our service dept went out and noted that the panel still said "connected" and the directories still would not populate after multiple codec reboots. The camera came up after 1st reboot.
They can get the AMX to respond to commands I wrote outside the module, but none of the module commands appear to be working. (unfortunately they did not port watch to see if strings were being generated and responded to). The rest of the code for the room was working fine - can a single Java module cease working?
After rebooting the AMX, service could see directories and the touch panel no longer indicated "connected".
My client is pissed and I have no resolution in sight.
Do you have any updates on this stuck in call problem?
Is there any way at all I could have a copy of this module? please help!
Subject: RE: Call state getting stuck
Replied by: David Bruun-Lie on 20-03-2012 04:20:03 PM
Kari,
hm, actually we haven't seen this in the AMX module (I misread your previous posting thinking it was the Crestron module where this has been a known issue).
We haven't had any reports on this. That the directory is not responding, especially after having rebooted the codec several times makes me pretty convinced that there is nothing wrong with the codec. If I were you I'd contact AMX and see if they could help you debug what is (not) going on on the controller.
Sorry for not being able to give you a clear solution on this one...
Cheers,
David
