No ${BLINDTRANSFER} set

Reply to No ${BLINDTRANSFER} set on Wed, 23 Oct 2013 06:20:49 GMT

dgoersch — Wed, 23 Oct 2013 06:20:49 GMT

Hi Nicolás,

that sounds good, so I wait for the next beta
Is there a mailinglist or the like where you announce new beta/version?

Kind Regards
Dominique Görsch

Reply to No ${BLINDTRANSFER} set on Tue, 22 Oct 2013 22:33:52 GMT

nicolas — Tue, 22 Oct 2013 22:33:52 GMT

It is not possible to change the order right now, but I might add the feature/option on the next version, so you can return pre and post ami commands somehow.

Reply to No ${BLINDTRANSFER} set on Tue, 22 Oct 2013 08:15:08 GMT

dgoersch — Tue, 22 Oct 2013 08:15:08 GMT

Hi,

thanks for your fast reply, but it still don't work. I guess, the problem is that the var is set after the redirect command. The redirect is done and the new channel is allready fired up (and my GotoIf to decide whether it is an transfer or not is done) 'till the AMI answers with Success on the Variable Set.

It is possible, to change the order? So that I can set the var before the Redirect-Command?

10.0.1.219:2916      <= 

127.0.0.1            -> Action: Redirect
127.0.0.1            -> Channel: SIP/ys2mAmt1-00030f5c
127.0.0.1            -> Exten: 488
127.0.0.1            -> Context: from-internal
127.0.0.1            -> Priority: 1
127.0.0.1            -> Async: True

127.0.0.1            -> Action: Setvar
127.0.0.1            -> Channel: SIP/ys2mAmt1-00030f5c
127.0.0.1            -> Variable: _BLINDTRANSFER
127.0.0.1            -> Value: SIP/4901-00030f5d

127.0.0.1            <- Response: Success
127.0.0.1            <- Message: Redirect successful

127.0.0.1            <- Event: Unlink
127.0.0.1            <- Privilege: call,all
127.0.0.1            <- Channel1: SIP/ys2mAmt1-00030f5c
127.0.0.1            <- Channel2: SIP/4901-00030f5d
127.0.0.1            <- Uniqueid1: 1382428822.208932
127.0.0.1            <- Uniqueid2: 1382428822.208933
127.0.0.1            <- CallerID1: 00216685828000104
127.0.0.1            <- CallerID2: 490

127.0.0.1            <- Event: Hangup
127.0.0.1            <- Privilege: call,all
127.0.0.1            <- Channel: SIP/4901-00030f5d
127.0.0.1            <- Uniqueid: 1382428822.208933
127.0.0.1            <- CallerIDNum: 490
127.0.0.1            <- CallerIDName: Goersch Dominique
127.0.0.1            <- ConnectedLineNum: 00216685828000104
127.0.0.1            <- ConnectedLineName: 
127.0.0.1            <- Cause: 16
127.0.0.1            <- Cause-txt: Normal Clearing

127.0.0.1            <- Response: Success
127.0.0.1            <- Message: Variable Set

Kind regards
Dominique Görsch

Reply to No ${BLINDTRANSFER} set on Mon, 21 Oct 2013 13:04:38 GMT

nicolas — Mon, 21 Oct 2013 13:04:38 GMT

Prefix the variable name with an underscore so it is inherited. You can use double underscore to inherit it further.

Variable: _BLINDTRANSFER

Best regards,

Reply to No ${BLINDTRANSFER} set on Mon, 21 Oct 2013 06:52:47 GMT

dgoersch — Mon, 21 Oct 2013 06:52:47 GMT

Thanks for your reply, but it don't work.

10.0.1.219:4319      <= 

127.0.0.1            -> Action: Redirect
127.0.0.1            -> Channel: SIP/ys2mAmt1-0003030c
127.0.0.1            -> Exten: 488
127.0.0.1            -> Context: from-internal
127.0.0.1            -> Priority: 1
127.0.0.1            -> Async: True

127.0.0.1            -> Action: Setvar
127.0.0.1            -> Channel: SIP/ys2mAmt1-0003030c
127.0.0.1            -> Variable: BLINDTRANSFER
127.0.0.1            -> Value: SIP/4901-0003030d

The variable will be set after the redirect is initiated on the Channel that is redirecting. But I need the var set on the new call, to see that this call is an redirected call.
If I redirect with the phone, asterisk fires up the new channel with this variable set. If I redirect via FOP/AMI that var is not set. Do you have any idea, how to fire up the new channel with this var set?

Kind regards
Dominique Görsch

Reply to No ${BLINDTRANSFER} set on Wed, 16 Oct 2013 13:37:11 GMT

nicolas — Wed, 16 Oct 2013 13:37:11 GMT

The way to extend FOP2 is via FOP2Callbacks.pm, you will have to intercept the redirect/transfer commands received from flash and act upon it on the callsbacks file (like setting the variable via AMI). In FOP 2.27, the blind transfer button sends the blindxfer command, so you can insert that into the flashCommand if/else block. You will have to modify the bellow code to your environment, the channel and value depends on your dialplan/configuration, so they might be wrong, look at the print output to see the data you receive that you can use to set them correctly:

    } elsif($command eq "blindxfer") {

         my $cont=0;
         foreach my $param (@parameters) {
             print "Parameter $cont = $param\n";
             $cont++;
         }

        // look at the above to see what parameter to use for your purpose

        $channel = $parameters[2];
        $value     = $parameters[3];

        $return  = "Action: Setvar\r\n";
        $return .= "Channel: $channel\r\n";
        $return .= "Variable: BLINDTRANSFER\r\n";
        $return .= "Value: $value\n";
        $return .= "\r\n";
        push @allreturn, $return;
        return @allreturn;

Best regards,