Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH1bgoswami
REV5mshanmugam
REV6hprasad
REV3adsingh
REV4agogoi
REV1vmishra
REV2gckumar

 

The

Spacevars
0series4
supports playing announcements, tones, and collecting digits.

Tone and Announcement Profile

Tones and announcements are configured by allocating a percentage of DSP cores to tones/announcements. If no transcoding is used, you may allocate up to 100% toward tones/announcements.

Show If
matchall
groupconfluence-users

Refer to DSP Channel Densities for SBC 5000 and 7000 Series for a comparison of different DSP card configurations for

Spacevars
0series
and
Spacevars
0series2
systems.

Hide If
matchall
groupconfluence-users

See  DSP Channel Densities for SBC 5000 and 7000 Series for a comparison of different DSP card configurations for

Spacevars
0series
and
Spacevars
0series2
systems.

Spacevars
0product
. An announcement package supports provisioning of up to 16 announcement names to segment ID mapping. For more information on configuring Media Profiles, see Media Profile - CLI or Profile Management - Media Profiles.

When using an external PSX, the PSX returns the tones/announcement profile and announcement or tone to be played in policy/trigger response. The

Spacevars
0product
plays out the specified announcement/tone using the specified profile.

Announcement files are stored in the directory:  /var/log/sonus/evlog/announcements

For more information on configuring tones and announcements, see following:


Note
When the SBC is configured to use an external PSX, there may be instances when hunt groups, or Automatic Call Distribution (ACD) groups, do not always operate as expected when the Tone and Announcement profile is used. A call can remain on-hold even after answering the call. PSX 09.02.01R000 and later can be configured using the parameters End To End Ack and No CDR Change In End To End Ack to resolve this. End To End Ack must be enabled before enabling No CDR Change In End To End Ack flag. See PSX Manager User Guide for configuration details.

Tone Profile

The

Spacevars
0product
supports a default tone package with a package ID of “1”. The default package contains the following default tone profile definitions.

  • defBusy
  • defCallWaiting1
  • defCallWaiting2
  • defCallWaiting3
  • defCallWaiting4
  • defCpeAlerting
  • defDial
  • defReorder
  • defRing
  • defSit1
  • defSit2
  • defSit3
  • fccBusy
  • fccDial
  • fccRingback

Tones are customized by provisioning tone packages and tone profiles. The tone profile feature supports tone generation methods as described in Table 1.

For details to configure tone profiles, see below:

Caption
0Table
1Tone Profile Generation Methods

Tone Type

Tones

Frequency

Power

Details

Single Tone

1

0-3999 Hertz

(-50 to +3) dBm

 

Dual Tone

1, 2

0-3999 Hertz

(-50 to +3) dBm

 

Composite Tone

1, 2, 3, 4

N/A

N/A

  • Cadences to which each tone is applied
  • Decay time constant in milliseconds
  • Decay frequency delta in Hz/second
  • Decay tone bit map of tones against which decay/frequency rate change are applied

Modulated Tone

N/A

  • Carrier Frequency
  • Signal Frequency
  • Carrier Power
  • Signal Modulation Index
N/A

 

Local Ring Back Tones (LRBT)

The 

Spacevars
0series4
is configurable to support LRBT as described below:

The

Spacevars
0product
generates LRBT in the following conditions:

  • Start LRBT upon receipt of 180 without SDP, the
    Spacevars
    0product
    .
  • Halt LRBT upon receipt of any18x with SDP or any final response.
  • Stop LRBT without waiting for media packet arrival.

The

Spacevars
0product
supports the following dynamic LRBT functionality related to RFC 3960:

  • Do not generate local ringing unless a 180 ringing response with SDP is received.
  • Generate local ringing if a 180 ringing is received but no incoming media packets are present from the UAS.
  • If incoming media packets are received from the UAS, play incoming packets and stop playing the tone.

When configured to operate with an external PSX, local ring back tones are provisioned on the PSX on a per-trunk group basis. The PSX returns this information in a policy response.

In a pass-through call scenario, the 

