GoogleVoice OAUTH + Configure locally
Rick:
I think I'll let the vendors argue who is at fault, but Steve you're getting the perspective from one side and the other side doesn't necessarily agree, and in fact are pointing fingers.
Callcentric has been in touch, by phone, with me today. They are working with one of the two carriers with the issues (they didn't say which one) and they said the issue existed yesterday but did not exist today. I then tested it and found it still does exist today and relayed that info to them minutes ago.
They explained, that from their perspective (perhaps a biased perspective), GV does not keep the routing consistent, so when an issue is "fixed" then some time later they see it's costing more money so someone may "unfix" it. I'm not an engineer, nor do I play one on TV, so I don't know if that's one of the transit carriers sending calls a different way to CC, or GV using a different transit carrier. Suffice it to say that CC seems to believe that GV is using the least expensive routing they can find, whether that's with a big player or not. Again, that's what I'm being told - it may be biased, it may be wrong, it may be right.
I think the key is that the problem currently exists and this makes GV unreliable to use with CC TODAY. While I've remedied the problem on my primary line by routing via IPComms and iNum, I don't see staying with that for long term as it begs "complex, please break me".
Right now I'm watching and seeing if it gets fixed in the next few days.
I also volunteer to come to Hawaii and help Roger work through this difficult issue. PM me and I will give you the info for you to book my travel. :D
ramjet73:
Quote from: Rick on October 16, 2014, 08:39:36 am
I also volunteer to come to Hawaii and help Roger work through this difficult issue. PM me and I will give you the info for you to book my travel. :D
What issue? Getting fewer calls means more beach time. ;)
Seriously though, I'm still thinking about trying one of those "Cheap DID's". Unless Google chooses their initial transit carrier based on the forwarding phone number, that would certainly help to isolate the source of the CID and call completion problems.
ramjet73
SteveInWA:
Quote from: Rick on October 16, 2014, 08:39:36 am
I think I'll let the vendors argue who is at fault, but Steve you're getting the perspective from one side and the other side doesn't necessarily agree, and in fact are pointing fingers.
Callcentric has been in touch, by phone, with me today. They are working with one of the two carriers with the issues (they didn't say which one) and they said the issue existed yesterday but did not exist today. I then tested it and found it still does exist today and relayed that info to them minutes ago.
They explained, that from their perspective (perhaps a biased perspective), GV does not keep the routing consistent, so when an issue is "fixed" then some time later they see it's costing more money so someone may "unfix" it. I'm not an engineer, nor do I play one on TV, so I don't know if that's one of the transit carriers sending calls a different way to CC, or GV using a different transit carrier. Suffice it to say that CC seems to believe that GV is using the least expensive routing they can find, whether that's with a big player or not. Again, that's what I'm being told - it may be biased, it may be wrong, it may be right.
I think the key is that the problem currently exists and this makes GV unreliable to use with CC TODAY. While I've remedied the problem on my primary line by routing via IPComms and iNum, I don't see staying with that for long term as it begs "complex, please break me".
Right now I'm watching and seeing if it gets fixed in the next few days.
I also volunteer to come to Hawaii and help Roger work through this difficult issue. PM me and I will give you the info for you to book my travel. :D
I've really tried to be patient, helpful, friendly, and all that other Boy Scout stuff with you. In return, I've gotten a lot of complaining and cranky replies.
As you know, I am also a long-time, loyal Callcentric customer, and I am very familiar with their history on this issue. I've been sympathetic to their position, and I did a lot of legwork to facilitate them actually troubleshooting the issue with the carriers that connect to them.
I already told you that Google uses several transit carriers, and that those carriers are some of the largest carriers in the industry, not Uncle Bob's Discount Phone Call and Stormdoor Company. Callcentric apparently didn't bother to contact the other carrier I listed in my note, so, of course, they're not going to find the problem. They're being unreasonable in claiming that it's all being caused by Google picking the lowest cost route. That's frankly bullshit. Yes, Google has routing algorithms. All carriers do. But, I can tell you from direct discussions with Google employees, that their focus is on reliability and call quality, not just cost. They have monitoring and automation in place to specifically detect and solve those issues, which they do not want their users to put up with. When a particular call route or particular carrier is causing problems, they either get it fixed, or ban that carrier on that route. These issues are downstream from Google, and CC will either need to cooperate and troubleshoot, or GV users will simply stop using CC Telengy DIDs. Perhaps CC doesn't make enough money on those DIDs to feel it's worth it to expend any effort on them.
My last word to you on this issue is to simply move on. Either use Google Voice directly on your OBi and forget about CNAM, or pay the small amount of mony to get better reliability by using Callcentric with a non-Telengy DID like Roger suggested, or abandon GV and use CC or some other quality ITSP like voip.ms directly, without GV. As always with telephony, the more direct and simple the path, the more reliable the service will be.
Rick:
Steve - please re-read what I posted. I stated what CC told me, I pushed back on them and told them exactly what the problem was, I told them that my VZW cell rings very quickly, so the issue is GV to CC, not GV to everything. I told them that both carriers have logs of the issue, and I then dialed it numerous times to show them it still existed.
You need to take a chill pill. I'm not being cranky or complaining to you. I merely posted what CC told me, and said it was probably biased and possibly wrong. You read way to much into things.
I have no intention of moving on. I intend to push CC to resolve the issue. I did that by opening a ticket and telling them that there FAQ was inadequate, and asked them to get more involved in solving the problem. I also told that that if it would help, I suspected that the person who got my info to GV (you) MIGHT be willing to connect them directly to the GV engineer and the two carriers so that the same people are talking together and brainstorming how to resolve the issue.
I don't know how a problem like this can exist for a month and it not be resolved by any of the parties, other than either they don't know it's happening, they don't know the magnitude that it's happening, or it's such a small portion of total volume that they cannot see it. To me, it's unacceptable (forget who is at fault). Doesn't matter if it's free service, the quality is unacceptable with these issues. All companies involved (GV, CC, the two carriers, etc.) should be focused on fixing the problem and not pointing fingers.
If you want to keep helping, that's much appreciated (right now I don't need any help). If not, fine, move on. I appreciate the help you've provided.
I'm going to keep pushing CC. I have no way to communicate to GV besides you, so if they ask for a contact I'll post that and you can provide it, or not, your choice.
Rick:
Steve -
Here is Callcentric's latest reply to my trouble ticket (I added bold and color):
We cannot know for sure where the problem lies. As a provider our main concern here is whether your number can be reached from the PSTN. As you said before it can. You have introduced GoogleVoice into the equation which is the point of pain for this issue.
If GoogleVoice can provide the logs showing that the call is failing at our gateway then we can better investigate it. However our tests show that Bandwidth and Broadvox are able to properly complete to our number, including your as you experienced yesterday.
Can GoogleVoice provide you with information they received from bandwidth or Broadvox showing that the calls are failing at our switch? This would be helpful if it can identify the reason for the failure.
If you want to connect these guys, feel free to reference my trouble ticket #212848-11 and open a trouble ticket at CC and provide them with whatever info you can, or your Google contact's information. I'm sure they would appreciate it, I know I would.
FYI, I responded to them as follows:
I'm a bit confused. I demonstrated yesterday, and found the same result today, that calls placed to my GV number that forwards directly to Callcentric are NOT completing in a timely manner - which is exactly the same problem that has existed for a month.
So, I don't understand how you were able to successfully test my number completing with Broadvox and Bandwidth.com, since it does not work properly. You dial my GV number and it takes 15 - 20 seconds to ring my phone (GV to CC), if I'm lucky I get one ring before GV picks up, sometimes a partial ring or no rings. Forwarding my other GV number to IPComms then CC rings immediately. Forwarding to my cell rings in about 5 seconds.
This problem has existed for at least a month, and nothing has changed in the past few days - so again, I don't know what you tested that worked successfully yesterday with my number. It worked fine from May until about a month ago (can't pinpoint exactly when it started because I don't get enough call traffic to notice it, and I was ringing both my cell and house phones simultaneously).
I have no way to get GV to contact you. There is a contact that I know that has a contact at GV. I am giving him your message in its entirety, and my response. Since he is a CC customer also, I suggested he provide whatever info he can in a trouble ticket and reference my trouble ticket number so you can connect the dots.
I'm frustrated because GV has had discussions directly with Broadvox and Bandwidth.com about this issue. You've had direct discussions with Broadvox and Bandwidth.com about this issue. Perhaps ALL OF YOU could get on the phone together, making sure everyone is communicating clearly, and get this resolved quickly.
I am sending this to Steve also, my contact that knows GV engineers. And, I will keep my fingers crossed that the four parties (CC, Broadvox, Bandwidth.com, and GV work TOGETHER, without pointing fingers, to resolve the issue and ensure that the you and GV are talking to the SAME contacts at Broadvox and Bandwidth.com.
Thank you.
Steve, if you could get them in direct touch with GV I, and I'm sure others, would greatly appreciate it.
Rick
Navigation
[0] Message Index
[#] Next page
[*] Previous page