Can't block CID
ianobi:
Quote
Note that in your message's suggested change, there are only nine x's instead of ten x's, which I assume was a typo on your part.
Yes, I think the "x" key on my keyboard may be getting worn after so many digitmaps! Every little "x" is important, so I will go back and add that one to my original post in case anyone copies it.
Quote
My "311/511/911/933" stuff is set in the PHONE1 OutboundCallRoute rather than the ITSP DigitMap.
This is fine so long as the same numbers also appear in the Phone Port DigitMap. 911 is there by default. If you put them in ITSP Profile B, then they will appear in Msp2, which is in the Phone Port DigitMap and OutboundCallRoute, so the numbers are there "by reference". If say 311 is not in the Phone Port DigitMap, then it may get processed by the "xx." rule in your PrimaryLine DigitMap (in your case also Msp2), which will work, but will add a ten second delay.
My original suggestion dropped these from the DigitMap: xx.|(Mipd)|[^*#]@@.
xx. matches any digit followed by any number of digits, the "catch all" rule. It adds two seconds to number processing and if all possible numbers are matched anyhow in the digitmap, then it has no purpose. Although see paragraph above.
Mipd allows you to dial IP addresses - I don't think you will do that using CC.
[^*#]@@. allows you to use sip uri calling. It allows any alphanumeric character followed by any number of alphanumeric characters, but not starting with "*" or "#". Again I don't think you will be using this for CC. This rule also acts as "xx." as far as digits are concerned.
Anyhow, it seems to me you have a good grasp on "How to Configure Your OBI". The problem is it is so configurable that there is often more that one way to achieve the same result.
tvBilly:
Quote from: ianobi on August 18, 2013, 02:36:18 am
Quote
My "311/511/911/933" stuff is set in the PHONE1 OutboundCallRoute rather than the ITSP DigitMap.
This is fine so long as the same numbers also appear in the Phone Port DigitMap. 911 is there by default.
And indeed my Phone Port Digimap has: [359]11
Quote
Mipd allows you to dial IP addresses - I don't think you will do that using CC.
[^*#]@@. allows you to use sip uri calling. It allows any alphanumeric character followed by any number of alphanumeric characters, but not starting with "*" or "#". Again I don't think you will be using this for CC. This rule also acts as "xx." as far as digits are concerned.
Thanks for the help, and the continuing education. I have another question, but it has nothing to do with this, so I'll start another thread.
This is a nice place to hang out.
ipse:
Guys, I have the same problem, but in my case it's with POTS....no funny business here, the phone connected straight to POTS works just fine blocking CID, once I send it through OBI110 it's understood but ineffective.
Do I really need to start playing around with the digits map for something as simple as this?
TIA
tvBilly:
Silly question 1: Are you sure the Obi is dialing out on your POTS line rather than one of your VoIP lines?
Without seeing your settings, the only think I can think of to suggest is to dial your outbound call that you want sent from your POTS line with CID blocked by prepending a # before the rest of the dial string. If I remember my reading here, the leading # tells the Obi to just connect your phone immediately to the POTS line, and whatever else you push on the touch tone pad will just go out your POTS line unmolested.
So if you wanted to call 12125551212 out your POTS line with your CID blocked, you would enter #*6712125551212.
Since you didn't go into a lot of detail, and I don't understand what you mean by "it's understood but ineffective", I can only suggest you try the above, and if it's not sufficient for what you want (or it just doesn't work either), then a little more info about what you want to do and what your settings are will help.
ps I don't know squat compared to a lot of others here...
Navigation
[0] Message Index
[*] Previous page