asterisk 系统变量

 

http://www.voip-info.org/wiki/view/Asterisk+Detailed+Variable+List

Asterisk standard channel variables 


There are a number of variables that are defined or read 
by Asterisk. Here is a list of them. More information is 
available in each application's help text. All these variables 
are in UPPER CASE only. 

to diaplay all channel variable use this command 

DumpChan(<min_verbose_level>) 

Variables marked with a * are builtin functions and can't be set, 
only read in the dialplan. Writes to such variables are silently 
ignored. 

${ACCOUNTCODE} * Account code (if specified) (Deprecated; use ${CDR(accountcode)}) 
${BLINDTRANSFER} The name of the channel on the other side of a blind transfer 
${BRIDGEPEER} Bridged peer 
${CALLERANI} * Caller ANI (PRI channels) (Deprecated; use ${CALLERID(ani)}) 
${CALLERID} * Caller ID (Deprecated; use ${CALLERID(all)}) 
${CALLERIDNAME} * Caller ID Name only (Deprecated; use ${CALLERID(name)}) 
${CALLERIDNUM} * Caller ID Number only (Deprecated; use ${CALLERID(num)}) 
${CALLINGANI2} * Caller ANI2 (PRI channels) 
${CALLINGPRES} * Caller ID presentation for incoming calls (PRI channels) 
${CALLINGTNS} * Transit Network Selector (PRI channels) 
${CALLINGTON} * Caller Type of Number (PRI channels) 
${CHANNEL} * Current channel name 
${CONTEXT} * Current context 
${DATETIME} * Current date time in the format: DDMMYYYY-HH:MM:SS (Deprecated; use ${STRFTIME(${EPOCH},,%d%m%Y-%H:%M:%S)}) 
${DB_RESULT} Result value of DB_EXISTS() dial plan function 
${DNID} * Dialed Number Identifier (Deprecated; use ${CALLERID(dnid)}) 
${EPOCH} * Current unix style epoch 
${EXTEN} * Current extension 
${ENV(VAR)} Environmental variable VAR 
${GOTO_ON_BLINDXFR} Transfer to the specified context/extension/priority 
after a blind transfer (use ^ characters in place of 
| to separate context/extension/priority when setting 
this variable from the dialplan) 
${HANGUPCAUSE} * Asterisk cause of hangup (inbound/outbound) 
${HINT} * Channel hints for this extension 
${HINTNAME} * Suggested Caller*ID name for this extension 
${INVALID_EXTEN} The invalid called extension (used in the "i" extension) 
${LANGUAGE} * Current language (Deprecated; use ${LANGUAGE()}) 
${LEN(VAR)} * String length of VAR (integer) 
${PRIORITY} * Current priority in the dialplan 
${PRIREDIRECTREASON} Reason for redirect on PRI, if a call was directed 
${RDNIS} * Redirected Dial Number ID Service (Deprecated; use ${CALLERID(rdnis)}) 
${TIMESTAMP} * Current date time in the format: YYYYMMDD-HHMMSS (Deprecated; use ${STRFTIME(${EPOCH},,%Y%m%d-%H%M%S)}) 
${TRANSFER_CONTEXT} Context for transferred calls 
${FORWARD_CONTEXT} Context for forwarded calls 
${UNIQUEID} * Current call unique identifier 
${SYSTEMNAME} * value of the systemname option of asterisk.conf 

Application return values 


In Asterisk 1.2, many applications return the result in a variable 
instead of, as in Asterisk 1.0, changing the dial plan priority (+101). 
For the various status values, see each application's help text. 

