> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/voice-and-media/tone-definitions.md). # Tone definitions #### Tone definitions It is possible through the Toolpack [Web Portal](https://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/other/web-portal) to specify the parameters of ringing, busy, congestion (or fast busy), and warning call progress tones. These settings are available in ``` Profiles -> Tone Profile Params ``` The tones are described using a programmable string of characters defined in the [H.248](/telecom-references/sip-and-voip/h248-mgcp.md) Dynamic Tone Definition Package. To learn more about tone description strings, see the [section](/telecom-references/developer-reference/caf/caf-working-with-cmc-call-legs.md#play-tone-with-signal-id-string) related to this subject. #### Examples of Call Progress tones The following table contains a few call progress tone definition strings that can be used to replace the default ones in the Toolpack Web Portal. | | Ring | Busy | Congestion | Warning | | -------------- | ------------------------------------------------------------------- | -------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------------- | | Australia | ((((#400)+(#450)),400),(#0,200),(((#400)+(#450)),400),(#0,2000))\*0 | ((#425,375),(#0,375))\*0 | ((#425,375),(#0,375))\*0 | ((#900),500) | | Bangladesh | ((#425,1000),(#0,4000))\*0 | ((#450,200),(#0,300),(#450,700),(#0,800))\*0 | ((#425,250),(#0,250))\*0 | ((#450,200),(#0,20),(#450,200),(#0,140))\*0 | | Brazil | ((#425,1000),(#0,4000))\*0 | ((#425,250),(#0,250))\*0 | ((#425,750),(#0,250),(#425,250),(#0,250))\*0 | *unused* | | China | ((#450,1000),(#0,4000))\*0 | ((#450,350),(#0,350))\*0 | ((#450,700),(#0,700))\*0 | *unused* | | France | ((#440,1500),(#0,3500))\*0 | ((#440,500),(#0,500))\*0 | ((#440,250),(#0,250))\*0 | *unused* | | Germany | ((#425,1000),(#0,4000))\*0 | ((#425,480),(#0,480))\*0 | ((#425,240),(#0,240))\*0 | ((#425,240),(#0,240),(#425,240),(#0,1280))\*0 | | Hong Kong | ((((#440)+(#480)),400),(#0,200),(((#440)+(#480)),400),(#0,3000))\*0 | ((((#480)+(#620)),500),(#0,500))\*0 | ((((#480)+(#620)),250),(#0,250))\*0 | *unused* | | Netherlands | ((#425,1000),(#0,4000))\*0 | ((#425,500),(#0,500))\*0 | ((#425,250),(#0,250))\*0 | *unused* | | North America | ((((#440)+(#480)),2000),(#0,4000))\*0 | ((((#480)+(#620)),500),(#0,500))\*0 | ((((#480)+(#620)),250),(#0,250))\*0 | ((#1400),500) | | Spain | ((#425,1500),(#0,3000))\*0 | ((#425,200),(#0,200))\*0 | ((#425,200),(#0,200),(#425,200),(#0,200),(#425,200),(#0,600))\*0 | (((#1400),400),(#0,5000))\*0 | | United Kingdom | ((((#400)+(#450)),400),(#0,200),(((#400)+(#450)),400),(#0,2000))\*0 | ((#400,375),(#0,375))\*0 | ((#400,400),(#0,350),(#400,225),(#0,525))\*0 | *unused* | | The Moon... | ((#262,2000),(#391,2000),(#523,4000),(((#659)+(#523)),250),(((#622)+(#523)),3750),(#262,400),(#196,400),(#262,400),(#196,400),(#262,400),(#196,400),(#262,400),(#196,400),(#262,420),(#196,460),(#262,540),(#196,620))\*0 | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | #### Playing and collecting tones To learn how to play these tones using the [Call Leg API](/telecom-references/developer-reference/caf/caf-working-with-call-legs.md), refer to the [Playing and Collecting Tones section](/telecom-references/developer-reference/caf/caf-working-with-cmc-call-legs.md#playing-and-collecting-tones). For example, to play the **ringing** tone, pass, either directly the `((((#440)+(#480)),2000),(#0,4000))*0` or `cg/rt` to the **AddToneString()** function. The `cg/rt` string refers to the current Tone Profile Params ringing tone setting from the Web Portal. #### Tone volume It is possible to change the ring tone volume. According to the syntax, you need to specify the desired volume after the tone duration. Here is an example: ((((#440)+(#480)),2000,**-15**),(#0,4000))\*0 The possible values are: -19, -15, -10, -5 and 0 dB. #### Available tones Below is a comprehensive list of all the tone strings that can be passed to the **AddToneString()** function. **Tone detection** | | | | | | ------------------------ | ----------------- | -------------------------- | - | | Package | Signal | String | | | Basic DTMF generation | 0 | dg/d0 | | | Basic DTMF generation | 1 | dg/d1 | | | Basic DTMF generation | 2 | dg/d2 | | | Basic DTMF generation | 3 | dg/d3 | | | Basic DTMF generation | 4 | dg/d4 | | | Basic DTMF generation | 5 | dg/d5 | | | Basic DTMF generation | 6 | dg/d6 | | | Basic DTMF generation | 7 | dg/d7 | | | Basic DTMF generation | 8 | dg/d8 | | | Basic DTMF generation | 9 | dg/d9 | | | Basic DTMF generation | \* | dg/ds | | | Basic DTMF generation | # | dg/do | | | Basic DTMF generation | A | dg/da | | | Basic DTMF generation | B | dg/db | | | Basic DTMF generation | C | dg/dc | | | Basic DTMF generation | D | dg/dd | | | Call Progress generation | Ring | cg/rt | | | Call Progress generation | Busy | cg/bt | | | Call Progress generation | Congestion | cg/ct | | | Call Progress generation | Warning | cg/wt | | | MF tone generation | 0 | mfg/mf0 | | | MF tone generation | 1 | mfg/mf1 | | | MF tone generation | 2 | mfg/mf2 | | | MF tone generation | 3 | mfg/mf3 | | | MF tone generation | 4 | mfg/mf4 | | | MF tone generation | 5 | mfg/mf5 | | | MF tone generation | 6 | mfg/mf6 | | | MF tone generation | 7 | mfg/mf7 | | | MF tone generation | 8 | mfg/mf8 | | | MF tone generation | 9 | mfg/mf9 | | | MF tone generation | KP | mfg/mfa | | | MF tone generation | ST | mfg/mfe | | | Telcofax | CNG | telcofax/cng | | | Telcofax | g164 | telcofax/g164 | | | Telcofax | g165 | telcofax/g165 | | | Package | Signal | String | | | Basic DTMF detection | 0 | dd/d0 | | | Basic DTMF detection | 1 | dd/d1 | | | Basic DTMF detection | 2 | dd/d2 | | | Basic DTMF detection | 3 | dd/d3 | | | Basic DTMF detection | 4 | dd/d4 | | | Basic DTMF detection | 5 | dd/d5 | | | Basic DTMF detection | 6 | dd/d6 | | | Basic DTMF detection | 7 | dd/d7 | | | Basic DTMF detection | 8 | dd/d8 | | | Basic DTMF detection | 9 | dd/d9 | | | Basic DTMF detection | \* | dd/ds | | | Basic DTMF detection | # | dd/do | | | Basic DTMF detection | A | dd/da | | | Basic DTMF detection | B | dd/db | | | Basic DTMF detection | C | dd/dc | | | Basic DTMF detection | D | dd/dd | | | MF tone generation | 0 | mfd/mf0 | | | MF tone generation | 1 | mfd/mf1 | | | MF tone generation | 2 | mfd/mf2 | | | MF tone generation | 3 | mfd/mf3 | | | MF tone generation | 4 | mfd/mf4 | | | MF tone generation | 5 | mfd/mf5 | | | MF tone generation | 6 | mfd/mf6 | | | MF tone generation | 7 | mfd/mf7 | | | MF tone generation | 8 | mfd/mf8 | | | MF tone generation | 9 | mfd/mf9 | | | MF tone generation | KP | mfd/mfa | | | MF tone generation | ST | mfd/mfe | | | Telcofax | CNG | telcofax/cng | | | Telcofax | g164 | telcofax/g164 | | | Telcofax | g165 | telcofax/g165 | | | Telcofax | ansam | telcofax/ansam | | | Telcofax | phase\_rev\_ansam | telcofax/phase\_rev\_ansam | | | Telcofax | v21\_flags | telcofax/v21\_flags | | | Telcofax | bell\_ans | telcofax/bell\_ans | | #### References * [Various tones used in national networks](http://www.itu.int/publ/T-SP-E.180-2003/en) * [H.248 Gateway Control Protocol Dynamic Tone Definition Package](http://www.itu.int/rec/T-REC-H.248.6-200011-I/en) * [H.248 Gateway Control Protocol](http://www.itu.int/rec/T-REC-H.248.1-200509-I/en) section E.7 (Call Progress Tone Definitions Package) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://prosbcdocs.telcobridges.com/telecom-references/voice-and-media/tone-definitions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.