Difference between revisions of "Mod cidlookup"

From FusionPBX
Jump to: navigation, search
(unixODBC)
(cidlookup.conf.xml)
Line 22: Line 22:
 
==cidlookup.conf.xml==
 
==cidlookup.conf.xml==
 
PostgreSQL:
 
PostgreSQL:
  SELECT v_contacts.n_given || ' ' || v_contacts.n_family AS name, v_contacts_tel.tel_number AS number  
+
  SELECT v_contacts.n_given || ' ' || v_contacts.n_family ||' ('||v_contacts_tel.tel_type||')' AS name, v_contacts_tel.tel_number AS number
  FROM v_contacts, v_contacts_tel  
+
  FROM v_contacts, v_contacts_tel
 
  WHERE v_contacts_tel.contact_id = v_contacts.contact_id AND v_contacts_tel.tel_number = '${caller_id_number}'
 
  WHERE v_contacts_tel.contact_id = v_contacts.contact_id AND v_contacts_tel.tel_number = '${caller_id_number}'
 +
LIMIT 1
 +
 +
  
 
MySQL:
 
MySQL:

Revision as of 18:13, 1 November 2011

Overview

The scope of this is to allow the use of FusionPBX's Contacts module to populate phones with Caller ID Name. This is aimed towards a linux user.

Preface

There's one major drawback of using this - you cannot assign multiple people the same number as it will only return the first result.

Requirements

unixODBC mod_cidlookup at least mod_cidlookup installed with unixodbc support.

unixODBC

For CentOS:

yum install unixodbc unixodbc-dev
cd /usr/src/freeswitch
./configure && make mod_cidlookup-install

For Ubuntu

apt-get install unixodbc
apt-get install unixodbc-dev

cidlookup.conf.xml

PostgreSQL:

SELECT v_contacts.n_given || ' ' || v_contacts.n_family ||' ('||v_contacts_tel.tel_type||')' AS name, v_contacts_tel.tel_number AS number
FROM v_contacts, v_contacts_tel
WHERE v_contacts_tel.contact_id = v_contacts.contact_id AND v_contacts_tel.tel_number = '${caller_id_number}'
LIMIT 1


MySQL:

SELECT CONCAT(v_contacts.n_given, ' ', v_contacts.n_family) AS name, v_contacts_tel.tel_number AS number
FROM v_contacts, v_contacts_tel
WHERE v_contacts_tel.contact_id = v_contacts.contact_id AND v_contacts_tel.tel_number = '${caller_id_number}'