Solved Forward calls

[UNVT-IT]

I am trying to figure out how to forward all the calls that come from the toll-free number to another number. I am in the process of porting the toll-free number out of Amazon Chime but during this process, I have to forward all incoming calls that would come into 3cx to now route to another phone system.

Where would I go to set this up with the phone number I want the calls to go to?

Any help is appreciated.
Thank you

 

[Evolute IT]

Inbound rules, forward the DID to an external number.

 

[UNVT-IT]

I added the rule. Tried making the call and it rang one time and then hung up. on the mobile phone, it says call failed.
I entered the XXX-XXX-XXXX and also tried +1XXX-XXX-XXXX.

is there something else I have to change or put in a different format?

 

[Evolute IT]

This could be the Caller ID issue. If your provider doesn't support Clip No Screening, you will need to set your trunk to send the caller ID of the trunk, and not the original caller that's getting forwarded.

 

[UNVT-IT]

This could be the Caller ID issue. If your provider doesn't support Clip No Screening, you will need to set your trunk to send the caller ID of the trunk, and not the original caller that's getting forwarded.

How would it do complete what you are indicating could be the issue?

i went to SIP Trunks > Caller ID > default Outbound Caller ID > it's blank

should there be something in that field?

 

[Evolute IT]

How would it do complete what you are indicating could be the issue?

i went to SIP Trunks > Caller ID > default Outbound Caller ID > it's blank

should there be something in that field?

Start by putting your main trunk number in that field and test it. If it's still doesn't work, you'll have to play with the parameters in the trunk.

That being said, are you getting any errors or warning in the Event Log?

 

[UNVT-IT]

ok, I copied the +1xxx-xxx-XXXX and placed it in the field. same error. call failed

in the event log,
Call or registration to (the number that is calling the toll-free number) has failed. 403 forbidden

 

[Evolute IT]

ok, I copied the +1xxx-xxx-XXXX and placed it in the field. same error. call failed

in the event log,
Call or registration to (the number that is calling the toll-free number) has failed. 403 forbidden

At that point, your provider should be able to help you finding out why you're getting a 403 Forbidden.

 

[UNVT-IT]

Amazon Chime Voice Connector is just SIP trunking, and cannot be configured for call forwarding. This is something that needs to be configured on a PBX system. this is what I got from them so it has to be on the 3cx

 

[YiannisH_3CX]

Amazon Chime Voice Connector is just SIP trunking, and cannot be configured for call forwarding. This is something that needs to be configured on a PBX system. this is what I got from them so it has to be on the 3cx

Well in that case check if the call is forwarded correctly by 3CX using either a packet capture or the activity log. Look at the call and see where the error is coming from. That should tell you what you need to adjust to get this working.
You will need to increase your logging level in the Activity log to Verbose for maximum details.

 

[UNVT-IT]

I did look in the activity log when I added the call forwarding and it gave me this
[Flow] Target endpoint for xxx.xxx.xxxx can not be built!

do you happen to know what this means?

ok, I can increase the logging level to try getting more details.

 

[YiannisH_3CX]

[Flow] Target endpoint for xxx.xxx.xxxx can not be built!

You see that error when you do not have a matching outbound rule for the call. If your outbound rules include groups of extensions or need to match specific extensions then this may explain it. Try adding a new outbound rule that is more general and see if that resolves your issue.

 

[UNVT-IT]

here are the settings for the outbound rule that I have in place
I have an outbound call rule:

calls to numbers starting with prefix: 9
calls from extension: blank
calls to numbers with a length of: blank

Make outbound calls on:
route1 amazon chime strip digits:1 prepend:+1 outbound caller id: blank

I thought I needed an inbound rule to forward the calls. do I need both now to make this work?

 

[YiannisH_3CX]

The inbound rule will decide the destination of the inbound call. For the PBX to be able to route the call outside the PBX it needs to match an outbound rule. So your rule that needs a prefix to operate will not fit the forwarding of the call. Try adding another outbound rule with calls to numbers starting with prefix: 0-9 as a test and see if that works for you. Then you can lock it down as needed.

 

[UNVT-IT]

created new outbound rule
calls to numbers starting with prefix: 0-9
calls from extension: blank
calls to numbers with a length of: blank

Make outbound calls on:
route1 amazon chime strip digits:1 prepend:+1 outbound caller id: blank

here is the error
call failed
Cause: 503 Transport failure: no transports left to try/INVITE from local

 

[YiannisH_3CX]

Ok so we are making progress. It seems that the call now is forwarded and reaches the provider and you are getting an error. Can you switch the trunk transport to UDP and try the same test again?
You can do so from the trunk settings, under the Options tab.

 

[UNVT-IT]

ok, I have the inbound and outbound rule and change to UDP. this is the error now:

Call has failed; Cause: 400 To is not valid E.164/INVITE from Public IP Adress

Also, it looks like it's striping the first digit of the forwarding number. +1xx.xxx.xxxx
dialing 9 digits instead of 10

 

[leejor]

You will need to modify the outbound rule, to send the correct digits.
How would you dial the number (the format), from the set?

Are you using exactly the same number in the forwarding number field?

 

[UNVT-IT]

if I am dialing out from my ext. I dial 9 then enter the 10 digit number

in the forward field, I just have the 10 digit number. do I need to add the 9 to it?

 

[UNVT-IT]

I went ahead and added the 9 in from of the 10 digit forwarding number and it worked. Thank you

SO then do I leave everything in place or do I need to change anything. like UDP back to TCP.