You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

In this section:


Use this feature to provision a tone and announcement profile, which specifies an announcement package and/or signaling tone package for the 

Unable to show "metadata-from": No such page "_space_variables"
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
Unable to show "metadata-from": No such page "_space_variables"
, which the 
Unable to show "metadata-from": No such page "_space_variables"
plays to callers upon receipt of an alert indication without a media stream or without an indication of in-band tones.

Note

For information on Delayed Local Ring Back Tone (DLRBT) and P-Early-Media, see P-Early-Media and DLRBT later in this section.

Note

For detailed information on D-SBC Support of Tones and Announcements, refer to D-SBC Support of Tones and Announcements.

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.

Tone and Announcement Profile Parameters

Parameter

Description

toneAndAnnouncementProfile

Use this object to configure the Tone and Announcement Profile.

localRingBackTone

Use this parameter to configure LRBT settings. See Local Ringback Tone Parameters table below for parameter details.

toneAndAnnouncement

This parameter configures the Tone and Announcement package.

  • announcementPackageState – Enable flag to configure the announcement package.
    • disable (default)
    • enable
  • announcementPackage – Enter the announcement package to use for calls associated with the specified ingress and/or egress trunk group(s).
  • override – When profiles are assigned to both ingress and egress trunk groups, enable this flag to override settings and use this specific announcement profile for both call legs.
    • disable (default)
    • enable
  • sigTonePackage – Enter the signaling tone package to use for calls associated with the specified ingress and/or egress trunk group(s).

Local Ringback Tone Parameters

Note

To configure localRingBackTone options, first enable the signalingTonePackageState flag.

Note

You must enable makeInbandToneAvailable in order to use Local Ringback Tone (LRBT).

Local Ringback Tone Parameters

Parameter

Description

flags

Use these flags to enable/disable LRBT for egress and ingress trunk groups.

  • announcementBasedTones – Use this flag to generate announcement-based ringback tones without using DSP resources.
    • disable (default)

    • enable

  • dynamicLRBT – Enable this flag for the SBC to select a provisional response for cut-through based on the arrival of media packets.

    • disable (default)

    • enable
      NOTE: To support dynamic LRBT for forking behavior of the last provisional response till 180 is received, both this flag and the SIP Trunk Group flag "firstRtp" must be enabled. If firstRtp is enabled, but dynamicLRBT is disabled, forking behavior defaults to the last provisional response. 

  • forceLRBT – Enable this flag to force the SBC to use the signaling tone package specified in this Tone and Announcement Profile, overriding any ringback tone generated/indicated by the egress end.

    • disable (default)
    • enable
  • useThisLrbtForEgress – Enable flag to use LRBT for egress trunk group.
    • disable (default)
    • enable
  • useThisLrbtForIngress – Enable flag to use LRBT for ingress trunk group.
    • disable (default)
    • enable
      • earlyMediaMethod - Used to play tone when P-Early-Media is configured as pEarlyMedia. The options are:
        • pEarlyMedia
        • none (default)

      • withOrWithOutSDP - Used to play tone when P-Early-Media is received in 18x response with or without SDP. The options are:

        • disable (default)
        • enable
makeInbandToneAvailable

Enable this flag to insert an in-band tone indicator (OBCI in the case of ISUP) in a backward message (for example, ACM) when playing local ringback tones.

  • disable (default)
  • enable
precedence

Set this parameter when both the ingress and egress trunk groups have a LRBT associated with them and you want to specify which trunk group has priority over the other.

  • higher
  • lower (default)
signalingTonePackage<package name> – Enter the signaling tone package to use for calls associated with the specified ingress and/or egress trunk group(s).

signalingTonePackageState

Enable this flag to configure a signaling tone package.

  • disable (default)
  • enable


P-Early-Media and Delayed RBT

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.

Note

If the egress call leg responds with P-Early-Media header in its 18x response, the SBC transparently relays it to the ingress call leg.


  • No labels