VoIP Bonding
Candy Chan (Talk | contribs) |
(Added link to 2.9) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 11: | Line 11: | ||
The feature has no effect on Virtual IP Interfaces configured in the Web Portal. Virtual IP Interfaces configured on either voip0 or voip1 physical ports still work exactly the same whether VoIP Bonding is activated. | The feature has no effect on Virtual IP Interfaces configured in the Web Portal. Virtual IP Interfaces configured on either voip0 or voip1 physical ports still work exactly the same whether VoIP Bonding is activated. | ||
| − | == Web Portal | + | == Web Portal Display == |
==== VoIP0 Port Status ==== | ==== VoIP0 Port Status ==== | ||
| − | Since VoIP0 and VoIP1 are bonded together, VoIP0 represents an aggregated status of the bonded ports. This means VoIP0 will be shown as " | + | Since VoIP0 and VoIP1 are bonded together, VoIP0 represents an aggregated status of the bonded ports. This means VoIP0 will be shown as "RED" only if both VoIP0 and VoIP1 ports are unavailable. |
==== VoIP1 Port Status ==== | ==== VoIP1 Port Status ==== | ||
| − | VoIP1 | + | VoIP1 port status represents its own physical connectivity. |
| + | ==== Web Portal Ports Display Status ==== | ||
{| cellspacing="0" cellpadding="4" border="1" class="wikitable" | {| cellspacing="0" cellpadding="4" border="1" class="wikitable" | ||
|- | |- | ||
| − | ! scope="col" | | + | ! scope="col" | |
| − | ! | + | ! scope="col" colspan="4" | Physical Connectivity |
|- | |- | ||
| − | ! bgcolor="#DDDDDD" rowspan=" | + | ! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP0 Interface |
| − | + | | scope="col" | UP | |
| − | + | | scope="col" | UP | |
| − | + | | scope="col" | DOWN | |
| − | + | | scope="col" | DOWN | |
|- | |- | ||
| − | ! bgcolor="# | + | ! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP1 Interface |
| − | + | | scope="row" | UP | |
| − | + | | scope="row" | DOWN | |
| − | + | | scope="row" | UP | |
| + | | scope="row" | DOWN | ||
|- | |- | ||
| − | ! scope="col" | | + | ! scope="col" | |
| − | ! bgcolor="#DDDDDD" colspan="4" scope="col" | | + | ! bgcolor="#DDDDDD" colspan="4" scope="col" | Web Portal Port Status |
|- | |- | ||
| − | ! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP0 | + | ! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP0 (Bonded Status) |
| − | + | | scope="col" | GREEN | |
| − | + | | scope="col" | GREEN | |
| − | + | | scope="col" | GREEN | |
| − | + | | scope="col" | RED | |
| − | + | ||
|- | |- | ||
! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP1 | ! bgcolor="#DDDDDD" rowspan="1" scope="row" | VoIP1 | ||
| − | + | | scope="row" | GREEN | |
| − | + | | scope="row" | RED | |
| − | + | | scope="row" | GREEN | |
| − | + | | scope="row" | RED | |
|} | |} | ||
== Configuration == | == Configuration == | ||
| + | *[[Toolpack:Hardware_Settings_B#IP_Network|Toolpack 2.9: VoIP Bonding]] | ||
| + | *[[Toolpack:Hardware_Settings_A#IP_Network|Toolpack 2.8: VoIP Bonding]] | ||
*[[Web_Portal_Tutorial_Guide_v2.7#VoIP_Bonding|Toolpack 2.7: VoIP Bonding]] | *[[Web_Portal_Tutorial_Guide_v2.7#VoIP_Bonding|Toolpack 2.7: VoIP Bonding]] | ||
| + | |||
| + | |||
| + | [[Category:Revise on Major]] | ||
Latest revision as of 10:32, 12 August 2016
VoIP Bonding refers to the capability of Tmedia units to use the two available VoIP Ethernet ports as a bonding pair. When the active port becomes unusable (cable disconnected, limited connectivity), the other port is used to transport Ethernet traffic.
Starting with Toolpack release 2.7.34, VoIP Bonding is available as a feature for Tmedia units. Detection of offline ports is currently achieved through two methods:
- Ethernet PHY polling to quickly discover if a cable is connected or not to the unit;
- Sending IPv4 ping requests to a known host to ensure that a logical IP path is available to the unit.
The voip0 (first VoIP port) MAC and IP addresses are used on both VoIP ports of the Tmedia unit when VoIP bonding is activated. However, in that mode, the voip1 port MAC and IP address are not usable (i.e. protocol stacks assigned to voip1 will not work and voip1 will not respond to ICMP requests). Therefore, IP services and stacks (such as SIP, SIGTRAN and port ranges) must be assign to voip0 only.
The VoIP Bonding feature also makes the Tmedia units report the bonding state as the voip0 port state. For instance, the IPv4 statistics reported by the Web Portal for voip0 are actually for the bonding pair. The PHY state is also for the bonding pair (so it would only be down if both voip ports are down). To know the true state of the physical voip0 and voip1 ports, the SNMP protocol must be used.
The feature has no effect on Virtual IP Interfaces configured in the Web Portal. Virtual IP Interfaces configured on either voip0 or voip1 physical ports still work exactly the same whether VoIP Bonding is activated.
Contents |
Web Portal Display
VoIP0 Port Status
Since VoIP0 and VoIP1 are bonded together, VoIP0 represents an aggregated status of the bonded ports. This means VoIP0 will be shown as "RED" only if both VoIP0 and VoIP1 ports are unavailable.
VoIP1 Port Status
VoIP1 port status represents its own physical connectivity.
Web Portal Ports Display Status
| Physical Connectivity | ||||
|---|---|---|---|---|
| VoIP0 Interface | UP | UP | DOWN | DOWN |
| VoIP1 Interface | UP | DOWN | UP | DOWN |
| Web Portal Port Status | ||||
| VoIP0 (Bonded Status) | GREEN | GREEN | GREEN | RED |
| VoIP1 | GREEN | RED | GREEN | RED |
