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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Auth codes 9.1 exclusive

Status
Not open for further replies.

phonecable5

Vendor
Jul 30, 2015
41
MX
Hello to everyone who read and helps on the forum.

I have a client that wants to limit external calls.

Setting is IPO 500 v2, 9.1.3.0

They will be configured ARS tables within which blocked certain numbers, certain numbers or ask authorization code.

up there is all right. If I want to be limited to a specific user, I move the user to corresponding ARS. If necessary, we put it in the ARS that requires an authorization code.

But now the customer wants auth codes are 100% exclusive to some users. For example: ext 1000 can call to mobile numbers using the code 509090, but if that code is used in ext 2000, the call is made, but with the name of the extension 1000 appears in the screen.

What is sought is that the authorization code that uses ext 1000 cannot be used in any way by ext 2000.

Reading manuals, I realize that behavior change authorization codes Release 9.0 to 9.1.

Is there any other solution that comes close to what I want to implement with the customer?

Many thanks in advance to all can read this trouble.
 
make a system shortcode with the number in question and block it (including the dialout number), then make a user shortcode also with the dialout number and ask for the auth code.

That way it should work and you don't need to setup multiple ARS' for that.
Still a lot of work and hopefully there is not a whole lot of numbers you need to setup but if there are then you need to program them as individual targets. You can eve go as far as not using auth codes and just use the shortcodes to allow or block.


Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
AVAYA has totally messed up Auth codes in 9.1 and they don't seem to have any plans to change it. AGHHHH!!!

NCDS | NCSS | APSS - SME | ACIS - SME | ACSS - SME | ACIS - UC | ACSS - UC | APSS - SCOPIA | APDS - SCOPIA | CCENT
 
What is sought is that the authorization code that uses ext 1000 cannot be used in any way by ext 2000.

why?
the whole point of auth codes is to enable someone(say a manager) to use someone else's phone to make a call that user would not otherwise be able to place.

I recomend you find out what the customer is actualy trying to achive, not how they think it should be achieved.



Do things on the cheap & it will cost you dear
 
OP, what they want isn't possible, they're going to need to hotdesk and use shortcodes/account codes, you can't combine the requirements into a single code/procedure :)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top