3CX 5.1 OutBound not working (RESOLVED)

Discussion in '3CX Phone System - General' started by Jared.Savage, Mar 3, 2008.

Thread Status:
Not open for further replies.
  1. Jared.Savage

    Joined:
    Nov 28, 2007
    Messages:
    7
    Likes Received:
    0
    I installed 5.1 fresh, after uninstalling 3. Restoring config failed miserably, with no connection being possible. The router is configured properly, and was working previously. I've since uninstalled and reinstalled fresh and reconfigured 3cx from scratch. It's working for inbound calls to local systems, but I still have two serious problems:

    1) Outbound calls. All outbound calls are failing, whether from local or remote (tunneled) connections. We are unable to place a single outbound call since installing 5.1. When attempting a call, the following errors are displayed in the server status:

    Code:
    12:55:22.171  	Call::Terminate  	[CM503008]: Call(2): Call is terminated
    12:55:22.171 	Call::RouteFailed 	[CM503014]: Call(2): Attempt to reach [sip:5141234567@192.168.0.175:5060] failed. Reason: Not Found
    12:55:22.156 	CallCtrl::onSelectRouteReq 	[CM503013]: Call(2): No known route to target: [sip:5141234567@192.168.0.175:5060]
    12:55:22.156 	CallCtrl::onSelectRouteReq 	[CM503010]: Making route(s) to [sip:5141234567@192.168.0.175:5060]
    12:55:22.156 	MediaServerReporting::SetRemoteParty 	[MS210000] C:2.1:Offer received. RTP connection: 192.168.0.177:42006(42007)
    12:55:22.156 	CallLeg::setRemoteSdp 	Remote SDP is set for legC:2.1
    12:55:22.156 	Extension::printEndpointInfo 	[CM505001]: Ext.104: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone v0.1] Transport: [sip:192.168.0.175:5060]
    12:55:22.140 	CallCtrl::onIncomingCall 	[CM503001]: Call(2): Incoming call from Ext.104 to [sip:5141234567@192.168.0.175:5060]
    12:55:22.140 	CallLeg::onNewCall 	[CM500002]: Info on incoming INVITE:
    INVITE sip:5141234567@192.168.0.175:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.177:5060;branch=z9hG4bK-d87543-f27eff56a05bb014-1--d87543-;rport=5060
    Max-Forwards: 70
    Contact: [sip:104@192.168.0.177:5060]
    To: [sip:5141234567@192.168.0.175:5060]
    From: "3CXPhone"[sip:104@192.168.0.175:5060];tag=db074e4e
    Call-ID: OTI2MTQ3NTE4ZmE3OGE5OTg2ZTUxNWUxYzBhMmM5YjY.
    CSeq: 2 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER
    Proxy-Authorization: Digest username="104",realm="3CXPhoneSystem",nonce="12849040521:3937ba92e74c9844041bf00ef97ed167",uri="sip:5141234567@192.168.0.175:5060",response="722241aef2ffd343f11256b4ab7aef74",algorithm=MD5
    Supported: replaces
    User-Agent: 3CX Phone v0.1
    Content-Length: 0


    2) Remote connections over the tunnel are unable to receive any calls whatsoever. Internal call, external call, it doesn't matter. No calls are received by remote connections. Not even a hint of the server connecting, or the softphone receiving the connection. They work fine when calling out to extensions, though. When attempting to call a remote extension (150) from a local (104), these errors are generated in the server status:

    Code:
    13:06:38.609  	CallLeg::onConfirmed  	Session 135 of leg C:3.1 is confirmed
    13:06:38.500 	CallCtrl::onLegConnected 	[CM503007]: Call(3): Device joined: sip:104@192.168.0.177:5060;rinstance=291cf431764a513c
    13:06:38.500 	MediaServerReporting::SetRemoteParty 	[MS210003] C:3.1:Answer provided. Connection(transcoding mode):192.168.0.175:7002(7003)
    13:06:38.406 	CallCtrl::onLegConnected 	[CM503007]: Call(3): Device joined: sip:
    13:06:38.375 	CallCtrl::onRerouteReq 	[CM503005]: Call(3): Forwarding: IVR:RecordMessage@[Dev]
    13:06:22.921 	MediaServerReporting::SetRemoteParty 	[MS210004] C:3.3:Offer provided. Connection(proxy mode): 74.57.223.80:9004(9005)
    13:06:22.812 	MediaServerReporting::SetRemoteParty 	[MS210004] C:3.2:Offer provided. Connection(proxy mode): 74.57.223.80:9002(9003)
    13:06:22.703 	CallCtrl::onSelectRouteReq 	[CM503004]: Call(3): Calling: Shared:150@[Dev:sip:150@127.0.0.1:5060, Dev:sip:150@74.57.223.80:55212;rinstance=4027fb11e26d941a]
    13:06:22.703 	CallCtrl::onSelectRouteReq 	[CM503010]: Making route(s) to [sip:150@192.168.0.175:5060]
    13:06:22.703 	MediaServerReporting::SetRemoteParty 	[MS210000] C:3.1:Offer received. RTP connection: 192.168.0.177:42008(42009)
    13:06:22.703 	CallLeg::setRemoteSdp 	Remote SDP is set for legC:3.1
    13:06:22.703 	Extension::printEndpointInfo 	[CM505001]: Ext.104: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone v0.1] Transport: [sip:192.168.0.175:5060]
    13:06:22.671 	CallCtrl::onIncomingCall 	[CM503001]: Call(3): Incoming call from Ext.104 to [sip:150@192.168.0.175:5060]
    13:06:22.671 	CallLeg::onNewCall 	[CM500002]: Info on incoming INVITE:
    INVITE sip:150@192.168.0.175:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.177:5060;branch=z9hG4bK-d87543-7f37a25571130a30-1--d87543-;rport=5060
    Max-Forwards: 70
    Contact: [sip:104@192.168.0.177:5060]
    To: [sip:150@192.168.0.175:5060]
    From: "3CXPhone"[sip:104@192.168.0.175:5060];tag=401ba775
    Call-ID: ZTIyOGEzMDBmMjlmMjk1MDE5MmI0ZWZlNzU1ZGIyMzA.
    CSeq: 2 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER
    Proxy-Authorization: Digest username="104",realm="3CXPhoneSystem",nonce="12849041182:a5a3815e16ffdae80683c3439fbd1681",uri="sip:150@192.168.0.175:5060",response="4a12a3d72fed7d0c9b9cd6790530e71d",algorithm=MD5
    Supported: replaces
    User-Agent: 3CX Phone v0.1
    Content-Length: 0
    

    These issues, especially the no outbound calls, are killing me right now. Any assistance or insight is very much appreciated!
     
  2. Jared.Savage

    Joined:
    Nov 28, 2007
    Messages:
    7
    Likes Received:
    0
    Re: 3CX 5.1 not working. (Inbound to remotes & All outbound)

    The problem was with the outbound rule. Plain calls were not getting through because it was misconfigured. I had a * in the prefix field, thinking it would match all calls.

    I've set mine up as follows and alls well now. Hope this helps anyone having similar troubles! A note to 3cx: The error message that occurs from this being misconfigured doesn't indicate to check the outbound rules. Might be a good idea to point people in that direction if they're getting outbound call problems.

    Cheers,
    -Jared
     
Thread Status:
Not open for further replies.