andrewgroup Posted January 10, 2008 Report Share Posted January 10, 2008 Using our configuration of a Windows XP Pro System with 45 Extensions and a regular call count of 15+ calls peaking at 23 (Full PRI) we base the following tips. A clean XP Pro or Server installation. 1GB RAM (ECC as a standard) 1 - Internal NIC for internal Phones 1 - Public Facing NIC for ITSP phones 1 - Nic for GATEWAY services (PRI or ANALOG) Set all services to manual and start to determine the minimal running services. we do use an Anti-Virus tool (but only with scheduled scans late in the day/morning. We do not use real-time scanning or real time updates as these services can consume CPU and affect active calls. We do apply the QOS recommended windows Patch. We do install Wireshark directly on the server and validate COS/TOS bits. We do use Wireshark to validate latency, SIP invites and SDP packets. We do use capable switches support both Port and VLAN tagging 802.1PQ We do use hardware based RAID Disk Controller with alerting. We do use SNMP and pull stats. We do use WMI performance monitoring. the above system when fully loaded with 23 active calls, the CPU peaks at 8% utilization and we can run Wireshark and create a complete trace and not affect call quality. your Mileage may vary. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 10, 2008 Report Share Posted January 10, 2008 Do you have a comparision number of CPU performance if you turn the real-time scanning on? I think it could be an important CPU performance difference. Also, I heared that once you installed PCAP (the Wireshark subsystem), it eats CPU no matter if you run Wireshark or not. This is because it puts itself somewhere in the driver stack and processes every packet. It is a rumor, maybe someone has more information about that. Quote Link to comment Share on other sites More sharing options...
Kristan Posted January 10, 2008 Report Share Posted January 10, 2008 I install wireshark as standard on all our PBX's, it just makes troubleshooting so much easier. I haven't noticed any major CPU problems, but then most of ours are well over spec'd anyway. Quote Link to comment Share on other sites More sharing options...
andrewgroup Posted January 10, 2008 Author Report Share Posted January 10, 2008 Do you have a comparision number of CPU performance if you turn the real-time scanning on? I think it could be an important CPU performance difference. An attachment is the last 24hours via WMI System Services a chart of the CPU processor on a 45 extension / with PRI 23channel SIP Gateway. This is an AMD 3100 single processor system, Also find a 48 hour incoming /outgoing call chart for the e1/t1 for reference. These represent a couple of slow days for the business thats affected by rainy days. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.