Topic: How to avoid blind transfer on out going calls

[compsos]

On out going calls that require inputs to their menus that are flagged as complete by the "#" are triggering a local transfer and then hangup the external line.

Is disllowing  the ALLOWHASHXFER variable the right way to allow the use of the # key on outgoing calls the right way to solve the entering of data on an external call the correct method? Or should the system not apply # as a transfer on outgoing calls.

db selintra setprop global ALLOWHASHXFER enabled


TIA

[SARK devs]

Hi Gordon

here are the rules the agi applies...

On outbound, the default is to allow the caller to make a transfer
On Inbound, the default is to allow the callee to make a transfer
On Internal, the default is to allow both parties to make a transfer

These equate to dialstring parameters of T (case 1), t (case 2) and Tt (case 3).

Setting ALLOWHASHXFER=disabled modifies only case 1 (outbound). It suppresses the T option, which will do what you require.  Alternatively, if you would like to be able to send a # to a remote IVR but still be able to do an Asterisk blind transfer then you can change the blindtransfer key in features.conf to something else (we tend to use ## when this is requested).

Kind Regards

S

[compsos]

The features.conf file is currently an empty shell where the ALLOWHASHXFER is in the extensions.conf.
If we disable the ALLOWHASHXFER it will only stop the transfer of an outgoing call to another local extension? I think that would be the solution as "rarely" transfer a call made from within the system. I assume internal calls (ext --> ext) would still transfer?

[SARK devs]

Correct

Best

S