Woof!

Misha Vodsedalek <vmisha <at> yahoo.com> writes:

> 
> 
> Woof! is rebuilding the AA component using JAVA and 
> freeswitch, so maybe you should look at his new version if it can do what 
> you want.  The language support in his new implementation is supposed to be 
> superior comparing to the current one.

Indeed, I am, and I feel it is...

>   "Bobbie Stivers" <bobbie <at> InformationProductsInc.com> 
>   wrote in message news:200808271518.m7RFI8bF073908 <at> 
lambda.sipfoundry.org...
>   
>   So how would one support multiple 
>   languages? Say, if I wanted to build a custom AA that prompts for the 
language 
>   to continue in and then reads back an extension directory in the selected 
>   language? 

In the new AA, the language/locale used is determined from the "locale=" 
parameter on the SIP request URI, and the attendant to use is determined from 
the "name=" parameter.  This best matches the old behavior.  In the end, it 
ends up setting a member variable "org.sipfoundry.attendant.Attedant.m_local" 
to the selected locale.  When the attendant is called, it pulls in 
configuration based on that locale.

In order to set up an initial "press 1 for english, 2 for espanol..." attendant 
a new action would be required to set that variable to a new value...easy 
enough to do.  Then this "pre-attendant" would chain to the real attendant and 
the new locale will take effect.

To do it without changing any code at all (at the expense of being 
ineffecient), set up multiple extensions which forward to the AA, each with a 
different "locale=" parameter, like this:

Ext 100  "pre-attendant" (locale="";name="preattendant")
Ext 105  English (locale=en_US;name="attendant")
Ext 106  Italian (locale=it_IT;name="attendant")
Ext 107  Chinese (locale=zh_CN;name="attendant")
...

Then set the "pre-attendant" to transfer to ext 105 if the "English" button is 
pressed, ext 106 if the "Italian" button is pressed, etc.

--Woof!

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to