Spacevars
0product
is prevented from selecting the preferred codec of the ingress offer to play the LRBT. The ingress offer codec may differ from the early answer codec that is used for the end to end cut-thru, and this change in codec can cause a media glitch to the ingress user. The 
Spacevars
0product
instead plays the LRBT with the same codec as the early answer codec that was received from egress (see the following call flow). The end to end cut-thru also uses the codec that plays the LRBT. The codec used between early media and to play tones therefore remains consistent. 

Info
titleNote

The call flow has the following configurations:

  • UAC and UAS supports PCMU and PCMA
  • Honor Remote Precedence is Enabled
  • LRBT is enabled

Caption
0Figure
1SBC LRBT Call Flow

Image required

Info
titleNote

In a transcode call scenario, the 

Spacevars
0product
selects the preferred codec of the ingress offer to play the LRBT because there is no common codec between ingress and egress.

Playing Tones as Announcements

The SBC Core supports playing announcements that are stored in G.711ULaw format. The SBC Core is enhanced to support playing compressed tones directly without allocating DSP resources by playing the tones from the pre-encoded files with various combinations of tones and codec types. The tone files are created for the required tone types with different codec combinations and stored as .wav files in the SBC. All these tones are stored with a ptime of 20 milliseconds.

The SBC Core includes the media profile tonesAsAnnouncement which uses the following parameters to configure the announcement file to play LRBT for each codec entry:

  • toneType
  • codecType
  • segmentId

The existing Tone Profile references the toneType in the tonesAsAnnouncement profile, whereas the new object toneCodecEntry references the codecType. With this enhancement, the user can associate default Tone Profile or can create a customized Tone Profile and assign it to the toneType of the toneAsAnnouncementProfile. The flag announcementBasedTones is included in toneAndAnnouncementProfile configuration to play LRBT without using DSP resources.

