Configuring Source Numbers

[jasonjthomas]

I have been able to do this before, but for some reason this does not seem to be working nearly as well as I believe it should (nor as I have had it work in the past).

Essentially, I want to allow unfettered access to a voicemail box for a user who is on a leave of absence. As a result, I want to give that access to an administrative assistant. Furthermore, I don't want the user to have to enter a passcode.

After adding the administrative assistant's extension (and a hunt group) as a source number for the user in question, I have been unable to get her access to the voicemail box without the system prompting her for a passcode. In both instances, the number has been configured to have the "V" before the extensions in question.

Any reason that I may have overlooked as to why this is not working as it should?

Thanks,
Jason

Jason J. Thomas

 

[telecomtekperson]

V95556667777

where 5 is the area code, 6 is the prefix and 7 is the number.. NOTE there is no 1(long distance code)

 

[disturbedone]

telecomtekperson has suggested the option for retrieving voicemail from an outside source which I don't believe is what you want. You want a user inside the office to be able to retrieve messages for another user, correct?

If so, is it VMPro or Lite or embedded? If Pro, is it in Intuity or IP Office mode?

eg UserA (xtn 201) is on leave, UserB (xtn 202) is going to check the messages. In UserB source numbers enter V201. Configure a button on UserB phone, or a short code to directly access the mailbox for UserA. That should be about it. If in Intuity mode I'm not sure if this will work - that last time I touched an IPO Intuity always asked for a PIN but it may work now.

 

[jasonjthomas]

disturbedone: Your presumption is correct. I want someone to be able to retrieve messages for another user while inside the office.

As for the VMPro or Lite or Intuity/IP OFfice Mode, how would I tell? I know just enough to be dangerous, but not enough to know this right off the top of my head.

It looks like the source numbers work when accessing voicemail using the AutoAttendant line. A direct dial number--which some of us have--apparently disregards that setting. That appears to be the problem I am having here.

Might it have something to do with your queries, disturbedone?


Jason J. Thomas

 

[disturbedone]

Hmm, I'll ask a few more questions and see how we go....

1. What model system do you have? IP403, 406, 412 or Small Office?
2. VMLite will be installed on a PC but have no GUI, VMPro will be installed on a PC and have a GUI, embedded will only be on the Small Office or IP406v2 and is a card that plugs in (has no GUI either).
3. If VMPro, from the Preferences/General option you'll see if it's Intuity or IP Office mode.

As for the 'AutoAttendant line' you mention, what do you do to access this?

 

[jasonjthomas]

1.) IP403
2.) VMPro
3.) According to VMPro, it is running in Intuity Mode.

The auto-attendant is essentially a default information line that listens on a direct-dialed number. Dial the number, hear the menu begin, then hit # to enter voicemail. Additionally, users use this to access voicemail from outside the office.

Somewhat unrelated note: I have always wondered if I should update the software I have for these two components as well. Of course, I have no idea how to do that. ;-)





Jason J. Thomas

 

[disturbedone]

Right, I don't actually work on these systems any more. The last time I touched one was probably about 7 months ago and at that time Intuity mode always asked for a PIN even if you had a Source Number. So if you're using anything before about 2.1(51) or 3.1(29) system software then this is probably your problem. I have a feeling that the newer versions do allow it to work as you want it. You could try changing it to IP Office mode but this will change the way the entire voicemail works for users and you'll totally confuse them so I don't suggest it!

So, we need to check what version you're using on both. In Manager go to the Unit area and you'll see the version of the system and modules. Then in VMPro go to Help/About and it'll tell you that version.

The upgrade procedure is well beyond the scope of any forum and you really need to know what you're doing to be able to do that. The actual procedure is pretty easy but if it doesn't work (and it's highly likely it will fail!) then that's where you need to know.

Let me know the versions and I can check with others I know to confirm one way or the other.

 

[jasonjthomas]

I figured that any upgrade procedure would be well beyond any forum, but as you said, the concern is not if it will work or not but what to do if it fails.

VMPro: IPOffice VMPro Client Version 3.0 (13)
Manager: Version 3.0 (40)

And, before I forget to do so, thanks for the wisdom. This has already been a productive discussion.

Jason J. Thomas

 

[disturbedone]

Well, if there's one piece of advice you take away.....get it off 3.0(40) as soon as you can!!!! It was utter crap! Bug upon bug upon bug and on it went.

I'm pretty sure that it's because it's Intuity mode on a reasonably old version - currently 3.2(something) - that what you want to do is not working.

I'll talk to some guys I know and double check for you. Unless someone else finds this thread and can shed some light on it. I'm reasonably sure that the current version will get it working for you.

I'll come back to you.

 

[fshaw]

You could just set the password to something simple while the person is away and they can reset it when they return.

VM Pro in Intuity mode does not use the Source Number. The caller will be prompted for password.

For reasons of sanity, I second the recommendation to upgrade to 3.2(17) to get away from 3.0 issues.

Good Luck,
Frank

Frank Robertshaw
The Phone Guy
Nashville, TN

 

[jasonjthomas]

fshaw: I am in complete and total agreement on the upgrade. I just need to find a good source on performing the upgrade and scheduling the appropriate downtime.

Additionally, I found that the only time the source number works is if the user accesses voicemail from our Auto Attendant line. Configuring my cell phone as a trusted number proved this. If I access voicemail in any other way using the same phone, however, I do onot get it.

I believe the person who is on leave is not planning to return. The other way I could get around this would be to forward voicemails as an email to administrative assistant, but I do not trust my users to delete these emails once they listen to the voicemail and act on it.

Time for some more research on the update, then.

Jason J. Thomas

 

[IPGuru]

if you want the source number fielkd in vM pro to have an affect this can be achived will a simple addition to the call flow

modify the default start point for get mail by inserting a get mail action (& linking it to the start point)
the GetMal action doed not need to be edited
now save & make live

any calls to this mailbox from a secure location should be able to access the mailbox without being prompted for Passcode.

 

[jasonjthomas]

IPGuru: This appears to be more complicated than it should be. The dearth of documentation from our implementer coupled with the current VMPro configuration leaves me just plain confused.

I believe I found what they configured, but I cannot link it to the starting point. I have tried the connection icon, but that has not worked at all.

I will have to poke at it some more.

Jason J. Thomas

 

[disturbedone]

Select the connection icon then you need to click & hold the From point, and release on the To point. Go from the bottom right to the upper left is my rule. Make sure you click inside the box not on the edge or outside.