Or you could use the sip proxies to route just SIP-SIP calls between
them, and if you have asterisks paired with the SERs on each location,
the asterisks could route calls(via IAX for example) between
themselves (with no sip proxies inivolved) to and from the PSTN, after
having checked users' billing information. The billing database (cdrs)
need not be updated so frequently as the registered users database(if
you plan on having dynamic user registrations, i.e. via website).
That's what I plan on doing, but I guess it depends on your billing
strategy as well.
On Sat, 26 Mar 2005 12:26:07 +0100, Marian Dumitru
<marian.dumitru(a)voice-sistem.ro> wrote:
Hello Roger,
There are couple of available approaches for distribution you want to have:
1) all server use same DB (not recommended - due stretched DB
connection, the DB access will become realy bottleneck)
2) each server has is own database and via replication you synchronize
their content - the DBs will be equivalent;
3) make a static distribution of the users among the servers and route
between SERs to find where the called user is registered - each server
will have its one DB, but they will be complementary.
Depending of your NAT traversal approach and of how you map user IDs,
you see which one matches your requirements.
About PSTN routing, depends on how many GW you have, about their
location, etc.
Best regards,
Marian
Roger Thomas wrote:
I am planning to have 3 SER servers to handle
North, Central and South regions.
1) in this scenario, do I maintain ONE database in the Central region or otherwise ?
2) How do I configure SER so that it knows where to route PSTN calls to which server ?
--
Roger
--
Voice System
http://www.voice-system.ro
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers