08-02-2013, 11:24 AM
Using DUNDi in a Cluster of Asterisk Servers!
1Using DUNDi .ppt (Size: 1.11 MB / Downloads: 25)
DUNDi and Asterisk Cluster
DUNDi™ is a peer-to-peer system
Fully-distributed with no centralized authority
Primarily used for dynamic extension lookup between Asterisk servers
Clustering Asterisk enables distribution of load
The Cluster can look and operate like one huge soft switch with built in failover and fault tolerance
DUNDi enables unified dial plans and Clustering gives scalability
Design considerations for IP Telephony networks
Design an environment that is self healing across the core soft switch (the Cluster)
Design an architecture with scalability and growth in mind, organic growth so incremental equipment costs are low
The provisioning process should be as simple as possible, but not simpler
Dynamic peer location and immediate contact of the User is the goal
ARA and MySQL Performance
Master database across network segment has performance limitations as Cluster scales
Replicate the Master database to each registration server Slave database
MySQL replication is simpler and cost less to implement than MySQL Cluster
Increase performance, small log file sent from Master to Slave database
Setup res_mysql to read from the local Slave database and write to the Master database (Digium Bug Tracker, Mantis Issue 5881)
Dynamic User Location
Where are Users registered?
It is the duty of the individual server to let the other servers in the cluster know where this SIP User is and how it can be contacted
The individual server has to realize that a SIP User is actively registered and in what context
Use ‘regcontext=<context>’ in sip.conf
Asterisk will dynamically create and destroy a NoOp priority 1 extension when a User registers and un-registers