In this section:



This section lists CLI commands to configure ingress IP attributes.

Command Syntax

% set profiles signaling ipSignalingProfile <SIP profile name> ingressIpAttributes 
	carrierInformation 
		generateTerminatingCa <disable | enable> 
		generateTerminatingCic <disable | enable> 
	flags 
		mapCalledPartyCategoryInPSigInfoHeader <disable | enable> 
		noSdpIn180Supported <disable | enable> 
		registrationExpiresinExpiresHeader <disable | enable> 
		send183OnInitiatingDisconnectTreatment <disable | enable> 
		sendSdpIn200OkIf18xReliable <disable | enable> 
		sendSdpInSubsequent18x <disable | enable> 
		sendTLSConnectionFailureResponse <disable | enable>
		sendUpdatedSDPin200Ok <disable | enable>
		set-cut-through-indication-in-OBCI <disable | enable>
		sip181Supported <disable | enable> 
		sip182Supported <disable | enable>
		suppress183For3xxRedirectResponse <disable | enable>
		suppress183WithoutSdp <disable | enable>
	ingressHistoryInformation
		supportRFC7044Ingress <disable | enable>
		applyHistoryInfoPrivacyIngress <disable | enable>

Command Parameters

The IP Signaling Profile SIP Ingress IP Attributes are shown below:

IP Signaling Profile SIP Ingress IP

Parameter

Description

carrierInformation

Indicates the carrier information parameters. The options are

  • generateTerminatingCa – Use this flag on the ingress SIP side to decide whether to interwork the terminating CA data from ISUP to SIP 18x messages. When enabled, the SBC maps the terminating CA data from ISUP to SIP 18x messages. When disabled, the SBC does not map the terminating CA data from ISUP to SIP 18x messages.
    • disable (default)
    • enable
  • generateTerminatingCic – Use this flag on the ingress SIP side to decide whether to interwork the terminating CIC data from ISUP to SIP 18x messages. When enabled, the SBC maps the terminating CIC data from ISUP to SIP 18x messages. When disabled, the SBC does not map the terminating CIC data from ISUP to SIP 18x messages.
    • disable (default)
    • enable

flags

  • mapCalledPartyCategoryInPSigInfoHeader – Enable this flag to map Called Party Category parameter to  theoutgoing SIP P-Sig-Info header. The P-Sig-Info header is a customer-specific SIP header used to convey ISUP information in SIP messages.
    • disable (default)
    • enable
  • noSdpIn180Supported – By default, the SBC includes SDP in outbound 180 messages. When enabled, the SBC does not include SDP in the outbound 180 messages. It converts the 180 message into a 183 message instead. When disabled, the SBC includes SDP in outbound 180 messages.
    • disable (default)
    • enable
  • registrationExpiresinExpiresHeader – Controls what the SBC signals back to a peer when it has received a REGISTER message from that peer. When enabled, SBC inserts the Expires header in the message. When disabled, SBC does not insert the Expires header.
    • disable (default)
    • enable
  • send183OnInitiatingDisconnectTreatment – Enable this flag to send a 183 message on initiating a disconnect treatment.
    • disable (default)
    • enable
  • sendSdpIn200OkIf18xReliable – Enable this flag to send SDP in final 200 OK response messages when provisional 18x responses are reliable.
    • disable (default)

    • enable

      NOTE:  This flag only applies to 200 OK sent for an early offer.

  • sendSdpInSubsequent18x – Enable the flag to allow the SBC to send SDP in subsequent 18x response messages after it sends the answer in non-reliable provisional response (until it is sends in reliable 18x message) to the INVITE. When disabled, the SBC does not send SDP in the subsequent 18x response messages.
    • disable (default)
    • enable
  • sendTLSConnectionFailureResponse -- Enable this flag to report TLS connection failure and respond with '408 Request timeout' message and Warning header instead of '504 Server timeout'.
    • disable (default)
    • enable
  • sendUpdatedSDPin200Ok – Enable this flag to send any SDP update before the answer (That is when the SDP changes between the last response sent and a 200 OK) on the ingress side in the 200 OK without using a re-INVITE. If there is any change in the SDP between 18x and 200 OK on the egress, then a SDP update is required at the ingress side.
    • disable (default) – The SBC sends the last sent SDP in 200 OK and updates it using re-INVITE.
    • enable – The SBC sends updated SDP on the ingress side in 200 OK for INVITE. This option avoids such issues as when the INVITE/re-INVITE gets challenged for authentication or when the endpoints change SRTP keys for every new SDP offer.

  • 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.

    • disable (default)

    • enable

  • sip181Supported – Enable this flag to allow the SBC to support 'SIP 181 Call Is Being Forwarded' messages in the backward direction on the ingress trunk group.

    • disable (default)
    • enable
  • sip182Supported -- Enable this flag to allow the SBC to support SIP 182 Queued messages in the backward direction on the ingress trunk group.
    • disable (default)
    • enable
  • suppress183For3xxRedirectResponse – Do not send 183 without SDP upon receiving 3xx Redirect Response.
    • disable (default)
    • enable

  • suppress183WithoutSdp – Never send 183 without SDP.

    • disable (default)
    • enable

