Versions Compared

Old Version 6

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.

...

FieldDescription
Teams Local Media Optimization Microsoft Teams Direct Routing media flow uses the shortest path to improve the SBC Edge's media quality and bandwidth usage.
Signaling/Media Source IP

Specifies the Logical IP address at which SIP messages are received. This address is used as the source IP for all SIP messages leaving the

Spacevars
0series3
or SBC 1000/2000 through this Signaling Group. The physical interface on which these messages leave the system is determined by the System IP routing configuration. The IP version (IPv4 or IPv6) for the SIP Server used by this Signaling Group determines the IP version used for all outgoing messages leaving the SBC through this Signaling Group.

Info
titleNote

If Static NAT is used, the configured NAT Public IP replaces the Source IP selected or acquired when set to Auto mode. When the  Outbound NAT Traversal  field is set to  Static NAT, the name of the   Signaling/Media Source IP option changes to  Signaling /Media Private IP. 

Note
titleWarning

It is recommended to set the Signaling/Media Source IP to the actual Ethernet IP Interface that the Signaling group uses to ensure Signaling and Media flow correctly.


    • Auto: The node automatically selects the IP address used as the source address of all outgoing SIP messages leaving the SBC through this Signaling Group. The IP address is based on the physical interface selected by the IP routing configuration.
    • Ethernet IP: Allows you to select a specific source IP address for outgoing SIP messages through this Signaling Group.

Private Media Source IP The private IP address that handles routing of messages for media. This field is displayed only when  Teams Local Media Optimization  is enabled. Valid entry: select an IP address from the drop-down list. 
Signaling DSCP

Each SIP-SG is configurable with the DSCP value to be used for signaling. This allows for improved quality of service in real-time applications, such as conferencing and conversations. The settings take effect for both client and server modes of SIP. The default value of 40 is the most common value used in the VOIP networks for signaling packets. The configured value should be chosen according to the QoS policies of the IP network in which the signaling packets travel.

Valid entry range: 0 to 63 (inclusive). Default value: 40.

NAT Traversal

Specifies whether or not the Signaling Group uses a third-party entity IP address inside the SIP message to support network address translation (NAT). Only visible when NAT Traversal is set to Static NAT.

    • None: Specifies that network address translation is not used.
    • Static NAT: Specifies that network address translation is used.
Note

Symmetric NAT (port forwarding) is the only supported NAT type. This NAT configuration type means that packets received on a specific NAT server port are always forwarded to the same SBC port, for example, packets on the NAT public IP, port 5060 are forwarded to a private (SBC) IP, port 5060.


ICE Support

Specifies whether ICE support is enabled/disabled. Enable/disable is displayed only when SIP Mode is configured to Basic Call.

    • Disable: When the ICE Support option is disabled, the 
      Spacevars
      0product
       
      Spacevars
      0product
       does not support ICE for both incoming and outgoing calls. If ICE is disabled on a Signaling Group and if the incoming offer contains ICE, the 
      Spacevars
      0product
       responds with no ICE attributes in the SDP.
    • Enable: When ICE support option is enabled on the signaling group, 
      Spacevars
      0product
      allows SIP to propose ICE candidates in INVITE and 183/200 responses based on the call direction for that Signaling Group. If no candidate is proposed by the other side, the call proceeds as if ICE was not enabled.
Note

When Interactive Connection Establishment (ICE) support is enabled, it takes precedence over all other media related NAT configuration.


ICE Mode

Specifies the Interactive Connection Establishment (ICE) Mode that is enabled/disabled. This field is displayed only when ICE Support is enabled.

For SBC 1000/2000:

Two ICE Modes are available:

    • Full: The SBC operates as an ICE (full) agent endpoint.
    • Lite: The SBC operates as an ICE-Lite agent endpoint (for SIP calls involving NAT devices) with a full ICE agent in the role of controlling agent.   


For 
Spacevars
0series3
:
    • Lite: For the
      Spacevars
      0series3
      , only Lite mode is supported.       The SBC operates as an ICE-Lite agent endpoint (for SIP calls involving NAT devices) with a full ICE agent in the role of controlling agent. 
 
For details on ICE, refer to Working with the SBC Edge Portfolio as an ICE-Lite Agent and Working with the SBC Edge Portfolio as an ICE Agent.


Static NAT - Outbound

If the selected Outbound NAT Traversal is Static NAT, you must enter the field NAT Public IP (Signaling/Media) appears.

Static NAT - Inbound

Detection

Enables and disables NAT Traversal detection for inbound SIP/RTP packets.

    • When detection is disabled, none of the following fields are visible.
Qualified Prefixes TableSpecifies which SIP NAT Qualified Prefix Table to use in association with this SIP Signaling Group. The Qualified Prefixes Table is used to determine whether or not a particular subnet is behind a NAT device. If None is selected from the Qualified Prefixes Table drop-down list, then all subnets are treated as if they were behind a NAT device. The options available from this drop-down list are configured as part of NAT Qualified Prefixes. 
Secure Media LatchingEnables and disables Secure Media Latching for inbound RTP packets. When enabled, media latching occurs only if the RTP packet's IP is in the same subnet as the public IP seen by SIP signaling. When disabled, no IP address security checks are performed during RTP latching.
Source Media Netmask

Specifies the netmask used to compare the SIP Signaling IP and the RTP IP used for latching.

    • The Source Media Netmask field is present if Inbound NAT Transversal Detection and Secure Media Latching are enabled.
    • The netmask must be specified in dotted decimal format (e.g., 255.255.255.255).
Registrar Max. TTL EnabledEnables and disables the time to live (TTL) functionality for inbound registrants from behind a NAT. If a client registers with an expires value greater than the value specified in the Registry Max. TTL field, the expiration is adjusted to the value specified in the Registrar Max TTL field.
Registrar Max. TTL

Specifies a maximum time to live (TTL) for the SIP registration. The SBC uses this feature to determine that the client is still active, and aid in keeping bindings to remote NAT devices alive. If the SBC does not receive a request to re-register from the client before the expiry, the call and the registration are torn down.

    • Note that this field is only applicable to clients registering from behind NAT devices.
    • Setting the Max. TTL to a low duration may result in excessively high system resource usage as the number of NAT clients increases.
Application Layer IP

Specifies how the Signaling Group will select the local IP.

    • Auto: Means that the SBC connects to the peer and queries the local IP which is used in SIP headers and SDP.
    • Bind: Binds to a specified interface and uses that IP address (1st/2nd) in headers and SDP.
NAT Public IP Address

Specifies the public IP of the NAT server visible from Internet. The NAT server's ports must be configured to allow SIP and RTP traffic, for example: port range 5060-5061 for SIP and 16000-17000 for RTP.

The IP address specified in this field must be publicly accessible.

...