Tony and Michael
Thanks for the replies. I can see both of your viewpoints and in they both make sense. In an imperfect world we make compromises and it sounds like you are on the way to making one that will do the job. Even if just the SBC gets admission control now that would help us engineer a solution that would give us the control we want. I am not sure if you guys have seen the Zultys IP PBX. It is similar to the Sipx in that it has an embedded SBC and a stateless proxy. There is a powerful policy engine that allows you to run either stateless, or stateful depending on a matrix of source/destination addresses/subnets. Even when your calls are stateless, it still keeps track of the calls and the bandwidth to each destination. It allows you to set a bandwidth limit on every SIP trunk and remote site (you can define sites by subnet). You can still come unstuck when all your remote users and remote trunks are through a single WAN link and the only way to guarantee you won't over commit the link is to make sure the sum of all your sites and servers don't exceed your link commit. This is not perfect, but I personally think it is better to have less capacity but perfect audio over the other way around. I will stick around and watch what is going on. The beauty of Virtualisation means I can keep all the systems running at once. -- Regards Mark Dutton _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
