In this section:
This section specifies the Ingress Flag parameters for both H323 and SIP Trunk Groups.
On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Signaling Profile > Ingress Ip Attributes > Flags. The Flags window is displayed.
On the Flags window, choose the Ip Signaling Profile as DEFAULT_H323 to view the Flags for H323 Trunk Group.
The following fields are displayed:
Parameter | Description |
---|---|
Convert Progress To Alert | Set this flag to convert Progress messages to Alert messages when communicating to endpoints that have difficulty with Progress messages. The options are:
|
Dont Send Facility Message | Set this flag to prevent sending Facility messages to endpoints that do not tunnel and have difficulty processing Facility messages. The options are:
NOTE: Enabling this flag on the ingress leg may result in no media establishment for H.323 calls with discrete H.245 (no H.245 tunneling) due to H.245 socket collision. To avoid this issue, either disable this flag or ensure the H.245 signaling port address (actual hex value) associated with this setting is greater than its peer. |
Refuse Fast Start Proposal | When this flag is set, SBC does not include FastStart proposal in early media calls. Instead, it relies on H.245 procedure to complete media setup. When cleared, SBC always includes fast start proposal in SETUP message for early media calls. The options are:
|
Send Fast Start Response In Cp | When this parameters is used, the SBC sends a FastStart response message in Call Proceeding messages. The options are:
|
On the Flags window, choose the Ip Signaling Profile as DEFAULT_SIP to view the Flags for SIP Trunk Group.
The following fields are displayed:
Parameter | Description |
---|---|
Sip181Supported | Enable flag to allow the SBC to support 'SIP 181 Call Is Being Forwarded' messages in the backward direction on the ingress trunk group. The options are:
|
Sip182Supported | Enable flag to allow the SBC to support SIP 182 Queued messages in the backward direction on the ingress trunk group. The options are:
|
Map Called Party Category In PSig Info Header | Enable flag to map Called Party Category parameter to outgoing SIP P-Sig-Info header. The P-Sig-Info header is a customer-specific SIP header used to convey ISUP information in SIP messages. The options are:
|
No Sdp In 180 Supported | By default, the SBC includes SDP in outbound 180 messages. When enabled, the SBC does not include SDP in outbound 180 messages. It converts the 180 message to a 183 message instead. When disabled the SBCincludes SDP in outbound 180 messages. The options are:
|
Registration Expires in Expires Header | Controls what the SBC signals back to a peer when it has received a REGISTER message from that peer. When enabled, SBCinserts the Expires header in the message. When disabled, SBCdoes not insert the Expires header. The options are:
|
Send183On Initiating Disconnect Treatment | Enable flag to send a 183 message on initiating a disconnect treatment. The options are:
|
Send Sdp In200Ok If18x Reliable | Enable flag to send SDP in final 200 OK response messages when provisional 18x responses are reliable. The options are:
This flag only applies to 200 OK sent for an early offer. |
Send Sdp In Subsequent18x | Enable flag to send SDP in subsequent 18x response messages. When disabled, the SBCmay not send SDP in subsequent 18x response messages. The options are:
|
Send TLSConnection Failure Response | Enable flag to report TLS connection failure and respond with '408 Request timeout' message and Warning header instead of '504 Server timeout'. The options are:
|
Supress 183For3xx Redirect Response | Do not send 183 without SDP upon receiving 3xx Redirect Response. The options are:
|
Supress 183Without Sdp | Never send 183 without SDP. The options are:
See SDP Support topic for details of |
Set-cut-through-indication-in-OBCI | Enable flag to set the BIT-H of BCI parameters in the outgoing 18x message to allow the node to temporarily halt call set-up and play tones or announcements, or both, and collect additional in-band information from the calling user before routing the call further. The options are:
|
Send Updated SDPin200Ok | Enable this flag to send any SDP update before the answer (i.e., when the SDP changes between the last response sent and a 200 OK) on the ingress side in the 200 OK without using a reInvite. An SDP update is required at the ingress side if any change occurs in the SDP between 18x and 200 OK on the egress leg.
|
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.