NOTE: Refer to SDP Support for details of suppress183For3xxRedirectResponse and suppress183WithoutSdp behavior.

ingressHistoryInformation
  • ingressHistoryInformation – Enable this flag to set the History-Info header's behavior in accordance with RFC-7044 towards the Ingress leg.
    • disable (default)
    • enable
  • applyHistoryInfoPrivacyIngress – Enable this flag to anonymize the History-Info header towards the Ingress leg.
    • disable (default)
    • enable


Command Examples

Configuring SIP Over TCP


To learn more about the various methods of controlling transport protocols for SIP signaling and how these work together, refer to Controlling SBC Core Transport Protocols for SIP Signaling.


To configure SIP over TCP:

  1. Assign this IP signaling profile to SIP trunk group(s):

    % set addressContext a1 zone EXTERNAL sipTrunkGroup EXT_NET policy signaling ipSignalingProfile SIP_IPSIGPROF

  2. If ipSignalingProfile is not configured for any transport protocols (if transport type1 is "none"), SIP call over TCP can be forced by configuring the transport preference on egress sipTrunkGroup.

    % set addressContext a1 zone EXTERNAL sipTrunkGroup EXT_NETWORK signaling transportPreference preference 
Possible completions: 
preference1 - This first choice of transport protocol for SIP calls. 
preference2 - This second choice of transport protocol for SIP calls. 
preference3 - This third choice of transport protocol for SIP calls. 
preference4 - This fourth choice of transport protocol for SIP calls.

  3. Select TCP.

     % set addressContext a1 zone EXTERNAL sipTrunkGroup EXT_NETWORK signaling transportPreference preference1 tcp 

Configuring SIP Over TLS

  1. Configure client and server profiles:

    1. Generate server certificate and show status.

      % set system security pki certificate server fileName server.p12 passPhrase gsx9000 type local state enabled 
> show status system security pki certificate 
certificate server { 
	encoding pkcs12; 
	status success; 
}

    2. Generate client certificate and show status. Both client and server certificates display.

       % set system security pki certificate client fileName clientCert.der type remote state enabled 
 > show status system security pki certificate 
certificate client { 
	encoding der; 
	status success; 
} 
certificate server { 
	encoding pkcs12; 
	status success; 
}

  2. Assign the installed certificates to the TLS profile:

    % set profiles security tlsProfile defaultTlsProfile serverCertName server clientCertName client 
% commit

  3.  Assign TLS to the SIP signaling ports:

    % set addressContext a1 zone ZONE1 sipSigPort 1 mode outOfService state disabled 
% commit 
% set addressContext a1 zone ZONE1 sipSigPort 1 tlsProfileName defaultTlsProfile 
% commit 
% set addressContext a1 zone ZONE1 sipSigPort 1 mode inService state enabled 
% commit 
% set addressContext a1 zone ZONE2 sipSigPort 2 mode outOfService state disabled 
% commit 
% set addressContext a1 zone ZONE2 sipSigPort 2 tlsProfileName defaultTlsProfile 
% commit 
% set addressContext a1 zone ZONE2 sipSigPort 2 mode inService state enabled 
% commit

  4. Associate IP Signaling Profiles with TLS over TCP:

    % set profiles signaling ipSignalingProfile IPSP_1 
% commit 
% set profiles signaling ipSignalingProfile IPSP_1 egressIpAttributes transport type1 tlsOverTcp 
% commit 
% set profiles signaling ipSignalingProfile IPSP_2 
% commit 
% set profiles signaling ipSignalingProfile IPSP_2 egressIpAttributes transport type1 tlsOverTcp 
% commit
  5. Associate SIP Trunk Groups to IP Signaling Profiles:
% set addressContext a1 zone ZONE1 sipTrunkGroup SIP_TG1 policy signaling ipSignalingProfile IPSP_1 
% commit 
% set addressContext a1 zone ZONE2 sipTrunkGroup SIP_TG2 policy signaling ipSignalingProfile IPSP_2
% commit