In this section:
Use this object to edit the fields directly under Signaling.
On the SBC main screen, navigate to All > Global > Signaling.
The Signaling window displays.
Edit Signaling
In the Edit Signaling pane, edit the values of the parameters and flags.
Edit Signaling
Global - Signaling - Edit Signaling
| Field | Description |
|---|---|
| Teams Support | Enable this flag to configure SIP Signaling for interfacing with MS Teams. NOTE: When you enable this global control, the SBC sends out both SDES and DTLS in the offer, if both are enabled in the Packet Service Profile. This might only be required if there is a Microsoft Teams client running in a browser.
|
| Max Num Transfers | Specifies the maximum number of transfers (10-100) that the SBC allows within a call; default is 10. |
| SIP IP Peer Stats | Enable this flag to configure support for SIP IP Peer Statistics in the SBC.
|
| Old Gsx Support | The SBC is enhanced with a configurable parameter to indicate a legacy meshed network exists on the GW-GW links. This ensures the size of a message to send to older GSXs or remote pre-9.1 SBCs does not exceed the supported size of the remote GW. Any SBC - running 9.1 or higher version - passes information about the maximum size GW message it can support in the initial GW link setup handshake. The SBC sending the GW message will now release the call with a 500 error response, if the size of the message to be sent is larger than can be supported by the remote GW. When the flag is enabled, the SBC reduces the maximum size of the PDUs sent over a GW-GW connection to a GSX to prevent the PDU sizes from becoming larger than the buffer size allocated on the GSX, which can cause crashes on the GSX. When changing this control, the GW-GW links need to be restarted in order for it to take effect. This functionality also applies to a remote pre-9.1 SBC.
|
Overview
Content Tools