dexman

It seems like the extension is restricted, but the $50k question is how?

I'm more versed with the Partner ACS than the Merlin Legend, so I'm going to throw a dart and see if it sticks to something.

If you have access to WinSPM, can you check the parameters of the extension and compare it with one that is known to work and see if there are any differences?

dagwoodsystems

Run a report on two extensions as Dexman suggested. Pay particular attention to the Disallowed Lists, Restriction and ARS Restriction fields. These parameters work independently to determine what can and cannot be dialed.

Here's how it works. Suppose you have two trunk groups: one with POTS and the other with digital PRI service. Now also suppose that you want a particular extension's phone calls to only go out over the POTS lines. To accomplish this, first make sure the extension is outwardly "Unrestricted", thus generally allowed to make outside calls. This is the crudest level of control.

Next, set ARS restrictions (a.k.a. FRL or Facility Restriction Level) for the extension and both available services: Set the PRI's FRL to 3, the POTS' FRL to 2 and the extension's FRL to 2. By making the extension's FRL equal to that of the POTS facilities, but less than that of the PRI facilities, a new level of control is introduced. The extension is still free to make outside calls, but only over the analog POTS.

Finally, Disallowed Lists (lists of undesirable phone numbers--or parts of phone numbers) provide one last level of control. Strings such as 900, 976, 411 and even 0 are common list entries. Assigning this list to a specific extension will prevent the station user from completing any call whose digits match a table entry.

So even if an extension is Unrestricted and FRL access to all available trunks and facilities, the Disallowed List will still have the last word on whether the call will complete or not.