[OGo-Discuss] phone call information to contacts in ogo

[Adam Tauno Williams]

--=-OnHypGt2ZdwY3nS85159
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> > > > > Either the asterisk/callweaver is writing the information directl=
y =20
> > > > > into the ogo database then, or is using an own database, and the =
=20
> > > > > info is synced to the ogo database. At least that would be sth. I=
 =20
> > > > > think I could implement, as I have no idea how to deal with two =20
> > > > > different databases at the same time, as the telephone numbers ha=
ve =20
> > > > > to be compared between these two.
> > > > I think there is nothing bad about storing a call log in the OGo =20
> > > > database. Though you should choose a better (more unique) table nam=
e!
> > > the table name is hardcoded in Asterisk, at least, when I take a look=
 at=20
> the=20
> > > config file, then I don't see a configuration option for the table na=
me.
> > 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.
> Many people use freepbx, that I mentioned earlier in an other thread. Thi=
s=20
> is based on mysql. I don't know much about mysql, but afaik trigger shoul=
d=20
> work there too.=20

Ugh.  Trigger/SPL support in MySQL is really primitive.  But you could
write some kind of slurp script easy enough to occasionally pull CDR
records into OGo.

> I'm not sure whether I can use such a trigger to pull data=20
> into an other type of database, running on another host or sth, but=20

Not from MySQL.

> generally you are right, a custom table in ogo, with only the stuff reall=
y=20
> needed makes sense for me too.
> > > > Personally I wouldn't want to have yet another tab in the person =20
> > > > viewer for just a call log. A generic journal would be nice, but al=
so =20
> > > > a lot of work.
> > > This is too much work for me right now, but what about overlaying the=
=20
> > > appointment tab with the phonecalls. After the phone call ended, info=
 is=20
> > > stored in teh database. Then when the user opens the appointment tab,=
=20
> > > 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 t=
o=20
> > > 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.
> I see, so they are more or less generally showing up in the using an=20
> appointment would have all the features needed, e.g. allow permissions,=20
> comments to the phonecall.

Yep.

> But also the other idea, adding notes to contacts seems a great idea for =
me,=20
> but where should they show up, in another tab, or maybe at the bottom of =
the=20
> attributes tab, or any better place?

I don't see how you'd do it other than another tab.  You quickly end up
with some contacts having lots of notes.  We've implemented contact
notes but we currently store them external to the OGo db.

--=-OnHypGt2ZdwY3nS85159
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBHYTxcLRePpNle04MRAgVMAJ9enCUEFRLwc1XN6TkSTVTvC4ZlKACdFG75
/w2NbsGu3mPMwSlUWL2FSN0=
=cTzE
-----END PGP SIGNATURE-----

--=-OnHypGt2ZdwY3nS85159--