Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Intercepted COR call to announcement?

Status
Not open for further replies.

tylamb19

IS-IT--Management
Jul 10, 2017
57
US
First off, this is my first time posting here, but the knowledge I've gained over the last few months just reading through this site has been amazing! A huge thank you to everyone.

Anyway, on to my question. Is it possible to route an intercepted/denied by COR outbound call to a specific announcement instead of getting the three fast dial tone beeps and then a dial tone? Preferably, I'd like to set up an announcement saying something along the lines of "This phone is not permitted to call this number. To override this message, please enter your authorization code now."

I've tried setting the "Restricted Number Dialed Intercept Treatment," "Invalid Number Dialed Intercept Treatment," and "Controlled Outward Restriction Intercept Treatment" to announcement and then putting in the extension for the announcement (8001) like the documentation and previous posts I've read recommend me to do, but a station restricted by COR still just receives the dial tone prompt when dialing a number not allowed by the COR. I am using CM 6.3.

Is there any way to make this happen? Does the announcement need to be some special type? I'm sure I'm just missing something small here. Any help would be much appreciated.
 
First, you would have to assign stations to a particular COR
Second, you would have to activate outward restriction on that COR

deactivation of controlled restriction for station or group of stations. Dial the user or group deactivation code, 1 for outward, 2 for total, 3 for termination, 4 for station-to-station, get second dial-tone, then dial station # or 2 digit COR group number that restriction(s) is to be removed from, receive a confirmation tone. Example if station deactivation code is #03 and station # is 2501 and you want to deactivate station-to-station calls only. At console or a station with console permissions, get dial-tone, dial #3, dial 4, listen for dial-tone, dial 2501, listen for confirmation.
Code:
display feature-access-codes                                    Page   2 of   9 
                               FEATURE ACCESS CODE (FAC)

             Group Control Restrict Activation: *03        Deactivation: #03
              User Control Restrict Activation: *13        Deactivation: #13
-------------------------------------------------------------------------------
display system-parameters features                              Page   4 of  20
                        FEATURE-RELATED SYSTEM PARAMETERS

 Controlled Outward Restriction Intercept Treatment: announcement 5999

               Controlled Toll Restriction Replaces: outward
    Controlled Toll Restriction Intercept Treatment: announcement 5999


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
 
Thanks for the info, however, I still just get the recall dial tone when dialing a COR restricted number.

The call is definitely getting intercepted (hence the recall dial tone waiting for users to input an auth code) but it still isn't playing the announcement. Should the other intercept values be changed as well as the Controlled Toll Restriction Intercept Treatment value you specified? It seems like there is something small that I'm missing somewhere.

We also want to do this for all phones with that COR instead of station-by-station if possible.

EDIT: whoops, recall dial tone, not intercept dial tone
 
post "status station xxxx" where xxxx is the station that has a COR that is user or group restricted outward.

Code:
status station 7303
                              GENERAL STATUS

                  Type: 2500               Service State: in-srv/on-hook or disc
             Extension: 7303             Download Status: not-applicable
                  Port: 01A0509            SAC Activated? no
           Call Parked? no              [b][COLOR=#CC0000]User Cntrl Restr: outward[/color]
[/b]      Ring Cut Off Act? no             Group Cntrl Restr: none
Active Coverage Option: 1             CF Destination Ext:

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
 
Code:
status station 2460
                              GENERAL STATUS

     Administered Type: 6408+              Service State: in-srv/on-hook
        Connected Type: 6408+              Network Region: 1
             Extension: 2460           Parameter Download: complete
                  Port: 002V324            SAC Activated? no
           Call Parked? no               
      Ring Cut Off Act? no             
Active Coverage Option: 1            one-X Server Status: N/A

          EC500 Status: N/A        Off-PBX Service State: N/A
       Message Waiting:
       Connected Ports:

  Limit Incoming Calls? no

      User Cntrl Restr: none             HOSPITALITY STATUS
     Group Cntrl Restr: none           Awaken at:
                                        User DND: not activated
                                       Group DND: not activated
                                     Room Status: non-guest room

Even though it says none, the phone still isn't calling external numbers. So it's still restricted.
 
Your issue is that the examples shown, require User or Group Controlled outward restriction to be directed to the announcement.
Controlled Restriction:
This User or Group state is set using feature access codes. This is not controlled by programming a COR that is restricted.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
 
Ok, so there's no way to just redirect all of the intercepted calls to the announcement via programming?
 
First choice would be "train your users"

Code:
Options:

change system-parameters features                               Page  18 of  20
                        FEATURE-RELATED SYSTEM PARAMETERS

INTERCEPT TREATMENT PARAMETERS
       Invalid Number Dialed Intercept Treatment: announcement tone
                   Invalid Number Dialed Display:
    Restricted Number Dialed Intercept Treatment: announcement attendant tone
                Restricted Number Dialed Display:
   Intercept Treatment On Failed Trunk Transfers? n

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top