This call could not be completed (Abyss server)

Discussion in '3CX Phone System - General' started by jonathanc, Sep 29, 2016.

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

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    I've looked at previous posts on this topic but couldn't find any solution relating to this error using the Abyss web server.

    Our 3CX system (v10.0.24018.2322 free) has been chugging away happily for years, when suddenly the IVR facility stopped working. Both internal and external calls to the voicemail extension (666) produce an American lady saying: 'This call could not be completed. Please try again later. We apologize.'

    Is a Windows automatic update to blame, I wonder? No-one touched any settings in 3CX.

    We're running Win10 Home on the server with Cisco phones (SPA 525G and SPA303).

    The voice prompts appear to be in their proper place in C\ProgramData\3CX\Data\Ivr\Prompts\Sets

    Here is the relevant section of the log:

    21:04:41.750 [CM503008]: Call(2): Call is terminated
    21:04:36.088 [CM503007]: Call(2): Device joined: sip:666@127.0.0.1:40600;rinstance=d1c8187058961bea
    21:04:36.087 [CM503007]: Call(2): Device joined: sip:106@192.168.1.31:5261
    21:04:36.083 [CM505001]: Ext.666: 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:666@127.0.0.1:5060]
    21:04:36.083 [CM503002]: Call(2): Alerting sip:666@127.0.0.1:40600;rinstance=d1c8187058961bea
    21:04:35.961 [CM503025]: Call(2): Calling Ext:Ext.666@[Dev:sip:666@127.0.0.1:40600;rinstance=d1c8187058961bea]
    21:04:35.944 [CM503004]: Call(2): Route 1: Ext:Ext.666@[Dev:sip:666@127.0.0.1:40600;rinstance=d1c8187058961bea]
    21:04:35.944 [CM503010]: Making route(s) to "Voice Mail"<sip:666@192.168.1.4>
    21:04:35.943 [CM505001]: Ext.106: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA303-7.5.4] PBX contact: [sip:106@192.168.1.4:5060]
    21:04:35.942 [CM503001]: Call(2): Incoming call from Ext.106 to "Voice Mail"<sip:666@192.168.1.4>

    Can anyone help, please?
     
  2. Chib@voip

    Joined:
    Feb 25, 2016
    Messages:
    21
    Likes Received:
    0
    Have you restart the services yet?
     
  3. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    Thanks for the suggestion, Chib@voip, but yes - I've restarted the services and even reinstalled 3CX (also on another machine) but still the symptoms persist. Mind you, I did a restore of the previous configuration, so if that's wrong I'll have re-imported the problem, I suppose. Perhaps I should try a basic installation with minimum alteration. In fact, I'll do that now.
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,855
    Likes Received:
    300
    Did you by chance have a Demo licence applied? All of the older ones have now been withdrawn.
     
  5. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    No, leejor - at least, I'm pretty sure not. It was back in the days of 'Here's a free version to tempt you - no strings, but some capabilities unavailable.' All the other elements that are supposed to work do work.

    Poss clue: pointing a browser to 127.0.0.1:5000 produces the error message: The current identity (NT AUTHORITY\SYSTEM) does not have write access to 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files'. The same message results from {server IP address}:5000 from across the network. Could this be connected?

    Many thanks for your help.
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,855
    Likes Received:
    300
    Well...not having write access, to a disk, might be a problem, if the call is tying to go to voicemail... if the issues are related.
     
  7. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    Yes, that's what I thought. I've searched the Web and although lots of other people seem to have this write-access problem I have yet to find a solution which works for me. When I've sorted that issue out I'll give 3CX voicemail another try and report back here in case it helps someone else.

    Many thanks again for your help.
     
  8. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    Solved.

    It wasn't actually a disk access problem - just the lack of a folder to write to.

    On the 3CX server I went to C:\Windows\Microsoft.NET\Framework64\v4.0.30319 an found no 'Temporary ASP.NET Files' folder.

    So I added one, and Robert's your cousin's father.

    Thanks again for your input.
     
Thread Status:
Not open for further replies.