Closed Bug 616145 Opened 15 years ago Closed 15 years ago

Phone conference rooms busted

Categories

(Infrastructure & Operations Graveyard :: Servicedesk, task)

All
Other
task
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: johnath, Assigned: justdave)

References

Details

Juan, Christian, Beltzner, Matt and I tried to have a regularly-scheduled conference call today at 8:30am PST and had a variety of failure. Conference 245 was "invalid", and beltzner and I assumed a toronto-specific bustage (8605 was also "invalid", but my conference, 286 worked locally). Trying to dial the 1-800 number never connected, and in the meantime Juan and Christian both had problems connecting as well. Might be a bigger problem than just the conference rooms, might be that MV phones in general are not reachable?
Bug fix upgraded to Asterisk was causing issues. Backed out about an hour ago. Let me know if you're still having issues.
Just tried to join conference 245, "not a valid conference" and ditto for 8605. Conference 286 (mine, toronto based) works.
toronto phone server is currently showing that it's unable to connect to the mountainview phone server. (however, mountainview is connecting back the other direction just fine). investigating...
Assignee: desktop-support → justdave
May or may not be related to the MV firewall again (seems pretty likely) but of the two people who can mess with it, one's on vacation and the other is on a plane (enroute to Toronto of all places) at the moment. We have a firewall bypass in place for ringring because of other similar issues in the past. I'd like to try re-routing the connection between toronto and mountainview to go through that bypass, as that will likely resolve this. However, there's a call in progress (inbound call from MV to ext 517) that will get dropped when I do it. So unless someone's in an urgent hurry, I'll wait for that call to complete.
Clarification - Ravi's in transit, Derek's at his desk.
yeah, I thought Derek was out today for some reason. He's poking at the firewall, and says we're getting a lot of packet loss outbound from toronto right now. I did do the re-route, and that does seem to have solved the immediate problem at least. (you can place calls to MV from Toronto again).
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.