${AGISTATUS} * agi() 
${AQMSTATUS} * addqueuemember() 
${AVAILSTATUS} * chanisavail() 
${CHECKGROUPSTATUS} * checkgroup() 
${CHECKMD5STATUS} * checkmd5() 
${CPLAYBACKSTATUS} * controlplayback() 
${DIALSTATUS} * dial() - see also ${HANGUPCAUSE} 
${DBGETSTATUS} * dbget() 
${ENUMSTATUS} * enumlookup() 
${HASVMSTATUS} * hasnewvoicemail() 
${LOOKUPBLSTATUS} * lookupblacklist() 
${OSPAUTHSTATUS} * ospauth() 
${OSPLOOKUPSTATUS} * osplookup() 
${OSPNEXTSTATUS} * ospnext() 
${OSPFINISHSTATUS} * ospfinish() 
${PARKEDAT} * parkandannounce() 
${PLAYBACKSTATUS} * playback() 
${PQMSTATUS} * pausequeuemember() 
${PRIVACYMGRSTATUS} * privacymanager() 
${QUEUESTATUS} * queue() 
${RQMSTATUS} * removequeuemember() 
${SENDIMAGESTATUS} * sendimage() 
${SENDTEXTSTATUS} * sendtext() 
${SENDURLSTATUS} * sendurl() 
${SYSTEMSTATUS} * system() 
${TRANSFERSTATUS} * transfer() 
${TXTCIDNAMESTATUS} * txtcidname() 
${UPQMSTATUS} * unpausequeuemember() 
${VMSTATUS} * voicmail() 
${VMBOXEXISTSSTATUS} * vmboxexists() 
${WAITSTATUS} * waitforsilence() 


Various application variables 


${CURL} * Resulting page content for curl() 
${ENUM} * Result of application EnumLookup 
${EXITCONTEXT} Context to exit to in IVR menu (app background()) 
or in the RetryDial() application 
${MONITOR} * Set to "TRUE" if the channel is/has been monitored (app monitor()) 
${MONITOR_EXEC} Application to execute after monitoring a call 
${MONITOR_EXEC_ARGS} Arguments to application 
${MONITOR_FILENAME} File for monitoring (recording) calls in queue 
${QUEUE_PRIO} Queue priority 
${QUEUE_MAX_PENALTY} Maximum member penalty allowed to answer caller 
${QUEUESTATUS} Status of the call, one of: 
(TIMEOUT | FULL | JOINEMPTY | LEAVEEMPTY | JOINUNAVAIL | LEAVEUNAVAIL) 
${RECORDED_FILE} * Recorded file in record() 
${TALK_DETECTED} * Result from talkdetect() 
${TOUCH_MONITOR} The filename base to use with Touch Monitor (auto record) 
${TOUCH_MONITOR_FORMAT} The audio format to use with Touch Monitor (auto record) 
${TOUCH_MONITOR_OUTPUT} * Recorded file from Touch Monitor (auto record) 
${TXTCIDNAME} * Result of application TXTCIDName 
${VPB_GETDTMF} chan_vpb 

The MeetMe Conference Bridge uses the following variables: 


${MEETME_RECORDINGFILE} Name of file for recording a conference with 
the "r" option 
${MEETME_RECORDINGFORMAT} Format of file to be recorded 
${MEETME_EXIT_CONTEXT} Context for exit out of meetme meeting 
${MEETME_AGI_BACKGROUND} AGI script for Meetme (zap only) 
${MEETMESECS} * Number of seconds a user participated in a MeetMe conference 

The VoiceMail() application uses the following variables: 


${VM_CATEGORY} * Sets voicemail category 
${VM_NAME} * Full name in voicemail 
${VM_MAILBOX} * Mailbox Number 
${VM_DUR} * Voicemail duration 
${VM_MSGNUM} * Number of voicemail message in mailbox 
${VM_CALLERID} * Voicemail Caller ID (Person leaving vm) 
${VM_CIDNAME} * Voicemail Caller ID Name 
${VM_CIDNUM} * Voicemail Caller ID Number 
${VM_DATE} * Voicemail Date 
${VM_MESSAGEFILE} * Path to message left by caller 

The VMAuthenticate() application uses the following variables: 


${AUTH_MAILBOX} * Authenticated mailbox 
${AUTH_CONTEXT} * Authenticated mailbox context 

