Categories
Web hacking

OOMA for Business

My church had been dissatisfied by the service from its phone carrier. Multiple annoyances led the office staff to seek an alternative but the most telling was that the phone system was difficult to manage. Most troubling was that the staff could not change call forwarding from outside the office.

The Incumbent

The incumbent was providing 2 line business service using VoIP off the cable. The cable split between a carrier provided ATA and a Motorola SurfBoard cable modem feeding a Linksys WiFI router. The carrier provides a custom front end web site for managing phone service that was proving difficult to navigate and use. And we were paying about $80/month for service. The box supported two AT&T office desk sets that are somewhat clunky to use.

The Challenger

Given the office’s frustrations I began looking about for alternatives and found Ooma for Business. Ooma for Business is Ooma’s small business VOiP offering and is similar to its home offering in many ways but different in ways important to businesses. And different in some ways important to UCN.

Objective Capabilities

  • Calling for 3 staff members, Minister, Office Administrator, and religious education director.
  • Ability to call out while an inbound call was active
  • Call forwarding for 3 internal phones
  • Voice mail for 3 internal phones
  • A single inbound number.
  • Auto-attendant to free the office administrator to roam the building as needed.
  • Off-site management during weather closures
  • Off-site voice mail access during weather closures

Testing your ISP Service

Ooma for Business requires about 256 Kbps or so of bandwidth to service an active call plus the auto-attendant. You can verify an adequate Internet service using the speed test on the Ooma support pages. This test verifies through-put, latency, and latency jitter. Successful completion of this test is recommended prior to ordering.

Ooma Premisses Equipment

The Ooma premisses equipment is a trade paperback sized black box with 2 Ethernet ports and a POTS port that connects to the Ethernet. You may connect it between the gateway router and switch using the two Ethernet ports or to an inside port on the switch. If you have a robust service, the internal location is preferred. With DSL service, connection between the DSL modem and switch is preferred.

The little black box runs a tailored instance of Asterix private branch exchange software that supports internal calling, an auto-attendant, and voice mail.

In addition, the base system comes with two DECT 6.0 Linx devices. These provide a wireless connection for a regular 1 line business or home phone with caller ID support. The base configuration supports 3 internal lines, one on the PBX device and 2 using included Linx devices. Two additional Linx devices may be added with current firmware for a total of 5 extensions. Future releases of software are expected to increase this to a total of 10 local RJ-11 drops.

The system can support an additional 10 virtual extensions. A virtual extension pairs a PBX number with a POTS phone number somewhere in the US or Canada. The PBX forwards the call to the paired number. To the caller it appears as a local call. This is very similar to Google Voice forwarding a call to your mobile number to your home phone.

The Ooma PBX also has a teleconference bridge. This service requires an additional extension to be used for joining conferences.

Lines?

Ooma’s marketing is a bit confusing on how Ooma for Business works. The best way to learn is to read the support pages. You purchase 2 resource types from OOMA, phone numbers and internal destinations (extensions or virtual extensions).

A phone number is a 10 digit dialed telephone service address associated with the system.  UCN needed one of these.

An extension is an internal port that is able to make and receive calls. These come in 3 varieties.

  • The RJ-11 POTS port on the Ooma PBX
  • The RJ-11 POTS port on each Ooma Linx wireless device
  • Virtual extensions.

It seems obvious that you would pay for numbers but shouldn’t extensions be free? Why is Ooma charging for them? The Ooma PBX creates one “line” for each extension. They are 100 percent provisioned for external service access. All may be active on external calls simultaneously. Most large scale branch exchanges assume that most calls will be internal and that some fraction will be external. This is an invalid assumption in a small office context.

Virtual extensions are internal extensions that are paired with a POTS phone number, typically a home office or mobile number.

UCN needed 3 extensions and 0 virtual extensions.

Pricing

Ooma prices the business service based on numbers and extensions.

  • Numbers are $20 per month
  • Extensions are $10 per month
  • Taxes, 911, and universal service fund are $5/month per number.

UCN’s bill is about $55 per month

Auto-Attendant

The auto attendant uses a synthesized voice to deliver a greeting and directory information. It has different greetings and behavior for business hours and non-business hours.

  • During business hours, you can dial an extension
  • Outside business hours, it sends you to extension voice mail or to the common office closed voice mail queue.

