Hello,
When attempting to upgrade the firmware on an RMX 1500 from 7.2.2.64 to 7.6.0.,172 I do not get the normally prompted screen to enter the activation license dialog box and therefore appears that the update fails.
Here are the steps I followed starting with 7.2.2.64
1. Reset the system
2. Adminstration-software management - software download
3. Browse to the latest firmware RMX_7.6.0.172.bin
4. Click install - copying files proceeds to the end and then prompts with a dialog box warning a license code is required
5. Click ok to acknoledge this message and nothing happens
Here is what I tried to resolve this
1. Close the upgrade dialog box
2. Selected setup - Product activation - Entered the license code for 7.6.0.172
Immediately the upgrade dialog reappears and proceeds to complete software loading and then IPMC burning
followed by the device resetting itself
Once reset and I can confirm 7.6.0.172 but now have a situation where both HDX4000 & HDX7000 units are unable to enter conferences.
There is no audio or video feedback from the IVR and eventually the calls are dropped. I restored the configuration (pre upgrade and confirmed the IVR is still in place as are the "meeting rooms")
On the RMX 1500 the HDX devices do not get to the conference. I tried dialing both conf@IP and IP##conf methods with no result.
I rolled back to 7.2.2.64 to resolve this issue but would like to get 7.6 working for the Active Directory integration feature.
Kesikun,
The issue with the product activation window not popping up is normal. Entering the activation key is all that is required and it is not an indication of an upgrade failure.
I doubt the issue was directly related to the upgrade itself. Did you happen to notice if there were any system on the bridge at that time?
No systems were connected at the time of upgrade , I actually performed this upgrade/downgrade a number of times in order to assure that the issue was reproducible.
I will perform the upgrade again and investigate a bit deeper into the issue, it could be that the Conference IVR was corrupted.
On the last test I used an PC H323 client (Ekiga) and successfully entered the default IVR with voice prompt, will do the same tests on the HDX units.
Many thanks
Whoops, I left a word out by accident in my last post. I meant to ask if there were any system alerts on the bridge at the time.
No system alerts were showing at the time of upgrade.
I will be performing the upgrade again tonight (EU time) and deliver some more feeback
Opps really sorry with the formatting above !
I now have more information on the error message and reason why HDX units cannot enter a "Meeting Room"
There appears to be no audio codec established betweeen the HDX + RMX.
< RMX Firmware - 7.2.2.64 HDX 4000 Firmware Release - 3.0.1-10628>
From a HDX400 CDR log - No audio codec shows - normally you see Siren22Stereo
On the RMX1500 the error message on one CDR is
PARTICIPANT DISCONNECTED Thursday, December 08, 2011 6:17:12 PM Participant Name: 8999test_(000)
Participant ID: 0
Call Disconnection Cause: h323_call_closed_audio_channels_didn't_open_before_timeout
Q931 Disconnection Cause: default cause or not available (0)
With Ekiga client I can connect to a non-encrypted conference- see below.
File Version: 675 Conference Routing Name: xxxxxx Internal Conference ID: 458 Reserved Start Time: Thursday, December 08, 2011 6:47:19 PM Reserved Duration: 01:00:00 Actual Start Time: Thursday, December 08, 2011 6:47:19 PM Actual Duration: 00:02:08 Status: Conference automatically terminated when empty File Name: c396 GMT Offset: +1:0 File Retrieved: Yes Reserved resources for Audio Participants: 0 Reserved resources for Video Participants: 0
CONFERENCE START Thursday, December 08, 2011 6:47:19 PM Dial-out Manually: No Auto Terminate: Yes Line Rate: 384 Kbps Audio Algorithm: auto Video Session: Continuous Presence Video Format: auto CIF Frame Rate: auto QCIF Frame Rate: auto
CONFERENCE START CONTINUE 1 Thursday, December 08, 2011 6:47:19 PM Talk Hold Time: 300 x 0.01 seconds Audio Mix Depth: 5 Video Protocol: Auto Meet Me Per Conference: No Chairperson Password: Cascade Mode: None Minimum Number of Participants: 0 Allow Undefined Participants: Yes Time Before First Participant Joins (Auto Terminate): 10 minutes Time After Last Participant Quits (Auto Terminate): 1 minutes Maximum Number of Participants: Automatic Message Service Type: IVR Service Conference IVR Service: Conference IVR Servi Lecture Mode Type: None Lecturer: Time Interval: 15 seconds Lecturer View Switching: No Operator conf: False
CONFERENCE START CONTINUE 4 Thursday, December 08, 2011 6:47:19 PM Conference ID: 9030 Conference Password: Chairperson Password: Info1: Info2: Info3: Billing Info:
CONFERENCE START CONTINUE 5 Thursday, December 08, 2011 6:47:19 PM Encryption: No
CONFERENCE START CONTINUE 10 Thursday, December 08, 2011 6:47:19 PM Display Name: XXXXX
OPERATOR MOVE PARTY TO CONFERENCE Thursday, December 08, 2011 6:47:19 PM User Name: Name of Source Conference: DefaultEQ(456) ID of Source Conference: 456
Participant Name: DefaultEQ(456)_(003) Participant ID: 3 Dialing Direction: Dial in Network Service Name: IP Network Service Audio Only: No Default Number Type: Taken from Service Identification Method: Called phone number, IP address or alias Meet Me Method: Participant Network Type: H.323 Video Protocol: Auto Broadcasting Volume: 5 Undefined Participant: Yes Node Type: Terminal IP Address: 10.1.80.154 Signaling Port: 1720 H.323 Participant Alias Type: H.323 ID H.323 Participant Alias Name: EKIGA-CLIENT H323
PARTICIPANT CONNECTED Thursday, December 08, 2011 6:47:28 PM Participant Name: DefaultEQ(456)_(003) Participant ID: 0 Participant Status: connected PARTICIPANT's LINE RATE CONNECTION Thursday, December 08, 2011 6:47:28 PM Participant Name: DefaultEQ(456)_(003) Participant ID: 0 Participant's Current Line Rate: 448 Kbps
And here is where the HDX tries to enter the conference
NEW UNDEFINED PARTICIPANT Thursday, December 08, 2011 6:47:57 PM Participant Name: HDX4000_(000) Participant ID: 1 Dialing Direction: Dial in Network Service Name: IP Network Service Audio Only: No Default Number Type: Taken from Service Identification Method: Called phone number, IP address or alias Meet Me Method: Participant Network Type: H.323 Video Protocol: Auto Broadcasting Volume: 5 Undefined Participant: Yes Node Type: Terminal IP Address: x.x.x.x Signaling Port: 1720 H.323 Participant Alias Type: H.323 ID H.323 Participant Alias Name: HDX4000
NEW UNDEFINED PARTICIPANT CONTINUE 1 Encryption: auto Thursday, December 08, 2011 6:47:57 PM Participant Name: HDX4000_(000) Participant ID: 1 H323_CALL_SETUP Thursday, December 08, 2011 6:47:57 PM Participant Name: HDX4000_(000) Participant ID: 1 Initiator: party Minimum Rate: 64000 Maximum Rate: 384000 Source Address: x.x.x.x Destination Address: x.x.x.x End Point Type: Terminal SET PARTICIPANT DISPLAY NAME Thursday, December 08, 2011 6:47:57 PM Participant Name: HDX4000_(000) Participant ID: 1 Display Name: HDX4000 PARTICIPANT DISCONNECTED Thursday, December 08, 2011 6:48:13 PM Participant Name: DefaultEQ(456)_(003) Participant ID: 0 Call Disconnection Cause: h323_call_closed_normal Q931 Disconnection Cause: default cause or not available (0) PARTICIPANT DISCONNECTED CONTINUE 1 Thursday, December 08, 2011 6:48:13 PM Rx Synchronization Loss: 0 Tx Synchronization Loss: 0 Rx-Video Synchronization Loss: 1 Tx-Video Synchronization Loss: 0 PARTICIPANT DISCONNECTED Thursday, December 08, 2011 6:48:27 PM Participant Name: HDX4000_(000) Participant ID: 1 Call Disconnection Cause: h323_call_closed_audio_channels_didn't_open_before_timeout Q931 Disconnection Cause: default cause or not available (0)
PARTICIPANT DISCONNECTED CONTINUE 1 Thursday, December 08, 2011 6:48:27 PM Rx Synchronization Loss: 0 Tx Synchronization Loss: 0 Rx-Video Synchronization Loss: 0 Tx-Video Synchronization Loss: 0 CONFERENCE END Thursday, December 08, 2011 6:49:27 PM Conference End Cause: Conference automatically terminated when empty
Kesikun,
I would upgrade the HDX to 3.0.3. In 7.6 the RMX added support for the Siren LPR audio codec, which the HDX supports on 3.0.1 and above. So calls between the two on 7.6 should be doing Siren LPR rather than Siren 22. However, in 3.0.1 there is a bug with Siren LPR that causes it to transmit its capabilities incorrectly and the RMX will reject them.
This issue is only documented as being present in 3.0.1 however, so an upgrade to 3.0.3 ought to resolve it.