DUNDiLookup() uses the following variables 


${DUNDTECH} * The Technology of the result from a call to DUNDiLookup() 
${DUNDDEST} * The Destination of the result from a call to DUNDiLookup() 

The Zaptel channel sets the following variables: 


${ANI2} * The ANI2 Code provided by the network on the incoming call. (ie, Code 29 identifies call as a Prison/Inmate Call) See also: NANPA ANI II Digits Assignments 
${CALLTYPE} * Type of call (Speech, Digital, etc) 
${CALLEDTON} * Dialplan for called number on PRI/BRI calls (17=international, 33=national, 65=local, 73=private, 0=unknown). Note: this is a misnomer, TON != dialplan. 
${CALLINGSUBADDR} * Called PRI Subaddress 
${FAXEXTEN} * The extension called before being redirected to "fax" 
${PRIREDIRECTREASON} * Reason for redirect, if a call was directed 
${SMDI_VM_TYPE} * When an call is received with an SMDI message, the 'type' 
of message 'b' or 'u' 

The SIP channel uses the following variables: 


${SIPCALLID} * SIP Call-ID: header verbatim (for logging or CDR matching) 
${SIPDOMAIN} * SIP destination domain of an inbound call (if appropriate) 
${SIPUSERAGENT} * SIP user agent 
${SIPURI} * SIP uri 
${SIP_CODEC} Set the SIP codec for a call 
${SIP_URI_OPTIONS} * additional options to add to the URI for an outgoing call 
${RTPAUDIOQOS} RTCP QoS report for the audio of this call 
${RTPVIDEOQOS} RTCP QoS report for the video of this call 

The Agent channel uses the following variables: 


${AGENTMAXLOGINTRIES} Set the maximum number of failed logins 
${AGENTUPDATECDR} Whether to update the CDR record with Agent channel data 
${AGENTGOODBYE} Sound file to use for "Good Bye" when agent logs out 
${AGENTACKCALL} Whether the agent should acknowledge the incoming call 
${AGENTAUTOLOGOFF} Auto logging off for an agent 
${AGENTWRAPUPTIME} Setting the time for wrapup between incoming calls 
${AGENTNUMBER} * Agent number (username) set at login 
${AGENTSTATUS} * Status of login ( fail | on | off ) 
${AGENTEXTEN} * Extension for logged in agent 

The Dial() application uses the following variables: 


${DIALEDPEERNAME} * Dialed peer name 
${DIALEDPEERNUMBER} * Dialed peer number 
${DIALEDTIME} * Time for the call (seconds) 
${ANSWEREDTIME} * Time from dial to answer (seconds) 
${DIALSTATUS} * Status of the call, one of: 
                (CHANUNAVAIL | CONGESTION | BUSY | NOANSWER  
| ANSWER | CANCEL | DONTCALL | TORTURE) 
${DYNAMIC_FEATURES} * The list of features (from the applicationmap section of 
features.conf) to activate during the call, with feature 
names separated by '#' characters 
${LIMIT_PLAYAUDIO_CALLER} Soundfile for call limits 
${LIMIT_PLAYAUDIO_CALLEE} Soundfile for call limits 
${LIMIT_WARNING_FILE} Soundfile for call limits 
${LIMIT_TIMEOUT_FILE} Soundfile for call limits 
${LIMIT_CONNECT_FILE} Soundfile for call limits 
${OUTBOUND_GROUP} Default groups for peer channels (as in SetGroup) 

  • See "show application dial" for more information


The chanisavail() application sets the following variables: 


${AVAILCHAN} * the name of the available channel if one was found 
${AVAILORIGCHAN} * the canonical channel name that was used to create the channel 
${AVAILSTATUS} * Status of requested channel 

When using macros in the dialplan, these variables are available 


