Telecom Technical Mitel SX-2000: how to (un)block area codes

>We have an SX-2000 that is (I think) currently blocking calls to area
>code 809 (the Dominican Republic.) I haven't been able to find anyplace
>in the switch that deals with this sort of thing, although I seem to
>recall stumbling over it once while looking for something else.

>I can't find any reference to such blocking in the Features and
>Services binder so maybe it is not the switch doing this. Can it? And
>where would I find its table in CDE?

>Thanks for any pointers,

> reedl@tatteredcover.com writes:
>

>>We have an SX-2000 that is (I think) currently blocking calls to area
>>code 809 (the Dominican Republic.) I haven't been able to find anyplace
>>in the switch that deals with this sort of thing, although I seem to
>>recall stumbling over it once while looking for something else.

>

>>I can't find any reference to such blocking in the Features and
>>Services binder so maybe it is not the switch doing this. Can it? And
>>where would I find its table in CDE?

>

>>Thanks for any pointers,

>
> There are a number of ways to block area 809 (or any particular digit
> string or range of digits for that matter) on the SX-2000
>
> First of all, blocked simply by omission. In other words, the digit string
> '809' does not appear in the ARS table and there are no wildcard
> combinations programmed to include this range. Open the AU (automatic
> Route Select) table, type in leading digit '8' and hit recall. With this
> table open, look for the digits dialed 09 and # of digits to follow = 7
> - OR leading digits 8 and "unknown" to follow, or leading digits '80' with
> 8 digits to follow. If none of these combinations appear then 809 is
> blocked by omission. You dial 809-xx etc and the phone displays "invalid"
>
> Secondly, blocked explicitly. This time one of the above described
> scenarios exists and is directed to a specific route. The route contains a
> trunk group but the trunk group contains only 1 trunk. The trunk
> assignment form shows an "Interconnect" number. You check the Interconnect
> Restriction table to find that the interconnect number assigned to the
> trunk is restricted from accessing all 64 other interconnects. You dial
> 809-xx etc and the phone displays "CALL BARRED"
>
> Thirdly, blocked permissively. In this scenario only specific numbers in
> area 809 appear in the ARS table. Companies do this when they have a
> business relationship there, i.e., with a bank, and so they wish to
> "allow" only a handful of numbers, perhaps only one or two, and so the
> entire digit string(s) of the ALLOWED numbers would appear in the ARS
> table.
>
> Fourth, blocked by a simple digit conflict. Example, to place a call to
> a/c 809 you might have to dial 9-1-809-xxx-xxxx. To stop these calls you
> need only program up a DN on the pbx with the extension "91809". Try to
> dial a number in a/c 809 and you'll never get past the 91809 part of the
> call. A really tricky to do this is to bury "91809" in the feature access
> code table.
>
> Fifth, blocked by customer request at the LEC or LD carrier. Here the
> customer has requested their LD provider to block area 809 for them. This
> is really simple to do and is usually provided as a free or no-charge
> service. You can test this easily by dialing the Individual Trunk Select
> feature code + the 4-digit trunk number of one of your outside trunks,
> followed by 1-809-xxx-xxxx. If the call goes through, your LEC or IXC is
> not the one blocking these calls.
>
> I could go on, but you probably get the idea.
>
> WDG
>

> And finally if you don't understand how COR works you shouldn't be dicking
> around in your switch.
>

>> reedl@tatteredcover.com writes:
>>

>>>We have an SX-2000 that is (I think) currently blocking calls to area
>>>code 809 (the Dominican Republic.) I haven't been able to find anyplace
>>>in the switch that deals with this sort of thing, although I seem to
>>>recall stumbling over it once while looking for something else.

>>

>>>I can't find any reference to such blocking in the Features and
>>>Services binder so maybe it is not the switch doing this. Can it? And
>>>where would I find its table in CDE?

>>

>>>Thanks for any pointers,

>>
>> There are a number of ways to block area 809 (or any particular digit
>> string or range of digits for that matter) on the SX-2000
>>
>> First of all, blocked simply by omission. In other words, the digit
>> string
>> '809' does not appear in the ARS table and there are no wildcard
>> combinations programmed to include this range. Open the AU (automatic
>> Route Select) table, type in leading digit '8' and hit recall. With this
>> table open, look for the digits dialed 09 and # of digits to follow = 7
>> - OR leading digits 8 and "unknown" to follow, or leading digits '80'
>> with
>> 8 digits to follow. If none of these combinations appear then 809 is
>> blocked by omission. You dial 809-xx etc and the phone displays
>> "invalid"
>>
>> Secondly, blocked explicitly. This time one of the above described
>> scenarios exists and is directed to a specific route. The route contains
>> a
>> trunk group but the trunk group contains only 1 trunk. The trunk
>> assignment form shows an "Interconnect" number. You check the
>> Interconnect
>> Restriction table to find that the interconnect number assigned to the
>> trunk is restricted from accessing all 64 other interconnects. You dial
>> 809-xx etc and the phone displays "CALL BARRED"
>>
>> Thirdly, blocked permissively. In this scenario only specific numbers in
>> area 809 appear in the ARS table. Companies do this when they have a
>> business relationship there, i.e., with a bank, and so they wish to
>> "allow" only a handful of numbers, perhaps only one or two, and so the
>> entire digit string(s) of the ALLOWED numbers would appear in the ARS
>> table.
>>
>> Fourth, blocked by a simple digit conflict. Example, to place a call to
>> a/c 809 you might have to dial 9-1-809-xxx-xxxx. To stop these calls you
>> need only program up a DN on the pbx with the extension "91809". Try to
>> dial a number in a/c 809 and you'll never get past the 91809 part of the
>> call. A really tricky to do this is to bury "91809" in the feature access
>> code table.
>>
>> Fifth, blocked by customer request at the LEC or LD carrier. Here the
>> customer has requested their LD provider to block area 809 for them. This
>> is really simple to do and is usually provided as a free or no-charge
>> service. You can test this easily by dialing the Individual Trunk Select
>> feature code + the 4-digit trunk number of one of your outside trunks,
>> followed by 1-809-xxx-xxxx. If the call goes through, your LEC or IXC is
>> not the one blocking these calls.
>>
>> I could go on, but you probably get the idea.
>>
>> WDG
>>

>
>

>Whats wrong with the scientific method ?