| | #12 (permalink) | ||||||||
| Junior Member ![]()
Rep Power: 39 ![]() | EXTN LOCKOUT The best way by far is to make 0 an extension n the dialplan & make it a hunt group access code. You will have to remove attd from sys parameters features under extension with retrieval permissions first. You should ALWAYS assign some over local (usually a set of 2 digits) as "Attd" if you do this. One advantage of making 0 a hunt access is that internal callers will not get cover tone when dialing zero which they will if you use the X-port solution. You can also use a hunt-ns key to provide night treament for the sial zero calls indepenedent of what you have done in the trunk group which can be an advantage. | ||||||||
| | |
![]() |
| 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 |
| Changing the number a set is forwarded to from off site. | pcutler | Meridian Systems | 7 | 11-28-2007 10:56 AM |
| moving extension | pab006 | IP Office | 3 | 08-30-2006 01:57 AM |
| dial extension in autoattendant | irvingalvarez | Meridian Systems | 1 | 05-05-2005 02:29 PM |
| I/C DID to CFW to COT fails | jshaw | Meridian Systems | 7 | 09-07-2004 10:34 AM |
| thru dial extension blocking | darby | Meridian Systems | 1 | 11-27-2002 11:29 AM |