${MACRO_EXTEN} * The calling extensions 
${MACRO_CONTEXT} * The calling context 
${MACRO_PRIORITY} * The calling priority 
${MACRO_OFFSET} Offset to add to priority at return from macro 

The ChanSpy() application uses the following variables: 


${SPYGROUP} * A ':' (colon) separated list of group names. 
(To be set on spied on channel and matched against the g(grp) option) 

If you compile with OSP support, these variables are used: 


${OSPINHANDLE} OSP handle of in_bound call 
${OSPINTIMELIMIT} Duration limit for in_bound call 
${OSPOUTHANDLE} OSP handle of out_bound call 
${OSPTECH} OSP technology 
${OSPDEST} OSP destination 
${OSPCALLING} OSP calling number 
${OSPOUTTOKEN} OSP token to use for out_bound call 
${OSPOUTTIMELIMIT} Duration limit for out_bound call 
${OSPRESULTS} Number of remained destinations 

Call File extension variables: 


${REASON} The reason why an auto-dialout call failed 




CDR Variables 



If the channel has a cdr, that cdr record has it's own set of variables which 
can be accessed just like channel variables. The following builtin variables 
are available and, unless specified, read-only. 

${CDR(clid)} Caller ID 
${CDR(src)} Source 
${CDR(dst)} Destination 
${CDR(dcontext)} Destination context 
${CDR(channel)} Channel name 
${CDR(dstchannel)} Destination channel 
${CDR(lastapp)} Last app executed 
${CDR(lastdata)} Last app's arguments 
${CDR(start)} Time the call started. 
${CDR(answer)} Time the call was answered. 
${CDR(end)} Time the call ended. 
${CDR(duration)} Duration of the call. 
${CDR(billsec)} Duration of the call once it was answered. 
${CDR(disposition)} ANSWERED, NO ANSWER, BUSY 
${CDR(amaflags)} DOCUMENTATION, BILL, IGNORE etc 
${CDR(accountcode)} The channel's account code (read-write). 
${CDR(uniqueid)} The channel's unique id. 
${CDR(userfield)} The channels uses specified field (read-write). 


In addition, you can set your own extra variables with a traditional 
Set(CDR(var)=val) to anything you want. 

NOTE Some CDR values (eg: duration & billsec) can't be accessed until the call has terminated. As of 91617, those values will be calculated on-demand if requested. Until that makes it into a stable release, you can set endbeforehexten=yes in cdr.conf, and then use the "hangup" context to wrap up your call. 

Certain functional variables may be accessed with ${foo(<args>)}. A list 
of these functional variables may be found by typing "show functions" 
at the Asterisk CLI.

Python分布式爬虫深度实战:反爬破解+数据清洗+性能优化全流程 分布式爬虫的核心是“调度中心化+执行分布式”,Scrapy-Redis是最易落地的框架,无需从零写调度逻辑;反爬破解要分级应对:基础反爬靠随机UA/限流,进阶反爬靠代理池,高级反爬靠第三方验证码API;数据清洗的关键是“批量处理+标准化”,避免内存溢出,核心字段去重和异常值过滤是必做步骤;性能优化不是单纯加节点,而是从架构(分片)、代码(批量写入)、服务器(索引/网络)三层协同优化,才能实现效率翻倍。 阅读详情

相关推荐

解决win11无法安装.net framework 3.5(包括.net2.0和3.0)错误代码:0x80070005

解决win11无法安装.net framework 3.5(包括.net2.0和3.0)错误代码:0x80070005

zeng699304的博客 2万+

Asterisk Detailed Variable List

Asterisk Detailed Variable List Asterisk standard channel variables  There are a number of variables that are defined or read by Asterisk. Here is a list of them. More information is availab...

iteye_2678的博客 218

Bochs源码分析 - 26:8259中断控制器介绍

