3CX Not Forwarding to 0800 number correctly

[RSSS IT]

We are trying to set up a rule to forward any calls to a DID to an external 0800 number however in the logs it is showing as dialing 44800 which gets a 404 Not Found error.
I've tried to edit the rules to stop the "remove 0 and prefix with 44" rule but that doesn't work,
Internally it works when calling an internal extension, but external calls won't forward

 

[NikolasA_3CX]

Hi @RSSS IT

Note that an outbound rule should not be empty. You always need to ensure that you have populated any of the fields shown below. If you already have, when the call fails, what do you see in the event log?

 

[RSSS IT]

Hi @RSSS IT

Note that an outbound rule should not be empty. You always need to ensure that you have populated any of the fields shown below. If you already have, when the call fails, what do you see in the event log?

View attachment 51260

Call or Registration to 448000488136@(Ln.10000@Spitfire) has failed. sip:62.133.0.196:5060;lr replied: Not Found (404)

This is the output

 

[NikolasA_3CX]

Call or Registration to 448000488136@(Ln.10000@Spitfire) has failed. sip:62.133.0.196:5060;lr replied: Not Found (404)

This is the output

This error is coming from your provider, and the PBX is displaying it. In this case, you need to check with the provider why they send this error.

 

[RSSS IT]

This error is coming from your provider, and the PBX is displaying it. In this case, you need to check with the provider why they send this error.

would that provider be our telecoms provider or the sip trunk provider?

 

[NikolasA_3CX]

would that provider be our telecoms provider or the Spitfire as displayed?

It should be Spitfire, the provider you use for your Trunk.

 

[paulodagraca]

Hello,

You could try to make a new outbound rule, that 'start with prefix' 44800.
In the outbound strip 2 digits, and prefix with '0', save and then move the outbound rule to the top of the list.

This will change the number dialed 44800xxx to 0800xxx and should be dialed out fine.

Paulo

 

[bitn2]

Why so complicated? Just check your outbound rules why they put 44 in front of your number. The problem is not your provider, the outbound rules are wrong.

 

[paulodagraca]

Hi bitn2,

Good question
Going on the Basis that this will come from the DID to outbound directly (not sure how this has been setup), it seems to me that the number has been setup in some strange format already, and needed some correction before going out. So the outbound rules would be the point to do that, however that indeed is my assumption to how this has been setup.

@RSSS IT, could you inform us how the inbound DID is configured to be forwarded to the 0800 number?

Paulo

 

[leejor]

Outbound rules simply deal with the numbers sent to them. You could create a rule that strips off the 44 from any "44800" number received, then replace the 44 with a zero, or, you could correct the dialed digits at the origin.

 

[bitn2]

Outbound rules simply deal with the numbers sent to them. You could create a rule that strips off the 44 from any "44800" number received, then replace the 44 with a zero, or, you could correct the dialed digits at the origin.

Thats not necessary if the other rules are correct.