Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The NAT Direct Media Group is a collection of public signaling IP addresses for NAT devices supporting Direct Media (DM). A NAT Direct Media Group name can be maximum of 32 characters; however. However, "0.0.0.0" (IPv4) and "::0" (IPv6) are not allowed.

...

To allow Direct Media between NAT devices, or between NAT and Non-NAT devices, the following configuration is necessary.

  • Enable directMediaAllowedBehindNAPT and DM flags at the Trunk Group level.
  • For Direct Media between endpoints behind same NAT, ensure the signaling IPs of the endpoints match.
  • For Direct Media across NAT devices, or from NAT to Non-NAT (Hybrid Networks), configure/group the Signaling IPs of the NAT or Non-NAT device (for Hybrid networks) in the new NAT Direct Media Group table at the Address Context level.

Direct Media is disallowed under following conditions:

  • One or both endpoints are behind NAT and directMediaAllowedBehindNAPT flag is disabled.
  • If directMediaAllowedBehindNAPT flag is enabled and Signaling IPs of the NAT devices do not match.
  • Signaling IPs of the NAT or Non-NAT (for Hybrid Networks) devices are not grouped in the same NAT Direct Media Group Table.
  • Address Context name of both endpoints do not match.
  • If the call is a Lawful Intercept call.
Note

The configuration of Direct Media with NAT is not allowed under following conditions:

  • If the addressContext name of both the endpoints does not match.
  • If the call is a Lawful Intercepted call.

Anchor
Configuration for Direct Media Between Endpoints Behind Same NAT
Configuration for Direct Media Between Endpoints Behind Same NAT
Configuring Direct Media Between Endpoints Behind the Same NAT

ACCESS SIDE:

  • At Sip Trunk Group Level
    • directMediaAllowed enabled
    • directMediaAllowedBehindNat enabled
  • At Packet Service Profile Level
    •  useDirectMedia enabled

CORE SIDE (towards Application Server):

  • At IPSP Level
    • sendDirectMediaInfoInSdpAttribute enabled
  • At Packet Service Profile Level
    • useDirectMedia enabled
Note

The dmNatPrefix table is not required to create as the endpoints are behind the same NAT.

Anchor
Configuration for Direct Media Between Endpoints Behind Different NAT
Configuration for Direct Media Between Endpoints Behind Different NAT
Configuring Direct Media Between Endpoints Behind the Different NAT

 ACCESS SIDE:

  • At Sip Trunk Group Level
    • directMediaAllowed enabled
    • directMediaAllowedBehindNat enabled
    • sdpTransparencyState disabled
  • At Packet Service Profile Level
    • useDirectMedia enabled

CORE SIDE (towards Application Server):

  • At IPSP Level
    • sendDirectMediaInfoInSdpAttribute enabled
  • At Packet Service Profile Level
    • useDirectMedia enabled
  • At Address Context Level
    • Creating the table dmNatPrefix on addressContext
    • Adding the signaling IP Address of NAT Box, which can have direct media among them.

Anchor
Configuration for Direct Media Between Endpoints Behind NAT and Non-NAT Endpoint
Configuration for Direct Media Between Endpoints Behind NAT and Non-NAT Endpoint
Configuring Direct Media Between Endpoints Behind the NAT and Non-NAT Endpoint

This is an occasional scenario where an endpoint behind NAT can have Direct Media with endpoint not behind NAT. However, if such a case exists, SBC exchanges the media IPs of such devices, while the actual exchange of media depends on the network.

ACCESS SIDE:

  • At Sip Trunk Group Level
    • directMediaAllowed enabled
    • directMediaAllowedBehindNat enabled
    • sdpTransparencyState disabled
  • At Packet Service Profile Level
    • useDirectMedia enabled

CORE SIDE (towards Application Server):

  • At IPSP Level
    • sendDirectMediaInfoInSdpAttribute enabled
  • At Packet Service Profile Level
    • useDirectMedia enabled
  • At Address Context Level:
    • Creating dmNatPrefix on addressContext
    • Adding signaling IP Address of,
      • NAT Box
      • Endpoint signaling IP not behind NAT.

The CLI syntax to enable Direct Media with NAPT on trunk group is the following:

...

A flow diagram of this behavior is depicted in the figure below. Please see CLI Command Reference Guide for command details and examples.

...

Code Block
languagenone
% set addressContext default zone ZONE1 sipTrunkGroup PERFIPS_SBX_INT media sdpAttributesSelectiveRelay enabled 

For command details, see sipTrunkGroup media SIP Trunk Group - Media - CLI or SIP Trunk Group - Media (EMA) page.

...