Your understanding about NAT related difficulties is partially correct: the issue really arises from the fact that H.323 is an umbrella that supports numerous protocols and transports. If a transport, such as HTTP or RTSP, embeds IP addresses in the payload portion of IP traffic (rather than just in the header), when those packets get segmented or fragmented, that data becomes difficult to track and use.
- setting up VPN links and punching specific ports through your firewalls
- working with robust NAT implementations that permit some addresses to be handled (obviously, public addresses are essential) without translation
- using a dual-homed gateway or gatekeeper and passing traffic through the public (untranslated) address side of the box
- situating a video-teleconferencing box in your DMZ or on the public side of your Internet interfaces and tunnelling traffic between that box and the private site of your network
- selecting alternate H.323 compatible transports that don't embed address data in streaming video payloads
Dig Deeper on Network Security Monitoring and Analysis
Related Q&A from Ed Tittel
If users encounter problems with a Windows 10 mouse or keyboard, IT pros can follow these steps to troubleshoot the connectivity issue quickly and ... Continue Reading
Microsoft Edge, Windows 10's default browser, includes a file-sharing tool called Near Share, which is helpful, if not truly groundbreaking. Continue Reading
The Windows ADK can help ensure Windows 10 compatibility for apps, software and hardware. There are six key steps to the installation process. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.