Digital Reception Error: Call Could Not be Completed

Discussion in '3CX Phone System - General' started by nthomthom, Sep 8, 2011.

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

    Joined:
    Sep 8, 2011
    Messages:
    23
    Likes Received:
    0
    Every time I set the digital receptionist I Get an error saying "This Call Could not be completed, please try again later.... we apologize." I'm not sure what is wrong. I know it is set up correctly, im using the right audio format etc, but for some unknown reason i cant get DR to work... Any idea why this may be occurring?

    My logs:

    08:28:36.171 Currently active calls - 1: [10]
    08:28:33.000 [CM503007]: Call(10): Device joined: sip:800@127.0.0.1:40600;rinstance=ab457b286e55c2a3
    08:28:32.984 [CM503007]: Call(10): Device joined: sip:xxxxxxxx@callcentric.com:5060
    08:28:32.984 [CM505001]: Ext.800: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:800@127.0.0.1:5060]
    08:28:32.984 [CM503002]: Call(10): Alerting sip:800@127.0.0.1:40600;rinstance=ab457b286e55c2a3
    08:28:32.781 [CM503025]: Call(10): Calling Ext:Ext.800@[Dev:sip:800@127.0.0.1:40600;rinstance=ab457b286e55c2a3]
    08:28:32.781 [CM503004]: Call(10): Route 1: Ext:Ext.800@[Dev:sip:800@127.0.0.1:40600;rinstance=ab457b286e55c2a3]
    08:28:32.781 [CM503010]: Making route(s) to <sip:800@192.168.1.57:5060>
    08:28:32.781 [CM505003]: Provider:[CallCentric - US] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:17772799700@www.domain.com:5060]
    08:28:32.765 [CM503001]: Call(10): Incoming call from 5555555555@(Ln.10000@CallCentric - US) to <sip:800@192.168.1.57:5060>
    08:28:32.671 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:800
     
  2. pat

    pat

    Joined:
    Feb 12, 2008
    Messages:
    34
    Likes Received:
    0
    the same for me.

    do you found a solution?

    thanks
    pat
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,129
    Likes Received:
    153
    Hi

    this is the scenario where the webserver cannot be reached. Can you check the webserver? What ws are you using?

    Tests:

    if you call Voicemail number default 999 does this work? Or is the problem only with IVR extensions?
    is the webserver running? if IIS is the application pool running?
    Can you access the site http://IP:5000/ivr ? If you get a blank screen right click view source - you should see an xml file.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. pat

    pat

    Joined:
    Feb 12, 2008
    Messages:
    34
    Likes Received:
    0
    Have you change the default Port (5000) of the Webserver?
    If yes, you must also change the port for ivr
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. mixig

    mixig Active Member

    Joined:
    Dec 13, 2011
    Messages:
    524
    Likes Received:
    12
    Hi,

    i have the same problem just like in the first post, what I tested till now it that IVR prompts are not corrupted, from local phone there is the same message as from the first post, I aslo readded the prompts but nothing. At Monday I will continue debugging from the post above, if someone had the same issue and solve it please share...

    Thanks
     
  6. mixig

    mixig Active Member

    Joined:
    Dec 13, 2011
    Messages:
    524
    Likes Received:
    12
    Problem update:

    today we tested 999 voice mail and get the message from above: "This Call Could not be completed, please try again later.... we apologize." Next thing we tested web server (abby), abby web service is started (3cx management console) but if we try to "telnet 127.0.0.1:5000" or anything else e.g. 127.0.0.1:5000/ivr we get nothing. It seems that 3cx wans`t listening on port 5000. We updated languages updates and restarted the machine (not 3cx services, we tried that before but no luck). After that IVR are working... we shall see for how long... :D

    3cx v11 is installed on XP SP3. Could that be a source of the problem?
     
  7. 3CXfoxhallsolutions

    3CXfoxhallsolutions New Member

    Joined:
    Sep 8, 2012
    Messages:
    211
    Likes Received:
    0
    3CX have told us that from V.11 onward, Windows XP is no longer supported.

    So - could be the source of the problem, but there is not going to be much that can be done to prove or disprove it.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.