Started by precht, December 11, 2017, 06:38:20 PM
Quote from: SteveInWA on December 12, 2017, 06:34:16 PMI'm sleep-deprived today. I have some time to test it tomorrow, and I have three different test/troubleshooting Google Voice accounts, so I'll see if I can duplicate it. Taoman, good idea about trying the IP phone to see if it's limited to the 20x models. Yes, I have a spare 1022 IP phone along with my "production" 1032 and 2182, so I have a lot of permutations.Off-topic, but I've also been trying to carve out test time to figure out why OBi IP phones (which all have OPUS wideband CODEC support) configured with Callcentric numbers will negotiate to use OPUS when no CC call treatments are used, but they can only do G.711 when one of the phones is part of a simulring call treatment group. Sheesh, VoIP sure has too many things that can go south.
Quote from: billsimon on December 13, 2017, 05:46:13 AMThis morning one of my GV numbers is showing this behavior.
Quote from: billsimon on December 13, 2017, 03:05:54 PMQuote from: billsimon on December 13, 2017, 05:46:13 AMThis morning one of my GV numbers is showing this behavior. The problem has gone away on this number.
Quote from: SteveInWA on December 13, 2017, 04:02:24 PMIs anyone still having this issue?
Quote from: SteveInWA on December 13, 2017, 04:02:24 PMJust to be clear, this specific symptom (calls from one GV/XMPP endpoint to another ring, but the session doesn't set up, thus not sending/receiving audio) was/is not caused by GVGW. Some GVGW users have posted issues that may have had other root causes with their GVGW/SIP/OBi configuration, which could complicate identifying the actual issue.Is anyone still having this issue? I chatted with one of my contacts at Google Voice today. In this scenario (one GV number calling another via XMPP), the calls are "on-net", meaning that they aren't traversing the PSTN, but instead, carried over the internal network. There have been some isolated incidents of the called endpoint ringing, but the call setup doesn't complete, so there's no audio stream. It hasn't been widespread enough to identify the root cause, so if this goes down hard again, they can investigate it further.As a side note, as with most large companies, software and infrastructure changes are coming to a year-end freeze, and this means, on the plus side, I don't expect anything else to mysteriously break. On the minus side, if this issue surfaces again this month, I don't expect anyone will be able to work on it.
Quote from: billsimon on December 14, 2017, 06:24:29 AMQuote from: billsimon on December 13, 2017, 03:05:54 PMQuote from: billsimon on December 13, 2017, 05:46:13 AMThis morning one of my GV numbers is showing this behavior. The problem has gone away on this number.This morning the problem is back on the same number (but not on my other numbers, which were never affected).