前言 现在我们跟着《x86/x64体系探索及编程》来分析17章内容 -- 8259中断控制器。这个是涉及硬件的,很遗憾,除了大学期间使用STM32搞过一个计算器,其余就没多少硬件编程经验,我在淘宝上找了下大概是这个东东。 https://pdos.csail.mit.edu/6.828/2010/readings/hardware/8259A.pdf 上面是8259A的芯片手册,里面讲的还是挺详细的,虽然里面很多东西还是看不太懂,但是结合着《x86/...

WriteAnything_的博客 972

Asterisk 入门教程

subscriber:加入某个group,从而遵从某一个call restricionsubscriber group:可以使用1种call restriction。call restriction:将numbering plan中各项取出,各自组成成不同的呼叫限制方案numbering plan:通用,是一个整体的计划,里面包括长途,本地,等各种形式的方案------------------

张拓的博客 9883

告别Keil手动分区!用CubeMX+VS Code一键生成带Bootloader的STM32 OTA工程

本文详细介绍了如何利用STM32CubeMX和VS Code实现STM32 OTA工程的自动化构建,告别传统Keil手动分区的繁琐流程。通过图形化配置Flash分区、自动生成链接脚本以及实现Bootloader跳转逻辑,开发者可以高效完成远程升级功能开发,显著提升嵌入式开发效率。

weixin_33720956的博客 390

拆开华为BBU5900,看看5G基站的大脑里到底装了啥?

本文深度拆解华为BBU5900,揭示5G基站核心处理单元的硬件架构与设计哲学。通过详细解析模块化设计、智能电源系统和动态散热方案,展现其支撑千兆速率、毫秒级时延的技术奥秘,为5G网络部署提供实用参考。

weixin_31456563的博客 572

Asterisk的拨号计划命令

  Asterisk的拨号计划命令,翻译自http://www.voip-info.org/wiki/vi ... pplication+commands网上有个《asterisk app命令中文翻译》,版本比较老,内容更像是软件翻译的。我参考了下,并根据voip-info.org现有新版本做了些修正。由于内容很多名词比较专业,翻译的不够完整,英文实在不好的可以参考一下。Asterisk Dia...

iteye_2678的博客 624

3小时学会AI建站!无需编程,个人简历独立站开发速成指南

3小时学会AI建站!个人简历独立站开发速成指南

pei_laoshi的博客 1267

Asterisk func callerid

Asterisk func callerid   2009-11-24 15:21:05|  分类: Asterisk|字号 订阅 Synopsis:  CALLERID()  Description:  CALLERID()  The allowed values for are:  name: alphanumeric stringn

whyhonest的专栏 1410

CLion for Mac(m1)配置GCC编译器

条件:电脑已经下载过XCode 一. 下载HomeBrew homebrew是一款macos,linux下的包管理工具,我们需要使用他来下载GCC 下载方法: 1.打开终端(terminal) 2.输入 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" ps.有可能会遇到的问题 我当初下载挂了VPN,优快云上还有很多解决问题的方法,可以将错误信

supermario19的博客 7847

Autosar诊断实战系列23-NRC优先级解析

NRC分类,优先级判断逻辑及测试注意事项介绍。

initiallizer的博客 2622

asterisk 使用脚本——Dialplan 基础

引言: Dialplan 是 Asterisk 的核心。它定义了一个呼叫怎么进入以及怎么离开 Asterisk 系统。 Dialplan 是一种脚本语言,它包含着 Asterisk 响应外部触发的各种指令。不同于传统电话系统,Asterisk 的 dialplan 是可以完全由用户修改的。 Diaplan语法 Asterisk 的 dialplan 定义在名为 extensions.conf 的配置文件中。 extensions.conf 文件一般安装在 /etc/asterisk/directory 目

nb_zsy的博客 2012

详述 MIMIC 数据库26张数据表(一)

作者按照自身理解和实验要求对MIMIC-III的26张数据表进行整理归纳并进行介绍。

越努力 越幸运 7237

asterisk 系统变量,研究拨号规则的需要用到

http://www.voip-info.org/wiki/view/Asterisk+Detailed+Variable+ListAsterisk standard channel variables There are a number of variables that a

