Writing about architecting communications solutions is like catching a tiger by the tail – narrowing down the amount of detailed information and background material required to provide a cohesive description on how to architect communications software demands omissions that that will inevitably be required by the reader to create their applications.  Architecting a communications solution requires a deep understanding of the protocols that will be used to access services, the platform on which the services will be developed, the environment that the services will be deployed and the requirements on the end user who will be consuming the services.

IP based communications has lowered the barriers of entry for companies developing communications systems.  The days of communications solutions requiring customized hardware and software have been superseded by the commoditization of fast hardware, off the shelf software and high speed data networks.  The evolution of application layer signaling protocols and the development of applications and frameworks simplifying access to these protocols is aiding the rapid pace of innovation.  Never before has it been easier for companies to develop robust communications solutions.

The goal of this blog is to provide a reference point for architecting communications solutions.  The first main thread through this blog will focus on applications based on the Session Initiation Protocol (SIP).   The initial postings will cover SIP and the IP Multimedia Subsystem (IMS), which is an architectural framework for delivering IP multimedia to mobile devices using SIP.  IMS has the potential to deliver on the promise of Fixed-Mobile Convergence (FMC) which provides both fixed and mobile services on a single user agent (for example, a mobile phone) that can seamlessly switch networks.  The following entries will then cover creating and maintaining SIP applications.

Finally, to introduce myself, I have spent my career architecting, designing and developing software solutions in the telecommunications industry.  I have worked in R&D, at major equipment vendors and at a major carrier.  Most recently I was a Systems Architect for a hosted IP telephony system at a telecommunications equipment vendor.  I have a Masters Degree in Telecommunications.