Tone and Announcement Profile - CLI

Use this feature to provision a tone and announcement profile, which specifies an announcement package and/or signaling tone package for the SBC to use to play announcements or signaling tones to calling or called parties. Tone and announcement profiles are assigned to ingress or egress trunk groups. Also, use this feature to provision Local Ring Back Tones (LRBT) for the SBC, which the SBC plays to callers upon receipt of an alert indication without a media stream or without an indication of in-band tones.

To associate a Tone and Announcement Profile to a Trunk Group, use the following syntax:

% set addressContext <addressContext name> zone <zone name> sipTrunkGroup <sipTrunkGroup name> policy media toneAndAnnouncementProfile <profile name> 

Command Syntax

% set profiles media toneAndAnnouncementProfile <profile name> 
	localRingBackTone 
		signalingTonePackageState <disable | enable> 
		flags
			announcementBasedTones <disable | enable>
			dynamicLRBT <disable | enable>
			forceLRBT <disable | enable>
			useThisLrbtForEgress <disable | enable> 
			useThisLrbtForIngress <disable | enable> 
		makeInbandToneAvailable <disable | enable> 
		precedence <higher | lower> 
		signalingTonePackage <name> 
	toneAndAnnouncement 
		announcementPackageState <disable | enable> 
		announcementPackage <name> 
		override <disable | enable> 
		sigTonePackage <name> 

Command Parameters

Tone and Announcement Profile Parameters

The Tone and Announcement Profile Parameters are described below.

Local Ringback Tone Parameters

P-Early-Media and DLRBT

To use the Force Local Ring Back Tone (FLRBT) feature, set the PSX flag DelayedRBTWithToneContinuation to enabled.The flag is available under the entity Tone Generation Criteria > Delayed RBT in the PSX.

• To create a Tone Generation Criteria entity with the flag DelayedRBTWithToneContinuation:
  create Tone_Generation_Criteria_Data Tone_Generation_Criteria_Id <string> Sequence_Number <int> [Response_Code <short>] [Attributes <int>] [Ingress_Tg <string>]
  
  
• To update a Tone Generation Criteria entity with the flag DelayedRBTWithToneContinuation:
  update Tone_Generation_Criteria_Data Tone_Generation_Criteria_Id <string> Sequence_Number <int> [Response_Code <short>] [Attributes <int>] [Ingress_Tg <string>]
  
  
• To delete a Tone Generation Criteria entity with the flag DelayedRBTWithToneContinuation:
  delete Tone_Generation_Criteria_Data Tone_Generation_Criteria_Id <string> Sequence_Number <int>
  
  

For more information on the flag DelayedRBTWithToneContinuation, refer to the PSX document Tone Generation Criteria Screen.

When a caller sends a SIP INVITE to the SBC (irrespective of the presence of "P-Early-Media: supported" header in the Session Description Protocol (SDP) of the INVITE), the SBC adds P-Early-Media header in its 18x (180 or 183) response towards ingress call leg only if:

• The SBC monitors and detects early media from the egress call leg.

  Note

  The SBC has an "observation" window for monitoring the stream of RTP packets. It also has a "silence" window before it restarts monitoring, to reject RTP packets from a previous announcement.

• The SBC plays a Ring Back Tone (RBT).

  Note

  The SBC plays LRBT only if it does not receive any early media from the egress call leg at the end of a monitoring cycle. If the SBC starts playing LRBT, it continues to play even if it detects RTP in the subsequent monitoring cycles, or exchanges a new set of SDP answers with the egress call leg.

  When the SBC receives an UPDATE from the egress call leg, and the caller (ingress call leg) does not support UPDATE, the SBC continues to feed tone in the same codec. When the ingress call leg supports UPDATE, the SBC feeds tone in a modified codec after a successful offer-answer negotiation.