I mentioned in my last post that I’ve been working mostly for Power Home Remodeling Group for a while. Primarily on the app that runs their business. We call it Nitro.
Initially, I plan to focus on our integration with Adhearsion. I’ll keep things to a functional level rather than getting too in-depth technically.
If you’d like more technical details about a topic leave a comment. I can get into specifics if there’s enough interest. The simple reason is that it takes longer to write a post with code examples. I think there’s sufficient value in describing what’s possible at a business level.
Our production environment lives on a number of virtual servers hosted in our corporate hosting center. Our current setup includes five web servers, five transaction servers and a single server which runs Asterisk and Adhearsion.
The transaction servers run cron jobs, background processes and our call loop which feeds our phone system with numbers to be called. More on that in a future post.
On our Asterisk/Adhearsion server we also have a separate application running on it we call Talkbox. This is a custom Adhearsion app with PowerHRG’s business logic. It runs as a service and communicates back and forth with our main Nitro application via API calls.
So what does Power Home Remodeling Group do?
PowerHRG sells windows, siding, doors, roofing and a few other products. We make a lot of phone calls to do that.
The majority are appointment confirmations and marketing calls. Around 48,000 outgoing calls every day. Yes. All with a single Asterisk/Adhearsion server.
Adhearsion is described as an
open-source voice application development framework.
It actually does a bit more. We’ve tied it into our LDAP server so our phone systems and applications use the same info and security. Adhearsion can even integrate over XMPP (Jabber) to support stuff like instant messaging.
In my next post, I’ll start talking about some of our specific uses of Adhearsion. Stay tuned.
Updrift is the home of J. Wade Winningham He helps make the web work