DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.

CLI Excerpt

The SBC gives precedence to SIP Privacy handling when the SIP Adaptive Transparency Profile is enabled. For example, if the incoming SIP message has "privacy: Id" and the flag applyPrivacyId under profiles services privacyProfile is set to enabled, the SBC does not include P-ASSERTED-ID header in the egress message.

For more information on privacyProfile, refer to the following pages:

 Several flags prevent the SBC from relaying a re-INVITE, or an UPDATE, to the other leg of the call. When you enable such flags, the behavior is contradictory to that of the SIP Adaptive Transparency Profile. 

To resolve such conflicts, the SBC gives precedence to the SIP Adaptive Transparency Profile over the following flags:

  • Parent Object: profiles signaling ipSignalingProfile <profile_name> commonIpAttributes flags
    • relayDataPathModeChangeFromOtherCallLeg
    • minimizeRelayingOfMediaChangesFromOtherCallLegAll
    • disableMediaLockDown
    • lockDownPreferredCodec
    • callHoldInterworking 
  • Parent Object: addressContext <addressContext_name> zone <zone_name> sipTrunkGroup <sipTrunkGroup_name> signaling
    • sdp100relIwkForPrack
    • rel100Support
  • Parent Object: addressContext <addressContext_name> zone <zone_name> sipTrunkGroup <sipTrunkGroup_name> media
    • lateMediaSupport

 

For more information on the flags mentioned above, refer to the following pages:

 

EMA Excerpt

The SBC gives precedence to SIP Privacy handling when the SIP Adaptive Transparency Profile is enabled. For example, if the incoming SIP message has "privacy: Id" and the flag Apply Privacy Id under Profiles > Services > Privacy Profile is set to Enabled, the SBC does not include P-ASSERTED-ID header in the egress message.

For more information on Privacy Profile, refer to the following pages:

 Several flags prevent the SBC from relaying a re-INVITE, or an UPDATE, to the other leg of the call. When you enable such flags, the behavior is contradictory to that of the SIP Adaptive Transparency Profile. 

To resolve such conflicts, the SBC gives precedence to the SIP Adaptive Transparency Profile over the following flags:

  • Parent Object: Profiles > Signaling > IP Signaling Profile > Common IP Attributes > Flags
    • Relay Data Path Mode Change From Other Call Leg
    • Minimize Relaying Of Media Changes From Other Call Leg All
    • Disable Media Lock Down
    • Lock Down Preferred Codec
    • Call Hold Interworking 
  • Parent Object: Address Context > Zone > SIP Trunk Group > Signaling
    • Sdp 100rel Iwk For Prack 
    • Rel100 Support
  • Parent Object: Address Context > Zone > SIP Trunk Group > Media
    • Late Media Support

 

For more information on the flags mentioned above, refer to the following pages:



  • No labels