Obi 202, managed via Obitalk, expert mode.
About 3 years ago set up the Obi with GV on SP1, Phonepower on SP2 with SP2 primary. Hadn't been touched since until recently
Because my wife's calls to distant relatives tend to be very loooong, we decided a few weeks ago to start using GV prefix on her outgoing phone calls to the distant relatives. Quickly discovered it wasn't working at all. After a spell on the forum, realized I needed to update the firmware to the latest from the ancient version. After doing that, I relinked the GV account. After that, dialing with **1 prefix worked fine. (I also enabled auto firmware update to stay up to date.)
We then decided to add GV to my wife's Gmail account so she could use her own private number for her outgoing calls. It took all of about 15 minutes to Establish a new GV number for her and set it up in the dashboard on SP3. **3 prefix worked on first go calling her sister.
Next, we decided to configure speed dials for the numbers where calls tend to last an hour or so. So, I set up five of those, using syntax "**31dddddddddd".
That also worked great. Until this week. Suddenly now, when my wife speed dials with those **3 prefixes, everything "seems" to work until the call connects. The number dials. Ringing heard in phone. Ringing stops when the sister answers. Only problem is, no sound reaches our end. Sister hangs up her phone after about 30 seconds of exasperation. If it matters, sister's phone is POTS land line in a fairly urban area in Riverside County CA.
If my wife dials **3 followed by 1 followed by the 10 digit number, everything works perfectly well!
Has anybody else seen this? The only thing I can see that changed in the past three weeks is the firmware. Is speed dialing with a prefix now broken?