[Spce-user] Network Configuration

Jon Bonilla (Manwe) jbonilla at sipwise.com
Thu Apr 18 18:14:54 EDT 2013


El Thu, 18 Apr 2013 14:04:56 +0200
Thilo Bangert <thilo.bangert at gmail.com> escribió:


> 
> we have solved this by having provider specific peering gateways, consisting 
> of a kamailio and sems combo on a different (virtual) host.
> 

I have found this requirement, where the peer requires a vpn or any other
tunnel scenario to be established to send the traffic and they will only accept
traffic from the tunnel. Most common carrier asking for this is British Telecom
(BT)

The extra_socket option does not work here because the rtp will still be sent
and received in the default ip address, which is not the one used for the
tunnel.

2 ways of dealing with it:

* Create the tunnel in your router. This is the "righ way" (imho). I've also
  seen operator purchasing a small cisco router just for this function. It's
  easy and cheap.

* Use an aditional spce to route the calls between the tunnel and the main
  spce. This is the same Thilo achieves with his kamailio-sems combo. This
  additional spce will listen in the tunnel address and that ip will be
  routeable from/to the main spce's default ip address.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130419/0e72dd36/attachment-0001.asc>


More information about the Spce-user mailing list