The first issue is that each pattern can only have one circumflex character
(^). So, your pattern is invalid since it uses three.
If you want to block on the line level, then you can substitute three
patterns (configured to block) in your BLOCK_PT
[^5]XXX
5[^5]XX
55[^5]X
Your next issue is that your phone level CSS contains your Internal_PT.
According to your post all directory numbers are in the Internal_PT. So,
even if you replace your block pattern it still won't work as you desire
because of how CUCM does digit analysis. The basic rule is that the
longest match wins. So, let's assume a phone's DN is 5540 and you want to
block calls to this pattern. The pattern 5540 is a longer match than
55[^5]X. So, CUCM will always pick 5540.
One option is to add an "arbitration" layer. In my dial plan approach I
never put directory numbers in partitions that are directly assigned to a
phone or line CSS. This allows me to put a translation pattern (e.g.
[1-8]XXX) that acts as a "traffic cop" to my internal extensions. If that
were true in your dial plan then the 55[^5]X would work as desired (since
55[^5]X is a longer match than [1-8]XXX).
A second option would be to create the following blocking patterns:
[^5]: Set Urgent priority flag and set Block flag
5[^5] : Set Urgent priority flag and set Block flag
55[^5] : Set Urgent priority flag and set Block flag
The idea here is that if you go off hook on the lobby phone and dial "4"
then you get a fast busy right away. If you dial "54" you get a fast busy
and so on.
Now, another gotcha. While you do want to restrict the lobby phones from
calling whoever they want in the organization you may not want to block 911
calls. In this case, you would then replace the [^5] pattern with a [^59]
pattern and then use other PSTN blocking patterns to do their job (assuming
you aren't blocking 911 elsewhere).
Just some thoughts.
HTH.
Regards,
Bill
Please remember to rate helpful posts.
On 9/3/10 9:17 AM, "ilicveselin" <supportforums-donotreply@jivesoftware.com
Message was edited by: William Bell
Apparently the e-mail I sent had some characters which got corrupted. Fixed them (hopefully).
