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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VM Transfer/Coverage Issue

Status
Not open for further replies.

KatraTech

IS-IT--Management
Aug 31, 2009
3
US
hey group! I am working with an in interesting issue. I have an extension that absolutely refuses to send calls to its voicemail box.. but _only_ when the transfer happens out of the Merling Messaging.

- I've checked the group 30 senders. Group 30 covers to 777.

- When you dial the extension number (#115) or dial in through the DID, it properly covers to voicemail after 4 rings.

- When you do a *T or when you use the "selector code transfer" option in the AA - it transfers to the extension, but it rings a bunch of times then it seems to send the call back to the "abandoned transfer extension".

What else can I check? What more information do I need to get? Thanks!
 
Does the extension have a "Coverage VMS Off" button on it, and is it turned ON?

Do you have local dialing prefixs starting with 46X? Sometimes folks miss the 9 for an outgoing call, hit the "#" instead, and accidently activate a feature.

You could try putting a Coverage VMS Off button on the set, toggle it off, and then deleting the button.
 
I will see if I can get someone to help me answer those questions tomorrow.

What does the Coverage VMS button control exactly? Thanks!
 
the button controls voicemail coverage
aka if a call goes to voicemail after a few rings or not.

Joe W.

FHandw., ACS

I don't suffer from insanity
I enjoy every moment of it :)
 
Look at the transfer return options. If the value is lower than the group coverage delay, it will never go to voice mail on a transfer. Probably someone set the group cover delay rings at a higher value.

 
The part that I am trying to figure out, is why this is only happening with a single extension? There are lots of other extensions that also have selector codes associated with them that cover properly.

I thought the transfer return option was global? It's rining at least 6-8 times.. My coverage delay is ~4 rings, so I know that component is set correctly.

I am apparently going to have to wait until I get back onsite to troubleshoot this anymore.

I will keep the thread updated. If you think of anything else, please don't hesitate to update as well. Thanks!
 
Transfer return options are global, Grooup Cover Delay is not. Check group cover delay and see if it is longer than the transfer return setting.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top