Extension

[PhoneTeck]

How would I go about setting an extension up to where you can call out but no one can call in on it.


Any Ideas?????

 

[jaymzter]

Assign this phone to a particular COR, let's say COR 10. Perform a 'change COR 10' and set called party restriction to whatever your preference from below may be.

Called Party Restriction - Enter one of the following: "inward," "manual," "public," "termination," or "none."
Inward - Blocks the calling party from receiving incoming
exchange network calls, attendant originated calls, and attendantcompleted calls.
Manual - Blocks the called party from receiving all calls except for those originated or extended by the attendant.
Public - Blocks the called party from receiving public network calls. Attendant calls are allowed to go through to the called party as are attendant-assisted calls if the Restriction Override field in the public restricted station's COR is set to "attd" or "all."
Termination - Blocks the called party from receiving any calls at any time.
none - No called party restrictions.

 

[AvayaHelp]

I'm not sure what you are looking for exactly but if you are looking for a way to lock down the outbound calls from Agents, you can use group dialing with an FAC code. This way you preprogram the outbound number and then assign a code to it. The Agent then uses the FAC and the associated code to dial out the number allowed and no other number. Is this what you want?

 

[PhoneTeck]

I dont have any agents im wanting to do this with, I was just looking for a way to be able to just dial out on a extension but to restrict calls from coming in.

 

[wmharris]

Setup an extension that is not a DID. So if you had DID's that were in the range 4400-4499 then assign another extension like 9999, 1500, etc. No one should be able to dial into these directly but they can still dial out. Be sure to change the dial plan if needed to support the internal extension range.

 

[Bobg1]

Follow what jaymzter suggested.
The other thing you can do within the cor is set which
other cors the ext will be allowed to call.

 

[avayaman]

If you have a console, another way is to give the extension client room COS. This way the Attendant can control the extension. In the feature form there is a prompt called "User control restrict activation". Note the 2 entries there eg *05 - deactivate #05). In system parameters set "controlled toll restriction replaces" to "station-station".

The console will be able change the behaviour of this extension.

This is the way Hotels (or their PMS systems)control the nature of guest room phones (eg. an unoccupied room phone can only call local to local)

The attendant would enter the following depending on how they want the extension to behave.

*051XXXX (where XXXX is the extension)- local to local only - incoming allowed
*052XXXX - No calls in or out
*053XXXX - Out but no in
*054XXXX - Out & In but no local to local

#05 (1-4)XXXX cancels.

Paul Beddows

Consulting, Avaya/EAS implementation, Training
Vancouver, Canada
E-mail use form on website at

http://www.vancouver.hm/email1.html

 

[avayaman]

By the way, I think its obvious, but maybe that's just me, but you set an extension to "client Room" in the COS form, put a "y" on the client room line under a spare COS & assign it to that phone, copy the "y" prompts from its current COS for the other lines. I might also add that *054XXXX above will force the extension to reference the Toll Analysis table which does nto seem to be used much these days, but it could cause some unexpected LD restrictions to appear on it. In your case, however you woudl be using choice 3, not 4.

Paul Beddows

Consulting, Avaya/EAS implementation, Training
Vancouver, Canada
E-mail use form on website at

http://www.vancouver.hm/email1.html