The phone system in the Toronto office currently doesn't have any configuration utility. In order to take advantage of new remote-office management features in the latest PBXManager and reduce the complexity of managing phones in Toronto, we will be installing the same Asterisk configuration utility here that we currently use in the rest of our offices. This basically amounts to a ground-up reinstall from scratch of the entire phone system in Toronto, so downtime is expected to be 4 to 6 hours.

My to-do list for this upgrade: Toronto isn't currently running Thirdlane, it's a bare Asterisk on the metal with hand-crafted configs, meant to operate as a proxy/satellite to the Mountain View installation, and requires manual config changes any time we add/change extensions. With this update, Toronto will be becoming a full remote office just like Denmark and Beijing, and Sean will be able to directly set up extensions there. :) 1. Take a complete backup of /etc/asterisk. Keep it online somewhere, as it'll need to be referred to repeatedly during the remainder of the ugprade. 2. Remove existing /etc/asterisk directory, use "make samples" from the Asterisk build directory to regenerate it with the samples that distribute with asterisk (Thirdlane starts from those to install its stuff) 3. Install Webmin 4. Set up Apache to reverse-proxy into Webmin from port 443 5. Install the PBXManager module into Webmin 6. Update auto-provisioning templates to match our Polycom configuration options 7. Manually re-create all of the extensions (there's only 20 or so) 8. Migrate all voicemail content for Canadian extensions from ringring to caadm01. 9. Remove all of the Canadian extensions from Mountain View. 10. Update routing data in Mountain View to route those extensions to Toronto directly. 11. Migrate softphones which are tied to Canadian extensions to caadm01. 12. Open ports 5060 (SIP), 4569 (IAX), and 10000-19999 (RTP) to caadm01 from the Internet on the firewall so softphones can connect. 13. Install greetings and phone tree from Mountain View onto Toronto's server. 14. Migrate the IAX login for the Toronto phone number to Toronto's server, so that number goes directly to them instead of Mountain View.

Steps 1 through 7 are done. Had some issues with the provisioning that took me a few hours to solve (turned out to be the provisioning system was telling the phones to connect to localhost when they registered!). I'm very tired and need to sleep. I did manage to get the routing set up so that everything behaves *almost* like it did before... calls between phones in Toronto will be delivered locally, just about anything else gets sent to Mountain View. Calls to Toronto phones routed via Mountain View, if not answered, might go into the voicemail in Mountain View or might go into the voicemail in Toronto, all depends on the timing (which end gives up first). Calls placed between phones in Toronto, if unanswered, will go into the voicemail in Toronto. You should properly get email from both. Dialing your own phone number will get the Toronto voicemail, dialing 90 will get the Mountain View voicemail. I'll merge anything in those boxes tomorrow when I'm awake enough to do so. If anyone runs into any problems with anything, feel free to page me or call me (my cell number is in Phonebook). With the exception of the voicemail kludge, everything should be working like it did before. Extension 512 (the common area conference phone I believe) never showed up in the registry - it probably needs to be rebooted.

(In reply to comment #2) > Extension 512 (the common area conference phone I believe) never showed up in > the registry - it probably needs to be rebooted. Rebooting now...

8, 9, and 10 are now done. Also migrated over from MV are the find me/follow me settings from the two people that were using it, and all passwords and config options for voicemail. 90 from a toronto phone will now dial the toronto voicemail system.

Personal conference rooms are in place for Toronto extensions. Softphones have been migrated. Phone tree is in place. Inbound Toronto phone number now connects to Toronto instead of Mountain View, and that line is used as a fallback for outbound if Mountain View can't be reached to get to our cheap provider we use there. And that wraps up this bug.