| | #1 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | MAX shutdown Hello, I am new to the world of PBX, slowly learning. I would like to prevent unathorized persons from dialing long distance from phones in the common areas of our building. But would like anyone to dial the alarm company's 800# in case of an emergency (on the common area phones). I can see the Class of Service but I am not sure if this is possible to do on a per phone basis... I am sitting with the manuals going through them now. Thanks [Edited on 20/5/2003 by prefont] | ||||||||
| | |
| | #2 (permalink) | ||||||||
| Junior Member
Rep Power: 0 ![]() | Hospital joke Ok, I'm going to attempt to answer my own question. To change the COR (Class of Restriction) per extension: "list cor" this lists the current COR levels "display cor #" where # is the level you would like to view once you have determined what COR you would like apply to the extension "change station xxxx" replace with the extension # and tab over to the right hand of the screen to COR and change this to the appropriate level. For our PBX COR 1 was 911,800,888,877 and 4 digit dialing, so this COR was chosen for the phones in the common areas to prevent unathorized dialing. Maybe this will help other PBX newbies. | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member
Location: Tolland, CT Rep Power: 6 ![]() | Merlin Legend programming help You are correct that the class of restriction on the station form is what you are going to want to adjust. But it's deeper than that. On each individual COR page is a list of restrictions, and one of these settings is the FRL. The FRL is a scale from 0 to 7. The FRL number is used to grant certain permissions when dialing. 0 is the most restricted, 7 being the least. Now to see just what is restricted, you will need to access your ARS tables. In your ARS tables, you will see all of the potential dialstrings someone could dial. Next to the minumum and maximum digits is a route pattern. A good ARS table should have one local route pattern and one long distance route pattern. Others aren't so clean (RAISING MY HAND....hey, I inheireted this mess). Anyway note the long distance route pattern and type disp route XX. Now on the route pattern, you'll see the trunk groups to be used listed in priority. To the right of the trunk group you'll see an FRL setting. This is where the FRL on the COR page will come into play. On a route pattern you can restrict access to certain trunks by raising or lowering the FRL requirement. So if your "non long distance" stations have an FRL of 2 in their COR form, then you want the trunks on your long distance route pattern to have an FRL of 3 or higher. I know this description is a little scattershot, so if you have any questions, give me a shout! __________________ Moderator - Avaya / Lucent Definity Boards | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| How to check External Transfer? | dominick | Meridian Systems | 10 | 03-21-2006 03:53 AM |
| Long Distance Routing Problem | javy_rdz | BCM and Norstar | 2 | 09-17-2004 04:35 PM |
| Long Distance Routing Problem | javy_rdz | Meridian Systems | 3 | 09-16-2004 10:06 AM |
| Help with long distance? | glehman | Meridian Systems | 4 | 10-03-2003 10:58 AM |