Made in USA: Enterprise Application Services

Call Today!817-210-4042

Asterisk, IVR, VoIP

Asterisk IVR VoIP Integration Services

Ayoka has provided clients throughout the United States in different business sectors with industry-standard, cost effective IT solutions. The case study below is architecture used for an e-government (City) application that enables citizens to either pay fees in person, online, or via telephone. The current City enterprise application is a .NET application running on client server architecture.

Asterisk case study :: Asterisk IVR VoIP Integration Services

The architecture of this VoIP (voice over IP) solution relies on three main components. First, the IVR (interactive voice response) server needs to be able to communicate with the City’s .NET application server over HTTPS. Next, the IVR server will need an inbound SIP (session initiation protocol) extension assigned to it through the City’s PBX (private branch exchange) system. Finally, because the .NET application server processes credit card payments, it will need a certificate either shared or unique to the server’s fully qualified domain name to offer security through SSL (secure sockets layer), a requirement for accepting online payments.

As illustrated above, the network domain can be thought of as three separate pieces. The left most side is the client side and can be either a phone device coming through the telephone network or a web browser coming through the internet. Typically a City will provide a security layer here such as a firewall to stop hackers and intrusion from taking place.

The next tier can be a DMZ (demilitarized zone) or similar architecture where the City can allow external access to required servers. Services such proxy/cache, NAT (network address translation), web servers, and PBX external interfaces are usually found here. This is where the IVR server will be located, as it needs a direct web interface. The City application, however, along with the database, will remain in the secure subnet, and will only accept connections from the IVR server.

The three main services running on the IVR server are an HTTP server such as Apache, Ruby servers running Ruby on Rails instances, and Asterisk. The Ruby on Rails framework will serve several purposes here:

  1. Integrate with the.Net application using web services through secure HTTP
  2. Serve custom web pages using this data
  3. Integrate with Asterisk for personalized IVR
  4. Provide a merchant processing mechanism for payments

Contact our software development team today to discuss VoIP, Asterisk, or integration with Ruby on Rails (RoR) that builds on our agile software development techniques. Our software development team is available for a complimentary consultation, through e-mail or the contact form provided below.