• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            八葉草

            學習資料記錄

            Asterisk Manager Interface C++ Interpretor for Linux [轉(zhuǎn)]

            Asterisk Manager Interface C++ Interpretor for Linux (http://advancedcodingconcepts.blogspot.com/2011/02/asterisk-manager-interface-c.html

            Through the past number of months in my full-time developer position for an online company and it's sales office, we've migrated to a VOIP telephony platform based on Asterisk, Linux and our custom call centre management application.

            In order to integrate an autodialer in to the application, I had originally written a script in PHP to read from two asterisk servers (local and offshore) to post information about whether an agent is on a call or not, and also inbound calls to the call centre application.

            The PHP script took a matter of hours to set up initially, but lacked proper structure - specifically, it could not track information when we switched to call queues, and was not easily portable between asterisk versions (1.8 locally, 1.2 in offshore)

            For the past week I have worked on the design and initial coding of an app in C++ that acts as a client to both servers, interprets the messages and creates internal structures.  I'm releasing that code here for review, and to help other's save some time, as I haven't noticed any other software out there that could accomplish this elegantly.  Currently, I am calling this application AMIflex based on the flexibility it provides to manage the Asterisk AMI protocol.

            This source code and it's derivatives can not be sold, licensed or packaged with any commercial software without my explicit permission.

            Download the source code here (.tar.bz2, 6kb)

            Installation instructions:

            1. unpack the file via "tar -xvjf" command
            2. create /etc/amiflex directory, and add a "servers.conf" file in the following format
            Server: server name (for display purposes only)
            Host: ip address or host name of ami server 
            Username: AMI manager username
            Secret: AMI manager password/secret

            Optional fields:

            RetryPeriod: number of seconds to wait between connection retries - ie if asterisk is rebooted (default: 300)
            Port: port number (default 5038)

            You can insert more than one server (connections will be maintained together) by entering the first server's details, placing a second new line after the last configration line for that server, and then entering the details for the second server (and so on)

            How to make this useful
            When a server connection is established, there's a AMI::RegisterAllEvents() call after authentication.  Add in your own events, and manipulate the structures or log output

            Example:
            AMI::RegisterEventCB("Dial", &AMI::MyDialCallback)

            void AMI::MyDialCallback(MSG *msg)
            {
                if (msg->Attr("SubEvent").value=="Begin")
                    cout << msg->Attr("Channel").value + " is dialing " +msg->Attr("Dialstring").value<<endl;
            }


            Current limitations
            I have some well known limitations with this software - I'll be resolving them myself for internal use, but my next step is to integrate proprietary MySQL links in to the source code, so I made sure to release this first.  Currently my task list with my employer is too long to not take some shortcuts :)
            1. The channel list linked list is a static member of the channel class - this means that you run AMIflex with multiple servers in the configuration file, all of the channels for all servers will be parallel.  If you have two servers and each server has the same extension, then there will be one device entry created and two channels open on that device, when each extension is busy.
            2. The bridge event currently only registered the first channel's Bridge member to the second member, and vice versa - If you are monitoring channels that will be bridged to more than one other channel, this will have to be expanded to a proper many to many-style linked list.
            /Files/byc/amiflex.0.1.tar.bz2.rar

            posted on 2011-11-27 18:54 八葉草 閱讀(525) 評論(0)  編輯 收藏 引用 所屬分類: asterisk

            九九热久久免费视频| 国产精品久久久久久久午夜片 | 少妇久久久久久被弄到高潮| 蜜臀久久99精品久久久久久| 中文字幕久久精品无码| 亚洲国产成人久久综合一| 久久国产影院| 久久99国产综合精品女同| 精品久久久久久无码免费| 精品国产99久久久久久麻豆 | 久久久无码精品亚洲日韩蜜臀浪潮| 久久久无码一区二区三区| 久久久久国产亚洲AV麻豆| 99久久婷婷国产综合亚洲| 久久黄视频| 精品久久久久久国产91| 久久久久久久久久久久久久| 久久国产精品-久久精品| 一本久久a久久精品综合香蕉| 久久精品国产亚洲网站| 囯产精品久久久久久久久蜜桃| 国产精品99久久精品爆乳| 久久人人爽人人爽人人AV东京热 | 久久精品亚洲欧美日韩久久| 日韩欧美亚洲综合久久影院Ds | 久久se精品一区二区影院| 久久精品国产免费观看| 一本色道久久88加勒比—综合| 久久狠狠爱亚洲综合影院| 人人狠狠综合久久亚洲高清| 97超级碰碰碰碰久久久久| 久久青青草原综合伊人| 97久久超碰国产精品2021| 亚洲精品无码久久久久去q| 久久免费看黄a级毛片| 久久涩综合| 久久无码人妻精品一区二区三区| 国内精品久久久久久中文字幕| 亚洲国产二区三区久久| 97超级碰碰碰碰久久久久| a级毛片无码兔费真人久久|