Understanding ip systems
Contents
- Private LAN IP Addresses
- Private LAN IP Addresses
- Network Address Translation (NAT)
- Port Forwarding: Tieline TCP and UDP Port Settings
To transmit audio streams within the public internet you should utilize an open Ip allotted to you from your ISP (Isp).
An open Ip is much like your public phone number and enables you to definitely be contacted on the internet in exactly the same people dial your public phone number. They are available in two forms dynamic (DHCP) and static. Most ISPs assign an engaged public Ip automatically, which could frequently change without you knowing. This really is appropriate for any quick demo of the Tieline codec, however for a lasting installation you will have to request a lasting static public Ip.
When the Static Public Ip is owned by your online connection (router) in the studio you have to produce a outcomes of the general public Ip as well as your codec’s private Ip around the LAN. This really is known as Network Address Translation.
Based upon the way your network is configured, it could also be easy to simply connect your Tieline codec straight into your ADSL modem/router and get a public address in the router.
Private LAN IP Addresses
Automatically your Tieline codec will usually be instantly assigned a personal Ip whenever you hook it up to some typical router more than a LAN.
To transmit audio streams within the public internet you should utilize an open Ip allotted to you from your ISP (Isp).
An open Ip is much like your public phone number and enables you to definitely be contacted on the internet in exactly the same people dial your public phone number. They are available in two forms dynamic (DHCP) and static. Most ISPs assign an engaged public Ip automatically, which could frequently change without you knowing. This really is appropriate for any quick demo of the Tieline codec, however for a lasting installation you will have to request a lasting static public Ip.
When the Static Public Ip is owned by your online connection (router) in the studio you have to produce a outcomes of the general public Ip as well as your codec’s private Ip around the LAN. This really is known as Network Address Translation.
Based upon the way your network is configured, it could also be easy to simply connect your Tieline codec straight into your ADSL modem/router and get a public address in the router.
Private LAN IP Addresses
Automatically your Tieline codec will usually be instantly assigned a personal Ip whenever you hook it up to some typical router more than a LAN.
Private IP Addresses are connected with LANs and normally reside behind a firewall and aren’t visible to the web. They can be within the ranges: 10…1 – 10.255.255.255, 169.254.. – 169.254.255.255, 172.16.. – 172.31.255.255 and 192.168.. – 192.168.255.255 and therefore are assigned by network DHCP servers and routers.
These IP Addresses are usually assigned for any predefined period (referred to as a lease) from your network’s DHCP server or router. This Ip will normally expire following the lease period. DHCP assigned IP Addresses might also change when the system is disconnected for extended periods or maybe capacity to the unit is switched off and back on. Consequently, it’s advised that you simply get this to Ip permanent by assigning it as being a Static DHCP Ip. This can ensure you’ll be able to always forward incoming audio packets for your codec utilizing the same private Ip in the studio using port forwarding (begin to see the section on port forwarding for more information). Talk to your Network Administrator if you’re unsure how to get this done.
Network Address Translation (NAT)
Network Address Translation (NAT) is a technique of connecting multiple devices to the web one public Ip.
The easiest method to explain NAT is by using the instance of the telephone system in an office which has one public phone number and multiple extensions. This kind of telephone system enables individuals to phone you on one public phone number and performs the translation and routing from the public number to particular private extension. Similarly, to be able to get an IP call from the remote codec within the public internet, exactly the same network address translation principle applies. NAT and port forwarding enables just one device, like a broadband router, to do something being an agent between your public internet along with a local private LAN.
The connection between private and public IP addresses and NAT is displayed within the following diagram and also the following section explains port forwarding configuration in greater detail.
Port Forwarding: Tieline TCP and UDP Port Settings
For the Tieline Codec to speak within the public internet an Ip alone isn’t sufficient. In TCP/IP and UDP systems the codec port may be the endpoint of the connection. Ports are doorways for IP devices to talk with one another. Picture a home and picture the leading door may be the access point symbolized with a private or public Ip. Then you need to reach several codecs in various rooms of the identical house and ports represent the doorways to every of individuals rooms. In principle this is the way port addressing works.
For instance, several codecs may dial to your studio utilizing the same public static Ip. In cases like this it’s important to configure codec ‘programs’ with audio streams using different audio ports for discretely routing each outgoing and incoming audio stream. Using this method your studio’s network routers know where IP packets for every audio stream ought to be routed, i.e. that codec and particular audio outputs.
When data packets are caused by remote codecs in a particular public Ip, port details are converted from data packets to guarantee the correct packets are delivered to the right studio codecs. This method is conducted by PAT (Port Address Translation), that is a feature of NAT (Network Address Translation) devices.
Tieline codecs use TCP ports for establishing the communication session and UDP ports for streaming audio. While TCP ports are usually open, UDP ports are usually blocked by network devices that have firewalls and can prevent you delivering your audio. With respect to the codecs you use, you have to configure your firewall to permit TCP and UDP protocols to feed the ports indexed by the table below.
Resourse: http://tieline.com/manuals/TLR5200D/en/v2_14/
