We do just that way - Kamailo to handle load balancing and clients, and Asterisk servers for routing, gateway etc....<div>You can forward calls to your main gateway which then will work with other gateways or calls from gateways to clients registered in Kamailio.<br>
<br><div class="gmail_quote">On Tue, Apr 3, 2012 at 3:15 PM, Rob Watkin <span dir="ltr"><<a href="mailto:robwatkin@gmail.com">robwatkin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br><br>I am just getting started with Kamailio and have been following the book "Building Telephony Systems with OpenSER" by Flavio E. Goncalves. The book describes an architecture with a SIP Proxy handling registrations and handing calls to a PSTN Gateway. I now have a basic test network running where calls are routed via the SIP Proxy (Kamailio) to a third party PSTN Gateway. I feel that a better design would be to implement my own PSTN Gateway using Kamailio. This single gateway would then handle all third party PSTN gateways. Thus one Kamailio server would be facing my clients while another would be facing my suppliers.<br>
<br>Is this a sensible architecture and are there any sample configurations for Kamailio performing this role?<br><br>Thanks<span class="HOEnZb"><font color="#888888"><br>Rob Watkin<br><br><br>
</font></span><br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br></div>