Cable Modem > Gigabit Router > Telo. No changes in home network in months. Normal calls don't drop.
(all times are central time)
Test 1 call into my toll free bridge:
3:15pm start - disconnected 3:16pm
Test 2 call into my toll free bridge:
3:17pm start - disconnected 3:18pm
Test 3 call into my bridge using my associated toll line number (a 719-387-XXXX):
3:19pm start - did not get disconnected while sitting there for 5 minutes
Test 4 call into my toll free bridge (this time I clocked it):
3:24:30 start (pick up the handset; ooma dialtone)
3:24:36 finished dialing the #
3:24:41 ooma connects me to the bridge... i hear the automated dude prompting me for my password
3:24:57 put in my passcode... no worky cuz i fat finger it
3:24:25 put in my correct passcode ... automated dude says he's gonna verify
3:24:44 verified and dumps me into the conf bridge (it officially 'starts' and opens up the bridge)
3?26:16 I get disconnected!
Test 5 call into my toll free bridge: (no problems this time!)
3:34:39 bridge officially starts..
3:38:15 I hang up ... no disconnect
Test 6 call into my toll free bridge (ugh)
3:39:54 bridge officially starts...
3:40:25 I get disconnected!
30 seconds seems to be the magic number although that only happens when I start my bridge myself. It's been sporadic when I have joined other people's call. Looks like the current workaround is to use your affiliated toll number(s) for your conference calls.
Thats interesting, so this may mean that if you use a google voice dialer to call in (as in calling your google voice number and then pressing "2" or initiating the call from the google voice page dialer) then the problem would cease to exist, since you are never calling the 800 number. This would be a great workaround for us. Would someone mind testing if that would work? I don't really have a conference number to test.chrisinhou wrote: Looks like the current workaround is to use your affiliated toll number(s) for your conference calls.
- Bobby B
- Ooma Moderator
- Posts: 1457
- Joined: Mon Feb 18, 2008 8:41 pm
- Location: Palo Alto, CA
This bug became much more prevalent with a routing change for 8XX calls that was made about a week ago. We're putting in a routing change (hopefully within a couple hours) for 8XX calls to work around the problem.
Have you read any of the posts above by the moderator?thomas wrote:I experienced the same issue when connecting to my conference line 866- no. I get dropped every few minutes. Started May 24th. Before that I have not used my line with Ooma for about 3 weeks. Prior to that it worked perfectly. Now I cannot use Ooma to start my conference calls. Notified Ooma. Got a ticket number, but they say they have a Master ticketno existing since May 10th. How long before they going to resolve this??