Closed
Bug 511175
Opened 17 years ago
Closed 16 years ago
Toronto conference room phone (511) doesn't always work after a system reboot
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Gavin, Assigned: dmoore)
Details
The phone is paired with the video system (I'm not really familiar with the details). When the system starts up, we sometimes have to reboot just the phone for it to be able to dial out while video is running. justdave has a theory that there's a race condition with both the phone and video system registering with asterisk, which would explain why rebooting only the phone helps.
I'll see if I can get the MAC address for both the phone and the video thingy, in case that's useful (I think the phone connects through the video system).
Comment 1•17 years ago
|
||
The HDX doesn't go through Asterisk and IIRC, the phone merely is an audio input into the HDX.
The MAC address should be on the bottom of the phone.
Updated•17 years ago
|
Assignee: server-ops → justdave
Comment 2•17 years ago
|
||
I have no idea how the HDX works, and their documentation was confusing as hell when I last saw it. Is there anyone around that knows how it's actually set up?
| Reporter | ||
Comment 3•17 years ago
|
||
I think the video unit is 00:e0:db:10:0b:2d, per bug 495074, and the phone's MAC is 00:04:f2:e6:0d:47.
Comment 5•16 years ago
|
||
Need to engage our A/V guy to troubleshoot.
Comment 6•16 years ago
|
||
OK, I discovered the release notes on version 3.2.1 of the Polycom firmware *strongly* recommend upgrading IP7000s to that version to properly support coupling with the HDX. We currently have 2.0.3 loaded on those phones. This may be part of the problem.
Comment 7•16 years ago
|
||
That asterisk is trying to feed them firmware 2.0.3 surprises me. We've been running 3.1.3 in Mountain View for a long time now, and I could swear I upgraded Toronto first to be a guinea pig on the new firmware. :) Although it looks like I only did that to the IP501 config and didn't get the IP6000/7000 config.
Comment 8•16 years ago
|
||
Extension 511 has been reloaded with firmware 3.2.1. See if that affects anything.
Comment 9•16 years ago
|
||
mike/gavin/johnath
Comment 10•16 years ago
|
||
er, i meant - can one of you test this?
Comment 11•16 years ago
|
||
I should have closed this bug as WFM a while ago; we actually stopped running into trouble shortly after having filed this bug. Sorry about that.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•