Public bug reported: If the 'g' argument is passed to Dial(), the functionality provided by the 'e' argument changes subtly (and, for us at least, breaks). If 'g' is passed to Dial(), when control is returned to the 'h' extension, it returns in a different context, e.g.:
[Feb 19 19:01:46] VERBOSE[5956] pbx.c: -- Executing [s@macro-queueexten:4] Dial("Local/1004@agents-46b9;2", "SIP/8930,50,rtge") in new stack [Feb 19 19:01:53] VERBOSE[5956] pbx.c: -- Executing [h@macro-queueexten:1] NoOp("SIP/8930-0005cea7", "") in new stack This new context, naturally, has none of the variables of the original context which breaks what we're trying to do in the 'h' extension. If I remove the 'g' argument, 'h' is invoked in the original context as expected. We're running asterisk 1:1.8.10.1~dfsg-1ubuntu1 on Ubuntu 12.04.2. This appears to be a regression from Asterisk 1.4, FWIW. ** Affects: asterisk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to asterisk in Ubuntu. https://bugs.launchpad.net/bugs/1130467 Title: 'g' argument in combination with 'e' causes Dial() to return to 'h' extension in a different context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1130467/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs