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

Requiring login for Voicemail Pro module

Status
Not open for further replies.

wfaulk

MIS
Jan 21, 2006
20
US
I have a VMPro module that I only want to be accessible if the user has logged in. This seems like it would be a common thing to want to do, but I can't figure out how to do it.

It doesn't really make a lot of difference to me as to how the user accesses the module, so a direct short code is fine, or modification of the normal collect flow (which I also can't figure out how to do, assuming it's possible).

Specifically what I want to do is to allow people to call in, authenticate, and toggle a relay on the IPOffice switch, which will unlock the front door, so if you can think of another way to do that that I haven't suggested, that's fine, too. But the authentication is a hard requirement, obviously.
 
easy

DDI to a v.mail module

Have a menu with the code as one of the menu options, e.g, "Please enter code" - Menu DTMF option = 1234

successful selection transfers to a SC that fires the relay

e.g SC 1112 / relay on / off / pulse
 
I didn't realize that the PIN could be configured to use the VMPro authentication data. However, it just asks for the PIN of the "presumed user". If the call is coming in externally, I have no idea what the "presumed user" is.
 
Well, preferably, I'd like the users to log in as if they were accessing their voicemail. So dial in, enter extension number, enter voicemail PIN. I'd rather not have a separate database. I'd be fine with using the VMPro database access to gain access to the VM authentication database, but I have no idea how to access it, assuming that it's accessible via that interface at all.
 
No one knows if it's possible to get VMPro to perform its voicemail authentication routine outside actual collection of voicemail? Or if there's some way to add a custom action to voicemail collection, or some other builtin feature that already requires a login?
 
Like 40 at this office, but I don't really see how that's relevant.
 
Build incoming call routes with the phone numbers that are allowed to go in to a module.

You still could protect it with a pin code and CLI (variable routing)

In that variable routing action you put the CLI of the callers and then add a generic action with the pincode of that user and then a transfer to a shortcode.

T%he max is 24 entrys but you can make another action with more CLI entry in it (connect it on the no match field)


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
I'm guessing that this seemingly trivial action is impossible, since everyone is suggesting things that I didn't ask for. I don't want to administer a second database of PINs. (Third, really; the "Phone Manager Pro" authentication is yet another set.)

It continues to amaze me how the simplest things are apparently impossible with IP Office. It's clearly hacked together from totally disparate things. Asterisk is tidier.

Though, maybe I'm just not explaining it well; let me try again.

I want people to be able to call in remotely, log in using their extension and voicemail password, and then do something that I define. I don't care if it's completely separate from the voicemail system, if it's something that I have to define as a separate voicemail module, or if I have to edit the normal voicemail workflow. I require separate logins for each user, and I do not want to keep a separate database of extensions and pins (unless there's some way to automatically keep it synchronized with the normal system).
 
Just send it to there own mailbox.
What do you want to do then ?

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Ow and do not compair asterix with ipo and vmpro please !!!
It does not even comes near it.

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Just add a menu before the code you made, press on the + and add any number you like.

Can't see why you won't get it to work, reading in the help will point you in the right direction. Done asterisk but you will never be able to create what the VMPro can do.


Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
@tlpeter:

Okay, if I send them to their own mailbox, how do I define a new action in the VM collection system to allow them to use a different module or call a short code directly? "*T" doesn't work; it seems to only allow transfers to actual extensions. I suppose I could set up an extension that transfers to the module, but then it would be trivial to bypass the authentication.

 
I don't think you will be able to do this using the running extn and v/m code. extn/code login is only used for login to a mailbox. These are part of the IPO config. Even if you export it, it encrypted (which I find odd as it is easily snadboyed through Manager!!!).

Maybe a GRIP request to allow an authentication option as well using PIN code to access modules???

It continues to amaze me how the simplest things are apparently impossible with IP Office. It's clearly hacked together from totally disparate things.
Odd statement about what is probably the most flexible kit on the SME market!!!

Jamie Green

Football is not a matter of life and death-It is far more important!!!!
 
@Bas1234:

What do you suggest I do with that menu? As far as I can tell, there is nothing in a menu that provides authentication.

I'd be happy to use a menu (or some other action that allows the user to dial a sequence of digits) to enter his extension number, and then use that input to define the "presumed user" for the PIN for the next action, but I can't see any way to do that, either.

Also, thanks for trying to provide an importable file, but the Voicemail Pro Client tells me "There was a problem importing from the file". And the file format is opaque, so I can't see what you were trying to provide.
 
@jamie77:

Thanks for the response. It is absolutely confounding to me that there is no way for me to use the builtin authentication mechanism. Especially since the developers exposed half of it by using "$" with an action's PIN.

Not only that, but the Voicemail Pro server and the IP Office are (obviously) different computers. There's clearly already some RPC going on for the voicemail server to do the authentication.

(It seems that a GRIP is Avaya's name for an RFE; right?)

I'm a Unix sysadmin by trade, and I deal with this IP Office system about once every few months, at most, for anything beyond basic user admin. Almost every time I've tried to do anything with it, I end up coming here (where the people are very obliging, which I appreciate), and most of the time I end up discovering "you can't do that".

If I were using Asterisk, I could have knocked this out in about five minutes: Authenticating against VM data in Asterisk

jamie77 said:
"I don't think you will be able to do this [on] ... what is probably the most flexible kit"
o_O
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top