Callcentric and Google Voice Setup Guide (with CNAM)
CoalMinerRetired:
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.
Another way to do eliminate the daley is add "S0" (uppercase S + zero) after the 911 and 933, as in the below markup. Explanation: S is CASE SENSITIVE. It should only be used either as the first element of a rule for hot/warm line implementation, or as the last element of a rule as a means of overriding the default interdigit timer.
([1-9]x?*@@.|[1-9]S9|[1-9][0-9]S9|911S0|933S0| etc ...
Disclaimer, I've used this, but not currently or recently.
heny:
Quote from: CoalMinerRetired on June 27, 2013, 03:22:51 pm
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.
Another way to do eliminate the daley is add "S0" (uppercase S + zero) after the 911 and 933, as in the below markup. Explanation: S is CASE SENSITIVE. It should only be used either as the first element of a rule for hot/warm line implementation, or as the last element of a rule as a means of overriding the default interdigit timer.
([1-9]x?*@@.|[1-9]S9|[1-9][0-9]S9|911S0|933S0| etc ...
Disclaimer, I've used this, but not currently or recently.
Thanks for the tip.
rickame:
I've gotten some good advice and will be making the leap, but am a little unclear how to set up Callcentric. I have a GV number set up on Obi100 as primary line for outgoing calls and incoming calls for folks calling GV number (on SP2 now). I want to port my landline to Callcentric (which is great since it can't be ported to GV), then have Callcentric for incoming calls to former landline number and for outgoing e911 calls. I assume that I should 'not' use the wizard that is linked from the Callcentric website, and just should configure on the ObiTalk site (as SPI) needing only the Callcentric number (my former landline) and password. Am I missing something, could it be this easy...Someone who knows please confirm as I don't want to mess with landline and access, my teen daughter would be upset:) Thanks....Rick
dircom:
you can get an idea of CC setup, by getting a free CallCentric DID
and using Obitalk website to configure it.
heny:
I followed instruction on this post and setup without problem. It worked ok. However recently I did noticed some delays when receiving calls. The symptom is that: sometimes when I picked up the phone, the other party continued to ring a couple seconds, so I didn't hear anything from the phone, usually I need waited a few seconds to see if other party connected. Very frustrated when this happen... What could be the possible issue? gmail side or callcentric side? Anyone has experience on how to fix it?
Thanks!
Navigation
[0] Message Index
[#] Next page
[*] Previous page