Hi all.
In further pursuing a 'Production Rollout' ready implementation of sipXecs, I had some final questions, mostly in regards to what can and cannot be Virtualized. Currently it is looking like anything that actually handles voice traffic (whether recorded messages or ongoing conversations) should remain physical due to timing constraints, but other Roles can be Virtualized. What I am loosely looking at then, in a server layout fashion, would be something along the lines of: SIPX1 - Physical Server (Internal network) - Management/Primary SIP Router SIPX2 - Physical Server (Internal Network) - Redundant SIP Router SBC1 - Virtual Server (DMZ) - Primary ITSP Gateway (SBC) SBC2 - Virtual Server (DMZ) - Redundant ITSP Gateway (SBC) SIPCN1 - Physical Server (Internal Network) - Conferencing SIPWM1 - Physical Server (Internal Network) - Voicemail SIPX3 - Virtual Server (Internal Network) - ACD/Instant Messaging Physical and Virtual Servers would all be 64bit, running a minimum of 8GB of RAM, the VM1 machine having extra storage space, and all with a good processors (well above the recommended listed in Michael's book) and GB Ethernet. Virtual Machines would have slightly less power, but the Roles are slightly less power hungry anyway. In this instance, Remote Workers would be connected via VPN to our internal network, so Remote Worker traffic would act just like 'inside user' traffic. Does the above seem like a plausible solution? As a secondary necessity - in regards to load testing - what tools of those available (like WinSIP) would any of you recommend? Peter Talbot [v1.0.07.109]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
