About Twilio BYOC
Using the Twilio bring your own carrier (BYOC) feature is great and gives you a higher level of freedom in controlling your call quality on the carrier side of things. Using this feature you no longer need to be blind to what happens after you initiate a phone call via programmable voice, or Zoom Phone UI.
On the other hand, we have noticed that when scaling up your BYOC trunks things get very messy and lack advanced routing control like least cost routing (LCR), Weighted distribution, etc… Especially for developers who do not have a Session Border Controller (SBC), or short message service center (SMSC) sitting between the Cloud Communication provider and the end carrier(s).Continue reading…
TelecomsXChange (TCXC) a founding Member of the API3 Alliance, To Offer First-Party Oracle Services on Web3
Leading Web API provider to provide data and services to the next generation of decentralized applications via Airnode
Miami, Florida– August 10, 2021 — TCXC, a leading Telecom digital transformation solution provider today joined with API3, a “first-party oracle” solution empowering data providers to offer APIs directly to Web3 applications, to launch the API3 Alliance 2. The API3 Alliance represents a strategic coalition of API providers who believe that we should be able to share the same data and services we currently offer to web applications directly to Web3 consumers, without having to rely on third-party middlemen. Traditionally, APIs have been forced to either build their own facilities or pay external oracle operators to implement the middleware necessary to make their data and services compatible with the blockchain. API3 offers the tools and individualized support to our growing community — already more than 100 API providers — to go direct to the consumers of our APIs on Web3.Continue reading…
A few important updates will land to TCXC production environment today.
TelecomsXChange (TCXC) is now officially registered in the Federal Communications Commission Robocall Mitigation Database holding number RMD0004338. We have already added the support for the STIR/SHAKEN required SIP headers last week. We have also exposed some UI/API tools for sellers to help them take action in real-time to stop/mitigate any suspicious traffic.
The new SIP Identity headers required by STIR/SHAKEN are now added to TCXC SIP stack. All members are welcome to start testing.
New CLID (Caller ID) policy for sellers
We have released a new policy for sellers which enable them to have full control over the CLID policy to be used for each SIP connection (route). For instance a seller can now define a default Deny all caller ids except defined entries in the table, this can come in handy for virtual number providers who wish to offer a local sip trunk but at same time allow it only to be used from DIDs that are sold via the platform.
Go Lang SMPP LB & Bind Proxy
We are at final stages of QA testing of the new SMPP load balancer and Bind proxy written in Go Lang, the test results were satisfying and in some areas very impressive. We will be posting a dedicated update regarding this topic.
If you have any questions or concerns regarding these updates , please write to email@example.com .