It can support multiple domains by using domain aliases... Again, they are not isolated though.
You'll want to test as there may be some features that don't work with domain aliases. I can't recall what they are off the top of my head though (this could be old stored knowledge though). Mike On Tue, Apr 26, 2011 at 9:17 AM, Deon Vermeulen <[email protected]>wrote: > Hi Tony > > Thank you very much for your explanation. > > I come from the SER environment and know how to manipulate the SIP > Signalling to do what I want it to do. > > SER is a great product and provides an excellent Provider/Carrier solution, > and I would advise anyone wanting to be a Carrier to use that platform, but > it really lacks in a Great Enterprise PBX like features, which is why I > decided to look into sipx. > > There are also a lot of similarities between SER and sipx, i.e. the > Scalability, Modular Design and also the ability to distribute services > across multiple physical hardware. > > Is there a way I can make sipx support multiple domains? > > > Thank you very much > > Rgds > > > > On Apr 26, 2011, at 12:55 PM, Tony Graziano wrote: > > > Media Relay: Determines the behavior adopted by the NAT traversal > > feature when it detects that two remote (i.e. far-end) NATed endpoints > > report the same public IP address. When in aggressive mode, a media > > relay will be used to carry the media between the two endpoints. When > > conservative is used, endpoints will be instructed to stream their > > media directly to each other. > > > > > > Though I doubt the aggressive setting will work with every scenario. > > Do not assume STUN is there to do anything OTHER than to allow the > > system to discover its IP address (when dynamic ip is used). The > > recommended setting for remote users is to not use stun, and to turn > > off any ALG or sip helper applications, including ICE, STUN, and let > > them connect to sipx. The aggressive media relay setting may not work > > reliably in every remote user scenario. > > > > This is where a commercial sbc would typically be deployed. > > On Tue, Apr 26, 2011 at 6:54 AM, Deon Vermeulen > > <[email protected]> wrote: > >> Hi Michael > >> Thank you for the reply. > >> At the moment I'm not really worried about multi tenant, but that would > >> really be a great benefit for further product offerings. > >> I'm actually more concerned and very interested int he way sipx will > handle > >> NAT traversal. > >> I only see documentation where STUN is being used for NAT Traversal. > >> I would rather have RTP go directly to end devices when detected behind > the > >> same NAT device then having to traverse the STUN server. > >> > >> Thank you > >> Rgds > >> > >> > >> On Apr 26, 2011, at 11:34 AM, Michael Picher wrote: > >> > >> There is no multi-tenant capabilities in the system (yet). The system > was > >> built as a communications platform for an enterprise (an as in 1). > >> > >> That being said, if you want to put up a small box per customer that's > >> probably the safest bet at this point. > >> > >> At eZuce we'll be working towards a hosted solution once some major > database > >> changes are implemented in 4.6. > >> > >> Mike > >> > >> On Tue, Apr 26, 2011 at 5:44 AM, Deon Vermeulen < > [email protected]> > >> wrote: > >>> > >>> Hi List > >>> > >>> I'm very new to the list, so please forgive me if this has been > mentioned > >>> in earlier discussions. > >>> > >>> I really like sipx especially the modular design. > >>> > >>> I would like to offer this as an Provider solution to my current > >>> customers. > >>> > >>> Can anyone refer me to documentation, guides, tutorials on how I can > setup > >>> sipX as a provider platform? > >>> > >>> I'll only work with Public IP's but server(s) will be behind Firewalls. > So > >>> No Private IPs on the Server(s). > >>> How will sipX handle NAT in this situation. > >>> My idea is that RTP should not be proxied but rather have RTP route > >>> directly between devices especially if they are behind the same NAT > device. > >>> > >>> > >>> Thank you very much > >>> > >>> Rgds > >>> _______________________________________________ > >>> sipx-users mailing list > >>> [email protected] > >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >> > >> > >> > >> -- > >> There are 10 kinds of people in this world, those who understand binary > and > >> those who don't. > >> > >> [email protected] > >> blog: http://www.sipxecs.info > >> call: sip:[email protected] > >> _______________________________________________ > >> sipx-users mailing list > >> [email protected] > >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >> > >> _______________________________________________ > >> sipx-users mailing list > >> [email protected] > >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >> > > > > > > > > -- > > ====================== > > Tony Graziano, Manager > > Telephone: 434.984.8430 > > sip: [email protected] > > Fax: 434.326.5325 > > > > Email: [email protected] > > > > LAN/Telephony/Security and Control Systems Helpdesk: > > Telephone: 434.984.8426 > > sip: [email protected] > > > > Helpdesk Contract Customers: > > http://support.myitdepartment.net > > Blog: > > http://blog.myitdepartment.net > > > > Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > > _______________________________________________ > > sipx-users mailing list > > [email protected] > > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- There are 10 kinds of people in this world, those who understand binary and those who don't. [email protected] blog: http://www.sipxecs.info call: sip:[email protected]
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