张拓的博客 1613

贝叶斯统计 [韦来生编]

贝叶斯(Bayes)统计是近几十年来迅速发展起来的数理统计的一个重要分支。贝叶斯方法与经典统计方法的主要不同之处是进行统计推断时除了利用样本信息外,还要利用参数的先验信息,因此可以提高统计推断或统计决策的效果。它在经济、金融、生物、医学、自然科学和社会科学等许多领域具有广泛的应用。贝叶斯方法的研究已渗透到了统计学的几乎所有领域。作者在给中国科学技术大学概率论与数理统计专业本科生开设的“数理统计”课程中有一章专门讲授“贝叶斯方法和统计决策理论”,近十年来也给中国科学技术大学概率统计专业研究生开设过几次“贝叶斯分析”课。本书是在对过去讲稿的内容作了适当的增减和调整的基础上完成的。  本书共分六章。第1章是绪论,介绍了贝叶斯统计的若干基本概念,同时对必要的数理统计的基础知识有重点地作了回顾。第二章介绍了确定先验分布的若干可供选择的方法。第三章介绍了几类常见统计模型参数的后验分布的主要结果和计算方法。第四章和第五章分别介绍了“贝叶斯统计推断”和“贝叶斯统计决策”的内容。第六章介绍了贝叶斯统计计算的若干方法,包括蒙特卡洛方法和马尔可夫链蒙特卡洛(MCMC)方法以及相关统计软件的简介。本书的每一章附右大量的例题和习题,书末附有常用的几个表格和部分习题解答供读者查用。  大约可在54学时内讲授本书的第1章至第六章的主要内容,教师可根据学时需要选讲本书第1章至第六章的部分内容。书中标“*”号的章节可略去不讲,留给读者作为阅读材料。第六章例题中的R代码和部分例题的数据文件等可从作者个人主页下载。  作者在编写本书的过程中参考了J.O.Berger教授的《统计决策论及贝叶斯分析》和茆诗松教授编写的《贝叶斯统计》等书中的一些内容,以及《贝叶斯分析》一书中由张伟平博士编写的有关贝叶斯统计计算的一些内容。在此表示衷心感谢。  本书编写准备过程中,中国科学技术大学统计与金融系的几个研究生帮助完成了本书部分中文的录入和排版,作者对他们的辛勤工作表示真诚的感谢。高等教育出版社为本书的出版给予了大力支持。在此一并致谢。

ET2012新版免狗免安装绿色软件

ET2012新版免狗免安祖昂绿色软件。,新界面,新视觉,

Asterisk 通道变量

Asterisk 通道变量${ACCOUNTCODE}: 用户计费帐号 sip.conf 里的 account=XXXX ${ANSWEREDTIME}: 通话时长(秒) ${BLINDTRANSFER}: 通道是否为转接类型 ${CALLERID(all)}: 主叫用户名(主叫ID) 格式 name(123454) ${CALLERID(name)}: 主叫用户名 sip.conf 里的 u

修己度人 1644

IEM模型,地表粗糙度模拟

利用微波反演土壤水分时候,利用IEM模型可以实现对随机地表的模拟

Asterisk标准通道变量

