We were unable to say the number

Home » Asterisk Users » We were unable to say the number
Asterisk Users 8 Comments

Hello,

Occasionally, I get the following warning in my asterisk log,

pbx.c: We were unable to say the number [n], is it too large?

n is two or one digit number, which doesn’t look like large to me!

Could anybody please tell more about this warning, like in what scenario I
may have this warning.

Thanks,
Mohammad

8 thoughts on - We were unable to say the number

  • Hi Mohammad,
    which application do you use to say the number [n]? you can use
    *SayAlpha()*application to say the number you want. Please read link:
    *http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+SayAlpha* for
    more infomation.

    Phuonghd

  • Please post the relevant context that is being executed, that’ll give us not
    only the actual application, but more info as to how it’s being passed.

  • I am using asterisk 1.4.38
    I am getting this warning occasionally when executing SayNumber in a macro
    with argument which is less than 100.

    On Sat, Mar 26, 2011 at 11:03 AM, Sherwood McGowan <
    sherwood.mcgowan@gmail.com> wrote:

  • Again, the relevant dialplan code is important. It is quite possible that
    there’s an issue with the dialplan code that you (as the person who’s
    dealing with the issue) may have missed. It happens all the time.

  • Here is the dialplan in macro:

    exten => s,n,SayNumber($[${ARG1} % 100])

    when 662 was passed as ARG1, I had the following at log:

    WARNING[15217] pbx.c: We were unable to say the number 62, is it too large?

    Do you see any odd in my dialplan?

    On Sat, Mar 26, 2011 at 2:44 PM, Sherwood McGowan <
    sherwood.mcgowan@gmail.com> wrote:

  • What do you have CHANNEL(language) set to at the time? What language
    packs do you have installed? What is the exact version of Asterisk you
    have installed?

    Usually, what this error indicates is that you have one or more sound files
    missing, unreadable, or in a format that cannot be transcoded to the codec
    you’re using.

  • here..Maybe Asterisk is being confused by actually getting 66.2? I’m not
    readily able to look into the source, but I *think* that Asterisk (or at
    least, SayNumber) cannot handle a number with a decimal point, but please
    don’t take that as gospel.

    If Tilghman’s question doesn’t result in a fix, the next thing I’d say is to
    check and make sure that a floating point number can be supplied as an
    argument to SayNumber.

    Also make sure you’re logging verbose, debug, error, and warning messages
    into a logfile, bump the verbosity and debug up to 5, and then run another
    test call that will result in the number(s) you’re testing. Next, send off a
    larger amount of the content from the logfile, the single WARNING line is
    not enough for anything more than a blind guess. For instance, it would be
    REALLY fantastic is you would send the log line that displays SayNumber
    actually being executed, like ( *[DATE&TIME] VERBOSE[23609] pbx.c: —
    Executing [s@contextname:priority] SayNumber(“CHANNELNAME”, “66.2”) in new
    stack *)… It would be even MORE fantastic if you included almost ALL of
    that call’s log output, but at the very LEAST there should be around 5
    lines, starting from the verbose output for execution of SayNumber. That
    way, we don’t just get the warning message you’re complaining about, but the
    EXACT executions and messages outputted leading up to the warning message.

    But then again, you could continue to do essentially the same thing and hope
    for different results…

  • ‘%’ is ‘modulus’, and 62 is the correct result. I am betting it is the
    language setting, and missing audio files.

    j