PLEASE HELP: We cannot make any outbound calls -

Discussion in '3CX Phone System - General' started by HPRG, May 11, 2012.

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

    Joined:
    May 11, 2012
    Messages:
    8
    Likes Received:
    0
    Call to 3526102365@(Ln.10002@Broadvox) has failed. [ V4 208.93.224.230:5060 UDP target domain=unspecified mFlowKey=828 ] replied: 403 Forbidden; from IP:208.93.224.230:5060
     
  2. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,132
    Likes Received:
    210
    Check with your voip provider to see if they are blocking something.
    Can you get inbound calls?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,586
    Likes Received:
    252
    Did this just start failing, or did it ever work? If it did work, then what changes have you made?
    Are you sending the correct digits/format?
    Does the number require any prefix digits, 0,00,1, 011, 001?
    Do you have enough credit with Broadvox to call that number?
     
  4. HPRG

    Joined:
    May 11, 2012
    Messages:
    8
    Likes Received:
    0
    Thank you all! ;-)

    1. I have plenty of credit with Broadvox
    2. It was all working fine before...There has been WAY TOO MUCH finger pointing by our 3CX reseller, and 3 different VoIP providers...we finally said enough.
    3. We took the 3CX out of the 1-NIC local IP address, behind the firewall, ports forwarded set-up.
    4. We then enabled the 2-NIC and gave it a Public IP and faced it outward at the Cable Modem switch port. *I know I know I know...Naked, exposed, yadayada...But we needed to eliminate the network from the equation on all SIP transactions in/outbound to the Telephone world.
    5. When we did this, we then shut off all all traffic to/from the 3CX on the Firewall so that the internal NIC would never route SIP or UDP traffic to/fro the 3CX.
    6. So...one NIC "outside" and one NIC "inside addressed.
    7. We then shut off STUN and Tunnel and we installed NetMon on the MS Server running 3CX and we see that authentications go out and registrations happen with Broadvox over the "outside" NIC and green pretty lightd on the management and INBOUND calls work fine. 3CX to 3CX internal PBX calls on the LAN and WAN work fine.
    8. But noone can FREAKIN dial out...
    ;-(
     
  5. HPRG

    Joined:
    May 11, 2012
    Messages:
    8
    Likes Received:
    0
    I guess my logs were deleted :( for my own good I assume...
     
  6. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,132
    Likes Received:
    210
    anything in NetMon for the outbound attempt or in the 3cx logs?
    you say logs deleted? who did that?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. HPRG

    Joined:
    May 11, 2012
    Messages:
    8
    Likes Received:
    0
    I posted my NetMon and my 3CX logs...but I "guess" that a moderator on this site deleted them. Maybe it is for security reasons?
     
  8. HPRG

    Joined:
    May 11, 2012
    Messages:
    8
    Likes Received:
    0
    NetMon Log

    172384 11:43:20 AM 5/11/2012 9884.4306069 3CXPhoneSystem.exe 208.93.224.230 "xx.xx.xxx.xx" SIP SIP:Response: SIP/2.0 100 Trying {SIP:8, UDP:7, IPv4:5}
    172385 11:43:20 AM 5/11/2012 9884.5203027 3CXPhoneSystem.exe 208.93.224.230 "xx.xx.xxx.xx" SIP SIP:Response: SIP/2.0 403 Forbidden {SIP:8, UDP:7, IPv4:5}
    172386 11:43:20 AM 5/11/2012 9884.5206862 3CXPhoneSystem.exe "xx.xx.xxx.xx" 208.93.224.230 SIP SIP:Request: ACK sip:3523455820@208.93.224.230:5060 SIP/2.0 {SIP:8, UDP:7, IPv4:5}
    172667 11:43:56 AM 5/11/2012 9920.3137791 3CXPhoneSystem.exe "xx.xx.xxx.xx" 208.93.224.230 SDP SDP:Request: INVITE sip:3523455820@208.93.224.230:5060 SIP/2.0; SDP:SessionName=3cxPS Audio call, Version=0, MediaDescription=video 40034 RTP/AVP 34 {SIP:8, UDP:7, IPv4:5}

    I "xx.xx.xxx.xx" all my server IP instances...everyone knows BroadVox's
     
  9. HPRG

    Joined:
    May 11, 2012
    Messages:
    8
    Likes Received:
    0
    The ENTIRE string of Logs looks like the one above...
    With...
    013523455820
    13523455820
    3523455820
    3455820
    18005551212
    17145551212
    7145551212

    etc..
     
  10. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Use "code" tag if you post logs. (select text press Code button above the "message editor" window)
    Please post log provided by PBX on verbose (debug) level. In the log (it should not be so long) please mask your IPs and Caller ids (not completely, just end of the IPs and called/calling number). It will help to somebody detect the problem if it was already solved.
    In this particular case, you need to post log (Verbose level) of ONLY one call which is rejected by the provider with 403 Forbidden response.

    Recommended:
    Please contact Broadvox technical support. Broadvox server answers 403 forbidden. It is almost impossible to guess the reason basing on responses received from remote system. Owner of the server knows everything about reasons.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. jfschneid

    Joined:
    Mar 13, 2012
    Messages:
    7
    Likes Received:
    0
    Having a similar problem. Cannot make outbound calls. After upgrading to v14 from 12.5 things were working fine. Then 4 days ago we had a small outage of outbound calls. They came back after a few minutes. Then yesterday, outbound calls just stopped working and we started getting a 403 Forbidden message from the system.. I spoke with our provider and they said that the calls are not making it to their system. When looking at our network monitor I am not seeing the traffic going out either. Any help would be appreciated.

    Code:
    06-Oct-2015 08:50:28.315   [CM504001]: Endpoint Extn:107: new contact is registered. Contact(s): [sip:107@127.0.0.1:5488 / 107,sip:107@192.168.XXX.XXX:5060 / 107]
    06-Oct-2015 08:50:23.813   Leg L:11.1[Extn] is terminated: Cause: BYE from PBX
    06-Oct-2015 08:50:23.753   [CM503020]: Call(C:11): Normal call termination. Call originator: Extn:107. Reason: Forbidden
    06-Oct-2015 08:50:23.753   L:11.1[Extn] failed to reach Line:10000>>1609932XXXX, reason Forbidden
    06-Oct-2015 08:50:23.752   Leg L:11.2[Line:10000>>1609932XXXX] is terminated: Cause: 403 Forbidden/INVITE from 208.93.226.215:5060
    06-Oct-2015 08:50:23.752   Call to T:Line:10000>>1609932XXXX@[Dev:sip:856310XXXX@dn01-04.fs.broadvox.net:5060] from L:11.1[Extn] failed, cause: Cause: 403 Forbidden/INVITE from 208.93.226.215:5060
    06-Oct-2015 08:50:23.744   [CM503003]: Call(C:11): Call to <sip:1609932XXXX@dn01-04.fs.broadvox.net:5060> has failed; Cause: 403 Forbidden/INVITE from 208.93.226.215:5060
    06-Oct-2015 08:50:23.582   [CM503025]: Call(C:11): Calling T:Line:10000>>16099329970@[Dev:sip:856XXXXXXX@dn01-04.fs.broadvox.net:5060] for L:11.1[Extn]
    06-Oct-2015 08:50:23.579   [MS006000] C:11.2: connection address is enforced to 173.61.XXX.XXX
    06-Oct-2015 08:50:23.531   [CM503027]: Call(C:11): From: Extn:107 ("Jason" <sip:107@192.168.XXX.XXX:5060>)  to  T:Line:10000>>1609932XXXX@[Dev:sip:856310XXXX@dn01-04.fs.broadvox.net:5060]
    06-Oct-2015 08:50:23.531   [CM503004]: Call(C:11): Route 1: from L:11.1[Extn] to T:Line:10000>>1609932XXXX@[Dev:sip:856310XXXX@dn01-04.fs.broadvox.net:5060]
    06-Oct-2015 08:50:23.531   Line limit check: Current # of calls for line Lc:10000(@BVOX[<sip:856XXXXXXX@dn01-04.fs.broadvox.net:5060>]) is 0; limit is 4
    06-Oct-2015 08:50:23.531   Call(C:11): Call from Extn:107 to 91609932XXXX matches outbound rule 'Rule for BVOX'
    06-Oct-2015 08:50:23.529   [CM503001]: Call(C:11): Incoming call from Extn:107 to <sip:91609932XXXX@192.168.XXX.XXX:5060>
    06-Oct-2015 08:50:23.529   NAT/ALG check:L:11.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks
     
  12. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,064
    Likes Received:
    58
    There is something in the Inite that your provider does not like.

    This is usually along the lines of the credentials not being correct or perhaps they expect to see a specific phone number by which they use to validate the connection.

    It may be that the easiest thing to do is to contact then and let them look at the SIP headers and tell what the error is.
     
Thread Status:
Not open for further replies.