Do you have a bunch of old Cisco phones lying around? Do you love the sound of phones ringing up until 4am in the morning? AutoLanPhone is for you!
AutoLanPhone provides a knockoff seat picker state-of-the-art Web application that allows you to design your LAN party, placing players, walkways, and most importantly - phones.
Just clone the repository, run npm install and then npm start! You will then be able to access the Web Planner on http://localhost:3000/.
You can also set the environment variable LAN_PORT if you want to run on a port other than 3000, though... why?
The Web Planner allows you to map out your venue in a grid. It is 13x7 by default - you can change this in main.js. It also assumes your venue is set up so that people are in pairs.
There are four options: player, phone, walkway, & wall. Once you click the button for that option, you can click squares in the grid to place & unplace that specific type. You can click "reset" to exit this mode.
You can rotate a grid square left, and rotate it back to middle. Other directions are a WIP.
A player represents a person / setup at your venue. A player can have a name, which should be the name of the person sitting in that position. A player can be in the same position as a Phone.
A phone represents a phone sitting at someone's desk. Each phone should be configured with a MAC address and a phone type. The phone type defaults to a Cisco 7970.
You're able to create ships, and select a Captain & Comms Officer for each ship. The Comms Officers of each ship can communicate with eachother - the captain can communicate with their comms officers only. You can also add a fleet admiral, who can communicate with all captains (and all captains can communicate back).
When you select Artemis mode and generate the configuration, any users who are part of the game will be given a new config based on their ship.
For extensions for each ship, it's recommended to use a ring group - this way, you can swap out comms/captains for each ship without having to restart each phone.
Walls & walkways have no purpose other than for visualisation & decoration.
Once you've mapped out your venue and correctly named each player and phone, you can click the "Convert" button.
The conversion will then assign each player a partner, and then for each phone it will figure out who it belongs to. If the desk it is placed at has two people, it will show both of their names.
This data is then sent to the Express server via a POST request. The POST server then takes the template.yaml, and adds all the phones that it has successfully mapped.
Each phone will then be given an incremental extension, and an 8-digit password. Each phone will have 7 quick dial lines generated, with the furthest away phones being higher on the list than ones that are closer.
- Implement support with FreePBX API to add extensions to the server
- Include Ansible playbooks that use the generated hosts file to allow configuration of phones
- Include automation to run Ansible playbook on generation, and restart phones
- Ensure generated extension numbers never include emergency numbers, like "999"
- Automatically acquire phone MAC address from switch
- Allow resizing of planner, to allow for venues of bigger sizes
- Allow planner to define groups of people and quick dial rules, in case they have special logic for who they should be able to call (mostly for Artemis)
- Maybe some automation to allow importing seating positions?
- Save planner data in database rather than in local storage - or at least, allow exporting the planner data.