6 Dec
2006
6 Dec
'06
4:44 p.m.
Greetings,
I've found some decent documentation on secure multilateral peering
for OpenSER, however I'm looking for something more simple.
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.
Right now I'd like to leave things unsecured if possible (no need for TLS).
Also, if there are any good pointers for setting up the DNS in each of
the four networks (each network will have its own DNS as well as SIP
server) those would be useful.
Finally, IPv4 references would be helpful, but seeing as this will be
a v6-only setup, any reverences to IPv6 configuration guides regarding
the above would be especially useful.
Thanks again,
~Aaron
6 Dec
6 Dec
4:45 p.m.
New subject: [Serusers] Simplified multilateral peering for a lab environment
Greetings,
I've found some decent documentation on secure multilateral peering
for OpenSER, however I'm looking for something more simple.
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.
Right now I'd like to leave things unsecured if possible (no need for TLS).
Also, if there are any good pointers for setting up the DNS in each of
the four networks (each network will have its own DNS as well as SIP
server) those would be useful.
Finally, IPv4 references would be helpful, but seeing as this will be
a v6-only setup, any reverences to IPv6 configuration guides regarding
the above would be especially useful.
Thanks again,
~Aaron
7 Dec
7 Dec
12:08 p.m.
New subject: [Serusers] Simplified multilateral peering for a lab environment
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%20Peering%20with%20S…
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.
You can hardcode the prefixes in ser.cfg and then test
src_ip to allow
INVITEs from one of the peers (if you have one fixed prefix for each
network).
Right now I'd like to leave things unsecured if possible (no need for
TLS).
Also, if there are any good pointers for setting up the DNS in each of
the four networks (each network will have its own DNS as well as SIP
server) those would be useful.
I'm not sure what you are looking for. If you
have domain1.com
domain2.com and so on, you just configure DNS SRV for each (ex.
_sip._udp.domain1.com.
http://www.voip-info.org/wiki-DNS+SRV
Finally, IPv4 references would be helpful, but seeing as this will be
a v6-only setup, any reverences to IPv6 configuration guides regarding
the above would be especially useful.
What do you think should be special for
IPv6?
g-)
Thanks again,
~Aaron
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
3:31 p.m.
New subject: [Serusers] Simplified multilateral peering for a lab environment
Aaron Daubman wrote:
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.
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. 
2:09 p.m.
Aaron Daubman wrote:
Greetings,
I've found some decent documentation on secure multilateral peering
for OpenSER, however I'm looking for something more simple.
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.
There is no single solution. You can either use dedicated extension per
server (if the user has a home proxy and always registers to its home
proxy), e.g.
1000-1999 server 1
2000-2999 server 2
....
or you can have a database where you store which extension is on which
server and load the next hop with avp_db_load (of course all proxies
need access to this database). If users choose a registrar dynamically,
you have to update this database, e.g. with avp_db_write after
sucessfull REGISTER.
you can also use a private ENUM tree (if users always have the same home
proxy)
Right now I'd like to leave things unsecured if possible (no need for TLS).
I would suggest to use TCP when the traffic goes via public internet as
UDP is spoofable, or use IPsec betwenn your proxies. Then UDP is fine too.
regards
klaus
Also, if there are any good pointers for setting up
the DNS in each of
the four networks (each network will have its own DNS as well as SIP
server) those would be useful.
Finally, IPv4 references would be helpful, but seeing as this will be
a v6-only setup, any reverences to IPv6 configuration guides regarding
the above would be especially useful.
Thanks again,
~Aaron
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
--
Klaus Darilion
nic.at
6564
days inactive
6565
days old
4 comments
4 participants
participants (4)
-
Aaron Daubman -
Greger V. Teigre -
Jim Dalton -
Klaus Darilion