Dbpbx

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
  
This module makes multi routing from a database.  
+
This module makes multi routing from a database. The file used for configuration is: dbpbx.conf.
  
 
For database access you can use [[PostgreSQL]] or [[MySQL]].
 
For database access you can use [[PostgreSQL]] or [[MySQL]].
Line 6: Line 6:
 
After enabling the multi routing parameter, the following queries can be done:
 
After enabling the multi routing parameter, the following queries can be done:
  
: - initial query to execute when module is initialized '''initquery'''
+
: - initial query to execute when module is initialized: '''initquery'''
: - Query for the initial routing message '''queryroute'''
+
: - Query for the initial routing message: '''queryroute'''
: - Query for subsequent retries '''queryretry'''. For this parameter '''retryneeds''' must be present to perform routing retries.
+
: - Query for subsequent retries: '''queryretry'''. Parameter '''retryneeds''' must be present to perform routing retries queries.
  
 
===Configuration===
 
===Configuration===

Revision as of 13:59, 11 June 2013

This module makes multi routing from a database. The file used for configuration is: dbpbx.conf.

For database access you can use PostgreSQL or MySQL.

After enabling the multi routing parameter, the following queries can be done:

- initial query to execute when module is initialized: initquery
- Query for the initial routing message: queryroute
- Query for subsequent retries: queryretry. Parameter retryneeds must be present to perform routing retries queries.

Configuration

File dbpbx.conf

[general]
; Global module settings that are read only at first initialization

; The following parameters enable handling of individual components
; Each must be enabled manually in this config file

; Enable multi router
;router=no


[priorities]
; Base priorities for each component

;router=20


[default]
; This section holds default settings for each of the following message handlers
; All these settings can be overriden in individual handler sections

; account: string: Name of the database connection to use
account=my
 

; In each of the following sections you have to specify the following:
; - initial query to execute when module is initialized
; - query to execute for each received message
; - result field to copy in message's textual return value (only for some)
; You can also override the settings from section [default]

[router]
; Multiple router
 
; Query for the initial routing message
queryroute=SELECT callto,mrid,priority FROM mroutes WHERE prefix='${called}' ORDER BY priority LIMIT 1

; Query for subsequent retries
queryretry=SELECT callto,priority FROM mroutes WHERE mrid=${mrid} AND priority>${priority} ORDER BY priority LIMIT 1

; Parameter that must be present to perform routing retries
retryneeds=mrid

; Inital query to execute on startup
;initquery=


See also

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers