Callcentric and Google Voice Setup Guide (with CNAM)
SteveInWA:
No, extensions were implemented over the summer. http://www.callcentric.com/new/
I read your post several times, and I guess I am stumped now. I tried to post a screenshot of my Callcentric extension routing page, but the Obitalk forum posting system said the attachments folder was full. WTF.
Anyhow, if you place a call to your GV phone number from some unrelated phone, and you see the inbound call in your GV account's history on your GV account's web page, and you see the inbound call show up on your CC account's log of calls (as Anonymous), AND you haven't blocked CC from ringing your extension (and I think you've confirmed all that), then it ought to ring your OBi-attached phone. I hate to say it, but perhaps you should try resetting your OBi to factory defaults, as you might have done something to your configuration to cause this behavior.
Right now, my OBi-attached phones (and my IP phones) ring when the anonymous calls come in via the free DID, and (of course) they ring when calls come in to my other GV number via my paid DID, with Caller ID. So, "anonymous" caller ID shouldn't interfere with calls being received on the OBi-attached phone, unless you have a configuration setting causing it.
BTW, thanks for your support over on the GV forum thread. I gave up debating that guy -- people get blinded by "I deserve free beer for life", and it's just hopeless.
tome:
Quote from: SteveInWA on November 11, 2013, 09:02:41 pm
No, extensions were implemented over the summer. http://www.callcentric.com/new/
I read your post several times, and I guess I am stumped now. I tried to post a screenshot of my Callcentric extension routing page, but the Obitalk forum posting system said the attachments folder was full. WTF.
Anyhow, if you place a call to your GV phone number from some unrelated phone, and you see the inbound call in your GV account's history on your GV account's web page, and you see the inbound call show up on your CC account's log of calls (as Anonymous), AND you haven't blocked CC from ringing your extension (and I think you've confirmed all that), then it ought to ring your OBi-attached phone. I hate to say it, but perhaps you should try resetting your OBi to factory defaults, as you might have done something to your configuration to cause this behavior.
Right now, my OBi-attached phones (and my IP phones) ring when the anonymous calls come in via the free DID, and (of course) they ring when calls come in to my other GV number via my paid DID, with Caller ID. So, "anonymous" caller ID shouldn't interfere with calls being received on the OBi-attached phone, unless you have a configuration setting causing it.
Thanks. I am talking with CC support and they think it is something in my config in the Obi as well - they sent a log that shows calls are being sent and then rejected by my Obi. I am going over the config with a fine tooth comb before doing a factory reset (ugh).
Quote from: SteveInWA on November 11, 2013, 09:02:41 pm
BTW, thanks for your support over on the GV forum thread. I gave up debating that guy -- people get blinded by "I deserve free beer for life", and it's just hopeless.
Ah, didn't make the connection before. No problem, and I agree. I like all the finely honed arguments which keep people from just admitting that really they're pissed because the free beer is going away :-)
Tom
SteveInWA:
;D
While you're troubleshooting with them, give 'em a hard time about their now-canned answer about anonymous CID...they've been pasting that same answer into multiple tickets, and something's fishy if caller ID does work on their paid DIDs.
tome:
So I figured out that my specific problem is due to my InboundCallRoute which is:
Voice Services -> SP2 Serivce -> X_InboundCallRoute -> {(?|x|xx|xxx|xxxx|xxxxx|xxxxx|un@@.|anon@@.):},{ph}
The intention of this is to keep Unknown, Anonymous and random digit calls from waking us up at night. It has worked fine up until now. Simply removing "|un@@.|anon@@." is not enough. I have to remove everything and set it to the Obi110 default which is "ph" and it to works, calls come in.
I would still like to prevent random numbers less than 7 digits (usually called by scanners, hackers, etc) from ringing the phones. The Obi documentation on Inbound Call Route says:
caller := number OR embedded-digit-map OR ? OR @ (?=anonymous, @=any number but anonymous)
So, perhaps the leading "?" is the actual problem. Perhaps this is matching anonymous...
Tom
ianobi:
This is a question of defining what we mean by anonymous!
"anon@@." is designed to match the actual word "anonymous". This is sent by some service providers when they receive no CallerID.
"?" will match an incoming call with no CallerID. Status > Call History > Peer Number will be blank.
This will stop any CallerIDs of less than seven digits:
Voice Services -> SP2 Serivce -> X_InboundCallRoute -> {(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph}
There are other methods which may suit you better. For example search for the "Oleg method".
Navigation
[0] Message Index
[#] Next page
[*] Previous page