VM Hunt group busy

[bajangerry]

Hi Guys,

I have a PBX that the Embedded VM Hunt group is always busy even though the individual VM Port numbers can be dialed and answer every time. I have rebuilt the entire VM with new numbers for the port and for the hunt group but with the same result.
Confirmed that the COS for the VM ports is set with the COV/ONS/E&M Voice Mail Port  = Yes, Message Waiting = Yes, Voice Mail Softkey = Yes and everything else left defaults.
Feature access codes have been entered and are working correctly.
Many system reboots have happened but no idea what is causing this as yet. Suggestions welcomed!

Gerry

[ralph]

When you call the VM hunt group from a display phone, does it say "busy?"

If you stat the individual ports, do they all say idle?
If you do a locate features on the hunt group, does it say DND?  - or forwarded?  Same question for the individual ports.

Ralph

[bajangerry]

Hi Ralph,

Yes, says BUSY.

All ports are idle

-> vmPortStatusInfo
vmPortStatusInfo
Port: 0 Waiting for call
Port: 1 Waiting for call
Port: 2 Waiting for call
Port: 3 Waiting for call

Pilot Number: 8890                                                             
Active Features : 

I can call the individual VM port number and get answered with no problem.

[ralph]

Silly question but I have to ask it:   Are the VM ports programmed in the hunt group as members?

Ralph

[bajangerry]

Yes they are... and there are not silly questions at this point 

[ralph]

The voice mail hunt group is set to be "Voice Mail", correct?

Without changing anything in the existing hunt group, try building a new hunt group and add those ports to it just to see if it works differently.

Ralph

[bajangerry]

Yes the Hunt Group is set as VoiceMail.

I have built a new hunt group and COS, removed the VM ports from the original hunt group and put them in the new hunt group and assigned them the new COS as well... same problem. 

[bajangerry]

Have sent a backup of the PBX to Mitel support and they are going to look at it in their lab environment now... will let you know what they discover.
Was thinking to do a software upgrade to see if there is some sort of database issue but then a restore of the database that i have already done to my lab PBX should have the same effect.

[johnp]

I would also check these extensions to see if they have additional buttons programmed

[acejavelin]

Check for DND or other features...

LOCATE FEATURE EXTENSION xxxx

for each VM extension.

[bajangerry]

All,

Thanks for your input... we discovered that somehow all of the VM ports have been placed into Make Busy mode!
They do not have ACD agents so I never even though of Make Busy but once I did a remote clear all features on the VM ports the calls were then answered correctly. Very odd that if you called the VM port directly it still picked up the calls even when in Make Busy mode as well.

All's well that ends well!

[johnp]

Did you check to see if some ports were set to be RAD's

[bajangerry]

johnp,

The VM ports were set to Make Busy somehow, still not sure how that happened but once we were able to disable the Make Busy from the ports the voicemail hunt group was accepting calls again.