Trunk sequence and 487 Request terminated leads to fail over instead of end

FreePBX Configuration
1

Hi,

given is an outbound route with two trunks in trunk sequence. If an outgoing call to an offline mobile is processed, the provider terminates the call with 487.

FreePBX now tries the next configured trunk - which doesn’t make any sense, because the callee can’t be reachable via any other provider, too.

How can I prevent FreePBX using the fallback trunk if there is a 487?

The 487 message contains the additional header (Deutsche Telekom):

Reason: X.int;reasoncode=0x00000A03;add-info=05CC.0008.0006

or (Easybell)

Reason: SIP;cause=487;text="Request Terminated"

Thanks for any hints!
Dirk