Page History
...
Parameter | Description | ||||||
|---|---|---|---|---|---|---|---|
| Set parameter to " When GIBA security mechanism is selected and Via header is configured to pass transparently to egress leg, SBC inserts a “received” parameter with the source IP address of the PDU if the host portion of the UE’s Via header does not equate to the source IP address seen by the SBC.
| ||||||
| Specifies if route validation should be done for the received message and if the message should be validated to ensure it is SIP-only or SIP-I. The call is released after invalidation if an invalid message type is received.
| ||||||
| Specifies the default value for the Max Forwards Header. The value ranges from 1 to 100 and the default value is 70. | ||||||
| If enabled, an INFO message will only be sent after confirmed Dialog.
| ||||||
| Enable flag to transparently relay (in egress SIP signaling) an ISUP mime body received in SIP signaling. When disabled, ISUP mime bodies are decoded and interworked based on the egress signaling configuration.
| ||||||
| Enable to allow option tag 100rel support for the reliability of provisional messages as specified in RFC3262.
| ||||||
| Enable (on Core network side) to parse and transparently pass “pref” SIP Option tag in incoming Require header of Register message. The “pref” option tag is used to publish and request support for RFC 3840 caller capabilities.
| ||||||
| Use this object to define SIP Privacy header parameter mapping (incoming to outgoing call).
| ||||||
Relay Non Invite request | Enable this flag to relay non-Invite requests.
| ||||||
Treat Port Zero as No Audio | Use this flag to control how audio portion of a call on port 0 is treated.
| ||||||
Relay Updatewith Sdp | This flag is used to relay UPDATE request with Offer immediately after receiving or sending answer in unreliable provisional responses. This flag is applicable only in case of interworking where one side supports reliable response (from where the UPDATE is received) and the other side does not (towards which it needs to be relayed). The options are:
| ||||||
| Specifies the inter-operator id (ioi) is a globally unique identifier shared between sending and receiving networks. The value ranges up to 23 characters. | ||||||
| Use this object to define URI presentation preference for outgoing messages.
| ||||||
| Enable this flag to reject requests which are understandable, but violate the relevant RFC Augmented Backus-Naur Form (ABNF) production rule.
| ||||||
| Enable flag to skip destination trunk group look-up on Route header when routing calls using Route headers received in a request. Egress IP trunk group is determined based on existing routing logic.
| ||||||
| Use this flag to determine "tgrp" parameter behavior.
| ||||||
Isub Param Preference | This trunk group attribute specifies how the ISDN Sub-Address parameter is handled in SIP.
| ||||||
Variant Type | Specifies the SIP variant type.
| ||||||
Factor Value | Enter the factor value to use to interwork the SIP Max-Forwards header and the ISUP Hop counter parameter. The value ranges from 1 to 50 and the default value is 1. | ||||||
Local Number Support | Enable this flag to allow P-CSCF to globalize. To hdr in Register,req URI in SUBSCRIBE for regevt and perform a PSX dip for non-INVITE for tel URI as well as control the dial string feature.
| ||||||
Disable Term IOIFor Pcscf | Enable this flag to prevent P-CSCF from adding “erm-ioi” parameter to any requests while creating P-Charging-Vector (PCV) header.
| ||||||
De Reg Parent With Child Dereg | Enable this flag to allow P-CSCF to delete parent RCB and all its childs during de-registration of any of the child IP Multimedia Public Identities (IMPUs).
| ||||||
Use PSXRoute As Req Uri in Reg | Enable this flag to allow P-CSCF to use the PSX returned route as the Request URI in the register.
| ||||||
Psx Route For Subscribe | Enable this flag to use PSX routes for routing OOD (Out-Of-Dialog) methods to registered users.
| ||||||
Default Calling Party Number | Specifies the default calling number for Caller Privacy feature. If the party number is configured and the flag msLyncPrivacySupport is enabled, the configured number is inserted as the user name of either the from header or the P-Asserted-Identity fields depending on the configuration. The value ranges up to 23 characters. | ||||||
Validate Aor | If enabled, the AoR must be validated. If disabled, calls from anonymous users or users whose AOR does not match with the one stored in SBC as part of RCB created during initial registration are allowed.
| ||||||
Source Address Validation | Enable this flag to support source address validation so that messages coming from a different IP address or port than expected are not allowed.
| ||||||
Cond Inc Meth in Allow Hdr | Enable this flag to use ingress message ALLOW header content in the egress message. Only methods which are configured as allowed at the egress TG are populated from ingress to the egress message. Methods with no configuration present are considered allowed (example: INVITE).
| ||||||
Flexible Policy Adapter Profile | Use this Zone/Trunk Group object to associate a If
| ||||||
Accept History Info | Enable this flag to accept History-Info header received on the ingress trunk group.
| ||||||
Egress Call Id Static String | String for generating the egress callid when configured option for egressCallIdType in PSX is "Use Static String". (default is a hyphen “-”). Egress Call-id is the aggregate of Ingress Call-id and locally generated string in SBC. | ||||||
Allow Bye Challenge | This flag enables the Bye-Challenge feature. When this flag is enabled, the BYE's might get challenged either by 401 or 407 and the call is released only when the BYE with appropriate credentials are received.
| ||||||
Enforce Tls if Sips Uri Scheme | Enable this flag to enforce using TLS to egress a request if the Request-URI/topmost Route header uses “sips” scheme on a per-peer group basis.
| ||||||
Enforce Sips if Egress is Tls | Enable this flag to change the URI scheme as described below.
| ||||||
Use Psx Route For Emergency Call | Enable this flag to allow SBC to use PSX returned Route instead of stored-service route information for processing Emergency calls from Registered users.
| ||||||
Ocs Support | Enable this flag to enable OCS (Office Communications Server, a.k.a MS Lync) support.
| ||||||
Relay Replaces Header | When enabled, P-CSCF relays Replaces header with INVITE.
| ||||||
Feid for PDCS | The FEID value sent out in egress PDCS-Billing-Info header when sendiing JIP value in PDCS header. FEID consists of hexadecimal string of up to 16 characters followed by a domain name (for example, abc1234@98.245.153.111). The value ranges up to 127 characters. | ||||||
Send Sdp to Psx | Enable flag to pass the SDP information to the PSX (excluding data up to the first occurrence of m-line).
| ||||||
Use GAPwhen Rn Disabled | Enable this flag to cause the SBC to populate the GAP/OCN in the R-URI and To headers at the egress Trunk Group. This flag is valid only when the egress profile flag "
| ||||||
Support199Option Tag | Enable flag to include Option tag in Supported Header for the 199 Extension.
| ||||||
Keep Support | Enable flag to support the keep-alive mechanism (RFC 6223).
| ||||||
Outbound Support | Enable flag to support outbound procedures specified in RFC 5626.
| ||||||
Silence Supp Treatment | Use this parameter to specify whether call is transitioned to fax or voice call when "silenceSupp:off" received in re-INVITE.
A call is considered a fax call when Packet Service Profile
| ||||||
Rfc3261Validate CSeq In BYE | When this flag is enabled, the SBC sends a 500 (Server Internal Error) response upon receipt of a BYE when CSeq is a lower value than the preceding INVITE request (as per RFC 3261).
| ||||||
Rfc3261Validate Invite200Ok Retransmissions | When this flag is enabled, the SBC starts a timer for 64 * T1 (32 seconds) upon receiving a 200 OK to an INVITE. The SBC does not acknowledge re-transmitted 200 OK to an INVITE after the timer expiry. When this flag is disabled, the SBC continues to acknowledge retransmitted 200 OKs (as per RFC 3261).
| ||||||
Use Random User Info In Contact Hdr | Enable flag to use randomly-generated value as UserInfo in contact header. The options are:
| ||||||
Suppress Non Route Invite Response | If enabled, response for non-route invite is suppressed. The options are:
| ||||||
Use Pcfa Ccf | If enabled, SBC uses CCF received in PCFA as CDF. The options are:
| ||||||
Honor Maddr Param | Enable this flag to allow SBC to process (and make routing decisions) the
The following behavior is supported with this feature:
| ||||||
Rewrite Identities |
When this parameter is disabled for egress trunk group, SBC does not update the originating and terminating identities in outbound SIP message as per policy response from PSX.
When this parameter is enabled, for egress trunk group, SBC updates the originating and terminating identities in outbound SIP message as per policy response from PSX.
| ||||||
Transit IOI | Use this parameter to specify a Transit IOI value for for inclusion in the P-Charging-Vector header. This parameter must be configured on the Trunk Group facing the transit network and the configured value is inserted on the other leg in case of an egress message. (see P-Charging-Vector Header for additional details) | ||||||
Use Port Range Flag | Enable this flag to allow the usage of different IP-Port as contact for each active registration towards Cisco Unified Communication Manager (CUCM). The SBC uses either an independent media port range configured per IP Trunk Group (IPTG), or a new port from the system-wide media port range if no independent media port range is configured per IPTG. The options are:
SBC supports this feature when:
Feature limitations and restrictions:
| ||||||
Store ICID | Enable this flag to allow SBC to retain the same ICID value generated in the first egressed INVITE for the crankback/redirect (3xx) call in the P-Charging-Vector header of the egressed INVITE. The options are:
| ||||||
Clear TCP Connectionsfor Registration | Enable flag to clear the TCP connection between UE and SBC once the registration becomes inactive. The SBC clears (closes) the TCP connection even when there are user agent failure registrations. When this flag is disabled, the SBC relies on the UE to clear the TCP connection between the two If the registration becomes inactive.
|
...
Overview
Content Tools