| Panel |
|---|
| borderColor | green |
|---|
| bgColor | transparent |
|---|
| borderWidth | 2 |
|---|
|
Additional sections: |
| Panel |
|---|
On In this pagesection:
|
...
- The "private" addressing local to the SIP peer is different from the "public" addressing uses to reach the peer through the NAPT device. Consequently, addressing information that SIP peer embeds within signaling messages is insufficient for routing purposes and the needs an alternate means of determining the appropriate destination IP address/port.
- Pinholes must be open in the NAPT device to exchange signaling and media between the and the SIP peer. Otherwise, any "unsolicited" packets the sends towards the SIP peer are dropped by the NAPT device. The implication for both signaling and media is that the must first receive packets from a SIP peer located behind a NAPT device before it can send packets to such a peer. (see refer to Adaptive NAT Pinhole Timer).
| Include Page |
|---|
| No_NAT_for_IPv6 |
|---|
| No_NAT_for_IPv6 |
|---|
|
Signaling Traversal
For the signaling aspect, the
supports a SIP registration relay service. No special support from the user endpoint/IAD is required for this method of NAPT traversal. REGISTER messages provide the
with a means for learning the destination IP address/port for signaling to the peer - the NAPT'd public source address/port in the IP header becomes the nexthop to reach the SIP peer's registered contact address. The
can then learn the addressing information embedded in SIP signaling messages accordingly.
...
| Code Block |
|---|
|
% set addressContext <name> zone <name> sipTrunkGroup <name> services natTraversal mediaNat <disable | enable> |
See Refer to Zone - SIP Trunk Group - CLI for CLI command details for these two flags.
...