Skip to main content
A
Anonymous
January 22, 2011
Answered

How to catch DTMF at FMS

  • January 22, 2011
  • 1 reply
  • 1188 views

When calling from SIP-client (x-lite) on the flash client is not an CallLegService.onLegMessage event occurs while clicking on the numbered buttons in the SIP-client.

What is the problem?

This topic has been closed for replies.
Correct answer

I am not sure if I understood this question properly.

  • Whenever, DTMF digit for a Flash Phone is sent to FMS by FMG, CallLegService.onLegMessage handler is invoked on the FMS Sever-side action script( SSAS) of telephony app.

  • Application.legService.onLegMessage method in the sample telephony/main.asc files implements CallLegService.onLegMessage.

  • Usually C:\Program Files\Adobe\Flash Media Server 4\logs\_defaultVHost_\telephony\_definst_\application00.log file would contain a new log message for onLegMessage whenever a new DTMF digit is received.

  • To generate the detailed logs, modify log level in telephony/main.asc to change the log level to verbose(most detailed)

                     i.e. modify application.legService.setLogLevel("warning"); to  application.legService.setLogLevel("verbose");

I hope it helps.

1 reply

A
Anonymous
Correct answer
January 23, 2011

I am not sure if I understood this question properly.

  • Whenever, DTMF digit for a Flash Phone is sent to FMS by FMG, CallLegService.onLegMessage handler is invoked on the FMS Sever-side action script( SSAS) of telephony app.

  • Application.legService.onLegMessage method in the sample telephony/main.asc files implements CallLegService.onLegMessage.

  • Usually C:\Program Files\Adobe\Flash Media Server 4\logs\_defaultVHost_\telephony\_definst_\application00.log file would contain a new log message for onLegMessage whenever a new DTMF digit is received.

  • To generate the detailed logs, modify log level in telephony/main.asc to change the log level to verbose(most detailed)

                     i.e. modify application.legService.setLogLevel("warning"); to  application.legService.setLogLevel("verbose");

I hope it helps.

A
Anonymous
January 23, 2011

I have done exactly as you wrote.

But CallLegService.onLegMessage does not occur when I press numpad buttons in the x-lite

Log tail:

onLegMessage.info.legID :: ca06484c-3807-4dbf-9997-2c5db1dc28da    -
onLegMessage.info.type :: leg.message.type.indication    -
onLegMessage.info.service :: DefaultID_129581224412080305    -
onLegMessage.info.data :: message.indication.answer    -
sending onLegMessage    -
onLegMessage    -
FMG Leg Service [Info]: Invoking onLegStatus    -
FMG Leg Service [Info]: info.service: DefaultID_129581224412080305, info.legID: ca06484c-3807-4dbf-9997-2c5db1dc28da, info.status: leg.state.sendrecv,     -
A
Anonymous
January 24, 2011

FMG Leg Service [Info]: info.service: DefaultID_129581224412080305, info.legID: ca06484c-3807-4dbf-9997-2c5db1dc28da, info.status: leg.state.sendrecv,     -

   Above logs are printed when the call has been established. Log for DTMF would follow as it is received.

   Since you already have detailed log (verbose) enabled;  it should be easier to play around. On my end, Following is an example log which was when flash phone was connected to a newly installed X-lite 4 (build 58832).

2011-01-23    07:10:44    9084    (s)2641173    FMG Leg Service [Info]: Invoking onLegMessage    -

2011-01-23    07:10:44    9084    (s)2641173    FMG Leg Service [Info]: info.service: DefaultID_129574680917142650, info.legID: 23dddeab-63ae-425d-8919-8d58d73ccf91, info.type: leg.message.type.dtmf, info.data: 8,     -

    Which version of x-lite are you using? I am still not sure what may be causing this on your setup.

    On the example setup from which above logs were generated, x-lite 4 was configured as shown on the picture below. It was installed on the same machine as FMG.

                         

       Do let know how it goes, if the problem persists; please share the SIP packet capture. Instructions to capture SIP packets should be searchable in few older threads.

-Pankaj

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices