Voicemail Never Picking Up On Hunt Group. 9

[dsm600rr]

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

 

[Westi]

Do you see the group in VmPro ?
do you have a duplicate name or number in the system as a User or in the SCN as another Group or User?
Makes no sense not to work but sounds interresting

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

 

[dsm600rr]

Hi Westi,

Yes, I do see the Group in VM Pro. I have recorded the Greeting for the mailbox, and outside of normal hours, the "Leave Mail" Function works as it should.

I have all of the Extensions in the 200 Range, Groups in the 300 range, no short codes in either of those ranges. No Duplicate Names

They do not have a SCN

If I Remove all members from the Group and call the DID, It briefly pops up in SSA (No Rings on my end) and then drops. It like the group does not know where to go for voicemail. Deleting it, Re-Naming it, Re-Numbering it does nothing.

So Strange...

In the Mean Time, I created an Overflow within the Group, that goes to a user, that is forwarded to a short code that goes to a VM Module with a Leave Mail Function. Works ok, just kind of ghetto if you ask me haha.

 

[dsm600rr]

Only other thing I can think of is maybe try an in-rev upgrate

 

[tlpeter]

I have had similar stuff when the group name had the same name that the IPO had.
Avaya says duplicate names while this wasn't case before 8.0


BAZINGA!

I'm not insane, my mother had me tested!

 

[dsm600rr]

Group name is "Property Mgmt". The only other name within the system, extension or groups that even start with a "p" is "Page All"

The IPO Is Named "JimSarosEstate"

Thank you for all the suggestions thus far.

 

[intrigrant]

If you create a shortcode like *99/"#groupname"/voicemailcollect what happens if you dial the shortcode?

 

[rdoubrava]

Does you version of Manager exactly match the IPO and VMPro version?

 

[dsm600rr]

Intrigrant: Created the Code, pointed a DID to it. What is did was ring the group.

 

[dsm600rr]

rdoubrava: IPO is: 9.0.1200.1006 VM Pro is: 9.0.12.0

 

[amriddle01]

Take the space out of the name

 

[dsm600rr]

amriddle01: I did when I did a rename to: "Property_Mgmt" - Of course the IPO Bitched about the "_"

Also Renamed it as "PropertyMgmt"

Same results, however.

 

[amriddle01]

It's still in there, needs to be PropertyMgmt in both the group name and shortcode.

 

[dsm600rr]

amriddle01: I am saying I tried to re-name it multiple times before testing the Short Code Suggestion Above. No matter what I named it, It would never hit the voicemail after ringing the members in the group. After nothing work, I put it back to the original
"Property Mgmt" as that did not seem to be causing the issue.

 

[dsm600rr]

Updated Everything:

Here is a DID to *99 Again

Rings the Group like last time:

 

[amriddle01]

Then it's not ringing in on the DID/DDI you think it is, no way will it ring the group when targeting a shortcode directly

 

[amriddle01]

Or your changes aren't happening due to corruption or silliness

 

[intrigrant]

Ah, I bet you use a condition in VM Pro which has a wrong logic option set.
By default the logical "AND" is selected (red circle) but for a Calendar or a Weekplanner is must be a logical "OR"(green circle) as it cannot be 10:00 o'clock AND 11:00 o'clock at the same time.
It is 10:00 o'clock OR 11:00 o'clock.

 

[dsm600rr]

 

[dsm600rr]

amriddle01: Ok, I had the customer go to a phone (You can see - She put me on Hold) and Dial *99 from another phone. Low and behold, the same thing happened. It dialed the Hunt Group Again.