Skip to end of metadata
Go to start of metadata



Macro Implementation.


Executes a macro using the context macro- name, jumping to the s extension of that context and executing each step, then returning when the steps end.

The calling extension, context, and priority are stored in MACRO_EXTEN, MACRO_CONTEXT and MACRO_PRIORITY respectively. Arguments become ARG1, ARG2, etc in the macro context.

If you Goto out of the Macro context, the Macro will terminate and control will be returned at the location of the Goto.

If MACRO_OFFSET is set at termination, Macro will attempt to continue at priority MACRO_OFFSET + N + 1 if such a step exists, and N + 1 otherwise.



Because of the way Macro is implemented (it executes the priorities contained within it via sub-engine), and a fixed per-thread memory stack allowance, macros are limited to 7 levels of nesting (macro calling macro calling macro, etc.); It may be possible that stack-intensive applications in deeply nested macros could cause asterisk to crash earlier than this limit. It is advised that if you need to deeply nest macro calls, that you use the Gosub application (now allows arguments like a Macro) with explict Return() calls instead.



Use of the application WaitExten within a macro will not function as expected. Please use the Read application in order to read DTMF from a channel currently executing a macro.


  • name - The name of the macro
  • args
    • arg1
    • arg2

See Also

Import Version

This documentation was imported from Asterisk Version SVN-branch-1.8-r418641

  • No labels

1 Comment

  1. You can call macro from another macro, but when you do this, the args are not cleared and called macro sees the args passed to parent macro. See examples in this bug report ASTERISK-1736 - Macros do not clear argument variables when calling other macros Closed