zapata.conf配置参数说明

097634e9169c6777120550ad61afb6bc-1.jpg 立即下载

Zap Channel Module ConfigurationThe Zap channel module permits Asterisk to communicate with the Zaptel device driver, used to access Zaptel telephony interface cards. You configure Asterisk's Zap channel module in the zapata.conf file.
Zap channel模块允许Asterisk与zaptel驱动程序之间通讯。通过配置zapata.conf文件实现

You will need the Zaptel kernel module device driver installed. See:


Although TDMoE is not directly related to Zapata hardware, it uses a pseudo-TDM engine, and gets configured here.

Using MySQL For Zap Channel ConfigurationIt is possible to store configuration settings for the Zap channel driver in a MySQL table, rather than editing the zapata.conf text file. You will have to compile a version of Asterisk with this support built in. See:
可以把zap channel而配置存储在mysql表中,而不是zapatap.conf中,这需要版本支持


The rest of this page assumes you are editing the zapata.conf file by hand.

Creating ChannelsThe format of the zapata.conf file is unfortunately not as simple as it could be. Most keywords do not do anything by themselves; they merely set up the parameters of any channel definitions that follow. The channel keyword actually creates the channel, using the settings specified before it. For example, you might create two channels like this:
zapata.conf文件,没有看上去那么复杂,大多数关键词自己不做什么,仅仅是定义通道参数,channel关键词才是真正的创建通道。

    signalling=fxo_ks
    language=en
    context=reception
    channel => 1

    signalling=fxo_ks
    language=fr
    context=sales
    channel => 2

This creates channel 1 with a default language code "en" and a context "reception". Channel 2 has a default language code "fr" and context "sales".

This is important, if you put something like echocancel=no before the channel definition, it will effect all channels unless you turn it on later with echocancel=yes. It progresses downward, but the definition must be above the channel=> statement.
非常重要的是,如果例如在通道前定义echocancel=no,会使影响所有通道,直到定义echocancel=yes,他会往下执行,因此,定义必须在channel=>前面进行定义

Available Settings
Signalling TypeThe signalling type to use with your interface is the only mandatory setting. You must set a signalling type before allocating a channel. If you are connecting analog telephone equipment, note that analog phone signalling can be a source of some confusion. FXS channels are signalled with FXO signalling, and vice versa. Asterisk 'talks' to internal devices as the opposite side. An FXO interface card is signalled with FXS signalling by Asterisk, and should be configured as such.
信令类型是唯一强制设置,在分配一个通道之前,必须定义信令类型。如果连接的模拟电话设备,注意模拟信令是导致混乱的来源。FXS通道采用FXO信令,反之,Asterisk通知内部设备采用相反方式。FXO接口卡采用FXS信令,同样须定义。

signalling : Sets the channel signaling type. These parameters should match the Zaptel driver configuration . The setting to use depends partly on which interface card you have. Asterisk will fail to start if a channel signaling definition is incorrect or unworkable, if the statements do not match the Zaptel driver configuration, or if the device is not present or properly configured. The correct setting to use is almost certainly one of the following four: fxs_ks, fxo_ks, pri_cpe or pri_net. This setting has no default value; you must set a value before allocating a channel. Asterisk supports the following signalling types:
signalling :设置通道信令类型,这些参数须与zaptel驱动配置匹配。设置基于采用什么样的板卡,如果通道信令设置错误,如果配置描述与zaptel驱动配置不匹配,或者如果卡不存在而配置正确,Asterisk不会工作。正确的设置通常包含下面4中信令中一种 ,fxs_ks, fxo_ks, pri_cpe or pri_net。该设置没有缺省值,必须在分配通道前设置信令值,下面是Asterisk支持的信令类型。

  • em: E & M Immediate Start
  • em_w: E & M Wink Start
  • em_e1: E & M CAS signalling for E1 lines
  • featd: Feature Group D (The fake, Adtran style, DTMF)
  • featdmf_ta: Feature Group D (The real thing, MF (domestic, US)) through a Tandem Access point
  • fgccama Feature Group C-CAMA (DP DNIS, MF ANI)
  • fgccamamf Feature Group C-CAMA MF (MF DNIS, MF ANI)
  • featdmf: Feature Group D (The real thing, MF (domestic, US))
  • featb: Feature Group B (MF (domestic, US))
  • fxs_ls: FXS (Loop Start)
  • fxs_gs: FXS (Ground Start)
  • fxs_ks: FXS (Kewl Start)
  • fxo_ls: FXO (Loop Start)
  • fxo_gs: FXO (Ground Start)
  • fxo_ks: FXO (Kewl Start)
  • pri_cpe: PRI signalling, CPE side
  • pri_net: PRI signalling, Network side (for instance, side that provides the dialtone)
  • sf: SF (Inband Tone) Signalling
  • sf_w: SF Wink
  • sf_featd: SF Feature Group D (The fake, Adtran style, DTMF)
  • sf_featdmf: SF Feature Group D (The real thing, MF (domestic, US))
  • sf_featb: SF Feature Group B (MF (domestic, US))
  • e911: E911 (MF) style signalling. Originating switch goes off-hook, far-end winks, originating sends KP-911-ST, far-end gives answer supervision, Originating-end sends KP-0-ANI-ST
  • The following are used for Radio interfaces:
  • fxs_rx: Receive audio/COR on an FXS kewlstart interface (FXO at the channel bank)
  • fxs_tx: Transmit audio/PTT on an FXS loopstart interface (FXO at the channel bank)
  • fxo_rx: Receive audio/COR on an FXO loopstart interface (FXS at the channel bank)
  • fxo_tx: Transmit audio/PTT on an FXO groundstart interface (FXS at the channel bank)
  • em_rx: Receive audio/COR on an E&M interface (1-way)
  • em_tx: Transmit audio/PTT on an E&M interface (1-way)
  • em_txrx: Receive audio/COR AND Transmit audio/PTT on an E&M interface (2-way)
  • em_rxtx: same as em_txrx (for our dyslexic friends)
  • sf_rx: Receive audio/COR on an SF interface (1-way)
  • sf_tx: Transmit audio/PTT on an SF interface (1-way)
  • sf_txrx: Receive audio/COR AND Transmit audio/PTT on an SF interface (2-way)
  • sf_rxtx: same as sf_txrx (for our dyslexic friends)

