Support for in-A/T telephony configuration

[Mike Rylander]

In cases where multiple, separate telephony configurations are required (if different systems use different Asterisk servers, say) the config-file approach is insufficient. The forthcoming branch allows configuration of the telephony system from within the A/T setup via A/T parameters.

From the commit message and Reactor documentation:

    The AstCall reactor module creates a callfile for Asterisk, given a
    template describing the message and an environment defining
    necessary information for contacting the Asterisk server and scheduling
    a call with it.

    If you have only one SIP server, you can set it up like this in the
    opensrf.xml configuration file:

        <telephony>
            <!-- replace all values below when telephony server is configured -->
            <enabled>0</enabled>
            <driver>SIP</driver> <!-- SIP (default) or multi -->
            <channels> <!-- explicit list of channels used if multi -->
                                    <!-- A channel specifies technology/resource -->
                <channel>Zap/1</channel>
                <channel>Zap/2</channel>
                <channel>IAX/user:<email address hidden></channel>
            </channels>
            <host>localhost</host>
            <port>10080</port>
            <user>evergreen</user>
            <pw>evergreen</pw>
            <!--
                The overall composition of callfiles is determined by the
                relevant template, but this section can be invoked for callfile
                configs common to all outbound calls.
                callfile_lines will be inserted into ALL generated callfiles
                after the Channel line. This content mat be overridden
                (in whole) by the org unit setting callfile_lines.
                Warning: Invalid syntax may break ALL outbound calls.
            -->
            <!-- <callfile_lines>
                MaxRetries: 3
                RetryTime: 60
                WaitTime: 30
                Archive: 1
                Extension: 10
            </callfile_lines> -->
        </telephony>

    To support more than one SIP server, say, per library, you can use
    Action/Trigger parameters like these, which model the same information
    as above:

            enabled = 0
            driver = "SIP"
            channels = ["Zap/1", "Zap/2", "IAX/user:<email address hidden>"]
            host = "localhost"
            port = "10080"
            user = "evergreen"
            pw = "evergreen"
            callfile_lines = ["MaxRetries: 3", "RetryTime: 60", "WaitTime: 30", "Archive: 1", "Extension: 10"]

[Mike Rylander (mrylander)]

Here's the branch: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp1375043_AT-telephony-config

[Galen Charlton (gmc)]

Pushed to master along with some release notes. Thanks, Mike and Steve!