wikipbx-dev team mailing list archive

[Dmytro Mishchenko <wikipbx@xxxxxxxxxxxxx>]

Stas Shtin wrote:
> Hi Dmitry,
> 
> 
> On 17.08.2010 14:18, Dmytro Mishchenko wrote:
>> Hello,
>>
>> In current version of Wikipbx Endpoint has one password field.
>> It's being used for SIP phone authentication and for accessing voice
>> mail box.
>>
>> I'm thinking about adding new field to Endpoint model for vm-password.
>> It'll allow to use secure passwords in SIP devices and at the same time
>> will allow to have simple password for voice mail box, which can be
>> entered from dial pad.
>>
>> Also it'll be great to support these fields too:
>>
>> vm-mailto       This is the user's email address for Voicemails
>>
>> vm-keep-local-after-email       Setting to false will delete the local
>> copy of the voicemail file after transmission of the mail message.
>>
>> vm-attach-file  Setting to true will attach the audio file to the main email
>>   
> Feel free to add this enhancements. Until we've added multi-tenancy in
> 0.8 we had to use our own voicemail app rather than mod_voicemail
> because the latter wasn't compatible with architecture that older
> versions of wikipbx used. That's why some things are missing in
> voicemail settings.
> 
> Those fields should have blank=True for people don't need voicemail,
> other than that it should be straightforward to implement.
> 
>> Let me know what do you think about it.
>>
>> In the same way we may need to extend SipProfile and Ednpoint models to
>> support options for controlling media path. Some general approach on
>> extending Wikipbx with FS supported features needs to be applied.
>>   
> As for extending WikiPBX:
> 
> * if we get a specific model with way too much optional fields, we can
> store them in another table as key-value pairs
> * we could allow user to override a specific model in settings file -
> just add it as a new setting and import model from that path rather than
> use hard-coded model object. User would be able to override this
> specific model in his apps.
> * we could let user override any config sent to freeswitch, i.e. add a
> setting like "CONFIG_OVERRIDES = {'config_name.xml':
> 'myapp.module.function'} and run that function when generating that
> config instead of that config.
> 
> So it's possible to make wikipbx extendable for a specific model. It's
> possible to override any view or template in user apps, so only
> overriding models is a problem. In our case, I think we should just add
> missing fields to SipProfile/Endpoint unless there would be too much of
> them.
> 
Thanks for explanation. I've extended Endpoint with voice mail relative
stuff.

Dmitry

> Stas.
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~wikipbx-dev
> Post to     : wikipbx-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~wikipbx-dev
> More help   : https://help.launchpad.net/ListHelp
> 
>