Archive for May, 2008

Creating a FreePBX module

miken32 writes:

The process of creating a module for FreePBX is, in theory, documented in a number of wiki pages, but these are worse than nothing. Full of outdated information — some of it labeled as such, some of it not — as well as broken links and vague promises of information “to be determined,” this collection of pages does more harm than good. Here, then, are some pointers to get a module working, presented as a list of files you need to have in your module’s directory.

Read the rest of the article here.

Although this article is pretty short, at least he’s making some effort to document how to create a module, which is more than the current FreePBX team ever did. In the past they have reminded me just a bit of the type of person who occasionally complains that no one ever offers to help, but then if someone does try to help they just can’t seem to meet the other person’s high standards. And the first person will never tell you exactly how things are supposed to be done. They’re the type who will say, “Nevermind, I’ll just do it myself, it’s easier for me to do it that to explain how.” Which is fine until you want something done that they have no real interest in accomplishing.

To me, that’s always been the problem with FreePBX – it’s a fabulous piece of software until you want to get it to do some little thing that it doesn’t currently do. Then, because of the way it’s designed, it’s nearly impossible to slip your modification (which might only entail adding two or three lines of code to a dialplan) in where it’s needed, because many of the configuration files get overwritten any time you make any change using the FreePBX web-based interface. Their preferred method for adding new features is to add a module – which again is fine, except that a) hardly anyone can figure out how (except the development team), and b) they only want modules written in PHP – too bad if you are an expert in some other language, and c) even if you overcome those hurdles, there are no guarantee that your module will be accepted, since it will probably violate some as-yet-unwritten design considerations (though you are free to distribute it as an unsupported module).

Anyway, at least miken32 has made some effort to document what he has learned so far, and I hope he’ll continue to document what he learns about FreePBX module creation. I would suggest that he add his information to the FreePBX Wiki, but that’s something else that’s difficult to use (compared to most wikis).

Leave a Comment

I can’t believe they still use these…

These are actual photos, taken yesterday, of equipment presumably still in use to provide something that is probably called telephone service (though whether it lives up to the definition of that term is open to serious debate – see my additional comments after the photos):

Station Carrier System equipment

Station Carrier System equipment

Station Carrier System equipment

Back in the early 1990’s I had the misfortune of receiving something that was billed as if it were real telephone service, but that actually delivered something that in my opinion was only a bit better than tin cans and string (and seemed as though it went out after nearly every lightning strike within a radius of a mile or two) using this same type of equipment. If I recall correctly, it actually provided about 15 volts on-hook (should be closer to 48 volts) and therefore many types of phone equipment (answering machines, fax machines, etc.) would only work marginally, or not at all. I can’t believe that in the year 2008 any self-respecting phone company would still be using this equipment, seeing as how the phone company repair techs that replaced those boxes (after the aforementioned lightning strikes) told me the equipment was already obsolete way back then.

The location where I photographed this was relatively close to an exchange boundary in a somewhat rural area, so it’s about where I’d expect to see such equipment still in use if I expected to see it anywhere, but still, you’d think that by now they’d have run some additional copper pairs down the road. Of course, I suppose it’s also possible that the people formerly served by this equipment gave up any hope of getting decent wireline service long ago, and either got cell phones or perhaps (more recently) got phone service from Charter Communications, which also has cable down this road. But my real suspicion is that older people may live in these homes, and they are so used to whatever grade of service they are getting from this equipment that they don’t even realize (or care) that there are better alternatives available. For all I know, they may still be using antique black rotary dial phones!

Still, if I were the phone company I’d be ashamed to have this junk hanging on my poles (and “junk” is my opinion of it, given the horrible excuse for phone service I got when we were on this stuff). It’s no wonder that people are giving up their landlines, if any phone company still considers this adequate service.

Leave a Comment

Maybe this is why phone bills are so high…

AT&T plastic bag

Puzzle question: What company would pay good money for DHL 2-day shipping to send a customer an unsolicited plastic bag? Might we assume that a certain large phone company would be capable of this? Of course we might!

Excerpt from AT&T: Your plastic bag. Delivered.:

Yes, it was an unsolicited, rush delivery, plastic iPhone bag. This is definitely not a first for AT&T and the monetary waste involved in packing and shipping a completely unnecessary plastic bag is, I assume, passed back to the consumer. Next time you look at your AT&T bill, you can think about my MISC iPhone PPA BAG … which I’ll be cherishing forever. Or at least until the novelty wears off.

Full story at The Unofficial Apple Weblog.

Leave a Comment

Verizon Wireless Reminds Michigan Nonprofits to Apply for HopeLine Grants

Like many corporations, Verizon occasionally gives away some money, possibly in the hope that we will see them as civic-minded and therefore overlook some of their other transgressions.  I’ll pass this little bit of PR along because it may mean that some Michigan organizations will get some funding, but at the same time I will note (as a male of the species) that the types of organizations that will benefit for Verizon’s contributions sometimes have a rather dismal record in protecting battered and/or physically/emotionally abused men – and yes, such creatures do exist. I could make some snarky comments about Verizon perhaps having a feminist agenda, but on the other hand this might really be an act of corporate goodwill, and there is no denying that such organizations as these sometimes save the lives of women and children.  I just wish that the organizations that are “guilty as charged” would get rid of their huge blind spot insofar as the battered or abused male is concerned – men aren’t always the abusers in a relationship.

SOUTHFIELD, Mich., May 5 /PRNewswire/ — Applications for Verizon Wireless’ HopeLine grants are due from community groups by June 30. Michigan non-profit groups are eligible to apply if they directly benefit domestic violence survivors and their families or offer programs that raise awareness of and prevent domestic violence, teen dating violence, partner violence or elder abuse.

