Many companies are looking for inexpensive and easy to manage VoIP systems, but because of the diversity of aggregated products in the market, they have to face the challenge of deploying VoIP. At the same time, the VoIP system they use must also be able to support emergency telephone services. It has become more difficult to achieve this due to the lack of standards.
TIA sets new standards
The Telecommunications Industry Association (TIA) is an organization established to facilitate the deployment of VoIP networks and perform failure analysis. The TIA draft standard (Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) makes it easier to share information between endpoints and network infrastructure. This data can simplify endpoint deployment and allow advanced device firmware management while driving E911 support from enterprise networks.
LLDP-MED is based on IEEE's 802.1AB LLDP and will become a new standard this month. LLDP is the neighbor discovery protocol of IEEE, which other organizations can extend. Information identified from network devices, such as switches and wireless access points, can help with failure analysis and allow management systems to accurately understand network topology.
Further simplify management
Devices that support LLDP will use messages called Type Length Value (TLV) to transmit information to neighboring devices. This information includes rack and port identification, system name, system function, system description, and other attributes. LLDP-MED implements these functions by adding media and IP phones specific to and which can be exchanged between the network and endpoints. The new TLV message will provide the media endpoint location and inventory of PoE (Power over Ethernet), networking policies, and emergency telephone services.
PoE management TLV allows endpoints to publish the levels they need and priority power levels, and allows network-connected devices to publish the power they can provide. These announcements enable switch suppliers to support advanced power management. For example, a switch can compare the power required by an endpoint to the power it can provide. If the switch does not have the ability to meet the endpoint requirements, it can choose to power the endpoints designated as having the highest priority, such as first aid IP phones.
Networking strategies have found that TLV can simplify the deployment of large-scale multi-vendor networks and facilitate failure analysis. This TLV allows endpoints and switches to publish their virtual LAN IDs, which are specified by IEEE priority and distinguished service code points (layer 3 advantage level). Network administrators can quickly find misconfigured endpoints. Although IEEE 802.1AB is not designed for configuration, endpoint vendors can let these devices modify their settings when they find mismatches between endpoints and networks.
Supports scalable
LLDP-MED inventory management found that TLV allows endpoints to transfer their own detailed inventory information to connected switches. This information may include the supplier name, model, firmware revision number, and serial number. When the switch receives this information, it is stored and provided to the network management system to generate a list report.
Finally, TIA discovered through the ECS endpoint location of LLDP-MED that TLV is seen as a way to support emergency telephone services within the enterprise network. Although other standards are being developed, LLDP-MED is ideal for use where it is added, moved, and changed frequently. This TLV contains information related to the campus telephone wiring diagram or other attributes that allow parsing the exact location of the endpoint. When an endpoint receives a TLV with ECS location data, it stores the data and uses it when it needs to communicate with the emergency communication accepting center. No matter where the ECS moves to in the network, this method ensures that the endpoint can discover accurate location information.
TIA's LLDP-MED is about to become a new standard in the first half of 2005, and the network policy, power, location and inventory data it provides are very useful for aggregation networks.
VoIP security advice
If VoIP is implemented, security is an important thing to consider, because every node in VoIP is accessible like a computer. It is recommended to start from several aspects to ensure the security of VoIP.
VoIP and internal network separate: There are several security devices that do not fully run VoIP signaling commands. Therefore, they may open dynamic communication ports, leaving the network vulnerable to bounce attacks. This will allow attackers to invade other critical business components in the internal LAN.
Based on the premise of meeting the needs: there may be both agreeable and an objection to the use of different protocols and VoIP devices of different manufacturers. To ensure that the device you choose meets your needs, changing the needs to support the equipment of a specific manufacturer is very dangerous.
Stop using unnecessary protocols: There is no need to enable unnecessary and unused protocols and services to provide more opportunities for hackers.
Ensure manageability: Even for phones and terminals, all VoIP systems are software systems that run on hardware, so make sure that this basic VoIP operating system can be managed. In addition to the above issues that need to be considered, the impact of network address translation on VoIP traffic should also be considered.
TIA sets new standards
The Telecommunications Industry Association (TIA) is an organization established to facilitate the deployment of VoIP networks and perform failure analysis. The TIA draft standard (Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) makes it easier to share information between endpoints and network infrastructure. This data can simplify endpoint deployment and allow advanced device firmware management while driving E911 support from enterprise networks.
LLDP-MED is based on IEEE's 802.1AB LLDP and will become a new standard this month. LLDP is the neighbor discovery protocol of IEEE, which other organizations can extend. Information identified from network devices, such as switches and wireless access points, can help with failure analysis and allow management systems to accurately understand network topology.
Further simplify management
Devices that support LLDP will use messages called Type Length Value (TLV) to transmit information to neighboring devices. This information includes rack and port identification, system name, system function, system description, and other attributes. LLDP-MED implements these functions by adding media and IP phones specific to and which can be exchanged between the network and endpoints. The new TLV message will provide the media endpoint location and inventory of PoE (Power over Ethernet), networking policies, and emergency telephone services.
PoE management TLV allows endpoints to publish the levels they need and priority power levels, and allows network-connected devices to publish the power they can provide. These announcements enable switch suppliers to support advanced power management. For example, a switch can compare the power required by an endpoint to the power it can provide. If the switch does not have the ability to meet the endpoint requirements, it can choose to power the endpoints designated as having the highest priority, such as first aid IP phones.
Networking strategies have found that TLV can simplify the deployment of large-scale multi-vendor networks and facilitate failure analysis. This TLV allows endpoints and switches to publish their virtual LAN IDs, which are specified by IEEE priority and distinguished service code points (layer 3 advantage level). Network administrators can quickly find misconfigured endpoints. Although IEEE 802.1AB is not designed for configuration, endpoint vendors can let these devices modify their settings when they find mismatches between endpoints and networks.
Supports scalable
LLDP-MED inventory management found that TLV allows endpoints to transfer their own detailed inventory information to connected switches. This information may include the supplier name, model, firmware revision number, and serial number. When the switch receives this information, it is stored and provided to the network management system to generate a list report.
Finally, TIA discovered through the ECS endpoint location of LLDP-MED that TLV is seen as a way to support emergency telephone services within the enterprise network. Although other standards are being developed, LLDP-MED is ideal for use where it is added, moved, and changed frequently. This TLV contains information related to the campus telephone wiring diagram or other attributes that allow parsing the exact location of the endpoint. When an endpoint receives a TLV with ECS location data, it stores the data and uses it when it needs to communicate with the emergency communication accepting center. No matter where the ECS moves to in the network, this method ensures that the endpoint can discover accurate location information.
TIA's LLDP-MED is about to become a new standard in the first half of 2005, and the network policy, power, location and inventory data it provides are very useful for aggregation networks.
VoIP security advice
If VoIP is implemented, security is an important thing to consider, because every node in VoIP is accessible like a computer. It is recommended to start from several aspects to ensure the security of VoIP.
VoIP and internal network separate: There are several security devices that do not fully run VoIP signaling commands. Therefore, they may open dynamic communication ports, leaving the network vulnerable to bounce attacks. This will allow attackers to invade other critical business components in the internal LAN.
Based on the premise of meeting the needs: there may be both agreeable and an objection to the use of different protocols and VoIP devices of different manufacturers. To ensure that the device you choose meets your needs, changing the needs to support the equipment of a specific manufacturer is very dangerous.
Stop using unnecessary protocols: There is no need to enable unnecessary and unused protocols and services to provide more opportunities for hackers.
Ensure manageability: Even for phones and terminals, all VoIP systems are software systems that run on hardware, so make sure that this basic VoIP operating system can be managed. In addition to the above issues that need to be considered, the impact of network address translation on VoIP traffic should also be considered.