[Serusers] Simplified multilateral peering for a lab environment

[Jim Dalton]

> Aaron Daubman wrote:
> > Greetings,
> >
> > I've found some decent documentation on secure multilateral peering 
> > for OpenSER, however I'm looking for something more simple.
> I assume you mean OSP, which is available for both SER 0.9.x 
> (in experimental CSV tree) and upcoming Ottendorf (in main 
> modules dir) http://siprouter.onsip.org/doc/modules/osp.html
> 
> http://www.transnexus.com/White%20Papers/Multi-Lateral%20Peeri
> ng%20with%20SER.pdf
> >
> > In a lab environment, I'm looking to set up four simulated 
> > geographically diverse networks all peering across a common 
> > backbone.
> > Each of the four networks should have its own SIP 
> > registrar.  What I'm 
> > looking for is a quick guide on how to allow each of the four 
> > registrars tell the other three what prefixes are 
> > registered with what 
> > address so that all SIP UAs can dial just an extension  to 
> > reach UAs in any of the four networks.

The CapabilitiesExchange message in the ETSI OSP protocol provides the
functionality you have described.  In the OSP model, each peer updates a
central OSP server with its routing capability rather than updating every
other peer in the network as you have described.  The OSP client on each SER
would send an OSP CapabilityExchange message to a central OSP server.  The
OSP CapabilityExchange message would tell the OSP server which prefixes are
served by the SER.  Each SER would then query the OSP server for
inter-domain routes.  A freely available version of the TransNexus
commercial OSP server can be downloaded from
http://www.transnexus.com/OSP%20Toolkit/Peering_Server/VoIP_Peering_Server.h
tm.  The OSP module for SER does not currently support the OSP
CapabiltiesExchange message as described above, but we can add this feature
to the OSP Module if you need it.