Grant applicants must have a 501(c) 3 tax status, and funding requests should not exceed $10,000. Proposals may be submitted in writing to Michelle Gilbert at michelle.gilbert@verizonwireless.com. The deadline for submitting proposals is June 30, 2008. All applicants will be notified between July 1 and Sept. 30. …..

Read the rest of the Verizon press release.

Leave a Comment

Death is tragic, but not the “fault” of VoIP

You have probably seen, or will shortly see, the news about how a Canadian toddler died because the family’s 911 call, placed via a VoIP service, never reached the local 911 dispatch center. As sure as I am that I breathe air, I’m just about as sure that some some phone company PR bastard will try to spin this as though it was an inherent fault of VoIP that caused the child’s death (and will maker sure that news media around North America gets that version of the story).

The facts, however, shed a bit more light on the subject. As the Toronto Globe and Mail reports:

Comwave is still trying to sort out that night’s events. The Luck family’s call was routed to a third-party call centre in Concord, Ont. Comwave had 10 staff members handling 911 calls across Canada.

According to Mr. Barzakay, the network automatically reconnected the call after the initial failed attempt to contact 911. He couldn’t yet say how many rings went unanswered.

The worker at the call centre had a hard time understanding the caller because of a language barrier, Mr. Barzakay said, and relied on the Mississauga address on file and dispatched an ambulance there. He added that customers are encouraged to stay on the phone, but in this case, the caller hung up.

“There was indeed difficulty,” Mr. Barzakay said. “Whether it was from hysterics on the call, I’m not sure.”

But he acknowledged that the family wasn’t to blame. “Clearly, the customer is entitled to receive 911 the moment they press 911.”

The above paragraphs are buried way down in the article, and I just wanted to call your attention to them.  Comwave, the VoIP company involved, is clearly not trying to shirk any responsibility they may have had, but as any 911 operator can tell you, in a panic situation callers sometimes do dumb things, like hanging up in the middle of the call.  And no 911 operator can be expected to understand every caller with a thick accent, or who is speaking in another language. After all, people who are fluent in many languages generally command a much higher salary than what we pay 911 operators.

There have been cases where traditional telephone companies have routed 911 calls to the wrong call center.  We reported a few years ago (on the old MI-Telecom mailing list) of a case where a Wisconsin man died of a heart attack when his 911 call was misrouted – and that call went entirely over the PSTN.  Two years ago, the mother of a 5-year-old boy died when a Detroit 911 operator thought the child was playing with the phone, and wouldn’t take the call seriously, and that was a PSTN call also.

Much of the problem that VoIP companies have had with VoIP calls is that the phone companies aren’t exactly trying to make it easy for VoIP companies to make the connections.  I know someone that works at a company that does VoIP, and he has told me that if they pass a VoIP call onto their upsteam carrier and it’s from a number that’s not in some database, they have to pay some astronomical sum ($20 or $25, if I recall correctly) for that one single call, even if it was just a misdialed call.  I don’t really understand why this is the case, but it apparently is.

Many years ago, the various regulatory agencies decided that it was important for telephone companies to pass the Caller ID number to each other as part of the call setup, without charging the company that receives the data (alas, such was not the case for Caller ID name information, which is why you often get calls showing something generic like “cell phone”, or a city and state, instead of the caller’s name). If they have the power to say that certain information must be passed without regard for compensation, shouldn’t that also be true of emergency calls?

The death of a child is always tragic.  But if there is any good to come from it, it might be that the CRTC and the FCC will order phone companies to pass 911 calls through to the correct 911 center expeditiously, and without charge.  We would think that in an emergency, concerns over who pays for a call should be a secondary consideration, yet no small VoIP company can afford to pay ridiculously high charges to pass 911 calls through to a company that can handle them (usually the incumbent local telephone company).

The thing you have to keep in mind is that 911 center operators – usually municipalities or counties – buy their 911 service (and often their equipment) from the telephone company, for the same reason that 20 years ago most businesses bought computers from IBM – it’s a “safe” purchase decision.  If the equipment doesn’t work, if the service has problems, you can blame the telephone company, but not the employee that made the decision to use the phone company’s services. The problem is that the phone companies can then control how calls access the 911 center, and they are not above making it difficult or expensive for VoIP companies to provide high quality 911 service.  That needs to change – 911 access must be “carrier agnostic” and even, insofar as is possible, “technology agnostic.”  The phone companies must not be allowed to set up barriers to the completion of 911 calls from alternative technology services, just because they can, and because it might put more money in their accounts.

I’m aware that part of the problem is number and device portability.  Nowadays you cannot look at the area code and first three digits of a phone number and determine the location of a caller – they might be using a cell phone, or a VoIP adapter plugged in somewhere other than the usual location.  It’s pretty certain that devices are only going to get more portable as time progresses, and we need a way to pass real-time location information along with 911 calls. The idea of associating a particular number with a fixed location is just plain nonsense that is costing lives.  I don’t have any “quick fix” for this, but acting as though we are still living in the 1950’s, when every phone number terminated at a fixed and specific location, is surely not the answer!

But there is one final point to keep in mind. Sometimes, bad things just happen. Children are killed because something goes wrong every year. Children choke on defective toys, but we don’t blame all toys.  Children drown, but we don’t try to ban swimming pools or say that children are not allowed to swim in a lake. Some children are even tragically killed by parents or caretakers in fits of anger, but we certainly don’t blame all parents or make it illegal to hire babysitters. Likewise, it would be totally irresponsible and repugnant for a telephone company to use this child’s death for some anti-VoIP propaganda.  This was one incident, which we surely wish would not have happened, but which also does not give the incumbent phone companies any reason to tar all VoIP service with the same brush – in fact, until the investigation is complete and all the facts are known, it doesn’t even give them the right to say anything bad about that particular VoIP company.

Leave a Comment