I think I had something similar message when one of my voicemail ports was stuck open. The backup would not work until that DN was free. YOu may want to try to busy and RTS the VM ports and see if that helps. Or try a system restart tonight and try the backup in the morning.
Busy 1 4 27, will busy the first 16 VM ports, 1 4 28 will get the rest, if it comes across a "busy" port courtesy down it until you can "resource" port and see if it has a terminating device, if not that's the culprit. If it does, you'll have to flip the coin if it shows a trunk, then it could be the issue or somebody still listening to the greeting, if it shows a user, call them to see if they're busy.
Ok - I think I'll take caution and try checking again and then go from there.
However, I may not have a VM issue but perhaps a paging issue.
Many times opur guys in our shop don't hang up the hook set from the old Superset 1's very well and screw up the system or cause an issue.
Maybe the cause?
Here is the procedure I used with that problem:
Also, try this for Paging system(Busy State):
stat 3 1 1 3 - Status of line - "busy"?
busy 3 1 1 3 - Use F option to force PLID to properly "busy" itself
reso 3 1 1 3 - What PLID/EXT caused issue?
rts 3 1 1 3 - Return PLID to Service
stat 3 1 1 3 - Check stat - should be "idle"
reso 3 1 1 3 - Check resources of Circuit/PLID
Hi Pichels,
I recently had a similar problem, when i did a loc fe ext on the voicemail port it showed as having a do not disturb on it.
You can dial the cancel dnd remote code + ext no. to clear it without havy to busy and rts the port.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.