[OGo-Discuss] phone call information to contacts in ogo
Adam Tauno Williams
discuss@opengroupware.org
Thu, 13 Dec 2007 07:39:47 -0500
> > On 13.12.2007, at 10:44, Sebastian Reitenbach wrote:
> > > Either the asterisk/callweaver is writing the information directly
> > > into the ogo database then, or is using an own database, and the
> > > info is synced to the ogo database. At least that would be sth. I
> > > think I could implement, as I have no idea how to deal with two
> > > different databases at the same time, as the telephone numbers have
> > > to be compared between these two.
> > I think there is nothing bad about storing a call log in the OGo
> > database. Though you should choose a better (more unique) table name!
> the table name is hardcoded in Asterisk, at least, when I take a look at the
> config file, then I don't see a configuration option for the table name.
If you want CDR data from Asterisk to appear in the OGo database and
both are using PostgreSQL there are several pretty simple DB magic
tricks to pull that off.
The easiest would be to just trigger from the CDR (Call Detail Record)
table to create a note (or whatever). It would also allow you to be
selective about what CDR data you bought over.
> Or maybe better a separate table like the date_info table?
Ugh, not another _info table. I think we already have enough
superfluous joins going on.
> > Personally I wouldn't want to have yet another tab in the person
> > viewer for just a call log. A generic journal would be nice, but also
> > a lot of work.
> This is too much work for me right now, but what about overlaying the
> appointment tab with the phonecalls. After the phone call ended, info is
> stored in teh database. Then when the user opens the appointment tab, the
> call record shows up, Allow the user to click on it, to make notes.
> Well, I think an own tab, with a plain list, would be easier for me to
> implement, but I think that is sth. I could do too.
We already store calls in the scheduler. The interface in our CRM just
adds the call with the caller and callee as participants and type "call"
and conflicts disabled. So far it works just fine.