Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

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

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9b90306, userName='null'}
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cca00892, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c749000c, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c95e0269, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ccd408f2, userName='null'}

Panel

In this section:

Table of Contents
maxLevel4

Info
iconfalse

Related articles:

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

  • Configuring Direct Media Between Endpoints Behind Same NAT
  • Configuring Direct Media Between Endpoints Behind Different NAT
    • Configuring Direct Media Between Endpoints Behind NAT and Non-NAT Endpoint

    Table of Contents
    maxLevel4

    Note
    titleCaution

    Direct Media with NAT will not work under following conditions:

    • If the addressContext name of both the endpoints does not match.If the call is a Lawful Intercepted call.
    • If Direct Media Group ID's do not match , directMediaGroupId should be same (Ensure the directMediaGroupId is identical on both the Trunk Groups.)
    • For a Lawful Intercepted call


    Multiexcerpt include
    MultiExcerptName_sip_direct_media_note
    PageWithExcerpt_SIP_Direct_Media_Note

    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 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 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 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 as follows:

    Code Block
    % set addressContext <name> zone <name> sipTrunkGroup <TG-Name> media directMediaAllowedBehindNapt <disable|enable>

    The CLI syntax to group the endpoint signaling IP addresses for which to allow Direct Media with NAPT is as follows:

    Code Block
    % set addressContext <name> natDirectMediaGroup <groupName> dmNatPrefix <IpV4_Address> <prefixLen>


    Related articles:

    Children Display