Hi,

As Daniel said, Kamailio is a SIP-Proxy, not an SBC, thus it does not provide such solution.

if you use SEMS (or it's commercial version: FRAFOS ABC-SBC) or any similar SBC, then you can use dispatcher-module to distribute the calls up to a certain limit to each SBC. Kamailio will send an "OPTIONS" request to the according SBC and the SBC would return with a "5xx"-error-code, so it would be temporarily removed from it's distribution list. As the OPTIONS request is only done only frequently, calls above that limit would be declined by the SBC with a "5xx" error-response as well, which then could be re-routed by Kamailio to another SBC from the distribution list. If you want to limit the load from the Kamailio side towards the SBC, that does work, too. However, it get's quite complicated (but doable) if you want to distribute the information on load to several Kamailio servers.

Thanks, Carsten

2014-12-09 11:16 GMT+01:00 Ludovic DURAND ldurand@sii.fr:

Hi,

The purpose of projet is to implement a VoIP secure solution with Kamailio as core IMS network. In this project VoIP call will be established with zRTP. SBC is transparent for zRTP call, zRTP is establish between 2 end point (terminals), SBC don't decrypt or encrypt the call. Thus SBC don't modify codec. Is there a SBC solution provided by Kamailio ?

How is managed the SBC failover mecanism ? is there SBC backup ? What is the status of context registered in Kamailio (P-CSCF & S-CSCF) in case of SBC failure ?

- Is it deleted automatically ?

- dispatched to another SBC (backup SBC) ?

Is there mecanism in Kamailio to check SBC overload and manage a dispatching of zRTP call to available SBC ?

Question related to P-CSCF and S-CSCF : - Is there redundant function (such as active/active or active/standby solution) of contextual data (customer data stored at the registration REGISTER on P-CSCF and S-CSCF) ?

Best Regards Ludovic DURAND SII

---

sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev