On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT
Started by mo832, April 30, 2023, 08:19:52 PM
Quote from: MSRobi on May 01, 2023, 04:34:03 AMSince your inbound calling is through CallCentric, I would scour the Callcentric settings for anything that looks wrong. It is possible CallCentric changed their interface, maybe added a new setting with a default that isn't right for your needs. I use personal GV, not Google Workspace GV, and I don't see anything in the settings that matter.
Quote from: MSRobi on May 03, 2023, 06:13:59 AMSince call waiting works if the first call is initiated from CallCentric when the second call comes in, but it doesn't when the first call is initiated outbound from GV, I suspect the problem on CallCentric side. I suspect CallCentric is handing the call off to GV differently when it doesn't know that the line is in use because you initiated the first call outside of CallCentric.I do not know CallCentric since I don't use it. And it is entirely possible (even likely) that there is nothing in your control to fix the problem.
Quote from: Taoman on May 19, 2023, 03:33:58 PMHow often is this actually an issue for you? Do you have a particular need to answer unknown callers (like running a home business)? If not, I suggest the following:1>If you haven't done so already, create a custom rule for all your Contacts to route them to Callcentric. (although they won't actually route there)2>Disable your OBi device in GV settings. This stops unknown callers from ever ringing your OBi device directly. But your Contacts will ring straight thru to your OBi (and not to Callcentric because routing straight to your OBi device is faster than forwarding to Callcentric so Callcentric loses the race).3>Enter all of your Contacts' names/numbers into your phone's phonebook so you still get name display on your phone for your Contacts (since you won't be getting CNAM from Callcentric for your Contacts)While you may think this is a hassle, consider that without forwarding to Callcentric you have one less hop in your call path which means less latency and better call quality which you probably want for your Contacts.If you follow the above steps, call waiting will work normally for your Contacts even if you initiated the call from your OBi. All unknown callers will still be immediately routed to GV voicemail. No getting around that unless you didn't initiate a call in which case unknown callers will still be routed to Callcentric.
Quote from: azrobert on May 22, 2023, 10:07:24 PMI was able to reproduce your problem using another provider's DID, so it looks like you're correct that it's a GV problem and not Callcentric.It appears that GV won't route inbound calls to a forwarding number when on an active outbound call.I got it to work by routing inbound calls to both the OBi and my DID. This won't help you because the GV direct to OBi calls should beat the GV to Callcentric, so all inbound calls when line is not busy won't get CNAM. I Think it might work if you delay GV direct calls.Do you have an open SP on your OBi or another OBi device? I'm thinking routing the direct calls to a 2nd extension on Callcentric and then back to the OBi. Hopefully, this will delay the direct calls long enough.I never got around to ask you if your zip code 85268?
Quote from: azrobert on May 23, 2023, 09:50:13 AMEnable the GV line by checking it in GV settings. Now the OBi will receive GV inbound calls on 2 lines. The bug prevents the Callcentric line from ringing when the OBi is busy with an outbound GV call, but the call will come in on the GV line and you will get the call waiting tone. I have tested this and it worked.
Quote from: azrobertsp4(firstname.lastname@example.org)You have to route the call with a URI, otherwise the CallerID won't route correctly.
Quote from: mo832 on May 23, 2023, 12:36:23 PMSo, given that GV is doing this and they never did it before, do you have a notion of why this is? I don't think it coincided with the EOL announcement or the removal of the legacy GV site, since this never showed up for me until recently. It seems like it could be no more than a few months.
Quote from: mo832Can you or Taoman explain how to route contacts to Callcentric ("although they won't actually route there")? Huh?
Quote from: mo832Also explain how to ring "straight thru to the Obi" even AFTER disabling the Obi in GV settings?
Quote from: Taoman on May 23, 2023, 01:15:44 PMNote: I pulled out my OBi200 to test on and I got different results. With the OBi200 disabled in GV settings, all inbound calls were routed directly to my GV trunk (including non-Contacts).
Quote from: azrobert on May 23, 2023, 03:20:58 PMIf calls only arrive via GV line when contacts are defined, how do you get CNAM from the Callcentric line?
Quote from: azrobertEdit:I get it, I think. You get CNAM from the GV contact definition. Callcentric is useless with this setup. Why have it? Or do I not understand?