Restrict users from calling certain extensions? 1

[mnealtx]

Background: Customer needed a group hotline (group call for emergency response situations). Created a hunt group to ring the phones and a vector to bring them into a meet-me conference.

Question: How can I keep other users from dialing the hunt group number and mistakenly triggering the conference call?

 

[smokinjoe2938]

give the hunt group a unique cor called restricted; then on page two or three you can tell this cor who has permission to call the hunt group,then the people who you do not want to call this hunt group give them a cor that is restricted for calling the hunt group cor.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[mnealtx]

Please bear with me - I'm learning all this stuff as I go and by reading the manuals - I've had no training.

And, I mis-stated something in the original post - my apologies.

To clarify: All crisis team phones have to ring (notification to implement the conference). Current set up is all phones are part of a coverage answer group (not a hunt group - my apologies) so that they simultaneously ring when triggered. I have an x-port extension that covers to the CAG as path 1, then to the vector. I also looked at a hunt group, but realized that it wouldn't ring all lines.

We already have a COR 14 set up for the loop phones. If I set up the x-ported "master number" as the only number in the Hunt group, would that make it where only the COR 14 phones could dial that extension and trigger the CAG ring/conference? What would I need to change, and where (besides adding the x-port ext as the hunt group member and setting COR 14 on the hunt group)? Would I need the x-port number if I set the coverage path in the hunt group, without any 'member' numbers?

 

[smokinjoe2938]

if the xported phone has a cor of 14 and lets say a user has a cor of 10, go to change cor 10 and on page two you can say no to calling permissions to cor 14 from cor 10, hope this helps if I understand you correctly

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[mnealtx]

I've got 3 phones set up here in the office to test the conference.

I removed the coverage path from the X-port 'master' extension, and added it to the hunt group. Changed the abbrev-dial group to dial the hunt group extension instead of the x-port.

Placed COR 14 on the hunt group and added the coverage path number for the CAG/meet-me vdn.

Went off-hook with a test phone (COR 1 default), got the intercept dee-doo-dee-doo tone.

Changed COR of test phone from COR 2 through COR 6 (normal COR range for our users), same result.
Changed COR of test phone to COR 14, coverage path triggered. Other test phones rang and COR 14 phone entered conference.
Picked up another test phone (still at COR 1), got the intercept.

Looks like it works.... thank you!!!!

 

[smokinjoe2938]

glad it worked out, thanks for the star!

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[mnealtx]

You pointed me to a solution for the problem, only right that I *star* you for it!!!


Thanks again.

 

[mnealtx]

Is there any easy way to see what other COR levels can dial into my COR 14?

Conversely, any easy way to prevent other COR from dialing into my COR 14 *without* having to individually look/change them?

 

[smokinjoe2938]

I would do a list stations, write down the cor's and then do a disp cor and look on page two, no easy way to do this that I know of

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.