DTMF inputs sent are not getting detected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Have a look at http://trac.pjsip.org/repos/ticket/855

Other than that, you may want to fine tune the duration (I don't know
what the "standard" values are), and sending DTMF inband is never
reliable anyway (it depends on the codec and network conditions).

On Thu, Aug 13, 2009 at 5:47 AM, Amritha
Nambiar<Amritha_Nambiar at infosys.com> wrote:
>
>
> Hi All,
>
>
>
> ?????????? I am using inband method to send DTMF digits and am calling an
> IVR system to process my DTMF inputs to test this. But I am encountering
> some issues with this as the digits I am sending are detected in a very
> inconsistent manner. Some of the digits I am sending are not detected at
> all, while some are detected repeatedly and in some cases only about half of
> the digits sent are detected. On testing with X-lite to hear the sounds for
> the dtmf inputs, the sounds are heard feebly at the far end.
>
>
>
> ?Below is a snippet of the code I have used to implement this. I have called
> the pjmedia_tonegen_play_digits api with the paremeter ?pjdigits? of
> pjmedia_tone_digit type to play the digits that are being sent.
>
>
>
> ??? pjdigits[i].digit = digits[i] /**< The ASCI identification for the
> digit. ??? */;
>
> ??? pjdigits[i].on_msec = 150;? /**< Playback ON duration, in
> miliseconds.??? ??? */
>
> ??? pjdigits[i].off_msec = 200; /**< Playback OFF duration, ini
> miliseconds.??? */
>
> ??? pjdigits[i].volume = 0; /**< Volume (1-32767), or 0 for default, which
>
> ??????????????????????? ?PJMEDIA_TONEGEN_VOLUME = 12288 will be used.
> */
>
>
>
> ????? I have also tried with different combinations of the values for
> on_msec (Playback ON duration) and off_msec (Playback OFF duration). ?Why
> are my dtmf inputs not being recognized properly? Any suggestion or
> direction would be greatly appreciated.
>
>
>
>
>
> Thanks,
>
> Amrita
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
> for the use of the addressee(s). If you are not the intended recipient,
> please
> notify the sender by e-mail and delete the original message. Further, you
> are not
> to copy, disclose, or distribute this e-mail or its contents to any other
> person and
> any such actions are unlawful. This e-mail may contain viruses. Infosys has
> taken
> every reasonable precaution to minimize this risk, but is not liable for any
> damage
> you may sustain as a result of any virus in this e-mail. You should carry
> out your
> own virus checks before opening the e-mail or attachment. Infosys reserves
> the
> right to monitor and review the content of all messages sent to or from this
> e-mail
> address. Messages sent to or from this e-mail address may be stored on the
> Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux