Just a question on the SBC's, as they are handling voice as well, wouldn't there be a (possible) issue with VM. TeTeTeTalking with the outside world should be PePePePerfect IMHoHO.
Paul From: Mark Theis <[email protected]> To: Discussion list for users of sipXecs software <[email protected]> Date: 23-09-2010 06:40 Subject: Re: [sipx-users] SIP Server Questions (Virtual vs Physical) Sent by: [email protected] Peter, I like your plan. I am not an expert (maybe because I have only been working with this for a month or so) yet, but…. What were you thinking to use as your SBC1 and SBC2? Each of your other devices’ names hinted at (or explicitly said) sipXecs… but the SBC has me wondering. Are you thinking to have 2 separate ITSP Gateway (SBC) sipXecs VM’s? As you might have noticed from my last post a couple minutes ago, I want to do something very similar to yours… but… all of my users will be external. And… I have my servers geo-diverse. This may be a problem for me, but I could not find another solution aside from sipXecs that claimed the ability to solve my problems. Thanks! Mark Theis Southern California Telephone and Energy Office (951) 693-1880 Ext. 212 Fax (951) 693-1550 Cell (951) 545-1013 or (949) 682-VOIP 27515 Enterprise Circle West Temecula, CA. 92590 [email protected] From: [email protected] [ mailto:[email protected]] On Behalf Of Talbot, Peter Sent: Wednesday, September 22, 2010 1:43 PM To: Discussion list for users of sipXecs software Subject: [sipx-users] SIP Server Questions (Virtual vs Physical) 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]_______________________________________________ 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/
