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/

Reply via email to