[Home]

Summary:ASTERISK-18962: The in CLI documentation for SayNumber is wrong
Reporter:Nir Simionovich (GreenfieldTech - Israel) (greenfieldtech)Labels:
Date Opened:2011-12-04 23:15:58.000-0600Date Closed:2012-01-04 12:32:01.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:General
Versions:SVN Frequency of
Occurrence
Related
Issues:
Environment:CentOS 5.7, Virtual Machine, 16GB RAM, 4 Core, ESXi 4.1Attachments:
Description:The documentation of SayNumber that appears in the CLI is completely incorrect. Currently is states:

*CLI> core show application SayNumber

 -= Info about application 'SayNumber' =-

[Synopsis]
Say Number.

[Description]
This application will play the sounds that correspond to the given <digit
s>. Optionally, a <gender> may be specified. This will use the language that
is currently set for the channel. See the LANGUAGE() function for more
information on setting the language for the channel.

[Syntax]
SayNumber(digits[,gender])

[Arguments]
Not available

However, starting from 1.4.X and upwards it should state:

*CLI> core show application SayNumber

 -= Info about application 'SayNumber' =-

[Synopsis]
Say Number.

[Description]
This application will play the sounds that correspond to the given <digit
s>. Optionally, a <gender> may be specified. This will use the language that
is currently set for the channel. See the CHANNEL() function for more
information on setting the language for the channel.

eg.

exten => _X.,n,Set(CHANNEL(language)=fr)
exten => _X.,n,SayNumber(2345)

*** Note: If mode=new in say.conf, male/female capabilities are not available.

*** Note: Setting mode=new in say.conf is mutually exclusive, it will negate
   the usage of internally compiled languages.

[Syntax]
SayNumber(digits[,gender])

[Arguments]
Not available

Well, at least it should say something like that.

Nir
Comments:By: Paul Belanger (pabelanger) 2011-12-05 11:19:03.497-0600

patch?

By: Leif Madsen (lmadsen) 2011-12-15 12:23:50.836-0600

"completely incorrect" seems like a bit of stretch here. The usage of LANGUAGE() of CHANNEL() certainly needs to be updated, but I see no other changes.