TelecomsXChange (TCXC) is excited to announce that the TCXC Platform legacy code is now updated, tested, and optimized to run in Amazon Web Services (AWS) ☁️. Thanks to our diligent and experienced development team and partners 🚀, we now have a Full-stack telecom wholesale digital transformation platform that is light-years ahead of the game that runs on the world’s most popular cloud infrastructure.
We are committed to providing you with industry-leading features to make carriers work easier, more streamlined, and more efficient.
Here is a quick list of the components which have been optimized to work with AWS:
Diagram for SMPP Setup with Go Arch ON AWS
✅TCXC SMPP Load Balancer (None TLS)
The TCXC SMPP Load Balancer is written in Go Lang and it’s responsible for handling the high load of SMPP traffic and distributing them across as many SMPP Upstream Proxies. The reason for building this component is to overcome the single-threading limitation of upstream proxy since it was originally written in nodejs. The load balancer can load balance SMPP traffic to as many upstream proxies on the same or remote server(s) as needed
Compliance: This component is SMPP v3.4 and 5.0 compliant
Estimated R&D time spent to date: 635 days.
✅TCXC SMPP Load Balancer (TLS version)
The TCXC SMPP Load Balancer (TLS) is written in Go Lang and it’s responsible for handling SMPP traffic coming over TLS and distributing them across many SMPP Upstream Proxies. The TLS load balancer can load balance SMPP traffic to as many upstream proxies on the same or remote server(s) as needed. As shown the the above figure, the TLS Load Balancer usually runs on a different port from none TLS load balancer.
Compliance: This component is SMPP v3.4 and 5.0 compliant
Estimated R&D time spent to date: 635 days.
✅TCXC SMPP Upstream Async Proxy
The TCXC SMPP Upstream proxy is written in NodeJS using Asynchronous programming, which is single-threaded. main responsibility is to perform Authorization and Accounting using TCXC Redis Async and MySQL DB operations and dispatch the traffic over to TCXC Bind Balancer for Message Termination (MT). You can run as many upstream proxies as needed on a single EC2 or multiple EC2s.
Compliance: This component is SMPP v3.4 and 5.0 compliant
Estimated R&D time spent to date: 900+ days.
✅TCXC SMPP Bind Balancer
The TCXC SMPP Bind Balancer (BB) is SMPP v3.4 and v.5.0 compliant written in Go Lang and it’s responsible for forwarding all submitted messages from upstream async proxy and controlling bind sessions, handling enquire_links, it also plays a critical role in Delivery Receipts (DR) routing to the right upstream instance using the origin TCP socket not basing its DR routing on Bind ID.
Compliance: This component is SMPP v3.4 and 5.0 compliant
Estimated R&D time spent to date: 450 days.
✅TCXC SMPP Proxy Async (Legacy)
SMPP proxy (async) is written in NodeJS, it was the original SMPP signaling for the SMS exchange functionality on the TCXC platform, it’s responsible for handling all SMPP operations and it’s pre-integrated with TCXC AAA, this component has known scalability limitations, it is recommended to migrate to Go Arch if your traffic exceeds 1000+ Transactions per second.
Compliance: This component is SMPP v3.4 and 5.0 compliant
Estimated R&D time spent to date: 1000+ days.
✅TCXC SIP Stack
TCXC SIP Stack is a combination of customized SIP Proxy and RADIUS RFC3261-compliant Session Initiation Protocol (SIP) B2BUA which represents an advanced SIP back-to-back user agent designed to be used with [RFC2865] compliant RADIUS billing engines.
✅TCXC AAA (Authentication, Authorization, Accounting)
✅TCXC SIP/SMPP Watchdog
✅TCXC Redis Async
This component works with Redis Server, it is an essential part of SMPP Go Arch, it helps with performing a large number of SMPP AAA lookups per second without hitting table locking bottlenecks in MySQL DB.
✅TCXC Carrier Digital Portal & Market Place
TCXC Carrier Digital portal is an intuitive Graphical User Interface (GUI) for buyers and sellers, it enables them to perform self-service SIP and SMPP interconnects, buy and sell communication services (Voice, SMS, Numbers) in realtime and communicate with each other transparently. It can be configured to work as a digital portal for a single service provider to automate their VoIP and SMS service offering for partners or set up as a marketplace. Additionally, it can be used for automatic API enablement for numbers, prices, testing, and trouble tickets.
✅TCXC Programmable API
Programmable Exchange, refers to communications service providers (CSPs) utilizing application programming interfaces (APIs) to automate the core actions for telecom wholesale buying and selling operations. Such as interconnection, carrier relations, market opportunity research, ticket escalation, communications, traffic routing control, ratings and reviews, and financial settlements for Voice, SMS, and Virtual Numbers. Learn more about Programmable Exchange.
Thanks for reading and please comment if you have any questions or feedback!
You may directly contact our support team here for further details on specific components.
You must be logged in to post a comment.