Note: You can play or download the MP3 audio of the “Telemarketer Torture” calls towards the end of the article.

When I first started working with VoIP, I began to hate telephony, and any and all things telephone related. This bothered me on many levels. You see, as a kid, I loved telephones. Growing up in the “big city,” pay phones seemed to be on every corner. Family stories talk about walking several blocks extra, just to avoid me seeing and wanting to play with a phone. But, as usual, I digress…

When I worked with an unnamed switch (let’s just say it rhymed with Broadmoft), I hated working with VoIP. I knew there had to be a better way and started playing with Asterisk. Soon, my memories of playing with phones started coming back and my love rekindled. Now, I look forward to working with phone systems, only because I truly feel that the use of a phone can only be limited by your imagination. And with companies like Twilio, Adhearsion, and Digium, the community of telephone developers seems only to grow.

With that long winded introduction, let’s discuss today’s topic — telemarketer torture. I, like every other person I know, receives the random yet continual undesired telemarketer call (yes, I’m on the DND databases and let’s not get into that). Thanks to Asterisk, I can send my telemarketers to a little place I call the Annoyatron.

Now, many developers and users implement their own version of Telemarketer Torture. Some like using IVR’s. Some like endless ringing. Personally, I like to keep them on the line for a long time. You see, since I add numbers to the Annoyatron after they call me, by the time they reach the Annoyatron they have already called and wasted my time at least once before. So, instead of just having them hang up and move on to the next home, I like to see if I can keep them talking for a while. My Goal? At least 2 minutes.

I use Asterisk’s “WaitForSilence” command to keep my torture conversational. When there’s a pause, the Annoyatron will play a file. While the telemarketer speaks, the Annoyatron will patiently wait. You put it all together, and wala — the Annoyatron Telemarketer Torture.

Today, I received unwanted calls regarding long distance to India. I added the number to the Annoyatron and well, the results of their continued calls no longer annoy me. Here are two examples:

Listen to Call 1:
Download audio file (annoyatron.mp3)
(or you can download the MP3)

Listen to Call 2:
Download audio file (annoyatron2.mp3)
(or you can download this MP3, too)

Ok, so here’s an example of how you would write the dialplan in Asterisk:

[annoyatron]
exten => s,1,Answer()
exten => s,n,Wait(2)
exten => s,n,Playback(annoy/annoy-hello)
exten => s,n,WaitForSilence(2200)
;...
; record a file for "your side" of the conversation
; wait for silence, and then play it
; lather rinse repeat
;...
exten => s,n,Hangup()

Simple, no? Just one of the reasons Asterisk allowed me to enjoy working with telephones. Awwww.

We’d love to hear about your fun examples with Asterisk. And you know, Leif Madsen is requesting some ideas for Asterisk Recipes himself.

Asterisk is free, open source software provided under the GNU General Public License (GPL). Asterisk is the most popular open source software available, with the Asterisk Community being the top influencer in VoIP.

Why free? It’s just how Digium rolls. They really take that GPL open source to heart.

What you VoIPing 'bout Willis?

Yes, you guessed it correctly. In today’s article, Diff’rent Strokes will be used as a metaphor for VoIP. Why? The correct question is “Why Not?” And the answer… well that’s simple — Diff’rent Strokes is the perfect metaphor. Take for example these classic lines from the show’s theme song:

Now, the world don’t move to the beat of just one drum,
What might be right for you, may not be right for some.

Classic. Pausing for Trivia… do you know which 80’s sitcom star wrote these lyrics? If you said Growing Pains actor and Canadian sensation Alan Thicke, you’d be right… but, as usual, we digress.

Those working within VoIP, and contrary to many medical reports there are people still working in the industry, have many flavors and styles of VoIP products to choose from. Although opinions vary, there really is no “right” or “wrong” product line. Selecting your VoIP implementation is an individual choice that is determined simply by what works best for you.

Asterisk versus FreeSWITCH versus Closed Source

Asterisk, by Digium, provides full PBX (private branch exchange) functionality in a (reasonably) small footprint, software package. Created by Mark Spencer in 1999, Asterisk provides itself to the VoIP community free of charge through the GNU General Public License. Asterisk does not require “per seat” licensing fees, maintains a very active community of developers, and requires no additional hardware for a strict VoIP deployment (although grabbing a Digium hardware card to connect to the PSTN makes this software very versatile).

FreeSWITCH, also an open source telephony software program, was developed after Asterisk, by people actively engaged in the Asterisk community. Much like the Facts of Life spun off from Diff’rent Strokes, FreeSWITCH developers thought that new software would be better for telephony; based on their experiences working with Asterisk. They worked hard and created a system that more suited their needs — and like Digium, they have shared this software with the world. The FreeSWITCH site posts a well-written, detailed explanation of “How does FreeSWITCH compare to Asterisk?” on their website (and keeping with the Facts of Life theme… FreeSWITCH approached the software with a “you take the good, you take the bad” approach).

Closed source systems, such as Broadworks, Cisco Call Manager, and Nortel IP Telephony solutions also provide VoIP software and hardware. Closed source systems pride themselves on providing “carrier” class solutions with dedicated support personnel. They also offer licensing fees, fancy logos, and lots of printed documentation.

So which is the best choice? 

Remember: “The world don’t move to the beat of just one drum.”

Choosing a VoIP solution demands thought. Yes, Virginia, you truly have to warm up the water and boil the brain noodle for a while. Is Asterisk best suited for this deployment? Brian West would say that FreeSWITCH would be better in all situations. Others would say, “Hey, use Cisco in large deployments” (although Sam Houston State University might say otherwise).

There simply is no right or wrong answer. As long as you keep well informed of the products out there, the different tools available, and can approach your needs by selecting from your set of tools, you’ll be making the right choice. Fred uses Asterisk. Why? It works for him, and he’s comfortable with it, and he can deploy solutions quickly. Others use FreeSWITCH for the same reason. And who’s right? Simply put, everyone is.

This same discussion can be applied to coding within the VoIP platform of your choice. Recently, when we discussed using Asterisk, Cepstral, and Perl to Get Parking and Weather Updates, we received many, many comments from people with different approaches.

Dug Song commented how Twilio could be used in this situation while Jason Goeke demonstrated how Adhersion could also be used. Within the comments we can see that some coders like jumping into the programming interface (and staying there) whereas Fred likes the “get in, get out” approach and stay in the Asterisk dial plan as much as possible.

So, again, who is right?

We turn once more, to the wise Alan Thicke and Diff’rent Strokes:

Everybody’s got a special kind of story
Everybody finds a way to shine,
It don’t matter that you got not a lot 
So what,
They’ll have theirs, and you’ll have yours, and I’ll have mine.
And together we’ll be fine…
Because it takes, Diff’rent Strokes to move the world.
Yes it does.
It takes, Diff’rent Strokes to move the world.

roll credits