weird voicemail auto attendant issue

[rwgs811]

so in reference to this issue thread940-1738184 , I am now getting the same problem on a completely different system.

I have the shortcode has "MainAA" and yet the system still tried to access it's mailbox when it is called.

If you traces are needed, what should I include, or should default settings be ok?

VM:

http://snag.gy/mkymX.jpg

and config:

http://snag.gy/H3fI6.jpg

 

[budbyrd]

Try it with out the "". The SC we have in our lab system doesn't use the quotes and work just fine.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[Qzwsa]

Make sure you don't have a group or user with the same name.

Your short code should be *610 (or whatever) // voicemail collect // "MainAA" if using VMpro or *610 // Auto Attendant // "AA:MainAA" if using embedded.

- Qz

 

[rwgs811]

definitely no group or user with the same name.

I've tried without the quotes, but Manager puts them in anyway (so can't be removed).

 

[budbyrd]

If they can't be removed, they can be moved. MainAA"" or ""MainAA. The need or lack there of, is certainly version dependent in the IPO, we have had to change it up through the years. Oh Duh.... I just reviewed the pic. Try Voicemail Node instead of collect.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[rwgs811]

Current software level is R6.1 on a IP406DS if this helps.

i tried with voicemail node as well already, but still to no avail. - It removes the quotes when you select Node though anyway.

any other ideas?

 

[amriddle01]

Try calling it "AutoAttend" or something. Sometimes the system is daft and may well match "MainAA" with "Main" which is the default group on IP Offices.
If it still insists on going to a non existent mailbox then create a group with that name and use the "Leave" action to do what you need, until you figure out what's wrong

 

[intrigrant]

Try another module name like myFirsModule or MenuForDummies and see what happens, do NOT use AA in the begin of the name.

 

[budbyrd]

The first pic showed me what's missing. You have to create an entry in the short code section of VM Pro (upper right pane) with a goto pointed at the module. Tested it on my 406 at 5.0(26).

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[amriddle01]

That should not be required, I never do that... ever. VM Collect to "Module" should work...that's it

 

[intrigrant]

The shortcode section is for backward compatibility or for delayed answer of voicemail, always use voicemail collect to point directly to the module.

 

[amriddle01]

Not even for delay Cor, adding a # to the code will achieve that on modules, as I'm sure you know

 

[rwgs811]

So i figured out what the issue was. I noticed that the IP office wasn't being fully recognised in VM Pro (it didn't show the name and IP in the top left of the client for example).

This was due to the IP office VM IP being set to broadcast, once the actual IP of the server was set, it started working straight away - weird i know as the voicemail was being seen, just not fully for whatever reason!

 

[intrigrant]

Yes I know but I see a lot VM callflows from my collegues using shortcode entry points, transfer to $ACD and a lot other stupid things.
They read this too and tomorrow we will have yet another discussion on how best to program VM Pro and it is always 5 against 1, they forgot that I was the one who trained them for IP Office (NOT VM pro though, they did that training with another reseller which was cheaper).
And with 5 against 1 I always lose as they are stubborn *ssh*les.

 

[amriddle01]

Just remind them that the ICR entry of VM:Module targets modules not shortcodes, and also the auto failover to a group of the same name should VM go down will not happen using shortcodes instead of modules...how many more reasons do you need?

 

[intrigrant]

Well, none but they think it is better to use shortcodes and put the shortcode in the ICR.
Don't ask me why, they cannot tell the advantage but they say "Avaya advise it that way so we do it that way" period.

Another thing : I prefer to use the timeprofiles within the IP Office instead of the VM Pro time profiles unless I have to.
Last week I had to go to the manager who told me not to so as my colleagues could not understand the way it works.... great!