Differences

This shows you the differences between two versions of the page.

--- userdoc:tt_asterisk-odbc [2014/07/03 18:41] – [Mass Deployment SQL Table] abelbeck
+++ userdoc:tt_asterisk-odbc [2014/07/03 19:02] (current) – [Mass Deployment SQL Table] droemel
@@ Line 121: / Line 121: @@
   );
-Following the examples above, adding a context to ''/etc/asterisk/func_odbc.conf'' to define a new function, the dialplan can use the PhoneProv data.
+Following the examples above, adding a context to ''/etc/asterisk/func_odbc.conf'' to define a new function, the dialplan can use the PhoneProv data. Here is an example which fits the new 'phoneprov' table:
+  [SIPACCOUNT]
+  dsn=asterisk
+  readsql=SELECT ${ARG1} FROM phoneprov WHERE ${ARG2}='${SQL_ESC(${ARG3})}'
+In the dialplan you could then use something like this:
+  same => n,Set(val=${ODBC_SIPACCOUNT(account,ext,100)})
+to get the SIP account (peer-name) from a given extension (100) via SQL.
 Detailed Mass Deployment documentation can be found here:
 **[[userdoc:tt_ip_phone_provisioning|IP Phone Mass Deployment]]**
 ===== CDR Call Logging with SQL =====