Outbound rings but doesn't answer

Discussion in '3CX Phone System - General' started by rlaney, Jan 2, 2008.

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

    Joined:
    Nov 27, 2007
    Messages:
    12
    Likes Received:
    0
    3cx v3, MP114FXO, GXP2000. Inbound works ok. Outbound rings called number but when answered, line is dead, no dial tone, and gateway continues to ring. Anyone know what I've missed?
     
  2. Mori

    Mori New Member

    Joined:
    Mar 23, 2007
    Messages:
    223
    Likes Received:
    0
    For v3, try "Bind to media server".
    If already checked, uncheck it and try again.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. rlaney

    Joined:
    Nov 27, 2007
    Messages:
    12
    Likes Received:
    0
    Thanks for the suggestion, but it didn't help. Here is the system log for what it's worth. It just shows the call initiated and ringing, then terminated when I hang up. But maybe it means more to someone other than me.

    11:45:25.921 StratInOut::eek:nHangUp [CM104007] Call(1): Call from Ext.103 to 2142885561 has been terminated by Ext.103; cause: CANCEL; from IP:192.168.2.106
    11:44:40.546 CallConf::eek:nProvisional [CM103003] Call(1): Ln:10000@Gateway 1 is ringing
    11:44:39.484 CallConf::eek:nIncoming [CM103002] Call(1): Incoming call from 103 (Ext.103) to sip:92142885561@192.168.2.103
    11:43:07.937 ListenConnect [CM114000] SL: connected TRINITYFW:0/PHPExtension_0 at [TRINITYFW]/PHPExtension_0
    11:00:40.718 StunClient::process [CM115002] STUN resolved external IP=69.149.35.62:5060 by server 64.69.76.23
    11:00:40.625 StunClient::process [CM115002] STUN resolved external IP=69.149.35.62:5060 by server 64.69.76.23
    11:00:40.546 StunClient::process [CM115001] Send initial STUN request to 64.69.76.23
    11:00:40.437 CallMgr::Stack::thread [CM106001] ** Enter Stack Loop **
    11:00:40.093 CallMgr::DumThread::thread [CM100004] ** Enter DUM Thread **
    11:00:39.031 MediaServerReporting::Service *** Connected to TRINITYFW:5483/IVRServer at 127.0.0.1:5483 ***
    11:00:39.015 IVRConnected [CM111000] IVR Server is connected
    11:00:39.015 ListenConnect [CM114000] SL: connected TRINITYFW:5483/IVRServer at [TRINITYFW]/IVRServer
    11:00:38.546 MediaServerReporting::Service *** Connecting to [127.0.0.1:5483] ***
    11:00:37.953 ListenConnect [CM114000] SL: connected TRINITYFW:0/VoiceBoxManagerService at [TRINITYFW]/VoiceBoxManagerService
    11:00:37.546 MediaServerReporting::Service IVR not found on 127.0.0.1:5483
    11:00:36.609 DBA [CM109000] ** Database connection Ok **
    11:00:36.468 MediaServerReporting::Service *** Connecting to [127.0.0.1:5483] ***
    11:00:35.468 MediaServerReporting::Service IVR not found on 127.0.0.1:5483
    11:00:34.984 CallMgr::Stack::Initialize [CM106000] ** Adding transports **
    11:00:34.765 CallMgr::Initialize [CM100003] ** Initializing SIP stack **
    11:00:34.765 CallMgr::Initialize [CM100002] Default Local IP address: 192.168.2.103:5060
    11:00:34.562 MediaServerConnected [CM112000] Media Server is connected
    11:00:34.562 ListenConnect [CM114000] SL: connected TRINITYFW:0/MediaServer at [TRINITYFW]/MediaServer
    11:00:33.718 CallMgr::Initialize [CM100001] Version: 3.1.2434.0
    11:00:33.718 CallMgr::Initialize [CM100000] Start 3CX PhoneSystem Call Manager
    11:00:33.625 LoadLicenceInfo [CM100008] Licence loading error
     
  4. bhavank

    bhavank New Member

    Joined:
    Apr 24, 2007
    Messages:
    109
    Likes Received:
    0
    are the ports opened properly
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. rlaney

    Joined:
    Nov 27, 2007
    Messages:
    12
    Likes Received:
    0
    Yes, the ports are opened. I even tried with the firewall off to make sure it wasn't the problem.
     
  6. rlaney

    Joined:
    Nov 27, 2007
    Messages:
    12
    Likes Received:
    0
    I set FXO Settings/Answer Supervision to Yes and it now works.

    Thanks to all for the suggestions.
     
Thread Status:
Not open for further replies.