3CX/Broadvoice/Cisco 7960G/No outdialing

Discussion in '3CX Phone System - General' started by ajohnson443, Mar 27, 2012.

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

    Joined:
    Mar 27, 2012
    Messages:
    30
    Likes Received:
    4
    have 3CX installed, registered to BroadVoice, am able to take incoming calls but when I outdial I get no ring, dead air, recipient phone never rings. If i wait long enough the call will terminate and the log will show "Normal call termination. Reason: No answer". I have a feeling it is the STUN error I am getting but I can't seem to figure where to resolve it. I tried changing the settings to use my external IP address (it is a semi-static IP from AT&T) but then I started having trouble with the trunk staying registered.

    Port/Trunk Status: Registered
    Extension Status: Registered

    Log Excerpt:
    23:07:15.875 [CM503020]: Normal call termination. Reason: No answer
    23:07:15.875 [CM503016]: Call(14): Attempt to reach <sip:91234567@10.232.1.15> failed. Reason: No Answer
    23:07:15.875 [CM503003]: Call(14): Call to sip:1234567@sip.broadvoice.com:5060 has failed; Cause: 408 Request Timeout; internal
    23:07:04.625 Currently active calls - 1: [14]
    23:06:43.796 [CM503025]: Call(14): Calling VoIPline:1234567@(Ln.10000@BroadVoice)@[Dev:sip:1231234567@sip.broadvoice.com:5060]
    23:06:43.750 [CM503004]: Call(14): Route 1: VoIPline:1234567@(Ln.10000@BroadVoice)@[Dev:sip:1231234567@sip.broadvoice.com:5060]
    23:06:43.750 [CM503010]: Making route(s) to <sip:1234567@10.232.1.15>
    23:06:43.750 [CM505001]: Ext.1000: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cisco-CP7960G/7.5] PBX contact: [sip:1000@10.232.1.15:5060]
    23:06:43.750 [CM503001]: Call(14): Incoming call from Ext.1000 to <sip:91234567@10.232.1.15>
    22:59:05.250 [CM503008]: Call(13): Call is terminated
    22:58:43.656 [CM503025]: Call(13): Calling VoIPline:1234567@(Ln.10000@BroadVoice)@[Dev:sip:1231234567@sip.broadvoice.com:5060]
    22:58:43.609 [CM503010]: Making route(s) to <sip:91234567@10.232.1.15>
    22:58:43.593 [CM503001]: Call(13): Incoming call from Ext.1000 to <sip:91234567@10.232.1.15>
    22:55:49.437 [CM506004]: STUN request to STUN server 199.192.206.228:3478 has timed out; used Transport: [ V4 10.232.1.15:5060 UDP target domain=unspecified mFlowKey=0 ]
    22:55:46.421 [CM506004]: STUN request to STUN server 199.192.206.228:3478 has timed out; used Transport: [ V4 10.232.1.15:5060 UDP target domain=unspecified mFlowKey=0 ]
    22:55:43.406 [CM506004]: STUN request to STUN server 199.192.206.228:3478 has timed out; used Transport: [ V4 10.232.1.15:5060 UDP target domain=unspecified mFlowKey=0 ]
    22:55:40.390 [CM506004]: STUN request to STUN server 199.192.206.228:3478 has timed out; used Transport: [ V4 10.232.1.15:5060 UDP target domain=unspecified mFlowKey=0 ]
    22:55:37.359 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 199.192.206.228:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 10.232.1.15:5060 UDP target domain=unspecified mFlowKey=0 ]
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. ajohnson443

    Joined:
    Mar 27, 2012
    Messages:
    30
    Likes Received:
    4
    I resolved the STUN issue, seems 3CX STUN servers weren't responding.
    Still a no go for out-dialing.
    Attached a log from a clean start through ext to ext dialing and then attempted to out dial. The rule is being applied correctly, stripping the 9.. It just seems to die. I get nothing on my end and the other gets nothing. Eventuall the call ends with my side getting a fast busy.

    I did have this working on an AXON PBX but I wanted what seemed to be a much higher quality system. :p
    Appreciate any insight that is offered.
     

    Attached Files:

    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. ajohnson443

    Joined:
    Mar 27, 2012
    Messages:
    30
    Likes Received:
    4
    After doing a lot of digging on google and tons of other forums, I tried one simple thing. I changed the outgoing proxy from proxy.mia.broadvoice.com to just plain old sip.broadvoice.com (same as the reg server) and now I can make outgoing calls. It is very strange because i used proxy.mia.broadvoice.com on the AXON PBX setup and it worked as of a few minutes before installing 3CX..

    Whatever, it works now. Now on to figuring out all the other bells and whistles.. :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.