Argg No Outgoing Calls

Discussion in '3CX Phone System - General' started by Brandt, Apr 24, 2009.

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

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    Version - 3CX Phone System v7.1.6589.0
    OS - Vista 64-bit SP1
    VOIP Provider - myBBVoice

    Firewall Test PASSED

    Log -
    20:46:29.637 [CM503008]: Call(27): Call is terminated
    20:46:29.635 [CM503015]: Call(27): Attempt to reach <sip:3302025782@192.168.1.100:5060> failed. Reason: Not Found
    20:46:29.634 [CM503014]: Call(27): No known route to target: <sip:3302015782@192.168.1.100:5060>
    20:46:29.628 [MS210000] C:27.1:Offer received. RTP connection: 192.168.1.100:40016(40017)
    20:46:29.627 [CM503010]: Making route(s) to <sip:3302015782@192.168.1.100:5060>
    20:46:29.625 Remote SDP is set for legC:27.1
    20:46:29.625 [CM505001]: Ext.10: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CXVoipPhone;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 3.1.6288.0] Transport: [sip:192.168.1.100:5060]


    I've been searching and tweaking and searching for hours now. Incoming calls work great. However, I can not get outside for the life of me. Any thoughts? I'm using the DR, have 2 extensions, and the soft phone.
     
  2. Brandt

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    I created a Outbound Dial Rule. Im attaching it.


    21:25:24.248 [CM503008]: Call(35): Call is terminated
    21:25:24.246 [CM503003]: Call(35): Call to sip:3302041578@209.17.160.130:5060 has failed; Cause: 302 Moved Temporarily; warning: Noisy feedback tells: pid=51393 req_src_ip=24.140.50.146 req_src_port=5060 in_uri=sip:3302041578@209.17.160.130:5060 out_uri=sip:3302041578@209.17.160.129:5060 via_cnt==1; from IP:209.17.160.130:5060
    21:25:24.244 [CM503015]: Call(35): Attempt to reach <sip:13302041578@192.168.1.100:5060> failed. Reason: Redirected
    21:25:24.244 [CM503014]: Call(35): No known route to target: <sip:3302041578@209.17.160.129:5060>
     

    Attached Files:

  3. Brandt

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    Anyone? :cry:
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,365
    Likes Received:
    227
    I'm assuming that this is going off to a VoIP provider? The line "3302041578@209.17.160.130:5060 has failed; Cause: 302 Moved Temporarily; warning: Noisy feedback" would seem to indicate, if that is the correct IP of your provider, that there is a problem with them. That IP is a Bell Canada IP address, is that who you are using?

    Although, in the first post there is...Attempt to reach <sip:3302025782@192.168.1.100:5060> failed. Reason: Not Found
    What device has 192.168.1.100 on your network that 3CX can't find?

    Who to and how are you trying to route outside calls?
     
  5. Brandt

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    209.17.160.130:5060 is the incoming address for mybbvoice (VOIP provider). 192.168.1.100 is the IP of my 3CX machine running the services.
     
  6. mhanson

    mhanson New Member

    Joined:
    Nov 6, 2008
    Messages:
    186
    Likes Received:
    1
    Hmm, a redirect error. How do you have your Voip Provider configured? Have not seen that error in awhile, If i remember correctly the last time I dealt with it, it was a provider issue (Cant remember which side it was on) but perhaps some additional info could spark my memory.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Brandt

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    Generic Voip Provider

    SIP Server IP - 209.17.160.130
    5060 in
    5060 out

    My # for External # and Auth ID
    My Password

    Outbound Rule
    Line 1 - 1 (Calls to numbers starting with)
    Line 2 - 10-99 (Calls from extensions)

    Hope this helps....this shouldnt be this hard right? :/
     
  8. Brandt

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    16:38:36.251 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.1.100:5060
    16:37:50.735 [CM503008]: Call(30): Call is terminated
    16:37:50.734 [CM503008]: Call(30): Call is terminated
    16:37:47.457 [MS210003] C:30.2:Answer provided. Connection(transcoding mode):127.0.0.1:7004(7005)
    16:37:47.457 [MS210000] C:30.2:Offer received. RTP connection: 127.0.0.1:40610(40611)
    16:37:47.456 Remote SDP is set for legC:30.2
    16:37:47.150 [CM503003]: Call(30): Call to sip:3304542597@209.17.160.130:5060 has failed; Cause: 302 Moved Temporarily; warning: Noisy feedback tells: pid=51396 req_src_ip=24.150.47.146 req_src_port=5060 in_uri=sip:3304642597@209.17.160.130:5060 out_uri=sip:3304642597@209.17.160.129:5060 via_cnt==1; from IP:209.17.160.130:5060
    16:37:47.149 [CM503015]: Call(30): Attempt to reach <sip:11@127.0.0.1:5060> failed. Reason: Redirected
    16:37:47.149 [CM503014]: Call(30): No known route to target: <sip:3304542597@209.17.160.129:5060>
     
  9. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Is it the first entry in log which is related to "Call(30)"?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Brandt

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    right...thats pretty much it. I just got off the phone with tech support and they called me from my number using xlite. So it's gotta be something with my configuration.
     
  11. Brandt

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    I just tried the v6 thats on this site for download and still the same thing.
     
  12. Brandt

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    Any thoughts anyone? :(
     
  13. Brandt

    Joined:
    Apr 24, 2009
    Messages:
    10
    Likes Received:
    0
    Heres what wireshark picked up when trying to make an outgoing call

    77 40.160100 192.168.1.100 69.0.208.27 STUN Message: Binding Request
    78 40.170600 192.168.1.100 69.0.208.27 STUN Message: Binding Request
    79 40.213601 69.0.208.27 192.168.1.100 STUN Message: Binding Response
    80 40.224619 69.0.208.27 192.168.1.100 STUN Message: Binding Response
    81 40.246548 192.168.1.100 209.17.160.130 SIP/SDP Request: INVITE sip:13306012993@209.17.160.130:5060, with session description
    82 40.461603 209.17.160.130 192.168.1.100 SIP Status: 302 Moved Temporarily
    83 40.461949 192.168.1.100 209.17.160.130 SIP Request: ACK sip:13306012999@209.17.160.130:5060
     
  14. ciscotech2007

    Joined:
    Jan 27, 2009
    Messages:
    94
    Likes Received:
    0
    Maybe something is incorrectly configured somewhere. Our advice.

    note: this is not detailed process but a rough overview

    (1) make a backup of your system via 3CX backup utility
    (2) remove 3CX server
    (3) use 3CX installation checker to ensure no 'pieces' of 3CX are still on your machine
    (4) we may even recommend resintalling IIS or Cassani web servers (whichever your using)
    (5) reinstall your selected web server (iis *OR cass. NOT both)
    (6) reinstall 3CX server, verify no errors during install
    (7) after 3CX server install, auto-run 3CX inital wizard will start
    (8) for FQDN insert the IP ADDRESS of your 3CX server, which should be static IP (not DHCP)
    *you can use FQDN if your internal network has internal DNS server w/ SRV records for SIP
    (9) choose (3) digit extensions
    (10) add ONLY 2 extensions, one for your 3CX VoIP softphone and 1 of your SIP hardphones. If would be better to use (2) computers each with their own softphone but some people don't have (2) computers.
    (11) configure all IP endpoints with SIP registration information (i.e. extension, ID, password, etc.)
    (12) ensure all extensions register in your 3CX extension status page (i.e. green light)
    (13) call from your (1) internal extension to the other internal extension, should have success, if you don't there is an issue
    (14) if no success, change 3CX server logging to verbose and post the log in this forum post. Remember to go to the log right AFTER your phone call fails.
    (15) if your call completes to the other internal phone extension you have verified the 3CX system works on a basic level
    (16) register an account with a 3CX RECOMMENDED AND VERIFIED VoIP trunk provider, like Broadvox, CallCentric and more.
    (17) follow the instructions for adding a VoIP provider here:
    http://www.3cx.com/manual/3CXPhoneSystemManual7/phone-system37.html
    (18) make sure the Add VoIP provider wizard sets up an OUTBOUND rule
    (19) make an 'easy' OUTBOUND rule... select '9' to the be ID for OUTBOUND CALLS. Meaning all calls beginning with '9' are to be forwarded to your VoIP provider
    (20) make sure the OUTBOUND rule strips the first digit after dialing out.. which is your '9'
    (21) check your dialplans (if any) and 3CX server logs and CONFIRM the OUTBOUND dialed number is correct.. if you only see '234' or '23444' something it wrong in your dialplan or OUTBOUND prepend or strips
    (21) CONFIRM with your VoIP provider what digits you must dial during OUTBOUND calls.. meaning.. some voip providers REQUIRE you to dial your destination area code even while dialing local numbers. Some require you to include a country code as well. So if you have a 1-123-456-7899 number from your voip provider, you may have to dial 9+1+XXX+XXX+XXXX even on local calls to the same area code as your number provided by your voip provider, in this case, '123'.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. ciscotech2007

    Joined:
    Jan 27, 2009
    Messages:
    94
    Likes Received:
    0
    note: if taking the reinstall route, please download the latest 3CX server build and DO NOT INSTALL ANY ADDITIONAL MODULES UNTIL THE SYSTEM IS WORKING

    note: apply your 3CX license, if you have one, right when the system startup wizard finishes are your system is finished installing and configuring itself for initial use and configuration by the 3CX admin (you).

    note: CONFIRM your router has the ability for STATIC NAT MAPPING and/or use the 3CX firewall checker. but firewall checker requires disabling some 3CX services take note.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.