Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
tbd:mass_virtual_domains [2009/04/29 15:29] janakj |
tbd:mass_virtual_domains [2009/04/29 15:46] (current) janakj |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| Such a server can figure out whether it is reponsible for a particular | Such a server can figure out whether it is reponsible for a particular | ||
| virtual SIP domain from DNS, adding support for a new SIP virtual domain | virtual SIP domain from DNS, adding support for a new SIP virtual domain | ||
| - | requires no manual intervention | + | requires no manual intervention |
| ===== State of the Art ===== | ===== State of the Art ===== | ||
| Line 46: | Line 46: | ||
| If the sip-router server receives a request for a domain that is not on the | If the sip-router server receives a request for a domain that is not on the | ||
| list of supported domains then the domain module can lookup the SRV record for | list of supported domains then the domain module can lookup the SRV record for | ||
| - | _sip._udp in that domain and if it points to the server itself then the server | + | _sip._udp |
| - | is reponsible for the domain. In such case the domain module will add the | + | the server itself then the server |
| - | domain to the list of supported domains automatically. | + | the domain module will add the domain to the list of supported domains |
| + | automatically. | ||
| ==== Deliverables ==== | ==== Deliverables ==== | ||
| - | * We will xtend the sip-router domain module with a function which gets as a hostname as an argument and consults DNS to determine whether the hostname should be part of a new or existing virtual domain supported by the server. | + | * We will extend |
| * We will modify the domain module to add missing entries into its internal memory cache of supported virtual domains. | * We will modify the domain module to add missing entries into its internal memory cache of supported virtual domains. | ||
| * We can enhance the module and make it synchronize the contents of the internal memory cache with the contents of the database. Newly added virtual domain (dynamically learned) will be added to existing entries in domain table. | * We can enhance the module and make it synchronize the contents of the internal memory cache with the contents of the database. Newly added virtual domain (dynamically learned) will be added to existing entries in domain table. | ||
| Line 58: | Line 59: | ||
| * Devise a system for storing additional configuration information about virtual domains in the DNS zone of a domain. The additional information we might want to store in the DNS zone comes in form of attribute-value pairs, it can be used, for example, to configure the unique id of the virtual domain, peering policy, various options related to digest authentication, | * Devise a system for storing additional configuration information about virtual domains in the DNS zone of a domain. The additional information we might want to store in the DNS zone comes in form of attribute-value pairs, it can be used, for example, to configure the unique id of the virtual domain, peering policy, various options related to digest authentication, | ||
| + | ===== Reading List ===== | ||
| + | * The domain module [[http:// | ||
| + | * [[http:// | ||
| + | * [[http:// | ||
| + | * [[http:// | ||
| + | * [[http:// | ||
| + | * [[http:// | ||
