[OGo-Discuss] OGo and asterisk

[Sebastian Reitenbach]

Hi,

discuss@opengroupware.org wrote: 
> On Nov 20, 2006, at 13:40, chris h wrote:
> > I think what is needed is a brief discussion on the management of
> > commercial/business voice mail, some standard practices or  
> > protocals and then a discussion on implementation.
> 
> Hm, yes. Personally I'm going to approach this from the technical  
> (that is: incorrect ;-) side. Its still on my tasklist to implement  
> the Asterisk dialout feature and as part of this I'm going to check  
> what other features the API provides (and implement "low hanging  
> fruits" :-)
> 
> I'm not really a fan of retrieving vmail manually from the  
> filesystem. Though it might be viable.

getting a bit more technically:
the asterisk can nfs export the voice mail directory structure, ogo could import
it, to 
have access to the voice-mails. or in the other direction, ogo exports a
directory, and 
the asterisk imports it to store the messages on it. However, I wouldn't go and
copy them.

Or the messages could be forwarded to the users mail account, Asterisk has to
add some 
special mail headers, like X-Asterisk-Callee: X-Asterisk-Caller:
X-Asterisk-Duration:
and so on, so that
1. other icons can be used for voice mails (to see at a first glance which is a
voice mail 
   and which is e-mail)
2. applying filters would be easy
3. these header lines shall be kept intact when forwarding the message to
another user


not only voice mails, but also call recordings shall then be handled the same
way as the 
voice mails.

> 
> 
> Wrt to adding tabs to the person or enterprise viewer: actually my  
> biggest concern is that the tabs will wrap or make the page  
> scroll! :-) We already have plenty of tabs which makes the page  
> really "wide" (well, not a big deal with all those widescreen  
> displays ;-)
> 
> What would be cool is a new UI "wrapper" element (similiar to  
> SkyTabView/SkyTabItem) which allows to arrange page sections in  
> either tabs or collapsibles [or xyz]. Actually this shouldn't be too  
> hard to implement though pages can get slow if users will put too  
> much information on a single one (eg all current tabs into a single  
> one :-)
well, a completely different topic, but this explains my why ogo does send a
status 
message for every folder to the imap server when opening the search or vacation
tab in ogo 
web mail.


kind regards
Sebastian