在asterisk中,定义了许多变量,或是有些变量能够被其读取。下面给出了它们的列表。在每一个application的帮助文档中,你可以获得更多的信息。所有这些变量都是大写的。 被*标记的变量是内建函数,不能在拨号方案中被设置,只能被读取。对这些变量的赋值将被忽略。 ${CDR(accountcode)}    * Account code (if specified) ${BLINDTRA

学习是为了探索这个世界的本质 2628

计算机控制技术及应用

《计算机控制技术及应用》通过总结作者的科研成果和吸收国内外的先进理论、方法和技术,以计算机控制系统的网络化、开放化、智能化和集成化发展趋势为主线索,主要介绍计算机控制系统的基本概念和计算机控制系统的典型形式,计算机控制系统的数学描述与基本分析方法,以及数字PID控制器、最少拍控制系统、达林算法、状态变量设计法等设计方法及其各种改进算法。重点突出计算机控制系统输入输出通道接口的设计方法和典型控制系统的设计案例与实现方法等。

Asterisk 变量明细列表

转自以下网址:http://www.voip-info.org/wiki/view/Asterisk+Detailed+Variable+List     Asterisk standard channel variables There are a number of variables that are defined or read by Asterisk.

语音通讯-软交换asterisk,Freeswitch 5001

Asterisk的拨号计划配置文件(extensions.conf)

这个文件是一个Asterisk的拨号计划配置文件(extensions.conf),它定义了Asterisk PBX系统的行为,包括如何处理来电和拨出电话。这个配置文件非常灵活,可以根据需要进行修改和扩展,以适应不同的业务需求。

liudong200618的博客 748

转 asterisk app命令中文翻译

常规指令 Authenticate:鉴别用户 VMAuthenticate:根据“voicemail.conf”鉴别用户 Curl:接受外接URLs的修复。支持POSTing DUNDiLookup:用DUNDi查寻号码 SendDTMF:发送独裁的DTMF数据 SendImage:发送图像档案 SendText:发送给客户正文消息 SendURL:发送给客户USL以显示 Syst...

weixin_33806300的博客 243

Asterisk之Dialplan编程一般规则

1. 变量设置 使用 Set() 来创建和修改变量: exten => 1002,1,Set(Favoriteanimal = "Tiger") exten => 1002,n,Set(Favoritenumber = 23) 使用 ${VARIABLENAME} 来读取和打印变量值. 可以在CLI界面打印变量名,通过NoOp()函数。 (verbosity level >=3 ): ex

宽简厚重—博约 6295

asterisk学习笔记5--Dialplan编程一般规则

1. 变量设置使用 Set() 来创建和修改变量:exten => 1002,1,Set(Favoriteanimal = "Tiger")exten => 1002,n,Set(Favoritenumber = 23)使用 ${VARIABLENAME} 来读取和打印变量值. 可以在CLI界面打印变量名,通过NoOp()函数。 (verbosity level >=3 ):e

oldnemo的专栏 2627

ASTERISK入门

subscriber:加入某个group,从而遵从某一个call restricion subscriber group:可以使用1种call restriction。 call restriction:将numbering plan中各项取出,各自组成成不同的呼叫限制方案 numbering plan:通用,是一个整体的计划,里面包括长途,本地,等各种形式的方案 ————————————

Commander_Officer的专栏 5813

asterisk入门

Asterisk译为星号(*)在很多应用中被用做通配符,Astrisk做为PBX系统的完美名称,原因之一是Asterisk可以连接数目庞大的接口类型,包括:   1模拟接接口,如你的电话线或模拟电话.   2数字线路,如T-1和E-1线路   3Voip协议,如SIP和IAX   目前正式版本是IAX2,但是IAX1的所有格式都已经停掉.所以当说到IAX都是特拽IAX2   使用接口配置

349

Asterisk Gateway Interface

Special extensionsAsterisk makes use of some special extensions, which we will explain now: Extension             Description       a               This extension is invoked when a user presses

Up to Me 882

Asterisk拨号方案中变量的应用

在拨号方案中使用变量可以减少打字、增加清晰度,也有助于在拨号方案中加入逻辑. 这里的变量有全局变量,通道变量和环境变量。 1.全局变量 全局变量应该在extensions.conf文件的开始利用[globals]这个context定义或利用 SetGlobalVar()应用.如: [globals] 80000=Zap/1或 [internal] exten => 123,1,SetGl

学习是为了探索这个世界的本质 1232
上一篇: features.conf配置文件参数配置
下一篇: Asterisk 中 队列的简单实现
whatsyourname
博客等级 码龄23年 13粉丝 326原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明:

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

余额充值