[Spce-user] Sipwise CE 2.7 SBC config revisited

Jon Bonilla (Manwe) jbonilla at sipwise.com
Sun Mar 24 05:50:35 EDT 2013


El Sat, 23 Mar 2013 22:21:55 -0700
"William Fulton" <wfulton at thirdhatch.com> escribió:

> 
> >Th spce will always use sip_ext as incoming and outgoing interface for the
> >sip traffic. sip_int is only for internal communication of the spce elements.
> 
> >If you want the spce to communicate to the asterisk server and register
> >there, it will use x.x.x.x ip to go to y.y.y.x
> 
> 
> >Do you have the network and the routes prepared for that? You router should
> >have the routes for the spce to reach the asterisk server in the internal
> >>network.
> 
> >I think this is more a networking issue here.
> So the SPCE does not know to use eth1 to access servers on that subnet?  Is
> there a way to designate both eth0 and eth1 for sip_ext?


Hi William.

No, the spce will listen only a single ip address. From that address, it's up
to the network to provide routes to the internet and to any internal network
you want to reach.

Can't your router provide that? Can't your internal elements reach the spce's
public ip address?

You can always do it via "route commands" and "ip_forward" enabled on the
system. But the "normal" way of doing this is network routing in a router.

-------------- 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/20130324/12266e3e/attachment-0001.asc>


More information about the Spce-user mailing list