What a 4-week softswitch pilot should prove

7 min read

The MOR online demo and the M4 SBC online demo open the admin screens. Neither screen can place a call on your carriers. An operator who has clicked through the menus has three questions left: what counts as a passed test, what to send before day 1, and what happens when the month ends.

A Pilot Project is that test. It runs for one month on a current MOR or M4 system, on your server or on a hosted server. You pass or fail on a written checklist. The cap is the same if you sell termination, hosted PBX seats, or dialer traffic: two providers, one tariff, and up to ten endpoints that match the service you sell.

The demo stops at the menus

Open either demo and you can click Providers, tariffs, and users. Both pages state that you get the web interface and that real calls are not possible. Your carriers are not connected, so a click there cannot show whether a prefix on your sheet would match the CDR.

A feature list has the same hole. It can show that failover and rate import exist. It cannot show that your two carriers accepted a call, or that a one-minute test matched the row on your sheet. Those two checks happen on the pilot, with support and a Zoom session while you do them.

Four proofs, in this order

The pilot page defines success as a go or no-go against a fixed list. The order is calls, then prices, then the endpoints you sell, then a written decision. A price check needs a completed call. An endpoint check needs a rate. The decision needs the written list.

Week What has to be true at the end of the week
1 Admin access works. Both providers pass inbound and outbound. You have written down the failover test.
2 You have imported up to two rate files and set one customer rate plan. Sample calls match the sheet.
3 Up to 10 endpoints, chosen for what you sell, register. You have placed an inbound call and an outbound call from them.
4 The handoff is written. The review ends in continue or stop.

Week 1: two of your providers, and a failover you watched

In the Zoom session you connect up to two providers, with an engineer on the call. For each provider, an inbound call and an outbound call have to complete. Then you configure failover, run the test, and write it down.

Bring two trunks you run today. Provider A is the first choice. Provider B is the second. Place a call to your test number. Then make provider A fail: pull the route, or dial a number provider A will not complete, and place the same call again. The second call has to leave on provider B. The switch tries the next provider when the first one does not complete the call. That second attempt is the failover test. One trunk cannot show it. If you also sort providers by price, that order is a separate setting from this test.

Set the currency and the time zone in this same week, before you judge a rate.

Week 2: your sheet, and a sample call that matches it

In the session you import provider rates from up to two files and set one customer rate plan, or one user tariff. Then you place sample calls and compare the rated price with the row for that prefix. If you bill end users, that one tariff is the user’s tariff, and the sample call is the charge you would show them.

A file the importer accepts has two required columns, prefix and price. Write prefixes in E.164, with no international prefix stuck on the front. Match the separator in the file to the separator in the system settings. Send the file you bill from, not a shortened sample. If the separator is wrong, the import fails, and the sample call prices against an empty tariff. On the ticket, name the billing increment and the date that rate starts. A prefix row can match and the CDR can still miss your sheet when those two differ.

Automatic Tariff Import, the add-on that pulls later files from email, is a separate module. The four weeks cover a manual import of those one or two files and the sample-call check. Name that add-on on the pricing form if you want email import on the quote after the pilot.

Week 3: your endpoints, both directions

In the session you configure up to 10 users or endpoints and check that they register. From those endpoints you place an outbound call and you receive an inbound call.

Ten is the cap, not a pile of desk phones. Pick the ones that match what you sell:

  • You sell termination. Use the slots for the SIP trunks or origination points you send. A desk phone is optional. Your pass is the two providers, the failover you watched, and the rated sample.
  • You sell hosted PBX seats. On MOR, one of the ten is an end user. If a reseller sells that user, create the reseller under Settings → Users with user type reseller, log in as that reseller, and create the user there with the one tariff on that user. Place one call. The charge is on that user, and the reseller’s balance moves with it. That is the Reseller addon. M4 has no reseller addon. The rest of the phones wait.
  • You send dialer or contact-centre traffic. One of the ten is the SIP leg the dialer uses. Place the sample calls the way the dialer places them and read those CDRs. That is enough to book. On MOR, recording is the Recordings addon: allow it on the user, and set Record calls for this Device to yes on that leg. MOR does not record a call that stays between two SIP devices, so the sample has to leave through a provider. M4 has no recordings addon, so on M4 the proof is the CDR, not an audio file. A report that ranks every campaign from last month, and the busy-hour CPS, are for the quote and the later move. The ten sample calls will not produce them.

If those endpoints register and complete both directions, you have the proof the checklist asks for.

Week 4: a written handoff, then continue or stop

Before the month ends, you and the engineer review the list. The handoff lists the configuration, the tests, the items left out, and the next step. Write the result you came for on that page: failover on your two carriers, one user rated on your tariff, or the sample CDRs from the dialer. The meeting ends in a go or a no-go. A note that the screens looked fine is not a line on that page.

What to send before day 1

The month starts when the trunk card and the files arrive. The login email is not the start.