Zap Channel Module ConfigurationThe Zap channel module permits Asterisk to communicate with the Zaptel device driver, used to access Zaptel telephony interface cards. You configure Asterisk's Zap channel module in the zapata.conf file.
Zap channel模块允许Asterisk与zaptel驱动程序之间通讯。通过配置zapata.conf文件实现

You will need the Zaptel kernel module device driver installed. See:


Although TDMoE is not directly related to Zapata hardware, it uses a pseudo-TDM engine, and gets configured here.

Using MySQL For Zap Channel ConfigurationIt is possible to store configuration settings for the Zap channel driver in a MySQL table, rather than editing the zapata.conf text file. You will have to compile a version of Asterisk with this support built in. See:
可以把zap channel而配置存储在mysql表中,而不是zapatap.conf中,这需要版本支持


The rest of this page assumes you are editing the zapata.conf file by hand.

Creating ChannelsThe format of the zapata.conf file is unfortunately not as simple as it could be. Most keywords do not do anything by themselves; they merely set up the parameters of any channel definitions that follow. The channel keyword actually creates the channel, using the settings specified before it. For example, you might create two channels like this:
zapata.conf文件,没有看上去那么复杂,大多数关键词自己不做什么,仅仅是定义通道参数,channel关键词才是真正的创建通道。

    signalling=fxo_ks
    language=en
    context=reception
    channel => 1

    signalling=fxo_ks
    language=fr
    context=sales
    channel => 2

This creates channel 1 with a default language code "en" and a context "reception". Channel 2 has a default language code "fr" and context "sales".

This is important, if you put something like echocancel=no before the channel definition, it will effect all channels unless you turn it on later with echocancel=yes. It progresses downward, but the definition must be above the channel=> statement.
非常重要的是,如果例如在通道前定义echocancel=no,会使影响所有通道,直到定义echocancel=yes,他会往下执行,因此,定义必须在channel=>前面进行定义

Available Settings
Signalling TypeThe signalling type to use with your interface is the only mandatory setting. You must set a signalling type before allocating a channel. If you are connecting analog telephone equipment, note that analog phone signalling can be a source of some confusion. FXS channels are signalled with FXO signalling, and vice versa. Asterisk 'talks' to internal devices as the opposite side. An FXO interface card is signalled with FXS signalling by Asterisk, and should be configured as such.
信令类型是唯一强制设置,在分配一个通道之前,必须定义信令类型。如果连接的模拟电话设备,注意模拟信令是导致混乱的来源。FXS通道采用FXO信令,反之,Asterisk通知内部设备采用相反方式。FXO接口卡采用FXS信令,同样须定义。

