asterisk App Dial 拨号 发起外呼

Synopsis

Attempts to establish a new outgoing connection on a channel, and then link it to the existing input channel.
尝试在通道上建立一个外呼的连接，并与现有通道桥接

Description

 Dial(type/identifier, timeout, options, URL)
 Dial(type1/identifier1[&type2/identifier2[&type3/identifier3... ] ], timeout, options, URL)
 RetryDial(announce|sleep|loops|Technology/resource[&Technology2/resource2...][|[timeout][|[options][|URL]]])

Attempts to "dial out" on all the specified channels (each specified by a type and identifier) simultaneously. The first channel that answers "wins", and all the other outgoing channels are hung up. The originating channel that triggered this Dial command is then Answered, if necessary, and the two channels are connected together ("bridged") allowing a conversation to take place between them. When the channel that triggered the Dial command hangs up, the Dial command exits.
尝试在所有定义的通道上（线路类型和可识别的号码、符号、分机等）同时发起外呼，首先应答的通道被桥接，其它外呼通道挂机。拨号命令产生的通道触发应答，如果必需，2个通道将被连接在一起（桥接），并允许2通道之间进行通话。当被拨号命令触发的通道挂机，拨号命令将退出，执行完毕。

RetryDial was added in Asterisk v1.2 together with the 'd' flag.

Parameters

• Jumping in Asterisk v1.2.14: In [general] you can set priorityjumping=yes/no. The default as of 1.2.14 is "yes". When set to "yes", the dialplan will jump to priority +101 on busy, congested, and channel unavailable. The wiki "used" to imply that the default was "no" if priorityjumping was not set. This does not appear to be the case in 1.2.14.
  跳转：可以在[general]中设置priorityjumping=yes/no，缺省设置是yes，当设置为yes时，拨号方案在遇忙、拥塞、通道不可用情况下，会跳转到n+101上执行，
• New in Asterisk 1.2.0: If you don't want to modify options on each app that used to have jumping behavior, you can set "priorityjumping=yes" in the [general] section of extensions.conf which will enforce the old behavior globally. As far as the Dial() application is concerned you can control the behavior with the 'j' option (see below).
  如果不想在常用于有跳跃行为的每个应用上修改他们的选项，可以在extensions.conf的[general]中设置 priorityping=yes，从而强制执行，直到Dial()应用连接。可以通过'j'选项来控制这种行为
• New in Asterisk v1.2.0: The Caller*ID of the outbound leg is now the extension that was called, rather than the Caller*ID of the inbound leg of the call. The "o" flag for Dial can be used to restore the original behavior if desired. Note that if you are looking for the originating callerid from the manager event, there is a new manager event "Dial" which provides the source and destination channels and callerid.
  外呼的Caller*ID,1.2版本中为被呼的分机号码，而不是呼入的主叫号码。如果需要的话，'o'选项可以用于恢复原有行为模式，如果在控制台信息上查找原始主叫，有事件"Dial"可以提供显示原始通道，目的通道和主叫号码.
  
• type specifies the