SIP Trunking Implementation: A Systems Approach by Ivan Sindell

SIP Trunking Implementation: A Systems Approach

Given opportunity for design errors when implementing SIP, extensive design planning and communication are critical to ensuring success.

Session Initiation Protocol (SIP) is inherently simple. It is readable, meaning that with a probe you can follow the session initiation by simply reading the messages as they travel between two devices. The protocol does not establish the route the content will traverse, nor its quality. After the session is established, SIP, as a protocol, is only responsible for ending the session.

SIP trunks were created to replace TDM B Channels in T1 lines -- one SIP trunk for one SIP Session. This allows VoIP premises switches to have a less expensive alternative to T1s. But more than 10 years after RFC 4904 created the specification for SIP trunks, more than 20% of SIP trunk installs today still have issues during implementation and operation. My SCTC colleague Beth English explored this last week on No Jitter. While Beth's article focused on organizational planning and communications complexity issues, this week's article will focus on challenges in design errors, procurement, and monitoring.

Ivan Sindell

Ivan Sindell, a technologist, leads GCSRi Corporation, a cloud voice consultant firm. We provide great solutions and careful management of...
Read Full Bio >>

 Read Full Article Here

Share this post:

Comments on "SIP Trunking Implementation: A Systems Approach by Ivan Sindell "

Comments 0-5 of 0

Please login to comment