This behavior is customizable and each day of the week can be a business day or a closed day. Each day of the week can have different business hours but only one period per day of business hours.

Phones

The system is bring your own device. Any RJ-11 POTS phone (desk set or cordless) may be used provided that it has an electronic ringer. The RJ-11 ports do not have the heft to power mechanical ringers or some older caller ID desk sets.

The system does not support direct pairing of DECT 6 wireless phones with the Ooma base station. Ooma uses a high definition voice codec to communicate between the base station and Linx end points. Ooma’s HD hand sets will not pair with the Ooma Business base station in current form.

Voice Mail

The system provides voice mail delivery in several ways.

  • Directly to the handset. Dialing the handset’s number takes you to its voice mail queue.
  • By E-mail. Ooma also delivers the recorded message by E-mail as an audio file attachment to an E-mail address paired with the extension. Transcription is not currently supported.
  • Voice mail can be managed from off site using a web browser.

Service Continuity

During power outages and Internet fades, Ooma HQ picks up service and will take messages in much the same way that your mobile carrier sends calls to voice mail when a mobile handset is indisposed. Ooma will read or play your recorded announcement and direct callers to voice mail.

Voice mails will be queued for delivery on site and delivered by E-mail as described above.

Reliability

UCN has experienced one service interruption associated with our router loosing its DHCP leases from our ISP. Basically, everything inside the router lost DNS access. Restarting the router and Ooma PBX corrected the problem.

Categories
Personal Computing

New Life for an Old (early 2009) Mac Mini

My beloved Oswald (named after Nick’s grand sire) was getting as slow as his deceased name sake. The internal disk was failing, boot and shutdown times were long, and the machine was getting unstable. Time for a new iMac? Being a retired moocher, the thought of parting with $2500 while totally out of pocket was a bit unsettling. What could I do with an overhaul?

The Symptoms

The machine’s symptoms were

  • Dying in its sleep. I’d find the forbidden icon up on a gray background
  • Slow to log in
  • Slow to log out
  • Programs like Aperture ran slowly
  • Machine was not CPU bound
  • Machine was not swapping
  • Disk I/O looked reasonable. Most things read, modify in memory, then write.

Initial Investigation

  1. Review syslog using Console.app. Nothing scary. No panics called, no device errors for disks mentioned.
  2. Reinstall Mavericks. This helped for a while
  3. Check /Library/LaunchAgents and /Library/LaunchDaemons. They were full of crap from 12 years of Mac OS X updates and retired software. Clean these out.
  4. Do a general clean up using Clean My Mac 2. Remove broken startup items and broken preferences. There were some.
  5. Run About This Mac and check the kernel extensions. I found some from PPC days and the OS was actually trying to load one.
  6. Check and remove all KEXT’s older than Intel only OS X, say 2009. Remove all that were PPC only.

At this point the machine was somewhat improved. At least log in and log out were moving nicely. But the machine died in its sleep a week later.

On to Hardware

Now that the system was cleaned up, was the hardware old, ailing, or failing? Time for a visit to the Genius Bar.

I took the machine and power supply to the local Genius Bar at the MacArthur Mall Apple Store. After a few minutes to review the symptoms and my corrective actions, the Genius rounded up a monitor and keyboard and began a quick inspection. Once complete, he recommended running diagnostics. The disk phase quickly found a failing Hitachi Death Star disk. Apple could only put a disk like the original back in. Apple business rules did not allow Apple to make an alteration equivalent to repair. So I elected to reinstall Mavericks at the Genius Bar and restore the disk from Time Machine upon my return home.

On the way out, I launched a few things on the Mac Pro. Blinding fast. What’s in that sucker? About this Mac found a 256 GB SSD. Ah Ha! What can I do?

Alternative Courses of Action

While Time Machine was chugging, about 8 hours for 1/4 TB to restore, I did some research.

  • How hard was it to replace a disk? Not very.
  • How hard was it to reinstall and restore? Been there, done that, got the tee shirt!
  • Could I increase the memory? Yes, from 4 GB to 8 GB if the last firmware update had been installed. It was.
  • Could I put an SSD in? Yes.
  • Whose SSD?

SSD Selection

After some reading, I concluded that Samsung and Crucial were the go-to SSD suppliers. Both made their own flash and Samsung made its own controllers. Crucial was using recent Marvel controllers that were well regarded.

