Back to Case studySIP Trunk Solution Enables Credit Company to Improve Customer Connect
ShareHighlights
- SIP Trunk: Ensured redundancy for incoming calls via a toll free number (TFN)
- High uptime and no single point of failure with uninterrupted calling
- Cost reduction due to TFN over SNS solution
Introduction
The customer is a gold loan company that provides online processing and a branchless business model to facilitate seamless transactions for its clients. They offer loans against gold that are consumer friendly, hassle free, paperless and convenient. The customer is known for following industry best practices in security, employing multiple threat mitigation techniques. They perform security audits and have a custom security strategy so that their clients’ data is kept safe from prying eyes.
Business Challenge
The challenge lay in ensuring a single contact number at the front end and multiple locations for the back end. The customer also required a revamped system with no complex infrastructure whilst providing the highest uptime and redundancy for 100 efficiency.
TTBS Solution
- Two SIP Trunks at two different locations were set up for a continuous run
- TTBS provided the SIP Trunk over Ethernet with SDH ring architecture
- The SIP Trunk was terminated over a Session Border Controller ( at the last mile
- To ensure redundancy, TTBS provided SIP Trunk 1 with 60 channels at one location and SIP Trunk 2 separately terminating at the SBC
- The Trunk bandwidth was created to support the aggregated SIP to achieve 100 concurrency
- The TTBS SIP Trunk was a P 2 P circuit with 30 IP address assigned by TATA The same IP address was to be transferred to the customer PBX’s NIC interface
- Codec on both trunks was configured to comply with the G 711 A law
- The Dual Tone Multi Frequency ( was set at RFC 2833
- The “P Preferred Identity” header was included in all SIP INVITEs for correct DID CLIP display on the outgoing calls
- DID number sending ( on SIP INVITE “ header on incoming calls
- A keep alive mechanism through SIP options was implemented The expected response was SIP 60 Ok from the CPE device
- TTBS system also provided parameters such as Customer IP (configured at the NIC port of the SBC), Gateway IP, SIP Server, IP Subnet Mask, Username, Password and DID Range
