Matches in DBpedia 2016-04 for { <http://wikidata.dbpedia.org/resource/Q17153880> ?p ?o }
Showing triples 1 to 24 of
24
with 100 triples per page.
- Q17153880 subject Q17484813.
- Q17153880 abstract "NAT traversal with session border controllers network address translators (NAT) are used to overcome the lack of IPv4 address availability by hiding an enterprise or even an operator’s network behind one or few IP addresses. The devices behind the NAT use private IP addresses that are not routable in the public Internet.The Session Initiation Protocol (SIP) has established itself as the de facto standard for voice over IP (VoIP) communication. In order to establish a call, a caller sends a SIP message, which contains its own IP address. The callee is supposed to reply back with a SIP message destined to the IP addresses included in the received SIP message. This will obviously not work if the caller is behind a NAT and is using a private IP address.Probably the single biggest mistake in SIP design was ignoring the existence of NATs. This error came from a belief in IETF leadership that IP address space would be exhausted more rapidly and would necessitate global upgrade to IPv6 and eliminate the need for NATs. The SIP standard has assumed that NATs do not exist, an assumption, which turned out to be a failure. SIP simply didn't work for the majority of Internet users who are behind NATs. At the same time it became apparent that the standardization life-cycle is slower than how the market ticks: Session Border Controllers (SBC) were born, and began to fix what the standards failed to do: NAT traversal.In case a user agent is located behind a NAT then it will use a private IP address as its contact address in the contact and via headers as well as the SDP part. This information would then be useless for anyone trying to contact this user agent from the public Internet.There are different NAT traversal solutions such as STUN, TURN and ICE. Which solution to use depends on the behavior of the NAT and the call scenario. When using an SBC to solve the NAT traversal issues the most common approach for SBC is to act as the public interface of the user agents. This is achieved by replacing the user agent’s contact information with those of the SBC.".
- Q17153880 thumbnail SBC_NAT_Call_Handling.jpg?width=300.
- Q17153880 wikiPageWikiLink Q11103.
- Q17153880 wikiPageWikiLink Q11135.
- Q17153880 wikiPageWikiLink Q11182.
- Q17153880 wikiPageWikiLink Q11186.
- Q17153880 wikiPageWikiLink Q1148274.
- Q17153880 wikiPageWikiLink Q1332614.
- Q17153880 wikiPageWikiLink Q1638883.
- Q17153880 wikiPageWikiLink Q17484813.
- Q17153880 wikiPageWikiLink Q191018.
- Q17153880 wikiPageWikiLink Q2067513.
- Q17153880 wikiPageWikiLink Q217082.
- Q17153880 wikiPageWikiLink Q2551624.
- Q17153880 wikiPageWikiLink Q321213.
- Q17153880 wikiPageWikiLink Q428933.
- Q17153880 wikiPageWikiLink Q581558.
- Q17153880 wikiPageWikiLink Q61694.
- Q17153880 wikiPageWikiLink Q81945.
- Q17153880 wikiPageWikiLink Q952898.
- Q17153880 comment "NAT traversal with session border controllers network address translators (NAT) are used to overcome the lack of IPv4 address availability by hiding an enterprise or even an operator’s network behind one or few IP addresses. The devices behind the NAT use private IP addresses that are not routable in the public Internet.The Session Initiation Protocol (SIP) has established itself as the de facto standard for voice over IP (VoIP) communication.".
- Q17153880 label "NAT traversal with session border controllers".
- Q17153880 depiction SBC_NAT_Call_Handling.jpg.