Error 604 when making outbound call

[thewinchester]

Ok, this has me scratching my head, and all help greatly appreciated.

Summary
Every time an outbound call is made, the call fails with an error of:
Cause: 604 Does not exist anywhere

Details
New 3CX setup, running on a Raspberry Pi, setup as a Generic VoIP Trunk with provider Westnet (their config settings). Westnet is owned by iiNet, and uses the same infrastructure, despite different domain names for the services.

Registration of the trunk is successful, and I can make calls between extensions successfully, as well as receive calls successfully.

However, whenever I go to make an outbound call and regardless of the number dialled, I get this persistent error:

Cause: 604 Does not exist anywhere

From looking at the logs, the outbound rule seems to be correctly set, and it's attempting to make the call with the right trunk, but I can't establish why the 604 error is happening, and no amount of searching has led me to a solution thusfar.

Outbound call rule configuration
Apply this rule to these calls: Calls from extension group(s), DEFAULT
Make outbound calls on:

• Route 1: Westnet, Strip Digits 0, Prepend left blank, Outbound caller ID set to public phone number for the VOiP trunk
• All routes beyond this set to BLOCK CALLS

I've not been able to find wherelse I should be looking on how to resolve this issue, so all tips and pointers in the right direction greatly appreciated.

Relevant logs

30/04/2021 23:16:49 - Leg L:3.1[Extn:10] is terminated: Cause: BYE from PBX

30/04/2021 23:16:49 - Leg L:3.2[Line:10000>>1300786068] is terminated: Cause: 604 Does not exist anywhere/INVITE from 203.59.49.10:5060

30/04/2021 23:16:49 - [CM503020]: Call(C:3): Normal call termination. Call originator: Extn:10. Reason: Not found

30/04/2021 23:16:49 - L:3.1[Extn:10] failed to reach Line:10000>>1300786068, reason Not Found

30/04/2021 23:16:49 - Call to T:Line:10000>>1300786068@[Dev:sip:[email protected]:5060] from L:3.1[Extn:10] failed, cause: Cause: 604 Does not exist anywhere/INVITE from 203.59.49.10:5060

30/04/2021 23:16:49 - [CM503003]: Call(C:3): Call to <sip:[email protected]:5060> has failed; Cause: 604 Does not exist anywhere/INVITE from 203.59.49.10:5060

30/04/2021 23:16:49 - [CM503025]: Call(C:3): Calling T:Line:10000>>1300786068@[Dev:sip:[email protected]:5060] for L:3.1[Extn:10]

30/04/2021 23:16:48 - [CM503027]: Call(C:3): From: Extn:10 ("Michael XXXXX" <sip:10@XXXXXXXXXXXX:0>) to T:Line:10000>>1300786068@[Dev:sip:[email protected]:5060]

30/04/2021 23:16:48 - [CM503004]: Call(C:3): Route 1: from L:3.1[Extn:10] to T:Line:10000>>1300786068@[Dev:sip:[email protected]:5060]

30/04/2021 23:16:48 - Line limit check: Current # of calls for line Lc:10000(@Westnet[<sip:[email protected]:5060/UDP>]) is 0; limit is 2

30/04/2021 23:16:48 - Call(C:3): Call from Extn:10 to 1300786068 matches outbound rule 'Default: Westnet'

30/04/2021 23:16:48 - [Flow] Call(C:3): has built target endpoint: Out#:>>Rule{Default: Westnet}>>1300786068 for call from L:3.1[Extn:10]

30/04/2021 23:16:48 - [Flow] Target endpoint for 1300786068 is Out#:>>Rule{Default: Westnet}>>1300786068

30/04/2021 23:16:48 - [CM503010]: Call(C:3): Making route(s) from Extn:10 to <sip:1300786068@XXXXXXXXXXXX:0/UDP>

 

[leejor]

It would appear that the 604 message is coming from your provider...so, while it may not be an incorrect outbound number, it may very well be something else, that is being sent. I would contact them, to see if they can assist in identifying the issue, rather than spending time making changes, until it works. It could be caller ID, or a trunk outbound parameter field, that requires changes.

 

[YiannisH_3CX]

I agree with @leejor on this. The logs you posted show that the call matches an outbound rule and goes out from the PBX before you receive the error from the provider.
The first suggestion would be to use a supported provider and if that is not an option you should contact your provider and ask why calls are failing. They should be able to tell you what the issue is and what is required for successful calls.