A server quotation is incomplete when it lists only CPU, RAM, and storage. The switch software, license, traffic pattern, support model, and operational responsibility determine whether the platform will work in production.
Define the traffic first
Estimate peak concurrent calls, CPS, average call duration, expected ASR, destinations, codec mix, whether media will be relayed, and whether recording or transcoding is required. A system handling short broadcast attempts behaves differently from one handling long support calls.
Confirm the software scope
Ask which switch and billing modules are installed, the version, license ownership, user and reseller limits, upgrade rights, rate-management tools, API availability, CDR access, fraud controls, and whether the operating-system license is included. Clarify recurring renewal or support fees.
Plan network and carrier connectivity
Confirm public IP addresses, data-center location, bandwidth, firewall policy, SIP and RTP ranges, carrier authentication method, supported codecs, and DDoS protection. If customers connect globally, consider latency to both users and upstream carriers.
Separate installation from management
Initial deployment may include the operating system, database, voice switch, portal, routes, rate tables, and sample customers. Ongoing work includes monitoring, backups, security updates, database maintenance, carrier changes, fraud review, and incident response. The contract should state which party owns each task.
Require acceptance testing
Before full payment or cutover, test account creation, billing, rate matching, origination, termination, caller ID, failover, CDR accuracy, concurrent-call limits, CPS, backup restoration, and administrative access. Keep a written configuration record and emergency contact process.