Queued and Still Queued

[jmarchi]

I'm trying to create Announcements in voicemail pro for Queued and Still queued for a particular Hunt Group.

I've created the proper start points for the Hunt Group i want to change, but it still only uses the default Announcements.

Am i missing something. I thought it was just as simple as creating the start points and it would take over the announcements.

 

[amriddle01]

No, you need to record something in a generic action and that's what it will play

 

[jmarchi]

I am creating a recording in a Generic or Menu action, but it still plays the default

 

[Okkie26]

Did you do the save & make live?

 

[jmarchi]

Yes. If i create the actions under Default Start Points it works and replaces the announcements. It just isn't working under Group Start Points

 

[amriddle01]

Remembering of course that it follows the settings of the pilot group in an overflow type of setup, is that the issue?

 

[jmarchi]

That doesn't appear to be the issue.

Does this make any sense:
Default Groups created by IP Office are 2:group1, 2:group2, 2:group3
Queued and Still Queued Don't work

If i create a new Group in VMPro called group1 and group2 (without the 2 then the queueedand still queued work

 

[Gunnaro]

Log out of VMPro, restart the service, and log in again.
Could be that VMPro is not getting any of your updates from the IPO.

As long as you have enabled Hunt Group announcement Queued and Still Queued in Manager, and made a specific Queued/Still Queued on the Hunt Group in VMPro, it works. (but empty actions will make default action take place)

Kind regards

Gunnar
__________________________________________________________________
Hippos have bad eyesight, but considering their weight, it’s hardly their problem

 

[Westi]

the name 2:Group1 might throw the VmPro off too as naming is a big issue with the voicemail

Rename it to something that doesn't start with a number and a colon as you should have an error in the Manager telling you that groups cannot start with a number or contain special characters.

Joe W.

FHandw, ACSS (SME), ACIS (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

 

[amriddle01]

I think it's a bug, someone on here recently posted a similar issue where 2: was appended to all modules an usernames in VM Pro

 

[Westi]

in that case upgrade to the latest release of the version in question will most likely fix it

Joe W.

FHandw, ACSS (SME), ACIS (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

 

[snowman50]

I think that issue was caused by the installer using the wrong client version for the one they were working on.

Use the rel 9 vm pro client for release 9 system as the older versions seem to cause an issue

 

[intrigrant]

General and mandatory rule in IP Office in respect to groups, users and the system name:
Names MUST be unique
Names are case sensitive but be aware that VM Pro is NOT case sensitive
Names may NOT begin with a number or a space
Names may NOT have one of the following characters in it : # ? / ^ > , . :
Names can be max 15 character in length

The goups with the names 2:Group1 2:Group3 etc are NOT allowed as it conflicts with the above rules.
Not following the rules may not be a problem but working is unpredictable as this thread shows.

 

[Westi]

nicely said intrigrant or should I say copied and pasted from the manual

Joe W.

FHandw, ACSS (SME), ACIS (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

 

[jmarchi]

The Groups that are listed in VMpro were created automatically by voicemail pro when the UCM Card was installed into the IPOffice 500v2

The actual groups in the IPO are ie. group1, group2

Users as well in the IPO are user1, user2, user3

ALL the users and groups are listed in VMPro ALL have 2: in front of their name. 2:user1, 2:user2, 2:user3

These users/groups were not created by me, but this is how vmpro imported them.

 

[Westi]

in that case I guess snowman50 has it right that someone made changes with a wrong version of VmPro client and it corrupted the programming a bit.
delete the groups and recreate them or better copy and paste them to a new name and use them again with the different name and delete the old ones after they work

Joe W.

FHandw, ACSS (SME), ACIS (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

 

[intrigrant]

@Westi, not copy and paste, straight from the head. Any IPO installer should be able to say that even on a saturday night at 03:00 hours and blind drunk.... that much important is it

 

[planetos]

snowman50 is correct. I had this exact issue a few months ago and the cause was that IPO was upgraded to Rls 9 but VMpro was still at Rls 8

 

[Westi]

@intrigrant: I am impressed that you are still awake at 3:00am, I have not been awake at that hour in a long time except to look at the watch and turn around to sleep another 3 hours


Joe W.

FHandw, ACSS (SME), ACIS (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