"Call transfer failed"

[autorescue]

I am having issues with forwarding to an external number when there is no answer in a ring group.

I found this thread, and attempted each fix described in it:

https://www.3cx.com/community/threa...d-when-transferring-to-external-number.71673/

None has worked. The calls out show up in the call log, but lacking the `+1` in the outbound number as configured, though I'm not sure whether this is reflective of anything meaningful. I cannot seem to get my outbound rules to append a +1 to it despite my best efforts.

I have created an outbound rule that allows all calls with a `+,0-9` prefix to be dialed out through my AWS Chime SIP trunk; and I have made sure that the 'supports re-invites' option is disabled; however, I have had no luck. What other troubleshooting steps might I take?

 

[bitn2]

You need to fix your outbound rules... One rule is not enough. In this case you a rule that put the +1 in front of your number.

 

[autorescue]

I do have 2 rules that put a +1 in front of the number. The first is applied to members of all call groups and 10 digit numbers, and doesn't seem to apply to calls forwarded by the call group itself.

The second rule applies to the prefix "+,0-9", and also appends a +1 -- I copied this rule from a link in the previous thread. There does not seem to be a +1 applied to the forwarded calls whether I include it in the outgoing number or not.

Is my second outgoing rule incorrect?

 

[bitn2]

The outgoing rule must be not restricted to groups because the forwarding call will be transfered by a system extension.

 

[autorescue]

I've tried removing the group restriction from the first rule but the same thing happens. The outgoing call fails and shows up in the logs without a +1 whether I set the number as including a +1 or not.

 

[autorescue]

I found the solution, this is an AWS Chime-specific issue: https://www.3cx.com/community/threads/call-transfer-failed-transfer-to-external-numbers.118021/