My main use case for AudioCodes Mediant Cloud SBC is that we activated it as the Session Border Controller, the border controller, and a Media Gateway. We used a fixed IP from the client's network, which used telephony only for physical, in-person work at the agency, a public agency here in Brasília, in Brazil. During the pandemic, we activated AudioCodes Mediant interface so that it could register extensions remotely, to provide home office for the agency's professionals, including Teams. During the pandemic, AudioCodes Mediant Cloud SBC was essential in this case.I had the opportunity to work with AudioCodes in support as an on-site technician at a government client, where I stayed at the G-Box Smart Space, known here in Brasília. I worked at a government client where I was on site. AudioCodes FXS converted telephony to analog extensions, conventional telephony, including for use in elevators, in deputies' offices, with the simplest possible telephony, with analog digital phones there. The ports of AudioCodes FXS would generate a 60-volt ring voltage, which we connected to the quick-coupling BLI block, internal cabling, and we did the jumpers and connections. A point in the main use case that I believe could evolve and further facilitate my work is the replacement of modules. The boards of AudioCodes FXS were very interesting and worked effectively. They have a positive and negative point in that they would burn out relatively easily, because the FXS did not have, in the physical circuit of the board, a protection capacitor to protect it. The resistors and micro-components would burn out easily when there was feedback on the metallic network of the FXS. This module would burn out, and often the module itself would burn out. However, since it was modular, both the power supply of the equipment and the fans of the physical equipment of AudioCodes FXS, we just replaced the module, replaced the fan, replaced the power supply, and the four-port FXS module. I also worked with physical AudioCodes that converted, which would be the Media Gateway part. It converted E1 to SIP, to E1, with BNC connector. There was the bus, functioning as if it were an E1 patch panel. It converted that bus to RJ45, so it would enter via pure SIP into our SIP server, which was a machine we ran with, actually several machines. There was a technology park there with six main servers: proxy, SIP server, database, application, the management server for the web part, and the internal PBX management system, with redundancy. I converted there to the network to reach these machines via the internal network. My history in the IP telephony area has always been with these positive and negative points regarding the physical part of the equipment, but I saw that the Media Gateway did not have issues, even with lightning in the region and power oscillation. The E1-to-SIP Media Gateway worked very effectively. AudioCodes FXS had that issue, but it was also excellent. The company carried these boards, which had 48 ports. We had around 16 FXS gateways and four E1-to-SIP gateways. The external operator's TDM E1s would arrive, the optical modems of the PSTN link, of the public telephone network, delivering the E1s, the 30 channels, and it would convert to SIP. We would put these channels into our internal PBX to handle incoming and outgoing calls. I also assisted international clients from Econ and Orange as well, who deployed SBC and deployed Teams. They activated Microsoft Teams on the network and used it as an SBC to interconnect with the operator. A challenging point in my previous job was that it was necessary to activate media bypass on the SBC for it to work with the telephone operator I work with today, which is an important detail. We had a little difficulty with that, but after we did it, everything worked fine.
AudioCodes Mediant Cloud SBC serves as the main communication solution between our internal telephony systems and our telecom operators, who are our suppliers. The integration between internal telephony and external providers is effectively supported by AudioCodes Mediant Cloud SBC.
AudioCodes Mediant Cloud SBC serves as my primary solution to support SIP trunking for direct routing for Microsoft Teams. We have a SIP trunk from LoopUp, which is connected to AudioCodes Mediant Cloud SBC, and the Cloud SBC, mostly using two SBCs for high availability, connects with direct routing through the Microsoft network to Microsoft Teams. With AudioCodes Mediant Cloud SBC, we can connect any devices that are not directly supported by Microsoft Teams, such as analog phones on the customer side, door openers, special entries that could not be connected directly to Microsoft Teams, DECT systems, and legacy PBX systems.
I use AudioCodes Mediant Cloud SBC for interconnection and call routing between Microsoft Teams and on-premises phone systems, and that has been the focus of my project work. I created a tenant on Microsoft Azure to deploy AudioCodes Mediant Cloud SBC, where I have an Avaya Communication Manager on-premises. I created a NAT on the firewall public IP address to allow communication between the on-premises phone systems and AudioCodes Mediant Cloud SBC in the cloud. I secured an SSL certificate from GoDaddy to deploy directly on AudioCodes Mediant Cloud SBC to establish a TLS connection to Microsoft Teams. From there, I created a SIP trunk from AudioCodes Mediant Cloud SBC directly to Microsoft Teams and another SIP trunk directly to the on-premises PBX, which has a TDM gateway allowing Microsoft Teams to consume the TDM on-premise E1 or PRI line. After implementing the project, I was able to call on-premises telephone systems from Microsoft Teams, and I can also utilize Microsoft Teams to consume the E1 line to call a PSTN line, which encapsulates the main focus of my project. We utilize AudioCodes Mediant Cloud SBC for call routing, specifically deploying a Huawei AICC, known as the Huawei Artificial Contact Center Intelligence, in a South Africa data center, where AudioCodes Mediant Cloud SBC serves as an intermediary connecting to other on-premises systems across Africa for call routing and SIP signaling.
Learn what your peers think about AudioCodes Mediant Cloud SBC. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
AudioCodes Mediant Cloud SBC is a Session Border Controller designed to streamline communication in cloud environments. It provides robust security, easy integration with existing systems, and support for multiple communication protocols.With the rise of cloud-based communications, companies need a reliable tool like AudioCodes Mediant Cloud SBC to manage voice services seamlessly. It ensures high availability and scalability while protecting calls from external threats. This tool integrates...
My main use case for AudioCodes Mediant Cloud SBC is that we activated it as the Session Border Controller, the border controller, and a Media Gateway. We used a fixed IP from the client's network, which used telephony only for physical, in-person work at the agency, a public agency here in Brasília, in Brazil. During the pandemic, we activated AudioCodes Mediant interface so that it could register extensions remotely, to provide home office for the agency's professionals, including Teams. During the pandemic, AudioCodes Mediant Cloud SBC was essential in this case.I had the opportunity to work with AudioCodes in support as an on-site technician at a government client, where I stayed at the G-Box Smart Space, known here in Brasília. I worked at a government client where I was on site. AudioCodes FXS converted telephony to analog extensions, conventional telephony, including for use in elevators, in deputies' offices, with the simplest possible telephony, with analog digital phones there. The ports of AudioCodes FXS would generate a 60-volt ring voltage, which we connected to the quick-coupling BLI block, internal cabling, and we did the jumpers and connections. A point in the main use case that I believe could evolve and further facilitate my work is the replacement of modules. The boards of AudioCodes FXS were very interesting and worked effectively. They have a positive and negative point in that they would burn out relatively easily, because the FXS did not have, in the physical circuit of the board, a protection capacitor to protect it. The resistors and micro-components would burn out easily when there was feedback on the metallic network of the FXS. This module would burn out, and often the module itself would burn out. However, since it was modular, both the power supply of the equipment and the fans of the physical equipment of AudioCodes FXS, we just replaced the module, replaced the fan, replaced the power supply, and the four-port FXS module. I also worked with physical AudioCodes that converted, which would be the Media Gateway part. It converted E1 to SIP, to E1, with BNC connector. There was the bus, functioning as if it were an E1 patch panel. It converted that bus to RJ45, so it would enter via pure SIP into our SIP server, which was a machine we ran with, actually several machines. There was a technology park there with six main servers: proxy, SIP server, database, application, the management server for the web part, and the internal PBX management system, with redundancy. I converted there to the network to reach these machines via the internal network. My history in the IP telephony area has always been with these positive and negative points regarding the physical part of the equipment, but I saw that the Media Gateway did not have issues, even with lightning in the region and power oscillation. The E1-to-SIP Media Gateway worked very effectively. AudioCodes FXS had that issue, but it was also excellent. The company carried these boards, which had 48 ports. We had around 16 FXS gateways and four E1-to-SIP gateways. The external operator's TDM E1s would arrive, the optical modems of the PSTN link, of the public telephone network, delivering the E1s, the 30 channels, and it would convert to SIP. We would put these channels into our internal PBX to handle incoming and outgoing calls. I also assisted international clients from Econ and Orange as well, who deployed SBC and deployed Teams. They activated Microsoft Teams on the network and used it as an SBC to interconnect with the operator. A challenging point in my previous job was that it was necessary to activate media bypass on the SBC for it to work with the telephone operator I work with today, which is an important detail. We had a little difficulty with that, but after we did it, everything worked fine.
AudioCodes Mediant Cloud SBC serves as the main communication solution between our internal telephony systems and our telecom operators, who are our suppliers. The integration between internal telephony and external providers is effectively supported by AudioCodes Mediant Cloud SBC.
AudioCodes Mediant Cloud SBC serves as my primary solution to support SIP trunking for direct routing for Microsoft Teams. We have a SIP trunk from LoopUp, which is connected to AudioCodes Mediant Cloud SBC, and the Cloud SBC, mostly using two SBCs for high availability, connects with direct routing through the Microsoft network to Microsoft Teams. With AudioCodes Mediant Cloud SBC, we can connect any devices that are not directly supported by Microsoft Teams, such as analog phones on the customer side, door openers, special entries that could not be connected directly to Microsoft Teams, DECT systems, and legacy PBX systems.
I use AudioCodes Mediant Cloud SBC for interconnection and call routing between Microsoft Teams and on-premises phone systems, and that has been the focus of my project work. I created a tenant on Microsoft Azure to deploy AudioCodes Mediant Cloud SBC, where I have an Avaya Communication Manager on-premises. I created a NAT on the firewall public IP address to allow communication between the on-premises phone systems and AudioCodes Mediant Cloud SBC in the cloud. I secured an SSL certificate from GoDaddy to deploy directly on AudioCodes Mediant Cloud SBC to establish a TLS connection to Microsoft Teams. From there, I created a SIP trunk from AudioCodes Mediant Cloud SBC directly to Microsoft Teams and another SIP trunk directly to the on-premises PBX, which has a TDM gateway allowing Microsoft Teams to consume the TDM on-premise E1 or PRI line. After implementing the project, I was able to call on-premises telephone systems from Microsoft Teams, and I can also utilize Microsoft Teams to consume the E1 line to call a PSTN line, which encapsulates the main focus of my project. We utilize AudioCodes Mediant Cloud SBC for call routing, specifically deploying a Huawei AICC, known as the Huawei Artificial Contact Center Intelligence, in a South Africa data center, where AudioCodes Mediant Cloud SBC serves as an intermediary connecting to other on-premises systems across Africa for call routing and SIP signaling.