Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Manging Ext 999 - Voice Mail

Discussion in '3CX Phone System - General' started by abruton, Jan 14, 2009.

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

    Joined:
    Dec 8, 2008
    Messages:
    7
    Likes Received:
    0
    Hi

    I'm battling to get Voice Mail (VM) to work. There is no extension 999 listed under the extensions. The rest of the system is running well.

    When I phone an extension, I do not get through to the VM system. Here is the logs:

    11:00:05.068 Call::Terminate [CM503008]: Call(63): Call is terminated
    10:59:40.099 CallCtrl::eek:nLegConnected [CM503007]: Call(63): Device joined: sip:999@127.0.0.1:40600;rinstance=e527a84568740144
    10:59:40.099 CallCtrl::eek:nLegConnected [CM503007]: Call(63): Device joined: sip:208@192.168.0.208:5060;transport=udp;user=phone
    10:59:40.099 Extension::printEndpointInfo [CM505001]: Ext.999: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX MakeCall helper] Transport: [sip:127.0.0.1:5060]
    10:59:40.099 CallCtrl::eek:nAnsweredCall [CM503002]: Call(63): Alerting sip:999@127.0.0.1:40600;rinstance=e527a84568740144
    10:59:39.568 CallCtrl::eek:nRerouteReq [CM503005]: Call(63): Forwarding: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=e527a84568740144]
    10:59:39.552 Call::RouteFailed [CM503015]: Call(63): Attempt to reach [sip:679@192.168.0.150;user=phone] failed. Reason: Not Registered
    10:59:39.552 CallCtrl::eek:nSelectRouteReq [CM503016]: Call(63): Target is not registered: Ext:Ext.679
    10:59:39.552 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:679@192.168.0.150;user=phone]
    10:59:39.552 Extension::printEndpointInfo [CM505001]: Ext.208: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream BT200 1.1.6.44] Transport: [sip:192.168.0.150:5060]
    10:59:39.552 CallCtrl::eek:nIncomingCall [CM503001]: Call(63): Incoming call from Ext.208 to [sip:679@192.168.0.150;user=phone]

    I've checked the settings and all extensions have VM activated.

    Any ideas how to manage the VM extension?

    Best regards

    Andre
     
  2. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    The VM extension 999 will not appear in the Extension list as it is not a physical extension.

    What exactly would you like to do OR what exactly is the issue you are encountering. VM is responding to calls.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. abruton

    Joined:
    Dec 8, 2008
    Messages:
    7
    Likes Received:
    0
    Hi

    There is no VM prompt or anything, just silence. Everything is switched on for VM (I think).

    Best regards

    Andre
     
  4. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    What OS and SP level are you running? What version and build of 3CX are you running?

    Can you enable Verbose mode and paste the Server Status logging for a call to 999 ? Please ensure you make the call to 999 from a 3CX VOIP Client in headset mode.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.