Send this:

  • Trunk details for up to two providers: IP or domain, how they authenticate, codecs, and a test number for each direction.
  • One or two rate sheets, in the format you send to customers or receive from carriers.
  • The currency and the time zone for the system and the reports.
  • Up to 10 endpoints, and how each one will register (IP, or username and password). Name what they are: SIP trunks, a reseller’s user on MOR, or the dialer’s SIP leg.
  • The result you want written on the handoff.
  • Peak concurrent calls and peak CPS, for the quote. This is not a load test.
  • Which product you are testing, MOR or M4. The split is on MOR vs M4.
  • Your own server, or hosted.

On your own server, prepare the machine before day 1. Kolmisoft gives 8 working hours for a simple single-server install, counted from the time the server and the access details are available. A multi-server layout or a redundant pair takes longer. On a hosted system, Kolmisoft provides the server, and you skip that machine prep.

The pilot page says up to 2 hours of shared-screen Zoom is the plan for the configuration and the questions that come up while you work. Book it with a support ticket. Name the time and the topics. If carrier auth runs past that window, book the rest from the same ticket. Open a support ticket for the other questions too. The support desk works Monday to Friday, 08:00 to 18:00 EET, and answers a blocker ticket at any hour.

noreply@kolmisoft.com sends the admin login when the system is up.

Work that waits until after you decide

The pilot is guided setup of a base configuration, plus the checks above. The month still proves failover, one rated tariff, and the endpoints you picked. Three other jobs are separate, and they start after you decide to continue:

  • A move off the switch you run today. Rates for the whole customer list, the DIDs, and the rest of the endpoints wait until a go.
  • A report, a field, or a routing rule the product does not have. That is a separate request after the go. The four weeks do not build it. The checklist still stands without it.
  • A fraud review or a margin review. The pilot rates the sample calls you place. Last quarter’s CDRs, and any redesign of routing for profit, are another piece of work.

Kolmisoft can extend the pilot by agreement if the checklist needs more time. The extension changes the schedule. It does not add those three jobs.

Capacity, without a load test

Two trunks and ten endpoints will not show your busy-hour ceiling. Do not point a traffic generator at the pilot and call the result a production limit.

Write down two peaks from your busy hour. Concurrent calls are the calls up at one moment, ringing and setup included. Calls per second are the new attempts in that second, failed attempts included. Add whether media, recording, or transcoding will sit on the same machine. How big a system you need explains those two numbers. Read the current figures on Softswitch performance and Recommended hardware. Kolmisoft updates those pages. If a number in the sizing post and a number on those pages disagree, use the pages.

On the performance page, the check of a proposed setup is a pilot that runs your traffic and the features you will turn on. In this month that means the sample calls from the endpoints you configured, and on MOR the recording addon if you will use it. It does not mean a day of your live customers on the pilot, and it does not mean a traffic flood. Send the busy-hour CPS with the quote. The ten endpoints will not produce it. If the servers are yours, use the production column on the hardware page, not the test column.

Two notes that are enough:

  • M4, your server or hosted, wholesale, peak concurrent calls and peak CPS from last month, media on the switch or audio end to end, same traffic in 12 months.
  • MOR, hosted, retail SIP trunks or a dialer, peak concurrent calls and peak CPS, recording on or off, same traffic in 12 months.

Put the note that matches you on the quote request.

Day 31

At the end of the month you keep the configured base and move it onto a paid plan, or you stop. The handoff is the list of what that base proved. Continuing does not mean the rest of your traffic has moved. If you continue, you can keep the same server or move the system to a new one.

Kolmisoft builds the monthly quote from the product, the add-ons, hosted or your own server, and the capacity. Read that order in How MOR pricing is calculated. The same four factors apply to M4. Send them on the pricing form:

  • MOR or M4
  • Peak concurrent calls and peak CPS
  • Hosted, or your own server
  • The add-ons you will use, by name

This page does not state a figure. Kolmisoft calculates it from the form.

FAQ

Can the online demo place a real call?

Both demo pages state that you get the web interface and that real calls are not possible there. Real calls go through the pilot.

Do I have to move every customer in the pilot?

The cap is two providers, two rate files, one tariff, and 10 endpoints, and you choose those endpoints for the service you sell. Moving every customer is a later project.

Can the pilot be longer than a month?

Kolmisoft can extend it by agreement if the checklist needs more time.

Where do I ask about the monthly cost after the test?

Use the pricing form. Send concurrent calls, CPS, hosted or your own server, and the add-ons. If a sales thread is open, reply in that thread with the same four facts.

Schedule the pilot

Reply with the result you want on the handoff: failover on your carriers, one user rated on your tariff, or sample calls from your dialer. That note is enough to schedule the pilot. Attach the two trunks and the rate sheet on the same note, or send them on the support ticket once an engineer is on it. If no sales thread is open, start from the contact page. The pilot page is the checklist for the review.


Schedule the pilot

Reply with the result you want on the handoff. That note is enough to schedule the pilot.

Contact us

Leave a Reply

Your email address will not be published. Required fields are marked *