[asterisk-dev] [Code Review] PreDial - Ability to run dialplan on callee channel and caller channel right before actual Dial

kobaz reviewboard at asterisk.org
Sat Nov 5 10:22:17 CDT 2011

This is an automatically generated e-mail. To reply, visit:

(Updated Nov. 5, 2011, 10:22 a.m.)

Review request for Asterisk Developers.


Minor changes:
- Removed todo to parse gosub arguments (it's supported now)
- Updated patch to be against latest trunk (343488).
- Removed some trailing tabs/spaces


  Say SIP/abc is calling SIP/def
  You have: Dial(SIP/def)
  SIP/def-123234 is created.  But how can you tell that from dialplan?

  You can use a pickup macro: M or U options to Dial(), but you have to wait till pickup to know.
  'PreDial' new option 'b' to Dial(), will let you run dialplan on the newly created channel before it is connected to the end-device.

  New way:
  Dialplan will run on SIP/def-123234 and allow you to know right away what channel will be used, and you can set specific variables on that channel.

You can also run dialplan on the caller channel (option 'B') right before the dial, which is a great place to do a last microsecond UNLOCK to ensure good channel behavior.
Example:  LOCK(foo)
          do stuff

With this above example, say SIP/123 and SIP/234 are running this dialplan.

SIP/123 locks foo
SIP/123 unlocks foo
due to some cpu load issue, SIP/123 takes its time getting to Dial(SIP/abc) and doesn't do it right away

Meanwhile... SIP/234 zips right by, lock 'foo' is already unlocked, it grabs the lock, does its thing and it gets to Dial(SIP/abc).  SIP/123 wakes up and finally gets to the Dial().  Now you have two channels dialing SIP/abc when there was supposed to be one.

If your intention is to ensure that Dial(SIP/abc) is only done one at a time, you may have unexpected behavior lurking.

New way:
  do stuff

context unlock {
  s => {

Now, under no circumstances can this dialplan be run through and execute the Dial unless lock 'foo' is released.

Obviously this doesn't ensure that you're not calling SIP/abc more than once (you would need more dialplan logic for that), but it will allow a dialplan coder to also put the Dial in the locked section to ensure tighter control.

Diffs (updated)

  trunk/apps/app_dial.c 343488 
  trunk/include/asterisk/pbx.h 343488 
  trunk/main/pbx.c 343488 

Diff: https://reviewboard.asterisk.org/r/1229/diff


context predial {
  s => {
    NoOp(I'm Here!);

   run predial on callee channel

  runs predial on all three callee channels

   runs predial on caller channel

   runs predial on callee channel and caller channel



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20111105/45a33d41/attachment-0001.htm>

More information about the asterisk-dev mailing list