News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Callcentric *67 Configuration

Started by Steve56, July 09, 2018, 09:16:37 PM

Previous topic - Next topic

Steve56

After the announcement of the retirement of Bill Simon's Google Voice gateway, I began making plans to migrate to another service provider. The free ride was nice while it lasted.

Callcentric has been configured and is currently working for receiving and placing calls. However, one feature I use very frequently doesn't appear to be working correctly: *67.

If I leave the star codes settings to their default, and precede a phone number with *67, my caller ID information is still sent to the called party. Callcentric does support *67 for caller ID blocking on a per-call basis, I'm just a little lost in how it needs to be implemented on the ATA side.

A little more info:
ITSP Profile A (Callcentric) Digit Map:
(*123|*66|*67|*69|*70|*72|*73|*78|*79|*80|*82|*77|*97|*87|911S0|933S0|<1201>[1-9]xxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011[1-9]xxxxxxxxxxS4|011[1-9]xxxxxxxxxxxS4|011[1-9]xxxxxxxxxxxxS4|011[1-9]xxxxxxxxxxxxxS4|011[1-9]xxxxxxxxxxxxxxS4|<211:18776521148>S0|<311:12126399675>S0|<411:18003733411>S0|<511:18665116538>S0|<811:18002721000>S0)

As it seems right now with *67 in the above digit map, the moment I dial *67, it is sent right to the service provider (Callcentric) which gets me an invalid number error.

Not sure what to do at this point, just need to get it working.
Thanks!

A_Friend

#1
Are you trying to block caller ID on ALL calls?

If so, you can do that from the Callcentric account page.  Just click on Extensions, modify, and set "Block Caller ID" to Yes.  You can then send caller ID on individual calls with *82.

FWIW, this is my Callcentric digit map:

(*xx.|**275*x.|[3469]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)

I'm not going to claim to be an expert in digit maps, but I think when you put something like *67 in there, that's explicitly exact for just what it will send.  In other words, after seeing those three keys in a row, it's done and stops listening for more digits.  What I have in mine ("*xx.") is way more permissive and probably what you want.  It'll send whatever you key in after * and at least two numbers until you're either done keying (as shown by a few seconds of silence) or hit #.

drgeoff

Quote from: Steve56 on July 09, 2018, 09:16:37 PM
After the announcement of the retirement of Bill Simon's Google Voice gateway, I began making plans to migrate to another service provider. The free ride was nice while it lasted.

Callcentric has been configured and is currently working for receiving and placing calls. However, one feature I use very frequently doesn't appear to be working correctly: *67.

If I leave the star codes settings to their default, and precede a phone number with *67, my caller ID information is still sent to the called party. Callcentric does support *67 for caller ID blocking on a per-call basis, I'm just a little lost in how it needs to be implemented on the ATA side.

A little more info:
ITSP Profile A (Callcentric) Digit Map:
(*123|*66|*67|*69|*70|*72|*73|*78|*79|*80|*82|*77|*97|*87|911S0|933S0|<1201>[1-9]xxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011[1-9]xxxxxxxxxxS4|011[1-9]xxxxxxxxxxxS4|011[1-9]xxxxxxxxxxxxS4|011[1-9]xxxxxxxxxxxxxS4|011[1-9]xxxxxxxxxxxxxxS4|<211:18776521148>S0|<311:12126399675>S0|<411:18003733411>S0|<511:18665116538>S0|<811:18002721000>S0)

As it seems right now with *67 in the above digit map, the moment I dial *67, it is sent right to the service provider (Callcentric) which gets me an invalid number error.

Not sure what to do at this point, just need to get it working.
Thanks!
Try disabling Code5 (it is *67) in the list in whichever of Star Code Profile A or B is appropriate.

Disabling that should mean that the code is passed to Callcentric.