AudioCodes Routers
Good day.
Today is a new review - AudioCodes routers. Yes, you were not mistaken and read correctly, namely the routers. Life does not stand still, and AudioCodes has long been a pioneer of VoIP and the world-famous brand of voice gateways of any scale, from one FXS port to several STM-1, turned into a manufacturer of complex and integrated solutions not only for the operator, but also for the corporate market . Now the company’s product profile has more solutions that are not in the voice gateway category than traditional gateways.
What is AudioCode Business Router?
After a visual inspection of the interfaces, many will say that this is a typical and familiar Mediant 500, Mediant 800 or Mediant 1000 gateway. However, let's take a closer look at all the series of devices.
Not all models of these series have analog or digital TDM interfaces. So, no longer a gateway. Although this statement does not mean that there is no VoIP support on devices without TDM interfaces. But first things first. AudioCodes Routers are the Mediant 500 / 500L MSBR, the Mediant 800 MSBR, and the Mediant 1000 MSBR. Each name is a series of devices with different configurations, which are distinguished by the presence and number of specific WAN / LAN interfaces and / or TDM interfaces.
')
The abbreviation MSBR (Multi Service Business Router) is added to the name of conventional gateways, which means that this type of devices is primarily intended as a router. In terms of software (firmware), Mediant and Mediant MSBR are different. However, replacing the Mediant MSBR firmware can turn into a regular voice gateway or SBC, about which we wrote earlier here and here .
As a router, models with TDM ports simultaneously additionally receive voice gateway functionality (from several FXS to 1-2 E1 streams). Models with LAN ports (up to 12 on the Mediant 800 MSBR) are simultaneously a LAN switch, and when using the SBC license, the device also receives SBC functionality. There are models with built-in WiFi access point. This is not enough, there are models with built-in OSN modules, which are an Intel server. And this feature can be used to install any operating systems and third-party applications or IP-PBX, implementing all-in-one boxed (one device) solutions on the device.
Consider an example. In a typical case, when connecting an office to a provider or different offices, one has to use several devices. Each of these devices performs its function (channel-forming device, router, Firewall, switch, SBC, gateway, QoS / QoE agent, etc.). In the case of using AudioCodes routers, there is no need to use multiple devices. One of our devices can simultaneously perform several or all of the following roles:
Schematically voiced approach is as follows:
As a result, in the ideal case, you get one device, which runs and implements all or most of the tasks to ensure communication in the offices. Typical schemes for office inclusions using a SIP trunk and for connecting to the cloud look like this:
All of the above raises many questions about the stability and performance of such an inclusion scheme. Multiservice imposes a lot of limitations on performance. How tenacious is such an application scheme? How will the device behave, being loaded with several functions? Different types of traffic exacerbate the situation: HTTP traffic is characterized by a small number of large packets, voice traffic - by a large number of relatively small packets. What data to use when evaluating performance? Should encryption be used (encryption + a large number of packets leads to a CPU load of up to 50% or more)? Whether to perform transcoding (as you know, performance also suffers from this)? And what if you enable NAT or QoS (by themselves, these functions can reduce packet rates by more than 80%)?
AudioCodes has the answers to such questions. The Mediant architecture contains several computational resources. We use different CPUs for voice and data processing and our own DSP. This means that there are separate resources for encryption, transcoding, NAT processing and QoS. In the end, it gives stable performance. Data and voice processing does not affect each other. And stable performance is an IMPORTANT advantage. And the total numbers when evaluating the performance in the context of the above are not only bits per second, but also packets per second (PPS).
Below are the PPS performance test data for some other manufacturers compared to the Mediant 800 for NAT and QoS modes.
Another important issue during a conversation about routers is its ability to route traffic and other traditional features of routers. We will not go into lengthy discussions, for review we restrict ourselves to basic information, and for details we will direct the reader to the descriptions on the site ( http://www.audiocodes.com/multi-service-business-router-msbr ).
Data routing
• PPP, MLPPP, PPPoE, PPPoA, L2TP, IPoE, IPoA
• ATM: Up to 8 PVCs
• OAM-F5 (send / receive): loopback, continuity check
• Shaping: UBR, VBR-NRT, VBR-RT, CBR
• DHCP Client, Relay, server
• VLAN, VRF
• Layer 3 routing and Layer 2 bridging, Jumbo frames
• Internal layer 2 switching
• Static and dynamic routing (RIP1, RIP2, OSPFv2, BGPv4), Policy-Based Routing
• Multicast routing: IGMPv2 / 3
• IPv6, IPv6 / IPv4 Dual Stack, ICMPv6, DHCPv6, SLAAC
Data security
- Malformed Request
- Ping of Death
- Properly formed request from unauthenticated source
- DDoS attack
- SYN flood
All configuration can be done through the command line. The syntax of the teams is not particularly different from the generally accepted approaches that have long become the hallmark of other manufacturers. Other control methods are supported:
For ease of consideration of the entire line of routers, we present a generalized comparative table of devices of all series.
* Depending on the configuration of a specific device from the series.
And finally, one more comparative table for understanding the positioning of MSBR devices in relation to competing solutions.
I will try not to delay for a long time and in the near future to draw up and consider several practical examples of using AudioCodes routers in projects with different telecom operators and not only, and also show examples of configurations for some switching schemes.
Successful connections!
Today is a new review - AudioCodes routers. Yes, you were not mistaken and read correctly, namely the routers. Life does not stand still, and AudioCodes has long been a pioneer of VoIP and the world-famous brand of voice gateways of any scale, from one FXS port to several STM-1, turned into a manufacturer of complex and integrated solutions not only for the operator, but also for the corporate market . Now the company’s product profile has more solutions that are not in the voice gateway category than traditional gateways.
What is AudioCode Business Router?
After a visual inspection of the interfaces, many will say that this is a typical and familiar Mediant 500, Mediant 800 or Mediant 1000 gateway. However, let's take a closer look at all the series of devices.
Not all models of these series have analog or digital TDM interfaces. So, no longer a gateway. Although this statement does not mean that there is no VoIP support on devices without TDM interfaces. But first things first. AudioCodes Routers are the Mediant 500 / 500L MSBR, the Mediant 800 MSBR, and the Mediant 1000 MSBR. Each name is a series of devices with different configurations, which are distinguished by the presence and number of specific WAN / LAN interfaces and / or TDM interfaces.
')
The abbreviation MSBR (Multi Service Business Router) is added to the name of conventional gateways, which means that this type of devices is primarily intended as a router. In terms of software (firmware), Mediant and Mediant MSBR are different. However, replacing the Mediant MSBR firmware can turn into a regular voice gateway or SBC, about which we wrote earlier here and here .
As a router, models with TDM ports simultaneously additionally receive voice gateway functionality (from several FXS to 1-2 E1 streams). Models with LAN ports (up to 12 on the Mediant 800 MSBR) are simultaneously a LAN switch, and when using the SBC license, the device also receives SBC functionality. There are models with built-in WiFi access point. This is not enough, there are models with built-in OSN modules, which are an Intel server. And this feature can be used to install any operating systems and third-party applications or IP-PBX, implementing all-in-one boxed (one device) solutions on the device.
Consider an example. In a typical case, when connecting an office to a provider or different offices, one has to use several devices. Each of these devices performs its function (channel-forming device, router, Firewall, switch, SBC, gateway, QoS / QoE agent, etc.). In the case of using AudioCodes routers, there is no need to use multiple devices. One of our devices can simultaneously perform several or all of the following roles:
- Channeling equipment - various types of WAN interfaces (optics, copper, SHDSL 2/4 wired, E1). You can use up to 3 WAN interfaces simultaneously.
- Static and Dynamic Routing Router (RIP1, RIP2, OSPFv2, BGPv4)
- Switch with GE / FE
- Firewall
- Voice gateway
- SIP server or IP-PBX
- Session Border Controller (SBC)
- QoS / QoE agent for voice and data quality control
- Methods to ensure fault tolerance for various voice solutions (SAS, CRP, SBC). Depending on the solution used and the switching scheme, it is possible to build fault-tolerant schemes in different ways (IP-PBX, virtual PBX, TDM backup).
Schematically voiced approach is as follows:
As a result, in the ideal case, you get one device, which runs and implements all or most of the tasks to ensure communication in the offices. Typical schemes for office inclusions using a SIP trunk and for connecting to the cloud look like this:
All of the above raises many questions about the stability and performance of such an inclusion scheme. Multiservice imposes a lot of limitations on performance. How tenacious is such an application scheme? How will the device behave, being loaded with several functions? Different types of traffic exacerbate the situation: HTTP traffic is characterized by a small number of large packets, voice traffic - by a large number of relatively small packets. What data to use when evaluating performance? Should encryption be used (encryption + a large number of packets leads to a CPU load of up to 50% or more)? Whether to perform transcoding (as you know, performance also suffers from this)? And what if you enable NAT or QoS (by themselves, these functions can reduce packet rates by more than 80%)?
AudioCodes has the answers to such questions. The Mediant architecture contains several computational resources. We use different CPUs for voice and data processing and our own DSP. This means that there are separate resources for encryption, transcoding, NAT processing and QoS. In the end, it gives stable performance. Data and voice processing does not affect each other. And stable performance is an IMPORTANT advantage. And the total numbers when evaluating the performance in the context of the above are not only bits per second, but also packets per second (PPS).
Below are the PPS performance test data for some other manufacturers compared to the Mediant 800 for NAT and QoS modes.
Another important issue during a conversation about routers is its ability to route traffic and other traditional features of routers. We will not go into lengthy discussions, for review we restrict ourselves to basic information, and for details we will direct the reader to the descriptions on the site ( http://www.audiocodes.com/multi-service-business-router-msbr ).
Data routing
• PPP, MLPPP, PPPoE, PPPoA, L2TP, IPoE, IPoA
• ATM: Up to 8 PVCs
• OAM-F5 (send / receive): loopback, continuity check
• Shaping: UBR, VBR-NRT, VBR-RT, CBR
• DHCP Client, Relay, server
• VLAN, VRF
• Layer 3 routing and Layer 2 bridging, Jumbo frames
• Internal layer 2 switching
• Static and dynamic routing (RIP1, RIP2, OSPFv2, BGPv4), Policy-Based Routing
• Multicast routing: IGMPv2 / 3
• IPv6, IPv6 / IPv4 Dual Stack, ICMPv6, DHCPv6, SLAAC
Data security
- IPSec, GRE, L2TP
- ESP - Tunnel mode
- Encryption (AES, DES, 3DES)
- Authentication Header
- IKE mode - IPsec VPN
- IDS / IPS:
- Malformed Request
- Ping of Death
- Properly formed request from unauthenticated source
- DDoS attack
- SYN flood
- Stateful packet inspection firewall
- DMZ
- Port triggering
- Packet filtering
- Application layer gateway
All configuration can be done through the command line. The syntax of the teams is not particularly different from the generally accepted approaches that have long become the hallmark of other manufacturers. Other control methods are supported:
- Graphic WEB interface for configuration and basic monitoring - active crashes and download schedules
- Command line for technical staff, scripts for configuration and in-depth technical analysis using Telnet / SSH / serial
- EMS management system to monitor and control any AudioCodes products
- Support for automatic updates - the ability to automatically change device configuration files and software versions using HTTP / HTTPS
- TR-069 support
For ease of consideration of the entire line of routers, we present a generalized comparative table of devices of all series.
* Depending on the configuration of a specific device from the series.
And finally, one more comparative table for understanding the positioning of MSBR devices in relation to competing solutions.
I will try not to delay for a long time and in the near future to draw up and consider several practical examples of using AudioCodes routers in projects with different telecom operators and not only, and also show examples of configurations for some switching schemes.
Successful connections!
Source: https://habr.com/ru/post/278677/
All Articles