odd Voicemail Behaviour

Discussion in '3CX Phone System - General' started by fraggle, Sep 2, 2009.

Thread Status:
Not open for further replies.
  1. fraggle

    Joined:
    Sep 22, 2008
    Messages:
    17
    Likes Received:
    0
    Have the latest build of 3CX Free running on SBS 2008

    have 3 extensions (just a test system at the moment) 1 Snom 300, 1 Linksys SPA322 & 3cx Voip Client. Using Sipgate as the Voip provider

    I can do everything properly, but voicemail. When I ring an extension and it forwards to voicemail, I get no prompt just a bleep & I can then record the voicemail. Obviously some form of greeting is desirable.

    From any of the phones if I dial the voicemail number (I've changed it to 321 - not sure I like dialling 999 here in the UK) I get the attendant but when I key 9 for advanced options I get nothing - the call doesn't drop, I just get nothing. * repeats the initial greeting & # logs me out.

    Happens to all extensions, between extensions & on voip call.

    Any suggestions greatfully received.
     
  2. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    You need to install "Desktop Experience" on WS 2008 or install any codec pack (K-lite for example) which will provide ability to play(read) the mp3 files.

    You can search for the "Desktop Experience" on the forum or to check the FAQ section on wiki.3cx.com for additional information

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. fraggle

    Joined:
    Sep 22, 2008
    Messages:
    17
    Likes Received:
    0
    have installed that & now no Voicemail at all.

    Server Status shows:

    22:46:23.566 [CM503008]: Call(12): Call is terminated
    22:46:23.560 [CM503015]: Call(12): Attempt to reach <sip:321@192.168.15.251:5060> failed. Reason: Not Registered
    22:46:23.558 [CM503015]: Call(12): Attempt to reach <sip:321@192.168.15.251:5060> failed. Reason: Not Registered
    22:46:23.556 [CM503016]: Call(12): Target is not registered: Ext:Ext.321
    22:46:23.556 [CM503010]: Making route(s) to <sip:321@192.168.15.251:5060>
    22:46:23.555 [CM505001]: Ext.100: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone 7.0.4526.0] Transport: [sip:192.168.15.251:5060]
    22:46:23.542 [CM503001]: Call(12): Incoming call from Ext.100 to <sip:321@192.168.15.251:5060>


    Voicemail No is 321 - haven't changed anything else so why should this occur after a reboot
     
  4. tpinnovations

    tpinnovations Member

    Joined:
    Jul 30, 2009
    Messages:
    296
    Likes Received:
    0
    You rebooted your server after install?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. fraggle

    Joined:
    Sep 22, 2008
    Messages:
    17
    Likes Received:
    0
  6. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,506
    Likes Received:
    100
    If it is a Codec problem then try to install the K-Lite Codec Pack http://www.free-codecs.com/download_soft.php?d=5305&s=775
    Restart your Machine, make sure all services have started Correctly and see what happens.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. fraggle

    Joined:
    Sep 22, 2008
    Messages:
    17
    Likes Received:
    0
    would a codec problem give the results in the log posted? How would I know if it is a codec problem?
     
  8. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,506
    Likes Received:
    100
    Please check for the following prompts:

    Record_your_message.wav
    and.wav
    press.wav

    If they exist in your Recordings folder it means that it could be a Codec Problem. It can also be seen in the Media Server Trace Logs.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. fraggle

    Joined:
    Sep 22, 2008
    Messages:
    17
    Likes Received:
    0
    Sorry to be thick, but I'm failing to grasp how "Attempt to reach <sip:321@192.168.15.251:5060> failed. Reason: Not Registered" can equate to a codec problem. Doesn't this sort of suggest that the voicemail service isn't running (it is, I've checked)?
     
  10. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,506
    Likes Received:
    100
    Sorry i didnt read all your posts, i didnt realise what that 321 Was the Voice mail :mrgreen:


    So wait...
    You call an extension and get Forwarded to the Voice mail which in it's turn does not play any Greeting Prompts and only plays the Beep to record your Message...
    Yet you just showed us that 321 ( Voice Mail ) isnt even Registered.

    I'm confused...
    If the Voice Mail Will not Registered, could you try and Change it back to 999 - Restart all Services and see if it does.
    Also as Stepan Mentioned have you installed Desktop Experience on W2008? If you havent i'd do that at least.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. fraggle

    Joined:
    Sep 22, 2008
    Messages:
    17
    Likes Received:
    0
    Installed the desktop experience & rebooted.

    Canged the voicemail back to 999 & restarted, then in desperation rebooted. Still nothing.

    I did get something before the desktop experience was installed....
     
  12. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,506
    Likes Received:
    100
    Could you Post a Clear Attachment of the Media Server Trace Logs here?
    Set the logs to verbose, restart the services, reproduce the call and get the fresh logs please.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Christoph

    Joined:
    Dec 17, 2008
    Messages:
    12
    Likes Received:
    0
    Hi

    I just returned from a 2 week holiday and did a Microsoft Windows Update on Sunday 13th of September. After reboot I have the same odd problem that we can't access any voicemail nor can anyone leave a message - it looks like voicemail service doesn't answer at all - even the service is running. My voicemail number is 99. This is what the log says when I try to access the voicemail via my phone.

    12:01:32.875 [CM503008]: Call(37): Call is terminated

    12:01:32.859 [CM503015]: Call(37): Attempt to reach "99"<sip:99@192.168.1.100:5060> failed. Reason: Not Registered

    12:01:32.859 [CM503015]: Call(37): Attempt to reach "99"<sip:99@192.168.1.100:5060> failed. Reason: Not Registered

    12:01:32.859 [CM503016]: Call(37): Target is not registered: Ext:Ext.99

    12:01:32.859 [CM503010]: Making route(s) to "99"<sip:99@192.168.1.100:5060>

    We are on Version 7.1 using Aastra 57i phones - so don't know what happened with Windows Upate this time - the following fixes from MS were applied based on the date in the system32 folder.

    $NtUninstallKB968816$
    $NtUninstallKB970653-v3$
    $NtUninstallKB967723$
    $NtUninstallKB968389$
    $NtUninstallKB956844$

    Any help would be appreciated before I start to uninstall the fixes for testing. Looks like the complete voicemail is disconnected somehow..

    cheers
    Christoph
     
  14. Christoph

    Joined:
    Dec 17, 2008
    Messages:
    12
    Likes Received:
    0
    Hi

    I missed one hotfix that was installed for IE 8.0, I deinstalled the following fixes from Windows Update and now the voicemail works well as before. I don't know which fix made it but it must be one of those three fixes:

    KB968816$
    KB970653-v3$ (is dependendent on fix IE KB971961) found in the windows\system32\ie8updates folder....

    After reboot the voicemail was working fine again, so if someone knows which of the 3 is the cause, please let me know.

    Christoph
     
  15. Christoph

    Joined:
    Dec 17, 2008
    Messages:
    12
    Likes Received:
    0
    so, finally nailed it down

    don't install KB Fix 968816 - Security Update for Windows Media Format Runtime 9.5 for Windows Server 2003 - it will somehow disable the whole Voicemail functionality. to fix the Problem just go to C:\WINDOWS\$NtUninstallKB968816$\spuninst and deinstall the fix. In may case I didn't have to reboot nor to restart the PBX.

    cheers
    Christoph
     
  16. tpinnovations

    tpinnovations Member

    Joined:
    Jul 30, 2009
    Messages:
    296
    Likes Received:
    0
    Just looked at the released from Microsoft;

    http://support.microsoft.com/kb/968816

    This does affect server 2008 boxes. While my 08 boxes haven't been affected by this, You may wish to check and see if its installed on your machine, and if removing it resolves your situation.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.