signalling : Sets the channel signaling type. These parameters should match the Zaptel driver configuration . The setting to use depends partly on which interface card you have. Asterisk will fail to start if a channel signaling definition is incorrect or unworkable, if the statements do not match the Zaptel driver configuration, or if the device is not present or properly configured. The correct setting to use is almost certainly one of the following four: fxs_ks, fxo_ks, pri_cpe or pri_net. This setting has no default value; you must set a value before allocating a channel. Asterisk supports the following signalling types:
signalling :设置通道信令类型,这些参数须与zaptel驱动配置匹配。设置基于采用什么样的板卡,如果通道信令设置错误,如果配置描述与zaptel驱动配置不匹配,或者如果卡不存在而配置正确,Asterisk不会工作。正确的设置通常包含下面4中信令中一种 ,fxs_ks, fxo_ks, pri_cpe or pri_net。该设置没有缺省值,必须在分配通道前设置信令值,下面是Asterisk支持的信令类型。

  • em: E & M Immediate Start
  • em_w: E & M Wink Start
  • em_e1: E & M CAS signalling for E1 lines
  • featd: Feature Group D (The fake, Adtran style, DTMF)
  • featdmf_ta: Feature Group D (The real thing, MF (domestic, US)) through a Tandem Access point
  • fgccama Feature Group C-CAMA (DP DNIS, MF ANI)
  • fgccamamf Feature Group C-CAMA MF (MF DNIS, MF ANI)
  • featdmf: Feature Group D (The real thing, MF (domestic, US))
  • featb: Feature Group B (MF (domestic, US))
  • fxs_ls: FXS (Loop Start)
  • fxs_gs: FXS (Ground Start)
  • fxs_ks: FXS (Kewl Start)
  • fxo_ls: FXO (Loop Start)
  • fxo_gs: FXO (Ground Start)
  • fxo_ks: FXO (Kewl Start)
  • pri_cpe: PRI signalling, CPE side
  • pri_net: PRI signalling, Network side (for instance, side that provides the dialtone)
  • sf: SF (Inband Tone) Signalling
  • sf_w: SF Wink
  • sf_featd: SF Feature Group D (The fake, Adtran style, DTMF)
  • sf_featdmf: SF Feature Group D (The real thing, MF (domestic, US))
  • sf_featb: SF Feature Group B (MF (domestic, US))
  • e911: E911 (MF) style signalling. Originating switch goes off-hook, far-end winks, originating sends KP-911-ST, far-end gives answer supervision, Originating-end sends KP-0-ANI-ST
  • The following are used for Radio interfaces:
  • fxs_rx: Receive audio/COR on an FXS kewlstart interface (FXO at the channel bank)
  • fxs_tx: Transmit audio/PTT on an FXS loopstart interface (FXO at the channel bank)
  • fxo_rx: Receive audio/COR on an FXO loopstart interface (FXS at the channel bank)
  • fxo_tx: Transmit audio/PTT on an FXO groundstart interface (FXS at the channel bank)
  • em_rx: Receive audio/COR on an E&M interface (1-way)
  • em_tx: Transmit audio/PTT on an E&M interface (1-way)
  • em_txrx: Receive audio/COR AND Transmit audio/PTT on an E&M interface (2-way)
  • em_rxtx: same as em_txrx (for our dyslexic friends)
  • sf_rx: Receive audio/COR on an SF interface (1-way)
  • sf_tx: Transmit audio/PTT on an SF interface (1-way)
  • sf_txrx: Receive audio/COR AND Transmit audio/PTT on an SF interface (2-way)
  • sf_rxtx: same as sf_txrx (for our dyslexic friends)

PRI 通道存在一个空闲Extension和一个微小闲置数字,只要闲置通道是空闲的,ZAP通道模块就会尝试在该通道上进行空闲拨号,然后Asterisk就 会执行定义为idelext的Context和Extension中的命令。当通道需要进行语音呼叫时,'空闲'呼叫会断开并让多数通道有效。(当然尽管 有微小闲置呼叫正在运行)。主要的用途是创建动态的服务,当闲置通道绑定了multilnk ppp协议后,将比传统的多重映射提供更有效率的提供综合的语音/数据服务。

minunused : The minimum number of unused channels available. If there are fewer channels available, Asterisk will not attempt to bundle any channels and give them to the data connection. Takes an integer.
minunused:最小可用闲置通道的数量。如果有很少的通道可用,Asterisk不会尝试捆绑任何通道进行数据 连接。该参数需要一个整数。
minidle : The minimum number of idle channels to bundle for the data link. Asterisk will keep this number of channels open for data, rather than taking them back for voice channels when needed. Takes an integer.
minidle:最小绑定进行数据连接的通道数量,Asterisk会为数据 开启这个通道数量,而不是在需要的时候返回到语音通道的使用上。该参数需要一个整数。

idledial : The number to dial as the idle number. This is typically the number to dial a Remote Access Server (RAS). Channels being idled for data will be sent to this extension. Takes an integer that does not conflict with any other extension in the Dialplan, and has been defined as an idleext.
idledial : 空闲拨号的数量,这是用于拨叫远程访问服务器最基本的一个数字,为数据预留的闲置通道被这个分机。该参数需要一个整数,与在拨号方案中定义了idleext的分机不会产生冲突。

idleext : The extension to use as the idle extension. Takes a value in the form of exten@context. Typically, the extension would be an extension to run the ZapRAS command.
idleext:用于空闲分机的extension,以[url=]exten@context [/url]的用法使用,典型的用法是被作为分机运行ZapRAS命令。
   minunused=2
   minidle=1
   idledial=6999
   idleext=6999@idle

Analog Trunk Features (模拟中继特征)usedistinctiveringdetection : Whether or not to attempt to recognize distinctive ring styles on incoming calls. This does not require audio analyisis because rings are simple transitions of the analog line. It's merely a matter of matching the transition pattern.
usedistinctiveringdetection :是否尝试识别来电特殊铃音,这不需要音频分析,因为铃音在模拟线路上是非常简单转换,只需要匹配转换样本。缺省值:no
Default: no.
    usedistinctiveringdetection=yes

dring1 , dring2 , dring3 : If you set usedistinctiveringdetection=yes, then you may define up to three different distinctive ring styles for Asterisk to attempt to recognize. Each style is defined as a comma separated list of up to three integers. Nobody has yet documented what these numbers mean, so you're on your own when it comes to trying to figure out what numbers to use for the distinctive ring syles used by your phone company in your country. But the tip is to use the Asterisk console in verbose mode, and apparently it reports numbers describing the ring patterns it sees. These patterns may be a starting point:
dring1 , dring2 , dring3: 如 果设置了usedistinctiveringdetection=yes,就需要定义三种不同特点的铃音风格,以便于Asterisk能够尝试识别。每 种风格使用逗号分割三个整数来定义。没有文档说明三个数字的含义,因此需要自己测试鉴别在不同国家不同公司中,不同数字代表的风格。Asterisk控制 台上也会显示识别的风格数字,具体风格可能会是以下一些情况。
    dring1=96,0,0
    dring2=325,95,0
    dring3=367,0,0

