Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Unable to make outbound calls - error: 604

Discussion in '3CX Phone System - General' started by sean.suntelnetworks, Jan 12, 2015.

Thread Status:
Not open for further replies.
  1. sean.suntelnetworks

    Joined:
    Oct 10, 2014
    Messages:
    34
    Likes Received:
    3
    Hello everyone,

    New to 3cx, but not new to IP PBX systems. Have been deploying Yeastar asterisk style boxes for the past year with little to no problems. The company I work for has decided to make the move to 3cx for it's VIP clients.

    I love 3cx and how it seems to function right out of the box, however, I'm getting an odd error when trying to make outbound calls.

    Explanation of network:
    Broadsoft Switch in the Cloud > FIOS > Edgewater Router (which is acting as a registration SBC ) > 3CX server

    Version: 12.5
    Steps to reproduce the issue.
    At 3cx Phone (windows client) dial external number and press call.
    Receive error: Call Failed. Destination Not Found.

    Checked the Server activity logs.

    Code:
    12-Jan-2015 17:49:33.420   Leg L:9.1[Extn] is terminated: Cause: BYE from PBX
    12-Jan-2015 17:49:33.370   [CM503020]: Call(C:9): Normal call termination. Call originator: Extn:102. Reason: Not found
    12-Jan-2015 17:49:33.370   L:9.1[Extn] failed to reach Line:44922>>7273755757, reason Not Found
    12-Jan-2015 17:49:33.370   Leg L:9.2[Line:44922>>7273755757] is terminated: Cause: 604 Does not exist anywhere/INVITE from 192.168.228.1:5060
    12-Jan-2015 17:49:33.370   Call to T:Line:44922>>7273755757@[Dev:sip:SUNTELTEST3CX@192.168.228.1:5060] from L:9.1[Extn] failed, cause: Cause: 604 Does not exist anywhere/INVITE from 192.168.228.1:5060
    12-Jan-2015 17:49:33.369   [CM503003]: Call(C:9): Call to <sip:7273755757@192.168.228.1:5060> has failed; Cause: 604 Does not exist anywhere/INVITE from 192.168.228.1:5060
    12-Jan-2015 17:49:33.219   [CM503025]: Call(C:9): Calling T:Line:44922>>7273755757@[Dev:sip:SUNTELTEST3CX@192.168.228.1:5060] for L:9.1[Extn]
    12-Jan-2015 17:49:33.170   [CM503027]: Call(C:9): From: Extn:102 ("Jorge Lopez" <sip:102@192.168.228.8:5060>)  to  T:Line:44922>>7273755757@[Dev:sip:SUNTELTEST3CX@192.168.228.1:5060]
    12-Jan-2015 17:49:33.170   [CM503004]: Call(C:9): Route 1: from L:9.1[Extn] to T:Line:44922>>7273755757@[Dev:sip:SUNTELTEST3CX@192.168.228.1:5060]
    12-Jan-2015 17:49:33.170   Call(C:9): Call from Extn:102 to 7273755757 matches outbound rule 'Rule for SUNTELTEST3CX'
    12-Jan-2015 17:49:33.169   [CM503001]: Call(C:9): Incoming call from Extn:102 to <sip:7273755757@192.168.228.8:5060>
    From what I can tell, error "604 Does not exist anywhere" is saying that the 7273755757 does not exist anywhere. Does that mean on the broadsoft switch or is that specifically on the 3CX server?

    From what my googling of this error means, it's something to do with the remote party ID? I do know for this Broadsoft switch, for outbound calls, the "From User" needs to be the same as the user name for the trunk. I didn't see a place for me to set that anywhere.

    Any suggestions?
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,073
    Likes Received:
    323
    I'm going to assume that it has something to do with your outbound rules.

    A route was found that matched the dialled number

    The question is...what happened after that?

    In your outbound rule(s) you can remove any prefix digits, or add any, as required, then send the digits out on a trunk group that you had previously created. I don't see the part where the call is attempting to route out on a trunk group.

    So, we are assuming that there is a trunk group, either a VoIP provider, or a gateway, of some sort and that it shows as registered.

    Here is a link to outbound rules, and creating them. http://www.3cx.com/blog/voip-howto/outbound-rules-a-complete-example/

    Outbound rules are read from top to bottom, so the first match that is "hit", is the route taken. That is important to remember if you want to send similar numbers out on different routes.
     
  3. sean.suntelnetworks

    Joined:
    Oct 10, 2014
    Messages:
    34
    Likes Received:
    3
    Thank you for your quick reply!

    Yes, the trunk shows registered, both within 3cx and the broadsoft switch. The trunk is called SUNTELTEST3CX.

    The Outbound Rules is just this: 1. SUNTELTEST3CX 0 blank (0 digits stripped, and nothing prepended). Just sending the 10 digit number out the trunk like we've always done.
     
  4. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,530
    Likes Received:
    298
    Are you sure the provider does not require 11 digits for Domestic calls?
    Have you tried adding a 1 prepend on calls with length of 10 digits?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. sean.suntelnetworks

    Joined:
    Oct 10, 2014
    Messages:
    34
    Likes Received:
    3
    I'm 100% sure that the service does require 11 digits.
    Yes, I have tried to pre-pend a 1 to the number, same issue. Still same error. 604 does not exist.
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,073
    Likes Received:
    323
    Thing is... in the logs the only IP I see mentioned is 192.168.228.1. I don't see the call "going out" on the trunk group IP or URL.


    This all appears to be "internal".

    You may want to post your outbound rule and the datafill for your trunk group. "X" out part of any sensitive data.
     
  7. sean.suntelnetworks

    Joined:
    Oct 10, 2014
    Messages:
    34
    Likes Received:
    3
    I understand what you're saying... however, I'm unsure if you're aware of my original post where it mentioned "Edgewater Router (which is acting as a registration SBC)". See when you have a local network SBC, you register to that IP, which then forwards both VOIP traffic out to the softwsitch (Broadsoft).

    This is a common setup on Hosted and Hybrid systems. We've deployed dozens of Yeastar (the Yealink PBX counterpart) using these. We love 3cx, just need it to work with our core / common configuration.


    Per recommendation of our support partner, we're removing the Edgemarc and will be testing behind a Mikrotik to see if we get different results.
     
  8. sean.suntelnetworks

    Joined:
    Oct 10, 2014
    Messages:
    34
    Likes Received:
    3
    I'm doing some additional testing... but after disabling the Windows Firewall completely (this is a demo box), and changing the Edgemarc Router (SBC) for a Mikrotik, all is well.

    I'm going to see if I can place the 3CX server back behind the edgemarc and see if the issue persists with the Windows Firewall turned off.
     
  9. sean.suntelnetworks

    Joined:
    Oct 10, 2014
    Messages:
    34
    Likes Received:
    3
    Ok, after testing again, it looks like 3CX does not like being behind a local SBC (session boarder controller).
     
Thread Status:
Not open for further replies.