Callcentric and Google Voice Setup Guide (with CNAM)
CoalMinerRetired:
> for the CNAM, it only show "city of XXX", "cell phone, IL" etc, is this normal?
Yes, the calls in all likelihood are from cell phones, which do not always have the CNAM field populated. Any outgoing calls from your number will probably appear like this also. FYI, you can override the CNAM entries in the CC Dashboard under Phone Book.
> For 911, I dial 933 but from call history, still using gv on SP1 instead of SP2.
Two things to check/verify:
- From the ObiTalk DashBoard > Device Configuration > Phone Port Configuration Summary, confirm "Emergency Service Call Routes to:" SPx for both Phone 1 and Phone 2
- In Expert Mode Configuration, confirm: Physical Interfaces > Phone 1 (or Phone x) > PHONE Port > OutboundCallRoute shows this at the beginning of the string: "{911:sp2},{933:sp2}," excluding the double quotes.
The 933:sp2 is what to look for here, If it's not there, I don't think you should add it manually because it's supposed to be inserted by the setup wizard, and if you're new to this you don't want to do expert mode digit map changes yet. The simple explanation is 911 and 933 both need explicit routing entries in the outbound call digit maps. In my case they just appeared at one point after I recreated the CC configuration (i,e., the setup wizard knew to create them). I noticed them and after reading something in CC's website was pleasantly surprised to see than 933 work as described, a voice reads back your address, i,e., a self test of 911.
Hope this helps,
heny:
> From the ObiTalk DashBoard > Device Configuration > Phone Port Configuration Summary, confirm "Emergency Service Call Routes to:" SPx for both Phone 1 and Phone 2
In the ObiTalk DashBoard > Device Configuration, I could not find phone port configuration summary.
>PHONE Port > OutboundCallRoute
In the PHONE Port > OutboundCallRoute, I didn't find that string, I added {911:sp2},{933:sp2} at the beginning of the string, now 933 is working, it repeat my address correctly. However the phone number(631 area code) it say is not my callcentric 631 area code phone number. is this a concern that needs to check with callcentric?
also when I call 933, it has about 10 seconds silence before the ring tone starts, is it normal?
thanks!
Shale:
Quote from: heny on June 27, 2013, 12:40:19 pm
>PHONE Port > OutboundCallRoute
In the PHONE Port > OutboundCallRoute, I didn't find that string, I added {911:sp2},{933:sp2} at the beginning of the string, now 933 is working, it repeat my address correctly. However the phone number(631 area code) it say is not my callcentric 631 area code phone number. is this a concern that needs to check with callcentric?
also when I call 933, it has about 10 seconds silence before the ring tone starts, is it normal?
I was going to suggest that heny modify the ITSP General DigitMap for his 911 provider to something like mine which is now this:
(933|*xx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.)
That's alarming to me. I am thinking it should be something like
([2-9]11|933|*xx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.)
The reason would be to cause 911 to not have to wait for the 10 second timeout. Is there something that I am missing, or should I be worried?
My existing string was put in by OBiTalk setup, and I have not overridden that field.
ianobi:
Quote
In the PHONE Port > OutboundCallRoute, I didn't find that string, I added {911:sp2},{933:sp2}
Your addition is correct and means that 911 and 933 are routed directly from the Phone Port OutboundCall Route and do not require to be in the ITSP General DigitMap.
The problem here is that 911 is in the Phone Port DigitMap by default, but 933 is not. Simply add 933 to the Phone Port DigitMap:
([1-9]x?*@@.|[1-9]S9|[1-9][0-9]S9|911|933| etc ...
The ten second delay is caused by 933 having to be processed by an xx. rule in the PrimaryLine DigitMap as it is not matched in any other DigitMap.
For an OBi202 the changes should be made for both Phone Ports 1 & 2 OutboundCallRoutes and DigitMaps.
heny:
Quote from: ianobi on June 27, 2013, 01:50:26 pm
Quote
In the PHONE Port > OutboundCallRoute, I didn't find that string, I added {911:sp2},{933:sp2}
Your addition is correct and means that 911 and 933 are routed directly from the Phone Port OutboundCall Route and do not require to be in the ITSP General DigitMap.
The problem here is that 911 is in the Phone Port DigitMap by default, but 933 is not. Simply add 933 to the Phone Port DigitMap:
([1-9]x?*@@.|[1-9]S9|[1-9][0-9]S9|911|933| etc ...
The ten second delay is caused by 933 having to be processed by an xx. rule in the PrimaryLine DigitMap as it is not matched in any other DigitMap.
For an OBi202 the changes should be made for both Phone Ports 1 & 2 OutboundCallRoutes and DigitMaps.
I added 933 to the digitmap and seems shorten the delay to 3~4 seconds. I found an even quick way by dial 933#
thanks
Navigation
[0] Message Index
[#] Next page
[*] Previous page