dring1context , dring2context , dring3context : Along with setting up to three distinctive ring patterns with dring1, dring2 and dring3, you also set corresponding contexts for incoming calls matching those distinctive ring patterns to jump into. If an incoming call does not match any of the distinctive ring patterns defined, then of course it will enter Asterisk with the default context defined for this channel.
dring1context , dring2context , dring3context :根据三种不同的铃音风格设置不同的context进行来电跳转,如果来电没有定义的风格匹配,就会进入该通道缺省的congtext。
    dring1context=line2incoming
    dring2context=business
    dring3context=chocolate

busydetect : If enabled, Asterisk will analyze the audio coming in on the line during a call or a dial attempt to attempt to recognize busy signals. This is useful on analog trunk interfaces both to detect a busy signal when dialing out, and for detecting when the person has hung up. See also Disconnect Supervision . Be sure that you don't use this on digital interfaces like QuadBri cards and so on. Otherwise you will run in "broken calls" problems. default=no
busydetect: 忙音检测,如果开启,Asterisk会拨号尝试或通话中分析在线的音频,从而尝试识别忙音信号。这非常在模拟中继接口上外呼时检测忙音信号非常有用,可以检测何时挂机。确认不能在例如QuadBri等卡上使用该参数,否则出现中断通话的问题,缺省值:no
   busydetect=yes

busycount : This option requires busydetect=yes. You can specify how many busy tones to wait before hanging up. The default is 3, but better results can be achieved if set to 6 or even 8. The higher the number, the more time is needed to detect a disconnected channel, but the lower the probability mistaking some other sound as being a busy tone.
   busycount=5
busycount :这个选项需要busydetect=yes,可以定义等待挂机的忙音信号数量,缺省值是3,但能达到的最好效果可能是设置6或者8,数字越高,检测挂机通道所需要的时间就越长,但小的数字可能会导致把其他声音错误的识别为忙音信号。

callprogress : Asterisk can attempt to monitor the state of the call to listen for a ringing tone, busy tone, congestion tone, and sounds indicating that the line has been answered. It appears that this feature is independent of the busydetect feature; it seems that both can run in parallel, and both will independently attempt to recognize a busy tone. The callprogress feature is highly experimental and can easily detect false answers, so don't count on it being very accurate. Also, it is currently configured only for standard U.S. phone tones. Default: no.
callprogress: Asterisk 可以通过尝试监控呼叫状态来侦听振铃音,忙音,拥塞音以及线路已经应答声音特征。这个特征不受busydetect特征影响,两者可以并行处理,独自尝试 识别忙音信号。callprogress的特征是高实验证明更容易检测错误应答,所以不要指望它非常准确。因此,目前仅仅在标准美国电话铃音中配置,缺省 值:no
   callprogress = yes

pulse : The standard installation of Asterisk does not permit you to specify that a Zaptel device use pulse dialing, even though the Zaptel driver supports pulse dialing. But you can apply a patch file to enable you to specify pulse dialing with the pulse keyword. See Pulse Dialing on Zap Channels for the patch.
pulse :Asterisk标准安装中,没有允许定义Zaptel卡使用脉冲拨号,尽管Zaptel驱动支持脉冲拨号,但可以更新补丁文件,使用pulse关键字去开启脉冲拨号。
    pulse=yes


Analog Handset Features 模拟电话特征adsi : If your handset has ADSI (Analog Display Services Interface) capability, set set adsi=yes. The ADSI specification is system similar to Caller ID to pass encoded information to an analog handset. It allows the creation of interactive visual menus on a multiline display, offering access to services such as voicemail through a text interface.
adsi :如果手持设备支持ADSI(模拟显示服务接口),设置set adsi=yes,ADSI类似来电显示功能,传递编码信息到手持设备。它可以在多行显示的手持设备上创建交互式可视化菜单,通过文本接口提供类似语音邮件的访问服务。

immediate : Normally (i.e. with immediate set to 'no', the default), when you lift an FXS handset, the Zaptel driver provides you a dialtone and listens for digits that you dial, passing them on to Asterisk. Asterisk waits until the number you've dialed matches an extension, and then begins executing the first command on the matching extension. If you set immediate=yes, then Asterisk will instruct the Zaptel driver to not generate a dialtone when you lift a handset, instead passing control immediately to Asterisk. Asterisk will start executing the commands for this channel's "s" extension . This is sometimes referred to as "batphone mode". Default: no.
immediate: 通常(immediate设置为no,缺省值), 当FXS话机挂机时,Zaptel驱动会马上提供拨号音,等待拨号并传递给Asterisk。 Asterisk等到接收到extension匹配号码时,就会开始执行相应的命令,如果设置 immediate=yes,Asterisk会命令 Zaptel驱动不要在FXS挂机时产生拨号音,而是把控制权交还给Asterisk,Asterisk会开始执行这个通道的s extension。这通常应用于batphone 模式(蝙蝠电话?),缺省No
    immediate=yes

callwaiting : If enabled, Asterisk will generate "call waiting pips" when you are already in a conversation on your FXS handset when someone tries to call you. If the channel has call waiting by default, you can temporarily disable it by lifting the handset and dialing *70, whereupon you will get a dialrecall tone and may then dial the intended number. There is no corresponding way to temporarily enable call waiting for channels that have it off by default. Default: no.
callwaiting :如果开启,在通话过程中如果有来电时,Asterisk就会产生呼叫等待提示音。如果通道缺省有呼叫等待,可以临时摘机按键*70取消,这种情况下,会收到重播提示音去拨打希望拨打的号码。没有合适的方法临时开启缺省设置为关闭的通道的呼叫等待。缺省为no
    callwaiting=yes

callwaitingcallerid : Sets whether Asterisk will send Caller ID data to the handset during call waiting indication. Requires also setting callwaiting=yes. Default: no.
callwaitingcallerid :设置在呼叫等待过程中是否传送主叫号码等数据,需要设置callwaiting=yes,缺省值:no
    callwaitingcallerid=yes

threewaycalling : If enabled, you can place a call on hold by pressing a hook flash, whereupon you get a dialrecall tone and can make another call. Default: no.
threewaycalling :(三方通话)如果设置开启,可以在按保持键切换话路,让原通话处于保持状态,这时会收到重拨提示音,并开启另外一方通话。缺省值:no
    threewaycalling=yes

transfer : This option has effect only when threewaycalling=yes. If threewaycalling=yes and transfer=yes, then once you've placed a call on hold with a hook flash, you can transfer that call to another extension by dialing the extension and hanging up. Default: no.
transfer :(呼叫转接)这个选项仅当三方通话=yes时有效,当设置了三方通话和呼叫转接,一旦通过或呼叫保持按键把当前话路置于保持状态,就可以拨号呼叫另外分机,把2个话路桥接起来,然后挂机。缺省值:no
    transfer=yes

cancallforward : If enabled, you may activate "call forwarding immediate" by dialing *72 (whereupon you get a dialrecall tone) followed by the extension number you wish to forward your calls to. If someone dials your extension, the call will be redirected to the forwarding number. You may disable the call forwarding by dialing *73. Default: no.
cancallforward: 如果呼叫前转启用,可以通过拨号*72+想要转向的Extension,立刻激活呼叫前转(同时会有重拨提示音),这时如果有来话,那么呼叫会被重定向到设置的转移号码上,可以通过拨打*73取消呼叫前转。缺省值:no
    cancallforward=yes

callreturn : If enabled, you may dial *69 to have Asterisk read to you the caller ID of the last person to call. You will hear the dialrecall tone if there is no record of a last caller. Default: no.
callreturn :如果开启此设置,可以通过拨打*69让Asterisk读出最后呼入的主叫号码,如果没有记录最后呼叫主叫号码,将听到重拨提示音,缺省值:no
    callreturn=yes

callgroup : A channel may belong to zero or more callgroups. Callgroups specify who may answer this phone when it is ringing. If this channel is ringing, then any other channel whose pickupgroups include one of this channel's callgroups may answer the call by dialing *8# . This feature is supported by Zap, SIP, Skinny and MGCP channels. Group numbers can range from 0 to 31. The default value is an empty string, i.e. no groups.
callgroup :通道可以不属于或者属于多个呼叫群组。呼叫群组定 义了当电话振铃时,谁可以接听。当一个通道振铃时,其它那些pickupgroups中包含该通道 callgroups其中之一的通道可以通过按*8#来接听电话。这个特性支持在ZAP,SIP。skinny和MGCP通道类型上使用,群组数字范围为 0-31,,缺省值是空字符串,即没有组。
   group=1
   callgroup=1,2,3

pickupgroup : A channel may belong to zero or more pickupgroups. Pickupgroups specify whose phones you may answer. If another channel is ringing, and this channel's pickupgroups include one of the ringing channel's callgroups, then this channel may answer the call by dialing *8# . Group numbers can range from 0 to 31. The default value is an empty string, i.e. no groups.
pickupgroup :通道可以不属于或者属于多个摘机群组,摘机群组定义了可以应答那些电话。如果其他通道振铃,而本通道pickupgroup是振铃通道callgroups群组其中之一,那么本通道可以通过按*8#来接听振铃通道。群组范围为0-31,缺省值为空字符串,即没有群组。
   group=1

See more about Channels and Groups

If you dial *8# when there is more than one channel whose calls you are eligible to answer, then it just answers the "first ringing channel", i.e. you have no control which one you pick up.
如果同时不止一路通道振铃符合条件可以通过按键*8#接听,只能接听第一条振铃通道,即不能控制选择接听哪一条。
   pickupgroup=3,4

useincomingcalleridonzaptransfer : If you set this option (Use Incoming Caller ID On Zap Transfer) to 'yes', then when you transfer a call to another phone, the original caller's Caller ID will get forwarded on too. Default: no.
useincomingcalleridonzaptransfer :如果设置了这个选项(在ZAP通道上启用来电转接),可以转接来电到另外一个电话,外部呼叫的主叫号码同时跟随。
    useincomingcalleridonzaptransfer=yes

智能体式AI漫游指南中文版 智能体式AI漫游指南中文版、智能体式AI指南英文原版 立即下载

相关推荐

YOLO26算法星形目标识别+训练好的模型+100张数据集+pyqt可视化界面.zip

附训练好的 YOLO 权重与 PyQt 可视化检测界面,页面底部含可视化效果预览,毕设/课设开箱即用。 【数据集概况】 · 检测类别(中文):[星星(Star)] 【训练曲线与评估图】 【模型训练配置】 参数 | 值 模型 | yolo26n 训练轮数 | 100 epochs 输入尺寸 | 640x640 批次大小 | 24 优化器 | auto 初始学习率 | 0.01 训练设备 【关键指标汇总】 训练了 85 个 epoch,最终轮指标: 指标 | 数值 mAP50 | **0.9950** mAP50-95 | 0.8477 Precision | 1.0000 Recall | 0.9954 train/box_loss | 0.8235 train/cls_loss | 0.7275 val/box_loss | 0.7248 val/cls_loss | 0.9621 【训练过程分析】 85 轮训练后,我们得到了一个 mAP50 为 0.9950 的模型,这真是让人惊喜的成绩。一开始,模型的训练过程进展非常迅速,loss 在前 20 轮内从 1.5000 下降到 1.0000 附近,此后,loss 依然保持稳步下降,但速度明显放缓,特别是在第 30 轮到第 50 轮之间,loss 曲线进入了一个平台期,大约在 0.85 附近徘徊了 10 轮,直到第 60 轮左右才再度加速下降。这样的表现说明模型在前期阶段收敛良好,但到了后期,确实需要更多的训练轮次以确保模型的稳定性。 在验证集上,val_loss 保持平稳,没有出现明显的波动,这进一步证明了模型没有过拟合。然而,我们注意到在第 80 轮和第 85 轮之间,val_loss 似乎有所微弱的反弹,尽管这种波动并不显著。在训练集上,前 50 轮训... 使用场景:毕业设计、课程设计、深度学习入门、工业场景落地验证。

如何使用ZAP代理查看和修改请求

如何使用ZAP代理查看和修改请求

m0_64845603的博客 1233

国央企如何利用AI工具提升科技创新项目管理与成果转化能力?.docx

国央企如何利用AI工具提升科技创新项目管理与成果转化能力?

zapata.conf配置文件参数配置

zapata.conf配置文件说明 1.文件说明Zap channel模块允许Asterisk与zaptel驱动程序之间通讯。通过配置zapata.conf文件实现。zapata.conf文件,没有看上去那么复杂,仅仅是定义通道参数,channel关键词才是真正的创建通道。非常重要的是,如果例如在通道前定义echocancel=no,会使影响所有通道,直到定义echocancel=ye

小小的太阳 2055

融合高斯扰动与竞争学习的改进型多目标部落竞争与成员合作算法(IMOCTCM)求解DTLZ1-DTLZ7及-盘式制动器设计研究(Matlab代码实现)

内容概要:本文档名为《Plecs全桥LLC谐振变换器仿真模型.txt》,但实际内容并非聚焦于该主题,而是一份涵盖多个科研领域的Matlab/Simulink仿真资源汇总清单。文档列举了包括多目标优化算法(如IMOCTCM、MOWAA)、电力电子变换器控制(如LLC谐振变换器、DAB变换器)、电机控制(如PMSM无感控制)、状态估计(如卡尔曼滤波)、微电网调度、无人机路径规划、图像处理、信号处理等多个方向的仿真研究课题,涉及Matlab、Python、Simulink、PSCAD等多种工具和编程语言。文档末尾频繁出现“完整资源下载:公众号——荔枝科研社”及百度网盘链接,表明其核心用途是推广和分享一系列科研仿真资料,服务于学术交流与资源共享。; 适合人群:适用于电气工程、自动化、控制科学与工程、电力系统、电子信息、机械电子、计算机科学等相关领域的研究生、科研人员及工程技术人员。; 使用场景及目标:①为科研工作者提供丰富的Matlab/Simulink仿真案例参考和技术实现思路;②辅助高校师生完成课程设计、毕业设计或学术论文复现工作;③通过获取开源共享资源加速个人或团队的项目开发与算法验证进程。; 阅读建议:该文档属于资源目录性质,缺乏连贯的技术论述与逻辑结构,建议使用者根据自身研究方向筛选相关条目,结合提供的代码和模型进行学习与实践,并注意核实所下载资源的有效性、完整性以及代码运行环境的兼容性。

储能双向Buck-Boost+模型预测电流控制+电压下垂控制仿真【附参考文献】(Simulink仿真实现)

内容概要:本文档详细介绍了一套针对储能双向Buck-Boost变换器的Simulink仿真资源,融合模型预测电流控制与电压下垂控制策略,适用于微电网及分布式能源系统中的能量管理与稳定控制。仿真模型全面呈现了双向Buck-Boost电路在储能系统充放电过程中的动态行为,重点引入模型预测控制(MPC)与下垂控制相结合的先进控制算法,有效提升了系统的响应速度、稳定性与鲁棒性。文档不仅提供了完整的仿真模型结构与参数设置,还附有详实的参考文献,便于使用者深入理解控制原理并开展理论延伸研究,是电力电子、新能源系统等领域科研与教学的重要实践资料。; 适合人群:电气工程、自动化、新能源等相关专业的硕士博士研究生、科研人员以及从事电力电子变换器与微电网系统设计的工程师。; 使用场景及目标:①用于微电网中储能系统的建模与协调控制策略研究;②开展模型预测控制(MPC)与电压下垂控制在直流变换器中的联合应用仿真分析;③支撑高校电力电子课程实验、毕业设计及科研项目开发,深化对双向DC-DC变换器非线性特性和先进控制算法实现机制的理解。; 阅读建议:建议结合Simulink仿真模型与配套文档同步学习,重点关注控制器的设计逻辑、参数整定方法及系统动态响应特性,推荐对比传统PI控制与先进控制策略的仿真结果,以深入掌握不同控制方案的性能差异与优化路径。

