Call forwarding using a sip trunk

[Uasgher]

Hi,

We are facing an issue and help is needed.
Here is the case:
When we transfer a call to an external number it gets failed. However, the same sip trunk works outside of 3CX for the forwarding to the same number.
what could be the reason?

 

[leejor]

Have you checked the 3CX Activity Log to see if there is a problem routing the call to an outside trunk? Are you doing a blind or attended transfer? Is this an extension being transferred, or an outside line?

 

[SOFTISS]

From my own understanding, do you have a prefix in your outbound rule that is affecting this, another thing is to check if the extension is permitted to.

 

[Uasgher]

I have created a rule on inbound rules to forward all calls to an external numbers with out even ringing

 

[Uasgher]

From my own understanding, do you have a prefix in your outbound rule that is affecting this, another thing is to check if the extension is permitted to.

No prefix and yes its permitted to make and receive calls for all

 

[Uasgher]

Sip trunk provider is Telnyx. They say that the call is dropped at 3CX

 

[SOFTISS]

Then check your activity log to determine where the issue is, I use Telnyx too.

Also check the Outbound Parameters for the SIP trunk itself, but be careful with what you do there.

Take a screenshot before you start anything.

 

[Uasgher]

What needs to be done with outbound parameters?
Calls are working fine when we dial normally from the same trunk to the same number!

 

[Uasgher]

Log says:
[Flow] Target endpoint for +44******** can not be built!

 

[Uasgher]

Does anyone know what is this target endpoint?

 

[SOFTISS]

Check within here.

Can you make a direct call.

 

[Saqqara]

You need to relax your outbound rules, as 3CX will use a system account for the redirect.

I suggest create a rule with the external number as the prefix, and place it at the top of the rules

'Target endpoint for +44******** can not be built!' means 3CX cannot match an outbound rule to dial the number

 

[SOFTISS]

Try to make a direct call first and see what the result is, then you can proceed to the forward part.

 

[Uasgher]

View attachment 25665

Check within here.

Can you make a direct call.

Yes direct calls are working fine

 

[Uasgher]

You need to relax your outbound rules, as 3CX will use a system account for the redirect.

I suggest create a rule with the external number as the prefix, and place it at the top of the rules

'Target endpoint for +44******** can not be built!' means 3CX cannot match an outbound rule to dial the number

Ahan, Let me try this as well

 

[SOFTISS]

This is good but what about when the number changes or for multiple sip trunks.

You need to relax your outbound rules, as 3CX will use a system account for the redirect.

I suggest create a rule with the external number as the prefix, and place it at the top of the rules

'Target endpoint for +44******** can not be built!' means 3CX cannot match an outbound rule to dial the number

In the outbound rules, add the + sign to the prefix, it should take care of this.

 

[YiannisH_3CX]

Add another outbound rule below your existing ones that will match these calls. You can set it using a prefix like *+* as suggested or via the number length if you are forwarding calls to the same country