Will GoogleVoice stop working on all deployed OBi devices after May 15?
lhm.:
@MikeHObi
I have the same setup and get CID but not Cnam (IpKall > 1777XXXXXXX@in.callcentric.com). Do you get Cnam inbound? If so how are you setup from IpKall?
carl:
Quote from: SteveInWA on December 12, 2013, 08:38:10 pm
They're leveraging that CLEC to make some money on the inbound call interconnection fees, and it isn't exactly a world-class CLEC...free means cutting corners and using the cheapest possible routes. It's not surprising that Google's CLEC might be reacting to that by also using some low-grade/low-cost route to connect. Some of those routes have been known to not pass CID at all, or to mess it up, which is exactly what's happening. I am not an apologist for either side;
It would need some good explanation what a terminating carrier like Telengy has to do with routing, incoming signalling and all of that.
SteveInWA:
Quote from: carl on December 14, 2013, 04:08:12 pm
Quote from: SteveInWA on December 12, 2013, 08:38:10 pm
They're leveraging that CLEC to make some money on the inbound call interconnection fees, and it isn't exactly a world-class CLEC...free means cutting corners and using the cheapest possible routes. It's not surprising that Google's CLEC might be reacting to that by also using some low-grade/low-cost route to connect. Some of those routes have been known to not pass CID at all, or to mess it up, which is exactly what's happening. I am not an apologist for either side;
It would need some good explanation what a terminating carrier like Telengy has to do with routing, incoming signalling and all of that.
Regardless of your desire for an explanation, the fact is, that calls routed from Google's CLEC to Telengy are either corrupting or losing caller ID or not being connected. Google and Callcentric are now aware of this fact, and they're trying to resolve it. Calls routed from Google's CLEC to other carriers (ILECs or CLECs) are working as expected, with a few periodic exceptions caused by LNP or inter-carrier routing errors.
SteveInWA:
Quote from: lhm. on December 13, 2013, 01:56:32 pm
@MikeHObi
I have the same setup and get CID but not Cnam (IpKall > 1777XXXXXXX@in.callcentric.com). Do you get Cnam inbound? If so how are you setup from IpKall?
As you may be aware, CID is (supposed to be) passed along with the call setup by the originating carrier. So, as long as it isn't broken (like it is with the GV-->Telengy situation at the moment), and as long as the originating caller hasn't blocked it, you'll get it at the terminating end. CNAM, on the other hand, is not transmitted with the call, but instead, is obtained via a database lookup by the terminating carrier during the ring period.
IPKall, being a free service like Google Voice, doesn't pay for CNAM -- it isn't doing the CNAM lookups. So, you won't get CNAM via IPKall. CC does do the lookups for its DIDs, even their free ones.
lhm.:
"IPKall, being a free service like Google Voice, doesn't pay for CNAM -- it isn't doing the CNAM lookups. So, you won't get CNAM via IPKall. CC does do the lookups for its DIDs, even their free ones."
It appears forwarded GV calls via IPKall to CC (free DID) via SIP will not show CNAM just CID. At least not for me.
Navigation
[0] Message Index
[#] Next page
[*] Previous page