Could I get the memory and SSD from the same source? Maybe. Who?

  • Amazon did not have a good memory advisor AI so I ruled them out.
  • Samsung did not have a good memory advisor so I ruled them out.
  • Tiger Direct and NewEgg? They did not have Mac savvy memory  advisors so I ruled them out.
  • Crucial has supplied memory upgrades in the past and had a good Mac memory advisor. Did they also have a good SSD? The consensus of Ars, Toms’s Hardware, and AnandTech was that Crucial’s M550 was in the hunt.

So, I ordered 8 GB of expansion memory, and a 512 GB M550 laptop form factor eSATA 3 SSD. The SSD included a 9 MM spacer that would be needed in the Mac Mini. I also ordered Crucial’s Apple tools which included a spudger and small screw drivers.

Installation

Crucial was a bit back ordered so it was 10 days waiting for parts to come. Oswald took another header so I put an OS image on my media Drobo Gen2 to limp along while waiting for parts.

Parts arrived in Tuesday’s evening UPS run so I elected wisely to do the installation Wednesday morning.

 

  1. Are you satisfied with your backup? No. Run Time Machine and be sure things are up to date. They weren’t so I kicked that off around noon on Tuesday. Note which TM volume of three had the fresh backup.
  2. TM1 was mounted read only. Why? Run  Disk Utility to repair the disk. Nothing was wrong but it was 12 hours to find that out. Better safe than sorry.
  3. Does a recovery partition boot and run? Yes, from thumb drive made using the recovery disk tool from the App store, and also the recovery partition on the external media disk.
  4. Clean up and draw file an edge on a putty knife as described at iFixit.
  5. Do a normal shutdown before breakfast on Wednesday.
  6. After breakfast do the replacement following OWC’s 2009 Mac Mini disk replacement video.

OWC advises that the replacement is easy but not so easy. As to be expected, I found out why.

  • Getting the old disk out and the new one in looks easy when you watch an experienced tech do it. In practice, there are some sticky bits
  • Getting the drive tabs into the riser socket is tricky because there are no guides for the drive body. But it can be done with patience.
  • Getting the drive carrier tab into the mother board connector is a bit tricky. It took me 3 tries.
  • Seating the ribbon cable on the disk connector is a bit tricky. It needs a good push.
  • Replacing the memory was trivial. No skinned knuckles like desk top memory transplanting produces.

Once all was back together (well, almost all, one screw went missing), I fired the machine up. No happy chord. I let the machine boot. No internal disk. Three checks to find all the stuff mentioned above. Then the lost chord was back.

System Installation

Mac OS X installation goes like this.

  1. Start from the thumb drive (Alt/Opt down while booting until the drop down box shows).
  2. Start disk utility and partition the SSD. One 64GB Win81 partition and the balance to OS X HFS+ Journaled. ESPlanner brought the camel into the tent. Frown!
  3. Connect the Time Machine Drobo and restore the system disk from Time Machine. This took 8 hours for 1/4 TB of data.
  4. When Time Machine completes, the machine restarts.
  5. Complete the setup wizard.

Other than being agonizingly slow, the whole process was without drama. Only a bit of futzing around to get connectors seated.

The Results

For $500 and a day of BS&T, I have a new machine that is quick to boot, quick to log in, and pleasant to use. Even Aperture launch and Aperture import, both painful, are reasonably quick. This without making a working Aperture library on the SSD. Aperture is quick enough that there is no need to make a working library in addition to the archival library on the Drobo. Even image correction, which was slow before, is reasonably quick. Here’s why.

  • 4GB of memory was too little although nothing appeared to be swapped. My normal workload shows about 4.5 GB of App memory so stuff that was paging is no longer paging.
  • There is about 3GB of buffer cache. Enough said.
  • The SSD eliminates seek latency and rotational latency. Apps load much more quickly because they page in without mechanical waits.

Why the slow logins?

Just what were those LaunchAgents and LaunchDaemons? Would  you believe

  • A Google daemon to enhance the user experience?
  • An Adobe daemon to find the latest screwed up version of Flash?
  • An Oracle daemon to find the latest Java vulnerabilities?

Any or all of these were ill behaved. They’re worm food now. And the machine is happy. And Google’s helper is not missed.