Versions Compared

Old Version 6

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 7

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ParameterDescription
addLoopBackRouteHeader

Enable flag to add the SBC URI as the second top-most Route header in the INVITE towards EATF.

  • disable (default)
  • enable
bgcfTargetSchemeTransparencyEnable flag to preserve the scheme used by the SIP INVITE Request-URI when the INVITE is routed by the
Spacevars
0product
, acting as a BGCF supporting Tel-URL. When disabled, the SBC changes the scheme used by the Request-URI parameter to SIP in the egress INVITE message.
  • disable (default)
  • enable
convertInactiveToSendrecvEnable flag to control the a-line in the SDP of an egress SIP INVITE message by converting a=inactive to a=sendrecv. When disabled, the 
Spacevars
0product
continues to use a=inactive, when appropriate, in the egress INVITE message.
  • disable (default)
  • enable
disable2806Compliance

If enabled, the 2806 Compliance Code is disabled and no phone context or user=phone parameters are signaled in egress messages.

  • disable (default)
  • enable
disableOptionalRegisterParametersEnable flag to prevent 
Spacevars
0product
from sending the DTG (Destination Trunk Group) parameter in the Contact header of egress REGISTER messages.
  • disable (default)
  • enable
ignoreSdpAfterOfferAnswerCompletedEnable flag to allow the SBC to ignore the new SDP at the egress leg in subsequent 1xx-rel or final 200 OK messages after the Offer Answer for the initial Invite dialog was completed by an earlier 1xx-rel (and does not trigger a new offer or answer).
  • disable (default)
  • enable
includeEnumParametersUse this flag to specify how to handle ENUM parameters in outgoing INVITE.
  • disabled (default) – SBC drops ENUM parameters received from ENUM server.
  • enabled – SBC sends ENUM parameters in the outgoing INVITE
map3xxContactUrlToRouteHeader

When map3xxContactUrlToRouteHeader  flag is enabled,  SBX adds 3XX contact header as second route header in the outgoing INVITE message.

This flag is enabled on a IBCF TG because when a call is routed by ECSCF to IBCF, the 3xx contact URI need to be added as second route header for subsequent routing to IP-PSAP.

  • disable (default)
  • enable
map181Or182MessageTo183Enable flag to allow 
Spacevars
0product
to map 181 or 182 response messages to 183. When disabled, the SBC handles 1xx response messages normally.
  • disable (default)
  • enable
mapContractorNumberInPSigInfoHeaderEnable flag to map the Contractor Number parameter into the 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.
  • disable (default)
  • enable 
qosBasedRouting

Enable flag to allow QoS-based routing.

  • disable (default)
  • enable
sameCallIdForRequiredAuthorization???

Enable this flag to support sending an INVITE with credentials on receiving a 401 (Unauthorized) or 407 (Proxy Authentication Required) response to initial INVITE with the same call ID as in the original INVITE.

  • disable (default)

  • enable

suppressUnregister

Enable flag to prevent 

Spacevars
0product
from sending an unregister message (Register=0) to the registrar upon expiration of a SIP UA registration. When disabled, the 
Spacevars
0product
generates unregister messages on the egress leg if the UA does not refresh the registration on time.

  • disable (default)
  • enable 

transitPAIFromUnregisteredPeer

Enable flag to transparently pass the received PAI to the INVITE if the default PUI procedure cannot add a PAI header.

  • disable (default)
  • enable 
Note

To use this flag, you must enable the enableDefaultPUIProcedures flag and disable the privacy disable the 'privacy transparency' flag (See egressIpAttributes - SIP - CLI section below).


ttcIsupMappingWhen enabled, and when the IP protocol type of the IP signaling profile entry is SIP or SIP-I, the application that receives the 
Spacevars
0product
policy response (which can be either the SIP signaling gateway application on the 
Spacevars
0product
or the SIP core proxy on the
Spacevars
0product
) applies the mapping necessary for TTC-ISUP signaling.
  • disable (default)
  • enable 
 useCalledPartyInRequestUri When enabled, the 
Spacevars
0product
copies the username selected for the "To" header to the Request URI instead of the registered username. When disabled, the 
Spacevars
0product
includes the registered username in the Request URI. This flag is used when interoperating with IP-PBXs that require the real end station number in the Request URI in order to do proper routing of calls terminating on them.
  • disable (default)
  • enable
useColonInSdpMediaTypeParameter

When enabled, a colon (:) is used as the separator between the SDP Media Type parameter key and value. When disabled, an equal sign (=) is used as the separator between the SDP Media Type parameter key and value.

  • disable (default)
  • enable
validateIsubAddress

When enabled, the 

Spacevars
0product
validates ISUB digits for called and calling parties. When isabled, the 
Spacevars
0product
will not validate ISUB digits.

...

ParameterLength/RangeDescription
phoneContextParameterLength0-31

Use this attribute to specify the length of phone-context parameter sent in RURI and To headers of the egress message (default = 0).

When a value greater than "0" is configured, and the called number is globalized using the existing globalization profile, the PSX sends the configured value in a policy response to the

Spacevars
0product
. The
Spacevars
0product
uses this configured value to insert phone-context parameter of received length in RURI and To headers.

Anchor
Privacy
Privacy
Privacy

Use this object to specify Privacy parameters.

...