{"id":7495,"date":"2025-08-29T22:02:12","date_gmt":"2025-08-29T22:02:12","guid":{"rendered":"https:\/\/wiki.xontel.com\/?post_type=manual_documentation&#038;p=7495"},"modified":"2026-08-15T12:47:11","modified_gmt":"2026-08-15T12:47:11","slug":"nat","status":"publish","type":"manual_documentation","link":"https:\/\/wiki.telsip.com\/ar\/documentation\/telsip-platform\/telsip-cloud-pbx\/pbx-v-1-x-x\/pbx\/nat\/","title":{"rendered":"NAT"},"content":{"rendered":"<p class=\"wp-block-paragraph\">In cloud-based PBX deployments, <strong>Network Address Translation (NAT)<\/strong> is a key factor in ensuring seamless communication between private internal networks and external public networks. As most enterprise environments operate behind firewalls and NAT devices, effective NAT handling is essential for maintaining reliable signaling and uninterrupted media flow in <strong>VoIP<\/strong> and <strong>WebRTC<\/strong> sessions. <strong>Telsip Cloud PBX<\/strong> implements NAT traversal mechanisms to preserve call quality and ensure consistent connectivity, even when endpoints are situated behind routers or firewalls.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large image-border\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"303\" src=\"https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/08\/nat-1024x303.jpg\" alt=\"\" class=\"wp-image-8787\" srcset=\"https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/08\/nat-1024x303.jpg 1024w, https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/08\/nat-300x89.jpg 300w, https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/08\/nat-768x227.jpg 768w, https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/08\/nat-1536x455.jpg 1536w, https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/08\/nat-18x5.jpg 18w, https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/08\/nat.jpg 1861w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\" style=\"font-size:25px\"><strong><strong>NAT Configuration<\/strong><\/strong><\/p>\n\n\n\n<figure class=\"wp-block-image size-large image-border\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"484\" src=\"https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/04\/nat2-1024x484.png\" alt=\"\" class=\"wp-image-2397\" srcset=\"https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/04\/nat2-1024x484.png 1024w, https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/04\/nat2-300x142.png 300w, https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/04\/nat2-768x363.png 768w, https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/04\/nat2-600x284.png 600w, https:\/\/wiki.telsip.com\/wp-content\/uploads\/2025\/04\/nat2.png 1061w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The NAT configuration defines how the PBX identifies its public address and local networks during SIP communication.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Enable NAT<\/strong>: Enables NAT handling for SIP and media traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>External IP<\/strong>: Defines the public IP address used by external SIP endpoints and providers to reach the PBX.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>Local Networks<\/strong><\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">The Local Networks area defines the private network ranges that should be treated as internal networks by the PBX. These entries help the system determine whether SIP endpoints are located inside the local network or connecting from an external network.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>","protected":false},"excerpt":{"rendered":"<p>In cloud-based PBX deployments, Network Address Translation (NAT) is a key factor in ensuring seamless communication between private internal networks and external public networks. As most enterprise environments operate behind firewalls and NAT devices, effective NAT handling is essential for maintaining reliable signaling and uninterrupted media flow in VoIP and WebRTC sessions. Telsip Cloud PBX [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":7440,"menu_order":7,"template":"","manualdocumentationcategory":[45],"manual_doc_tag":[],"class_list":["post-7495","manual_documentation","type-manual_documentation","status-publish","hentry","manualdocumentationcategory-telsip"],"_links":{"self":[{"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/manual_documentation\/7495","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/manual_documentation"}],"about":[{"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/types\/manual_documentation"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/users\/3"}],"version-history":[{"count":6,"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/manual_documentation\/7495\/revisions"}],"predecessor-version":[{"id":9326,"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/manual_documentation\/7495\/revisions\/9326"}],"up":[{"embeddable":true,"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/manual_documentation\/7440"}],"wp:attachment":[{"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/media?parent=7495"}],"wp:term":[{"taxonomy":"manualdocumentationcategory","embeddable":true,"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/manualdocumentationcategory?post=7495"},{"taxonomy":"manual_doc_tag","embeddable":true,"href":"https:\/\/wiki.telsip.com\/ar\/wp-json\/wp\/v2\/manual_doc_tag?post=7495"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}