• <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>

            八葉草

            學(xué)習(xí)資料記錄

            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 八葉草 閱讀(523) 評論(0)  編輯 收藏 引用 所屬分類: asterisk

            日本久久中文字幕| 日本五月天婷久久网站| 国产精品免费福利久久| 伊人久久综合无码成人网| 996久久国产精品线观看| 999久久久免费国产精品播放| 国产精品狼人久久久久影院| 2020国产成人久久精品| 国产精品久久自在自线观看| 久久久久国色AV免费看图片| 777午夜精品久久av蜜臀 | 亚洲精品乱码久久久久久久久久久久 | 蜜臀久久99精品久久久久久小说| 国产A三级久久精品| 99久久人妻无码精品系列| 岛国搬运www久久| 精品熟女少妇AV免费久久 | 久久精品人妻一区二区三区| 人妻少妇久久中文字幕一区二区 | 亚洲精品WWW久久久久久 | 欧美亚洲国产精品久久久久| 偷偷做久久久久网站| 久久99中文字幕久久| 精品久久久久久国产| 久久97久久97精品免视看| 久久电影网2021| 99久久精品影院老鸭窝| 国产精品久久新婚兰兰| 国产精品成人久久久久久久| 久久久久亚洲Av无码专| 精品国产乱码久久久久久人妻| 久久激情亚洲精品无码?V| 久久国产精品成人片免费| 亚洲va中文字幕无码久久 | 久久久久人妻一区二区三区vr| 久久福利资源国产精品999| 久久精品国产99国产精品| 亚洲精品高清久久| 日本一区精品久久久久影院| www.久久热.com| 丁香五月综合久久激情|