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!

Voicemail Never Picking Up On Hunt Group. 9

Status
Not open for further replies.

dsm600rr

IS-IT--Management
Nov 17, 2015
1,444
US
I got an interesting one for you guys/gals.

I recently built a very simple ICR for a Sub-Division within a company. Basically the call comes in, Hours are checked and it either rings the Hunt Groups Members or goes Directly to the Hunt Group Mailbox.

When I call the DID within the hours, it rings the people for the 20 seconds, and rather than go to voicemail, the counter restarts and it just keeps ringing the people. Voicemail is on, and its set to 20 seconds. The No Answer is on, and also set to 20 seconds. I have raised this a bit for testing, nothing changed.

If I set the ICR outside of normal business hours - it goes to the correct mailbox.

I have tried Deleting and Renaming the HG
I have tried Deleting and Re-Numbering the HG
I have tried restarting the Services
I have Tried restarting the Voicemail Pro Server
I have tired restarting the IPO
I have set a DID Directly to the HG - Behaves the same - Rings and Rings.
I have removed everyone from the HG and called the DID - Call Rings once and Drops.

They are on 9.0
 
Remove the condition, test then add it back, I'll also bet that's the issue.

I never stack conditions like that (assuming you have more than on in that check condition), check one after the other :)
 
amriddle01: A DID Directly to the Hunt Group Behaved the same way. Ring and Ring - No Voicemail Picks up.
The only condition being used for that DID call flow is the Property Mgmt Hours Condition.
 
Delete (or rename) the group "Leave" startpoint and try again.
I am pretty confident there is the root of the problem.
 
Hang on, we're all being dumbasses, you can't have a mailbox when the group name matches a module, for failover purposes with the ICR in the event of VM failure

You'll see it's gone from the group mailbox section in VM Pro too :)
 
intrigrant: I have already completely deleted the group, merged, recreated the group "With a different name", Merged - Same Issue. I have also have the group a totally different Extensions number - Same Issue.

All of the HG's may be behaving this way. This is the only group that rings people and goes to voicemail. All the other groups receive their mail through a "Leave Main" Module - Which works with all the groups.

I am thinking something might be corrupt in the system.
 
amriddle01:

VM_Pro_vx0os1.png
 
amriddle01: Isn't what you are saying actually the opposite? If The VM Pro Goes Down, having a Hunt Group that is named exactly the same as the Module will allow the system to fall back to that Hunt Group.

Even in the error panel, if you do not have a Hunt Group Matching a VM Pro Module, you will get the error: "The incoming call route targets the Voicemail Module xxx. If a hunt group was created with the name xxx then if Voicemail was unavailable the call would route to this group.
 
Trust me, it'll never work, that just directs it to the module. They used to remove it, must have changed that but the functioning remains the same.

Has always been like this :)
 
Having a group named as a module is for failover, it's to be a temp thing until your VM is fixed, not to be used on production/always in use groups.

End of discussion, it will never work the way you have it :)
 
amriddle01: You are the man. It all makes since now. Learn something new every day. I wish I could buy you a beer.

VM_xklxpc.png
 
amriddle let's shower you with pink stuff, I know you like that colour.

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
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top