CallCentric digit map
tome:
I signed up with Callcentric for 911 services. I have set it up on SP2 (and modified my outboundroutemap to add the 911 stuff RonR has posted in other threads. I tested a 911 call, an outbound to a mobile number and an inbound call from Callcentric's test stuff. Everything seems to be working fine. I have a question on their setup information:
In the setup information on the Callcentric web site they say:
Service Providers > ITSP Profile > General
Digit Map: (*xx.|**275*x.|[3469]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
What does this digit map do?
Tom
RonR:
*xx. -> Star Codes (this will disable the OBi's Star Codes)
**275*x. -> Sip Broker support
[3469]11 -> 311/411/611/911 (911 is already handled in the PHONE Port DigitMap/OutboundCallRoute)
1xxxxxxxxxx -> 11-digit dialing
<1>[2-9]xxxxxxxxx -> 10-digit dialing
011xx. -> International dialing
xx. -> let anything through
(Mipd) -> IP dialing
[^*]@@. -> SIP URI dialing (bad rule : matches way too much)
tome:
Quote from: RonR on August 30, 2011, 08:55:45 pm
*xx. -> Star Codes (this will disable the OBi's Star Codes)
**275*x. -> Sip Broker support
Thanks Ron, some questions...
Why would they want the * codes disabled and should I? And is the Sip Broker support required to use Callcentric? What is it exactly?
Quote from: RonR on August 30, 2011, 08:55:45 pm
[^*]@@. -> SIP URI dialing (bad rule : matches way too much)
Should I remove it or change it?
Tom
RonR:
Quote from: tome on August 31, 2011, 06:16:25 am
Quote from: RonR on August 30, 2011, 08:55:45 pm
*xx. -> Star Codes (this will disable the OBi's Star Codes)
Why would they want the * codes disabled and should I?
Just about everyone, including the OBi, supports Star Code features to block CallerID (*67), return the last call (*69), etc. The way the OBi is set up, it handles Star Codes unless DigitMap rules turn them over to someone else. This can be done selectively (*67|*69|...) or collectively (*xx|...). Unless you need a particular (or all) Star Code(s) to be handled outside the OBi, I recommend you don't change anything in this area.
Quote from: tome on August 31, 2011, 06:16:25 am
Quote from: RonR on August 30, 2011, 08:55:45 pm
**275*x. -> Sip Broker support
And is the Sip Broker support required to use Callcentric? What is it exactly?
Sip Broker might allow you to call users on other networks: Sip Broker
Unless/until you need Sip Broker support, I wouldn't worry about it.
Quote from: tome on August 31, 2011, 06:16:25 am
Quote from: RonR on August 30, 2011, 08:55:45 pm
[^*]@@. -> SIP URI dialing (bad rule : matches way too much)
Should I remove it or change it?
There are some DigitMap rule situations where [^*]@@. matches way too much and prevents the intended result (this rule matches ANYTHING that doesn't start with an *). Since the purpose of this rule is to match SIP URI's, I recommend using @@.'@'@@. (anything@anything) instead of [^*]@@. There is currently a bug on the OBi firmware, necessitating that this rule be written as [^*]@@.'@'@@. to prevent it from interfering with *60, *62, *72, and *74, which should not be occurring. If/when this bug is corrected, the [^*] can be removed.
tome:
Quote from: RonR on August 31, 2011, 09:37:28 am
There are some DigitMap rule situations where [^*]@@. matches way too much and prevents the intended result (this rule matches ANYTHING that doesn't start with an *). Since the purpose of this rule is to match SIP URI's, I recommend using @@.'@'@@. (anything@anything) instead of [^*]@@. There is currently a bug on the OBi firmware, necessitating that this rule be written as [^*]@@.'@'@@. to prevent it from interfering with *60, *62, *72, and *74, which should not be occurring. If/when this bug is corrected, the [^*] can be removed.
Ok, I will change it to: [^*]@@.'@'@@.
By the way, it was written as [^*#]@@. (with the #) on the CallCentric config page.
Thanks,
Tom
Navigation
[0] Message Index
[#] Next page