-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 5 Mar 2006, Daniel Swarbrick wrote: >> For example, a caller with a UK caller ID could automatically be >> played all prompts in one of the available UK accents without having >> to rewrite the dialplan. It would also make IVR scripting with >> interleaved use of male and female voices easier. > This scheme would rely being able to accurately identify the geographic > origin of a call, which in some cases may be presumptuous. I think at > the moment it is simpler to just set the channel language variable. That > in itself however, needs to be expanded from the current two letter > language code to a full locale code.
I am doing exactly this but by using the dialplan instead. The automatic language detection shouldn't be coded into opbx since it is pretty simple to achieve. Possibly an app_guesslang could be made tho. My approach is this: * Check the callerid to see if it's from a supported country, if so set LANGUAGE. * If not, check which trunk the call came in on and set LANGUAGE * A menu option allows the caller to change it. >> So, yes, this needs to be sorted out, but it is not trivial, it will >> require some serious work. > No, it is certainly not trivial to teach a computer about natural > languages. Perhaps we should decide whether we attack this is two steps. > Firstly, just implement slightly smarter handling of what is already in > the code, by adding the locale support to the existing simple language > support. Then, attempting to strip out hard-coded regional code, and > express that somehow in a language template file similar to what you > propose. We should define a generic voice prompt API that takes care of that for all apps and does the language dependent stuff. An app should just have to call a opbx_read_number(language, speaker, number) or something and be done with it. We can gradually add the complexity needed to handle all oddities in the languages later without rewriting all apps if we use this approach. /B - -- * GPG-Key: http://evil.gnarf.org/mrbk.pgp A: Because we read from top to bottom, left to right. Q: Why should i start my reply below the quoted text? - -- http://www.i-hate-computers.demon.co.uk/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFECsqPckvkFeO3ANARAmhPAJoC8Ty14BIeAj2dAde5X9+vzCGPhwCg1aHj h7afN5504nul0RnuLG+zVvc= =EWbE -----END PGP SIGNATURE----- _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
