Voicemail Rings twice then hangs up

[mpark]

Our voicemail pilot is set to extension 999. Nothing was changed on the server when this all went down. Now when anyone dials 999 it rings once or twice and then the call is disconnected. I have worked on this all weekend and have gotten no where. I have attached the log of what it looks like when a call is placed to check voicemail. 3CX Phone system version 8.0.

09:56:35.593  [CM102001]: Authentication failed for SipReq:  REGISTER 192.168.5.225 tid=-l8vhxssck3ap cseq=REGISTER [email protected]:2051 / 280206 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
09:56:33.546  [CM503008]: Call(43): Call is terminated
09:56:32.796  [CM102001]: Authentication failed for SipReq:  REGISTER 192.168.5.225 tid=-cwyojza4yoib cseq=REGISTER [email protected]:2051 / 592813 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
09:56:30.812  [CM503007]: Call(43): Device joined: sip:[email protected]:40600;rinstance=5f46d0fe7e0512e6
09:56:30.812  [CM503007]: Call(43): Device joined: sip:[email protected]:62310;transport=UDP;rinstance=ead7065baebfb13d
09:56:30.812  [CM505001]: Ext.999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:[email protected]:5060]
09:56:30.812  [CM503002]: Call(43): Alerting sip:[email protected]:40600;rinstance=5f46d0fe7e0512e6
09:56:30.608  [CM503025]: Call(43): Calling Ext:Ext.999@[Dev:sip:[email protected]:40600;rinstance=5f46d0fe7e0512e6]
09:56:30.577  [CM503004]: Call(43): Route 1: Ext:Ext.999@[Dev:sip:[email protected]:40600;rinstance=5f46d0fe7e0512e6]
09:56:30.577  [CM503010]: Making route(s) to <sip:[email protected]:5060>
09:56:30.577  [CM505001]: Ext.118: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 6.0.20943.0] PBX contact: [sip:[email protected]:5060]
09:56:30.562  [CM503001]: Call(43): Incoming call from Ext.118 to <sip:[email protected]:5060>
09:56:22.374  [CM102001]: Authentication failed for SipReq:  REGISTER 192.168.5.225 tid=-u92ksgu2ebsx cseq=REGISTER [email protected]:2051 / 280213 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

 

[leejor]

09:56:30.812 [CM503007]: Call(43): Device joined: sip:[email protected]:40600;rinstance=5f46d0fe7e0512e6
09:56:30.812 [CM503007]: Call(43): Device joined: sip:[email protected]:62310;transport=UDP;rinstance=ead7065baebfb13d

The log shows the caller joined to voicemail, then terminated.

09:56:33.546 [CM503008]: Call(43): Call is terminated

I'm wondering if having the logs set to verbatim, would provide any additional information?

Why are some extensions having a problem with registration, could that be related?

I assume that all services show as running in 3CX?

Did you try backing up the system, then re-installing 3CX? There may be either a firmware (3CX) corruption, or, possibly a hardware or Windows software issue. What type of hardware, Windows version are you running? If you have an automated attendant set-up, do you hear audio when calling into that? If not, it could indicate an audio driver issue.

 

[mpark]

I set the logs to verbose and tried a call to 999 and it did not provide any additional info about the call and why it was dropped. It still said terminated just after the device joined the call. The extensions that are having trouble registering are not related to this current problem I believe.

If it is a last resort I call backup and reinstall. I am using a Windows Server 2008 Standard 32-Bit with 4GB ram.

 

[leejor]

Being a server, you may want to confirm that it is not a machine audio issue. Will the server "play" any audio files (wav) that you select?

 

[lneblett]

Some phones have an option whereby they may still be allowed to dial even if not registered. I assume that some of the rules could be set such that I'f the phones are not registered to go to Vmail. Then a phone that is also not registered could make a call to a non-registered phone, get a ring or two and then be terminated by the system upon recognizing the issue.
I don't know this to be the case as I have not tried nor do I have V8 around, but it seems plausible.

I would concentrate on getting the registration issue resolved if these are supposed to be active and then attack the Vmail disconnect issue.