The SBC supports playing tones for three seven groups of codecs. If the required tone playback falls under one of the following codecs and the flag annoucementBasedTones is enabled, the SBC must avoid allocating DSP resources and play a tone as an announcement. If the required tone playback does not fall under one of the following codecs and the flag annoucementBasedTones is enabled, the SBC does not fall back to the DSP mode and continues the call without playing the tones.

  • G.711 (G.711ALaw and G.711ULaw)
  • G.722
  • EVRC (EVRC, EVRC0, EVRCB, and EVRCB0)
  • amrwbBandwidthEfficient (AMR-WB-BWE(, 9 variants)
  • amrwbOctetAligned (AMR-WB-BWE OA (, 9 variants)

  • amrBandwidthEfficient (AMR-NB-BWE (all modes, 8 variants)

  • amrOctetAligned (AMR-NB-OA (all modes)

    G.722

    , 8 variants)

     
Note

The SBC supports playing default ringtones with 41 different types of codec variants.

The compressed tone files are stored in the standard .wav file format. The SBC uses the same naming convention for the compressed tone files as the announcement files. For example, in a sDDDDD.wav file, where DDDDD is a decimal number from 1 to 65,535, the decimal number represents the segment ID of the file.

The announcement and the tone files share the 5-bit segment ID space, and thus, every file name must have a unique segment ID. The compressed tone files are stored in the same directory path as the announcement files (/var/log/sonus/sbx/announcements). The tone file is played continuously until the tone is stopped due to a trigger.

The following table provides the .wav file mapping information for the application announcements:

Caption
0Table
1Application Announcements
3Application Announcements
File NameAnnouncement IDRBTAudio Message

s20001.wav

20001RBT_MULAWUS Ring Back Tone
s20002.wav20002RBT_ALAWUS Ring Back Tone
s20003.wav20003RBT_EVRC (interleaved mode)US Ring Back Tone
s20004.wav20004RBT_EVRCB (interleaved mode)US Ring Back Tone
s20005.wav20005RBT_AMRWBBE_6_6KUS Ring Back Tone
s20006.wav20006RBT_AMRWBBE_8_85KUS Ring Back Tone
s20007.wav20007RBT_AMRWBBE_12_65KUS Ring Back Tone
s20008.wav20008RBT_AMRWBBE_14_25KUS Ring Back Tone
s20009.wav20009RBT_AMRWBBE_15_85KUS Ring Back Tone
s20010.wav20010RBT_AMRWBBE_18_25KUS Ring Back Tone
s20011.wav20011RBT_AMRWBBE_19_85KUS Ring Back Tone
s20012.wav20012RBT_AMRWBBE_23_05KUS Ring Back Tone
s20013.wav20013RBT_AMRWBBE_23_85KUS Ring Back Tone
s20014.wav20014

RBT_EVRC0 (Header free packet mode)

US Ring Back Tone
s20015.wav20015RBT_EVRCB0 (Header free packet mode)US Ring Back Tone
s20016.wav20016RBT_AMRWBOA_6_6KUS Ring Back Tone
s20017.wav20017RBT_AMRWBOA_8_85KUS Ring Back Tone
s20018.wav20018RBT_AMRWBOA_12_65KUS Ring Back Tone
s20019.wav20019RBT_AMRWBOA_14_25KUS Ring Back Tone
s20020.wav20020RBT_AMRWBOA_15_85KUS Ring Back Tone
s20021.wav20021RBT_AMRWBOA_18_25KUS Ring Back Tone
s20022.wav20022RBT_AMRWBOA_19_85KUS Ring Back Tone
s20023.wav20023RBT_AMRWBOA_23_05KUS Ring Back Tone
s20024.wav20024RBT_AMRWBOA_23_85KUS Ring Back Tone
s20025.wav20025RBT_AMRNBBE_4_7KUS Ring Back Tone
s20026.wav20026RBT_AMRNBBE_5_9KUS Ring Back Tone
s20027.wav20027RBT_AMRNBBE_5_15KUS Ring Back Tone
s20028.wav20028RBT_AMRNBBE_6_7KUS Ring Back Tone
s20029.wav20029RBT_AMRNBBE_7_4KUS Ring Back Tone
s20030.wav20030RBT_AMRNBBE_7_95KUS Ring Back Tone
s20031.wav20031RBT_AMRNBBE_10_2KUS Ring Back Tone
s20032.wav20032RBT_AMRNBBE_12_2KUS Ring Back Tone
s20033.wav20033RBT_AMRNBOA_4_7KUS Ring Back Tone
s20034.wav20034RBT_AMRNBOA_5_9KUS Ring Back Tone
s20035.wav20035RBT_AMRNBOA_5_15KUS Ring Back Tone
s20036.wav20036RBT_AMRNBOA_6_7KUS Ring Back Tone
s20037.wav20037RBT_AMRNBOA_7_4KUS Ring Back Tone
s20038.wav20038RBT_AMRNBOA_7_95KUS Ring Back Tone
s20039.wav20039RBT_AMRNBOA_10_2KUS Ring Back Tone
s20040.wav20040RBT_AMRNBOA_12_2KUS Ring Back Tone
s20041.wav20041RBT_G722US Ring Back Tone

Note

The .wav files for tones other than g711 a and u law are in Sonus proprietary format.

LMSD - Tone Play Support

The SBC supports playing tones when an Alert-Info header is received in the Legacy Mobile Station Domain (LMSD) format (Alert-Info: <http:/LMSD/tone?sig-id=rt>). The SBC is enhanced to play the LRBT without using DSP resources whenever it receives 180 with Session Description Protocol (SDP) answer with Alert-Info header (Alert-Info: <http:/LMSD/tone?sig-id=rt>). The Alert-Info header, present in the 180 ringing with SDP, carries the tone package information required by the SBC to play LRBT. To support this feature, the existing LRBT framework is enhanced.  

The SBC supports generating LRBT when:

  • The flag acceptAlertInfo is enabled on the egress TG.
  • The provisional response is 180 ringing with SDP and the tone flavor is normal.
  • The P-Com.DropEarlyMedia header is not present in the original INVITE.
  • The SDP answer is received in 180 or in a previous provisional response (183).
  • The 180 contains an Alert-Info header having sig-id = “rt” only (bt/ct does not play tone).
  • The flag announcementBasedTone in the toneAndAnnouncementProfile associated with the ingress TG is enabled.
Note
titleNote

The SBC supports fallback to LMSD inter-working state, if the flag acceptAlertInfo is enabled and the playing tone is failed. If the flag acceptAlertInfo  is not enabled, the SBC continues to process the call without playing a tone.

LMSD - Playing Tones Using Lock Down Preferred Codec

The SBC plays tones using the “lock down" preferred codec when the following flags are enabled:

  • sendOnlyPreferredCodec (IPSP)
  • honorRemotePrecedence (PSP)
  • announcementBasedTones

The codec that is used for playing tone towards the ingress leg is based on whether the session is established as pass-through or transcoded. If the SBC receives SDP answer from the egress peer, the selected codec is the egress peer's preferred codec. However, the ingress peer's preferred codec is used to play the tone, if the session outcome is transcoding.

Note

The SBC plays tones when it receives 180 responses with SDP for the egress peer preferred codec. When the 180 response is received without SDP from the egress peer, the SBC plays LRBT based on the existing LRBT implementation using the ingress peer preferred codec.

LMSD - Handling UPDATEs for the Tones

 The SBC is enhanced to stop playing LRBT upon receipt of any of the following messages:

  • UPDATE message with different SDP
  • subsequent 183 with SDP
  • 200 OK with or without SDP

For more information on Tone and Announcement feature, refer to:

 Alert-Info and P-Early Media Headers Interworking

Multiexcerpt
MultiExcerptNameAlert-Info_P_Early_Media_Interworking

The SBC supports the following Alert-Info to P-Early Media interworking functionality using the SIP trunk group flag aiToPemInterworking:

  • Interworking between a network supporting Alert-Info header (based on the Legacy Mobile Station Domain (LMSD) format) to a network supporting P-Early Media header. The SBC supports interworking irrespective of the existence of a provisioned tone on the SBC.
  • Interworking between a network that does not support P-Early Media header to a network that supports P-Early Media header. For example, the ingress network supports P-Early Media header; however, the egress network does not.
  • Interworking between networks that support P-Early Media headers.
Info
titleNote

Tone playing is not dependent upon Alert-Info and P-Early Media headers interworking.

These functionalities interact with each other based on the Trunk Group and Signaling profile configuration on the SBC, to which tone profile is configured and attached:

When a tone is configured on the SBC,

  • If the flag aiToPemInterworking is disabled on the egress TG, the SBC plays tone based on the LMSD format. For more information, refer to Tones and Announcements
  • If the flag aiToPemInterworking is enabled on the egress TG, the SBC supports interworking between Alert-Info and P-Early Media headers. The SBC plays tone when it receives Alert-Info header with sig-id=rt in the 180 provisioning response (either first 180 response or subsequent 180 response) from the Mobile Switching Center (MSC) (CDMA network). 

    Info
    titleNote
    • When all the tone playing criteria are fulfilled, the SBC inserts P-Early Media header as SENDRECV (P-Early Media: SENDRECV) and sends it towards the ingress network.

    • When the SBC fails to play tone, the SBC inserts P-Early Media header as INACTIVE (P-Early Media: INACTIVE) and sends it towards the ingress network.

When tone is not configured on the SBC; and the IPSP flag acceptAlertInfo is enabled on the egress TG, and the INVITE message is received with P-Early Media: SUPPORTED,

  • If the flag aiToPemInterworking is disabled on the egress TG, the SBC falls back to the existing LMSD interwoking functionality. For more information, refer to LMSD Interworking without Tones.
  • If the flag aiToPemInterworking is enabled on the egress TG, the SBC supports interworking between Alert-Info header (received in the LMSD format) and P-Early Media header.
     

    Info
    titleNote
    • When the User-Agent Server (UAS) plays tone, the SBC inserts P-Early Media header as SENDRECV (P-Early Media: SENDRECV) and sends it towards the ingress network.
    • When the User-Agent Client (UAC) plays tone, the SBC inserts P-Early Media header as INACTIVE (P-Early Media: INACTIVE) and sends it towards the ingress network.
 

Pagebreak