Originally posted by *69:
Originally posted by telephoneguy:
[b] You can break down LCR in command 8A405, something like this:
...
8A405>554>001
8A405>5550>001
8A405>55510>001
8A405>55511>001
8A405>555121>001
8A405>555122>001
8A405>5551231>001
8A405>5551232>001
8A405>5551233>001
8A405>5551234>002 this no. is blocked, invalid route
8A405>5551235>001
...
8A405>5551239>001
8A405>555124>
...
8A405>555129>
8A405>55513>
etc.
This looks like what i`m needing just have a few questions about this.
Is this a system wide feature or is there another program that i need to specify what extension will use this lcr?It's system wide, if you want to specify numbers that can or can't be called, but you can restrict it to certain phones.
2nd do i have to manualy input all numbers associated with 555 meaning 555-1***, 555-2***, 555-3***, 555-4***, etc.
Yes,if you want to be able to call them at all
My assumption is that all i have to do is mess with 555-1*** block of numbers. And i`m hoping i can put in a range of 555-1000-1999 as 001 and manually go back and change 555-1234 to 002.
Not exactly. >5551 means "all numbers that start 555-1xxx." If you have 5551 in the table, you can't put 55510, 55511, 55512, etc. This is not like Mitel, which allows conflicting numbers in the ARS table.
Kind of confused about why you put 554 on the list.
To illustrate that you need a route pattern for every possible step, and you have to break out every digit down to the one you want.
3rd i dont see in the manual that 001 specifies that it is allowed and 002 says its not allowed. [/b]
That's part of the Routing... I gave that as an example...
Okay... Dr. PBX has a point, LCR done wrong is something that can easily screw up a system. A qualified tech would make a world of difference. Failing that, write down everything that you do, so that you can undo it if the results aren't what you wanted.
LCR in the 2000 works like this (overview):
CM 200 (dialing plan) points a digit string (like 9) at the LCR charts.
Note: With IVS, the number of digits in the commands may vary (i.e. 8a405 = 8a4005 in IVS2/IPS) :
200>9>A126
There's a voodoo command, 8AA00. Don't ask why, just do this:
8AA00>0>405
8AA00>1>406
8AA00>3>407
Then your LCR table is 405 (you can also use 406 and 407, but that's more advanced). So in 8A405,you list every number that you want to dial:
8A405>554>001 means that 9,554-xxxx will go out route pattern 001. The 9 automatically gets stripped off.
If you don't have that entry, no one can call 554-xxxx. But that's not the right way to block numbers.
If you notice the example I gave, every possible dial string between 554-xxxx and 555-13xx are pointed to a route pattern (001 or 002).
My next step would be to put a trunk group and toll restriction pattern on the route pattern. Don't panic, it's easier than it looks.
8A001 means route pattern 001 (from 8a405)
8A001>1>44 222 means that route pattern 001 goes out trunk group 44 with toll restriction pattern 555. The 1 means "first choice." If you want a second choice, you use:
8A001>2>33 222 (trunk group 33, toll pattern 222)
Okay, now calls will go out.
Now I make a second route:
8A002>1>44 777 (this route pattern, 002, uses the same trunks, 44, but a different toll pattern, 777).
Now we set toll restriction. This coordinates with command 8103, but you don't need to make any changes in 8103.
8A5222 (the 222 is from 8A001>1>44222)
8A5222>00>03 because we want everyone to be able to use this route.
8A5777>00>06 because we want to restrict this route.
Now, last step: setting toll restrict for the phones:
1202>xxxx>11 This phone can use either route, day or night.
1202>xxxx>33 This phone can use route 001, but not route 002, day or night.
1202>xxxx>44 This phone can't use either route.
1202>xxxx>14 This phone is unrestricted by day, and totally restricted in night mode.
Okay, that's LCR in a nutshell. It should answer the questions you asked.