On a Partner ACS R3 with pvm card (small)...I have Auto VMS cover on for two extensions. 78 and 79 are assigned correctly. Cover delay is set to 5 rings for each extension, but when I dial either extension, it rings 7 times before going to the correct voice mailbox. I tried changing the number of rings in delay to 4 rings, and even 2 rings, but it still delays 7 rings. Even tried turning on DND...still 7 rings. Whassup? I appreciate any ideas.
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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
PVM card answer delay
- Thread starter pjolly
- Start date
Cover delay relates to number of rings at that extension before forwarding to another extension (not vmail), and is not used on the vmail ports themselves. If these values were altered for the vmail ports themselves, leave those values as-is, they'll have no effect on operation and not be worth going back to reset.
Be sure Auto VMS Coverage is set for the extensions using #310. Then verify VMS Cover Rings is set under #117 to whatever you need.
The reported failure to immediately forward to vmail when DND is enabled is troubling, though. Verify 78 & 79 are the only members included in Hunt Group 7 under #505. If an errant port is included, it'll ring that until forwarding occurs to the next hunt port, causing at least 3 if not 6-7 rings (if more than 1 port accidently included in the group) before vmail answers.
My suggestion is to verify programming using the remote software so you can see what may be out of place graphically. Great for allow/disallow tables, restriction errors and troubleshooting strange programming errors like this one.
Be sure Auto VMS Coverage is set for the extensions using #310. Then verify VMS Cover Rings is set under #117 to whatever you need.
The reported failure to immediately forward to vmail when DND is enabled is troubling, though. Verify 78 & 79 are the only members included in Hunt Group 7 under #505. If an errant port is included, it'll ring that until forwarding occurs to the next hunt port, causing at least 3 if not 6-7 rings (if more than 1 port accidently included in the group) before vmail answers.
My suggestion is to verify programming using the remote software so you can see what may be out of place graphically. Great for allow/disallow tables, restriction errors and troubleshooting strange programming errors like this one.
TouchToneTommy
Vendor
On an ACS R3, the VMS cover rings is programmable on a station-by-station basis. Instead of #117 for global VMS cover rings, use #321-XX-N, where XX is the Extension Number, and N is the number of rings from 1 to 9.
392 is on target about the extra extension in hunt group no. 7. It will cause erratic behaviuor, so be sure to look through the extensions assigned in #505-7
392 is on target about the extra extension in hunt group no. 7. It will cause erratic behaviuor, so be sure to look through the extensions assigned in #505-7
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
