Closed Bug 702406 Opened 14 years ago Closed 14 years ago

dialing in via toronto asterisk server is really voipy

Categories

(Infrastructure & Operations :: Telecom, task)

task
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

References

Details

I just dialed 416-848-3114 to try and join a conference call, on my landline, and the connection was massively voipy -- I couldn't even understand the automated greeting. My Polycom also isn't working at this time, which may be related (when I dial, I just get hung up on).
I had the same issue this morning. 9:30 am PT to be exact calling 416-848-3114 and then ext. 212. I could barely understand the autogreeting or the instructions to join a conference call My softphone worked clearly fwiw.
Confirmed. I can dial into Toronto from Mountain View and it's nice and crystal clear. Dialing in the 416 number is jumpy as hell. Opening a ticket with Junction.
Assignee: server-ops → justdave
Summary: dialing in via toronto asterix server is really voipy → dialing in via toronto asterisk server is really voipy
Junction says it's probably the ISP's fault and wants us to make sure they don't have issues first before coming back to them. Would like someone in the toronto office to run this: http://www.onsip.com/extras/voip-test Haven't been able to raise anyone in #toronto on IRC.
Assignee: justdave → network-operations
Component: Server Operations → Server Operations: Netops
QA Contact: cshields → mrz
Assignee: network-operations → server-ops-telecom
Component: Server Operations: Netops → Server Operations: Telecom
(In reply to Dave Miller [:justdave] from comment #3) > Junction says it's probably the ISP's fault and wants us to make sure they > don't have issues first before coming back to them. > > Would like someone in the toronto office to run this: > http://www.onsip.com/extras/voip-test > Haven't been able to raise anyone in #toronto on IRC. cc'ing the Toronto alias. If no one else can, I'll do it tomorrow.
14:00:44 < kats> justdave: jitter = 0.1ms, packet loss = 0.6%, MOS score = 3.5
Component: Server Operations: Telecom → Server Operations: Netops
/me grumbles about firefox's caching after reloads
Component: Server Operations: Netops → Server Operations: Telecom
I'm attempting to switch this over to SIP instead of IAX to see if it makes any difference (since Junction offers both). Will report back here with the results.
Er, I made comment 8 a while ago and didn't notice it midaired when I submitted it. It's been successfully switched over to SIP and that did fix the problem, so something is suddenly interfering with IAX traffic getting out of that office apparently. It's all changing when we get GBLX all the way online anyway, so this'll do for now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.