Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-2384

unified phone directory for a multi system directory setup



    • ToDo:
    • Asterisk Version:


      ok I'm attaching a diff of the changes I made to the agi-bin/directory file. Here was my thought process for the changes.

      You have one central system and one or more distributed satellite systems each running in a smaller office with maybe a hard line line or two for emergency services and local incoming calls. because the calls to any office should be handled in a similar way and of they are using the phone system any number they dial should be reachable. (This part is done via dial plan and IAX or DUNDi, etc). The issue is each office has only some of the recorded names for employees and how do you gather them all up on any other system so that changes to one don't destroy the other.

      So in the /etc/asterisk directory we create directories for each other server using the FQDN for it. In the /var/spool/asterisk/voicemail/ directory we do the same thing.

      Then we do a rsync from one system /etc/asterisk/voicemail.conf to remote:/etc/asterisk/FQDN/ and then rsync the same systems greet.* files and directory structure So /var/spool/asterisk/voicemail/greet.* to remote:/var/spool/asterisk/voicemail/FQDN/

      greet.wav and greet.WAV are the files that only contain a persons name NOT the greeting. it's the file that is played when you press # and have it say a name instead of spelling it.

      I was looking to create a entry in amportal.conf called ASTSERVERLIST and that will be a comma separated list of all other servers in the group that we can read in. (This part have not finished as I'm not sure where to start).

      The idea being that by using the FQDN it ties each system together in the existing directory structure (and those names would not be normally used as contexts).

        Gliffy Diagrams




              • Assignee:
                GameGamer43 Bryan Walters
                fskrotzki fskrotzki
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created:


                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.