Hello,
On 26.04.23 00:38, jdprsaga@gmail.com wrote:
Hello All, new subscriber here.
I've been reading kamailio documentation to check if kamailio has a use case on the architecture for the solution for my company's software, here an small architecture diagram of our solution.
sipclient <----> [ Middleware ] <-----> SBC
Our middle ware is both a sip proxy and media proxy. we have a large number of sip clients but a small calling number,
our current bottleneck is that the middleware can't handle a high number of registration, i would like to deploy Kamailio as a load balancer for registrations, making sure it is statefull so registrations and calls are hashed into the same middleware server.
sipclients < ----> [ kamailio ] <------> [ middleware1, middleware2,...,middleware N] <-----> SBC
Any thoughts or pointers?
assuming the middleware is the registrar server, if it support the Path header extension for SIP, the it should be simple, in kamailio side you can use dispatcher module for load balancing and path module to add Path headers to REGISTER requests.
If the registrar does not support Path, then you need to mangle the contacts in order to ensure that traffic towards sipclients go through kamailio, so NAT traversal can be ensured. Doable, but with some extra operations done in kamailio config.
Cheers, Daniel