[asterisk-users] Locking phones at night...

Benjamin Jacob benjamin.jacob at masconit.com
Wed Oct 18 05:35:34 MST 2006


Tzafrir Cohen wrote:

>On Wed, Oct 18, 2006 at 05:26:49PM +0530, Benjamin Jacob wrote:
>  
>
>>Conrad Wood wrote:
>>
>>    
>>
>>>On Wed, 2006-10-18 at 13:24 +0200, Tzafrir Cohen wrote:
>>>
>>>
>>>      
>>>
>>>>On Tue, Oct 17, 2006 at 09:42:37PM +0100, Conrad Wood wrote:
>>>>  
>>>>
>>>>        
>>>>
>>>>>On Wed, 2006-10-18 at 08:55 +1300, Hadley Rich wrote:
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>>>On Wednesday 18 October 2006 05:47, Conrad Wood wrote:
>>>>>>      
>>>>>>
>>>>>>            
>>>>>>
>>>>>>>To do something similar, I created a dialplan extension that - if
>>>>>>>dialled - creates a file on the server. If dialled again, it removes 
>>>>>>>the
>>>>>>>file again.
>>>>>>>Then, in the context of the phone I check for existence of that file 
>>>>>>>and
>>>>>>>if it exists I play a busy signal and hangup. (Of course, unless the
>>>>>>>extension to re-enable it is dialled ;) ).
>>>>>>>Additionally, I ask the user for a password to lock/unlock it.
>>>>>>>        
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>This is a good use for the AstDB
>>>>>>      
>>>>>>
>>>>>>            
>>>>>>
>>>>>Sure is,  but files in the filesystem are easier to process from
>>>>>external (non-asterisk) programs. In my case, I have a web interface
>>>>>that locks/unlocks phones too.
>>>>>I find it most convenient  to use 'ls' to look up the current status of
>>>>>stuff.
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>asterisk -rx could also be used. Or a phone menu. Problems with a phone
>>>>menu: how can you tell the status?
>>>>
>>>>  
>>>>
>>>>        
>>>>
>>>asterisk -rx requires access to the asterisk console which throws its
>>>own bunch of problems with permissions and scalability.  I'd then prefer
>>>to code it through the manager interface but that seems like a terrible
>>>overkill here ;)
>>>How would you use a phone menu for that? That sounds interesting. Our
>>>users here like doing phonestuff on their phones rather than on websites
>>>etc.
>>>
>>>Conrad
>>>
>>>
>>>_______________________________________________
>>>--Bandwidth and Colocation provided by Easynews.com --
>>>
>>>asterisk-users mailing list
>>>To UNSUBSCRIBE or update options visit:
>>> http://lists.digium.com/mailman/listinfo/asterisk-users
>>>
>>>
>>>
>>>      
>>>
>>am I missing something important over here??
>>DB, more specificaly, having ODBCput and ODBCget operations solve all 
>>these issues, dont they.
>>read the post abt "Stopping putgoing calls after working hours" (well.. 
>>the subject says so!! )
>>
>>have your astdb in sql. simple.
>>    
>>
>
>This means that there is a ODBC lookup per call. 
>
well.. i believe it wud be beter than running an external script, thru 
asterisk for every call. gotta test that :-)
u'll be eating up cpu, along with asterisk doing its own work.
there was some talk abt local dbs n remote dbs and the performance on 
some voip-info page for asterisk. Cant seem to find it right now.

>And if the remote
>database fails, the PBX fails as well. 
>
well. thats where redundancy n HA come into picture... for that sake, 
even the internal Berkely DB could fail.

>For the sake of simplicity, it
>might be preferred to use the internal Asterisk DB.
>
>  
>
aahh.. i wasnt talking of simplistic setups :-)

>Is there a simple and safe way to query the astdb database outside of
>Asterisk?
>
as i said. ODBC ops!!

cheerz
- Ben


More information about the asterisk-users mailing list