Voice mail was working fine until I shut the system down to repair a corroded battery contact on the 308ACS. When powered up the next day, the 308 works just fine, but the VM Power, Test and HDD LEDs came on, the drive started to spin up then after about 3 seconds, all the LEDs went out. This happens every time I cycle the power. Sounds like maybe power supply? Can anyone tell me if the VM card uses the same power supply as the 308ACS? Thanks.
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 biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Partner Mail VS R4.0 power supply question 3
- Thread starter lwsalter
- Start date
- Thread starter
- #21
Although it's working, the VM has been somewhat random- about half the time it answers a ringing line after 4 rings, as it's programmed to do. The rest of the time it may go (approximately) 7 rings or 12 rings or maybe never!
Same thing with VM access- usually answers in 1/3 of a ring or less but sometimes it takes 4 rings. ???????!
Same thing with VM access- usually answers in 1/3 of a ring or less but sometimes it takes 4 rings. ???????!
TouchToneTommy
Vendor
Did you remove the OLD ports assigned to Hunt Group 7? From before you moved the VS Mail to the correct slot?
The hunt group is circular, so if it hits an extension that doesn't answer (such as a non-voice mail port extension included in the group), it will wait 4 rings, and then try the next extension in the group. It keeps doing that until it hits a real VM port and gets answered. The next 3 calls will be OK (for a 4 port VM), then it's back to the misprogrammed ports.
The hunt group is circular, so if it hits an extension that doesn't answer (such as a non-voice mail port extension included in the group), it will wait 4 rings, and then try the next extension in the group. It keeps doing that until it hits a real VM port and gets answered. The next 3 calls will be OK (for a 4 port VM), then it's back to the misprogrammed ports.
- Thread starter
- #23
![[ponder]](/data/assets/smilies/ponder.gif "[ponder] [ponder]")
- Thread starter
- #25
The ports are correct.
One way to tell if a port is in trouble would be to assign a button on a phone to each voicemail port (Intercom 20, Intercom 21...). Watch and see if all 4 ports picks up correctly when checking voicemails and answering incoming calls.
If it ain't broke, I haven't fixed it yet.
One way to tell if a port is in trouble would be to assign a button on a phone to each voicemail port (Intercom 20, Intercom 21...). Watch and see if all 4 ports picks up correctly when checking voicemails and answering incoming calls.
If it ain't broke, I haven't fixed it yet.
I just had another idea. Press "INTERCOM XX" where XX is 20, 21, 22 and 23. See if the voicemail answers correctly each time.
If the license is bad, I believe the voicemail defaults to 2 active ports.
This could account for the sporatic problems.
If it ain't broke, I haven't fixed it yet.
If the license is bad, I believe the voicemail defaults to 2 active ports.
This could account for the sporatic problems.
If it ain't broke, I haven't fixed it yet.
- Thread starter
- #29
It has a comcode 847180783 expansion card. However, I dialed the extensions and found that 20 & 21 do not answer. 22 & 23 work just fine. As a quick-fix, I unassigned 20 & 21. This would suggest a problem with the expansion card, yes? I'll check to be sure it's fully seated, etc. since I did move it to another VM module temporarily.
- Thread starter
- #32
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question