Dial out problems

Discussion in '3CX Phone System - General' started by randyintejas, Mar 27, 2008.

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

    Joined:
    Mar 27, 2008
    Messages:
    6
    Likes Received:
    0
    I have 3cx Small Business, AudioCodes (with Firmware update to 52) and Snom 360 phones.
    I got everything setup and working fine except for the outbound dial. You can call-in and to other extensions with no problem. I also setup the Soft Client and have the same issue. I have searched the voipstore and the 3cx forums and can not find an answer. I have the outbound rule set to:

    Calls to num: Blank

    Calls from ext: 100-200

    Calls to number with a length of: 10

    Route 1 AudioCodes MP114 strip digits 0 prepend blank

    The 3cx server is 192.168.1.2 and the AudioCodes is 192.168.1.4

    Extensions are 100, 101, 102 103 etc…

    Line status is all Green

    On the Audio Codes I changed Hot to Enable and this allowed inbound calls but, other than that I followed the 3CX instructions and guides

    This is a copy of the 3CX server log:

    22:08:46.812 Call::Terminate [CM503008]: Call(5): Call is terminated

    22:08:46.796 Call::RouteFailed [CM503014]: Call(5): Attempt to reach [sip:9035715841@192.168.1.2:5060] failed. Reason: Not Found

    22:08:46.796 CallLeg::eek:nFailure [CM503003]: Call(5): Call to sip:9035715841@192.168.1.4:5060 has failed; Cause: 404 Not Found; from IP:192.168.1.4:5060

    22:08:46.656 MediaServerReporting::SetRemoteParty [MS210004] C:5.5:Offer provided. Connection(proxy mode): 192.168.1.2:7042(7043)

    22:08:46.656 CallLeg::eek:nFailure [CM503003]: Call(5): Call to sip:9035715841@192.168.1.4:5060 has failed; Cause: 404 Not Found; from IP:192.168.1.4:5060

    22:08:46.500 MediaServerReporting::SetRemoteParty [MS210004] C:5.4:Offer provided. Connection(proxy mode): 192.168.1.2:7040(7041)

    22:08:46.500 CallLeg::eek:nFailure [CM503003]: Call(5): Call to sip:9035715841@192.168.1.4:5060 has failed; Cause: 404 Not Found; from IP:192.168.1.4:5060

    22:08:46.406 MediaServerReporting::SetRemoteParty [MS210004] C:5.3:Offer provided. Connection(proxy mode): 192.168.1.2:7038(7039)

    22:08:46.390 CallLeg::eek:nFailure [CM503003]: Call(5): Call to sip:9035715841@192.168.1.4:5060 has failed; Cause: 404 Not Found; from IP:192.168.1.4:5060

    22:08:46.296 MediaServerReporting::SetRemoteParty [MS210004] C:5.2:Offer provided. Connection(proxy mode): 192.168.1.2:7036(7037)

    22:08:46.296 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(5): Calling: PSTNline:10802@[Dev:sip:10802@192.168.1.4:5060, Dev:sip:10800@192.168.1.4:5060, Dev:sip:10801@192.168.1.4:5060, Dev:sip:10803@192.168.1.4:5060]

    22:08:46.281 MediaServerReporting::SetRemoteParty [MS210000] C:5.1:Offer received. RTP connection: 127.0.0.1:42000(42001)

    22:08:46.281 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:9035715841@192.168.1.2:5060]

    22:08:46.281 CallLeg::setRemoteSdp Remote SDP is set for legC:5.1

    22:08:46.281 Extension::printEndpointInfo [CM505001]: Ext.200: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone v5.1] Transport: [sip:192.168.1.2:5060]

    22:08:46.281 CallCtrl::eek:nIncomingCall [CM503001]: Call(5): Incoming call from Ext.200 to [sip:9035715841@192.168.1.2:5060]

    Thanks for any help!
     
Thread Status:
Not open for further replies.