<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
I tried to respond to all replies in one response, forgive the delay.<BR>
<BR>
1) Nicolas Chapleau wrote:<BR>> <BR>> > This would also render "say" functions<BR>> > to not play the correct language syntax for numbers, dates and times as<BR>> > the functions are not aware on how to play fr_special1, fr_special2, ...<BR>> <BR>> I believe you might be right, in which case this is a bug that must be<BR>> fixed. All parts of Asterisk that interpret LANGUAGE should handle it<BR>> the same way.<BR>
<BR>
tilghman reports that this issue has been fixed:<BR>
<BR>
> Actually, that it worked only for a particular 2-digit language code was a bug<BR>> and has since been corrected. So creating a specific derivative of a language<BR>> should not be a problem.<BR>
<BR>
Are the derivatives created in code or in a .conf file of some sort. I've been looking at the docs to no avail, other then in code.<BR><BR>2) Andreas Sikkema wrote:<BR> <BR>> What I think he means is something slightly different.<BR>> <BR>> That you can have multiple voices within one language so that there <BR>> will be no problems wrt digit pronunciation because that already <BR>> "works" for the language.<BR>> <BR>> Currently all the special stuff for pronunciation is related to the <BR>> two digit country code. If you need more than two voices for a <BR>> specific language (multi tenant asterisk install or something like <BR>> that) you need to create a special language (in his example fr and <BR>> fr_special) but then I think you'd lose the pronunciation rules <BR>> because that only works for the two digit country code and not for <BR>> something else.<BR>> <BR><BR>
Andreas is pretty much bang on as to what we are trying to achieve and I believe many others are probably having this issue. I'm still trying to come up with a "fix" or "solution" for digits/letters and phonetics to behave the same way as normal play functions and I will report later.<BR>
<BR>
<BR>
3) Kevin P. Fleming wrote:<BR>
<BR>> My point was that Asterisk is already prepared (when finding prompts) to<BR>> automatically 'shorten' the LANGUAGE code by removing suffixes until it<BR>> finds what it is looking for; so if you have set LANGUAGE to fr_special,<BR>> and you ask for 'demo-instruct' to be played, Asterisk will first look<BR>> for demo-instruct in the fr_special directory, then in the fr directory,<BR>> and finally in the 'no language code' directory.<BR>> <BR>> I am suggesting that the code in Asterisk that directly responds to<BR>> language codes (say.c, app_voicemail.c and other places) should *ALSO*<BR>> automatically shorten language codes, so that if LANGUAGE is set to<BR>> fr_special then say.c will still use the fr syntax for speaking<BR>> numbers/dates/times.<BR>> <BR>
<BR>
They already do. However I believe that there should be a better way to set this up other then creating special language flags for different voices in the same language ONLY for the SAY functions. <BR>
All works fine and dandy for normal playback functions.<BR>
<BR>
English:<BR>
sounds/voice1<BR>
sounds/voice2<BR>
sounds/digits<BR>
sounds/voice1/digits<BR>
sounds/voice2/digits<BR>
<BR>
French - or add your language here ;)<BR>
sounds/fr/voice1<BR>
sounds/fr/voice2<BR>
sounds/fr/digits<BR>
sounds/fr/voice1/digits<BR>
sounds/fr/voice2/digits<BR>
<BR>
ie: language set to fr => playback(welcome), playback(voice1/welcome), playback(voice2/welcome), ...<BR>
<BR>
but not for "say" functions and such:<BR>
<BR>
ie: sayNumber(1234) -> OK, sayNumber(voice1/1234) -> wrong, sayNumber(voice2/1234) -> wrong<BR>
<BR>
and this is what I'm trying to achieve. It would be nice for both to behave the same. I also do not wish to change any syntax for these commands. I have an idea, so I will test it out and report back shortly.<BR>
<BR>
Thanks all for your valued input and I hope I'm not wasting anyone's time.<BR>
<BR>
NicChap.<BR>
<BR>
<BR>
<BR></body>
</html>