CARRIERROUTE :: The Kamailio carrierroute Module

The module provides routing, balancing and blacklisting capabilities. More...

Files

• file carrierroute.c

  Contains the functions exported by the module.

  
  

• file carrierroute.h

  Some globals.

  
  

• file modules/carrierroute/config.h

  Carrierroute :: Configuration.

  
  

• file cr_carrier.c

  Contains the functions to manage carrier data.

  
  

• file cr_carrier.h

  Contains the functions to manage carrier data.

  
  

• file cr_config.c

  Functions for load and save routing data from a config file.

  
  

• file cr_config.h

  Functions for load and save routing data from a config file.

  
  

• file cr_data.c

  Contains the functions to manage routing data.

  
  

• file cr_data.h

  Contains the functions to manage routing data.

  
  

• file cr_db.c

  Functions for loading routing data from a database.

  
  

• file cr_db.h

  Functions for loading routing data from a database.

  
  

• file cr_domain.c

  Contains the functions to manage routing domains.

  
  

• file cr_domain.h

  Contains the functions to manage routing domains.

  
  

• file cr_fifo.c

  Functions for modifying routing data via fifo commands.

  
  

• file cr_fifo.h

  Functions for modifying routing data via fifo commands.

  
  

• file cr_fixup.c

  Fixup functions.

  
  

• file cr_fixup.h

  Fixup functions.

  
  

• file cr_func.c

  Routing and balancing functions.

  
  

• file cr_func.h

  Routing and balancing functions.

  
  

• file cr_map.c

  Contains the functions to map domain and carrier names to ids.

  
  

• file cr_map.h

  Contains the functions to map domain and carrier names to ids.

  
  

• file cr_rule.c

  Contains the functions to manage routing rule data.

  
  

• file cr_rule.h

  Contains the functions to manage routing rule data.

  
  

---

Detailed Description

It reads routing entries from a database source or from a config file at Kamailio startup. It can uses one routing tree (for one carrier), or if needed for every user a different routing tree (unique for each carrier) for number prefix based routing. It supports several routing domains, e.g. for failback routes or different routing rules for VoIP and PSTN targets.