zapata.conf配置参数说明(中英文对照)(转)

转自:http://bbs.voip88.com/thread-45-1-3.html zapata.conf配置参数说明: Zap Channel Module ConfigurationThe Zap channel module permits Asterisk to communicate with the Zaptel device driver, used to access Zaptel telephony interface cards. You configure Asterisk's

seven407的专栏 1467

基于双向Buck-Boost电路的锂电池储能充电+放电控制Simulink仿真

内容概要:本文档围绕基于双向Buck-Boost电路的锂电池储能系统展开,详细介绍了其在充电与放电过程中的Simulink仿真设计与实现方法。通过构建双向Buck-Boost电路模型,结合模型预测电流控制与电压下垂控制策略,实现了对锂电池储能系统的高效能量管理与双向功率流动控制。文档提供了完整的仿真模型架构、控制算法设计流程、系统稳定性分析及动态响应性能验证,涵盖了从主电路建模到闭环控制参数整定的关键环节,适用于储能系统中能量双向变换的科研与工程实践。; 适合人群:具备电力电子、自动控制理论及新能源系统基础知识的高校研究生、科研人员以及从事储能系统、微电网、电动汽车等领域技术研发的工程技术人员。; 使用场景及目标:①用于锂电池储能系统的教学实验与科研仿真研究;②支撑微电网、电动汽车、V2G(Vehicle-to-Grid)等应用场景中的能量双向变换与功率调度研究;③深入理解Buck-Boost电路的工作原理及其在实际系统中的先进控制策略实现机制。; 阅读建议:建议在Simulink环境中实际搭建并调试所提供的仿真模型,重点关注控制环路的设计逻辑与参数整定过程,结合文中引用的参考文献深化对系统建模、控制理论与工程应用之间关系的理解。

Zaptel配置

Configuration File /etc/zaptel.conf The zaptel.conf file is where you configure the TDM-specific interface parameters required by your Zaptel card(s). It is read by the /sbin/ztcfg program. Both /e

修己度人 3745

PSIM-三相维也纳VIENNA整流器电压电流双闭环+中点电位平衡SVPWM控制仿真

内容概要:本文档围绕基于PSIM软件实现的三相维也纳(VIENNA)整流器展开,重点研究其电压电流双闭环控制系统与中点电位平衡控制策略。该仿真模型面向高效率、高功率因数的应用场景,详细构建了维也纳整流器的主电路结构及控制架构,涵盖电压外环与电流内环的双闭环PI控制器设计,以确保系统具备优良的动态响应与稳态性能。针对三电平拓扑中存在的中点电压偏移问题,引入空间矢量脉宽调制(SVPWM)技术进行优化调控,有效抑制中点电位波动,提升输出电压质量和系统运行稳定性。文档还配套提供了Mathcad计算书、仿真模型及相关参考资料,便于读者开展参数设计、控制逻辑分析与仿真复现工作。; 适合人群:电力电子、电气工程及其自动化等相关专业的研究生、科研人员,以及从事新能源变换器、工业电源、电动汽车充电设施等领域的研发工程师和技术人员。; 使用场景及目标:①深入理解三相三电平维也纳整流器的工作原理与数学建模方法;②掌握电压电流双闭环控制系统的结构设计与PI参数整定技巧;③学习SVPWM在中点电位平衡控制中的实现机制与调制策略;④为高功率密度PFC整流器、充电桩前端电路、航空航天电源等高端电力电子装置的研发提供仿真验证平台与技术支撑。; 阅读建议:建议结合PSIM仿真环境动手实践,利用所提供的计算书和参考文献,重点剖析双闭环控制环路的动态特性与SVPWM调制逻辑,并通过改变负载条件、输入电压或系统参数等方式测试系统的鲁棒性与控制有效性,进一步深化对控制策略的理解与工程应用能力。

基于透镜天线阵列的毫米波大规模多输入多输出(MIMO)系统可靠波束空间信道估计研究(Matlab代码实现)

内容概要:本文围绕Plecs环境下全桥LLC谐振变换器的仿真模型展开研究,系统阐述了其在电力电子系统中的建模方法、控制策略及动态性能分析。文章详细介绍了LLC谐振变换器的工作原理与典型拓扑结构,基于Plecs仿真平台构建了高精度的系统模型,并对谐振参数设计、软开关实现条件、变频控制策略等关键技术进行了深入的仿真验证。研究进一步探讨了系统在不同负载与输入电压条件下的效率特性、动态响应及稳定性表现,充分展示了LLC变换器在实现高效率、高功率密度电源变换方面的显著优势和应用价值。; 适合人群:具备电力电子与电力系统基础知识,从事开关电源、新能源变换器设计、仿真与控制的研究生、工程师及科研人员。; 使用场景及目标:①作为全桥LLC谐振变换器的仿真教学与科研验证平台;②指导实际工程中LLC变换器的谐振腔参数设计与控制环路优化;③支撑高频高效AC-DC或DC-DC电源系统的开发与综合性能评估。; 阅读建议:建议读者结合Plecs软件动手实践,重点关注谐振参数设计与变频控制环路调试部分,通过对比仿真结果深入理解变换器的软开关实现机理、负载适应性及效率优化方法。

ASTERISK–E1–DAHDI–PRI的配置和调试

E1语音板卡+ pri的电信线路。 1)先在asterisk中把e1驱动配置好,配置好后一般要去掉dahdi的CRC校验,在 /etc/dahdi/system.conf 这个配置文件中去掉CRC4的校验,有几个E1模块,就去掉几个CRC4的参数。如下: 把  #span=1,1,0,ccs,hdb3,crc4   改为  #span=1,1,0,ccs,hdb3 ,然后停掉asteris

yine的专栏 5907

基于window的sftp上传工具(64位)

基于window的sftp上传工具,支持win7以上系统,支持局域网电脑之间文件传输。

常用参数配置

extensions.conf 拨号方案配置文件,下面是一个简单的拨号方案,通过此处对拨号方案有一个简单的了解。 [from-sql]-----------对应sip配置文件中的context,由此关联执行相应的拨号方案。 exten => 111,1,Answer() -----拨打111的第一步操作,进行应答摘机。 exten => 111,n,AGI(start.ph

Commander_Officer的专栏 1269

独立储能的现货电能量与调频辅助服务市场出清协调机制(Matlab代码实现)

内容概要:本文介绍了“Plecs全桥LLC谐振变换器仿真模型”这一技术资源,聚焦于全桥LLC谐振变换器在电力电子系统中的建模与仿真研究。该资源提供了基于Plecs平台的高精度仿真模型,完整呈现了变换器的主电路拓扑、谐振参数设计、软开关实现机制及变频控制策略,能够有效支持对系统效率、动态响应与稳态性能的深入分析。模型充分体现了LLC谐振变换器在实现零电压开关(ZVS)、降低开关损耗和提升能量转换效率方面的优势,适用于新能源发电、储能系统及高效率电源设计等应用场景。; 适合人群:具备电力电子、自动控制及电路理论基础知识,从事电力电子变换器设计、新能源系统开发或相关领域研究的研究生、高校教师及工程技术人员。; 使用场景及目标:①用于全桥LLC谐振变换器的工作原理教学与参数设计实践;②支撑软开关特性、变频控制策略、效率优化等关键技术的仿真验证与性能评估;③作为科研项目、课程设计或毕业设计中电力电子系统仿真的核心参考模型,促进理论与工程实践的结合。; 阅读建议:建议使用者在掌握LLC谐振变换器基本工作原理的基础上,结合相关电力电子教材与Plecs软件操作指南,通过调整谐振元件参数、负载条件及控制策略进行多工况仿真,深入理解其工作机理与优化方法,并结合实验数据对比验证仿真结果的准确性。

PSIM-串联谐振半桥LLC开关电源+PFM变频闭环控制【仿真+计算书+参考文献】

内容概要:本文档围绕“PSIM-串联谐振半桥LLC开关电源+PFM变频闭环控制”展开,系统性地提供了基于PSIM仿真平台的半桥LLC谐振变换器完整技术资料,包括主电路建模、谐振参数设计、脉冲频率调制(PFM)变频控制策略及闭环反馈系统设计。重点阐述了LLC谐振变换器在宽负载范围内的高效软开关实现机制,涵盖谐振腔参数匹配、变频控制原理、系统稳定性分析、软启动策略及动态响应优化等内容,并配套提供仿真模型、详细计算书与参考文献,全面支持理论分析与工程实践的结合。; 适合人群:面向电力电子、电气工程及其自动化等相关领域的高校研究生、科研人员及从事高频开关电源研发的工程技术人员,尤其适合具备电路拓扑基础、控制理论及仿真能力的专业人士进一步深化对LLC变换器设计与闭环调控的理解。; 使用场景及目标:①用于高校课程设计或研究生实验教学,帮助学生掌握LLC谐振变换器的工作机理与PFM控制方法;②支撑科研项目中对高效率隔离型DC-DC变换器的建模与性能验证;③指导实际工程中半桥LLC电源的参数计算、控制环路设计与系统调试。; 阅读建议:建议结合所提供的PSIM仿真文件、数学计算书与参考文献同步研习,重点关注谐振元件(Lr、Cr、Lm)的参数设计过程与PFM闭环控制逻辑的实现细节,通过调整负载与输入条件进行仿真实验,深入理解系统效率、增益特性与稳定性的内在关系。

asterisk架构

这些模块通常都是以.so为扩展名的文件,这些文件存放在Asterisk的modules子目录中(通常是/usr/lib/asterisk/modules)。在Asterisk启动时,它会加载这些文件,把它们的功能添加到系统中。Asterisk的模块中,内核部分的文件名是pbx_xxxxx.so。通道驱动模块 例如:SIP通道驱动,用于与使用SIP协...

weixin_34050389的博客 178

ddrc111111111111111111

ddrc1111111111111111111

上一篇: JAMES定制开发
下一篇: 硬盘安装ubuntu9.10备忘
MapleElf
博客等级 码龄20年 1粉丝 3原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值