Hello everyone,
I've had a bit of an on-going problem with an ip office 4.2(14) running embedded voicemail.
The problem is that a couple of months after installation the user started experiencing difficulties with voicemail collect for a generic collective huntgroup mailbox, customer uses *59 to access the mailbox... However system status shows a VM waiting for the group the customer uses *59 to collect advised that they have x new messages then they just hear a faint clicking, this only happens on the one mailbox all other huntgroup/user mailboxes function correctly.
So far we have attended site and powered down removed the card and reseated the card, upgraded the software on the system, swapped out the embedded card (as advised by our distributor) upgraded the prompts on the new card which appeared to have cured te problem until now (distributor checked the config and gave it a clean bill of health)checked the spelling of the group names, source codes etc, removed all users bar 1 and tested then added individual users back in to the group to see if this isolated the problem. No joy
Just wondered if any of you guys have experienced anything like this before and if so could shed any light.
Many thanks in advance
I've had a bit of an on-going problem with an ip office 4.2(14) running embedded voicemail.
The problem is that a couple of months after installation the user started experiencing difficulties with voicemail collect for a generic collective huntgroup mailbox, customer uses *59 to access the mailbox... However system status shows a VM waiting for the group the customer uses *59 to collect advised that they have x new messages then they just hear a faint clicking, this only happens on the one mailbox all other huntgroup/user mailboxes function correctly.
So far we have attended site and powered down removed the card and reseated the card, upgraded the software on the system, swapped out the embedded card (as advised by our distributor) upgraded the prompts on the new card which appeared to have cured te problem until now (distributor checked the config and gave it a clean bill of health)checked the spelling of the group names, source codes etc, removed all users bar 1 and tested then added individual users back in to the group to see if this isolated the problem. No joy
Just wondered if any of you guys have experienced anything like this before and if so could shed any light.
Many thanks in advance