Use case 1—Using session.xml files to detect tones

By setting browser.tonedetection.tone_event.enable in a session.xml file, you can selectively disable tones that your application doesn’t handle.

Say a service provider is hosting three applications: App1 handles fax tones, App2 handles SIT tones, and App3 handles fax, SIT, and TTY. Setting server.toneDetector.configFile enables all tones. Any tone that is not handled by an application results in an exception, which is unacceptable. To prevent this situation, create a session.xml file for each application and disable the tones that the application doesn’t handle.

The syntax in session.xml is:

...

<sessionparameters>

  <browser>

    <param name="browser_td_parameter"><value>value</value></param>

  </browser>

</sessionparameters>

...

For App1, which handles only fax tones, its session.xml would look like this:

...

<sessionparameters>

  <browser>

   <param    name="browser.tonedetection.amd.enable"><value>false</value></param>

   <param    name="browser.tonedetection.sit.enable"><value>false</value></param>

   <param    name="browser.tonedetection.tty.enable"><value>false</value></param>

  </browser>

</sessionparameters>

...

See Application defaults for more information about session.xml. See Specifying a session.xml file for more information on executing them.