Asterisk Manager API Action Redirect
Action: Redirect
Synopsis: Redirect (transfer) a call
Privilege: call,all
Description: Redirect (transfer) a call.
Variables: (Names marked with * are required)
*Channel: Channel to redirect
ExtraChannel: Second call leg to transfer (optional)
*Exten: Extension to transfer to
*Context: Context to transfer to
*Priority: Priority to transfer to
ActionID: Optional Action id for message matching.
where 8600029 is the extension in the 'default' context which goes to a meetme room.
Synopsis: Redirect (transfer) a call
Privilege: call,all
Description: Redirect (transfer) a call.
Variables: (Names marked with * are required)
*Channel: Channel to redirect
ExtraChannel: Second call leg to transfer (optional)
*Exten: Extension to transfer to
*Context: Context to transfer to
*Priority: Priority to transfer to
ActionID: Optional Action id for message matching.
Example
Transferring existing 2 party call to a meetme room:Action: Redirect
Channel: Zap/73-1
ExtraChannel: SIP/199testphone-1f3c
Exten: 8600029
Context: default
Priority: 1
Channel: Zap/73-1
ExtraChannel: SIP/199testphone-1f3c
Exten: 8600029
Context: default
Priority: 1
where 8600029 is the extension in the 'default' context which goes to a meetme room.
Don't use variables
If you are tryng to use asterisk variables in redirect via manager (ex: Context: artic_feat_${featgroupid}) the input will not be parsed, so you will be redirected tu a 'null' extensions in this case.See also
- Asterisk Manager API
- Example: Redirect
- Example: Transfer
- app_bridge in bug/patch 5841 - similar to bristuff Steal
- New in Asterisk 1.4: app_ManagerRedirect: Break a bridged call and send called party to some context|exten|priority; see example here

Comments