Views: 0 Author: Alice Publish Time: 2026-05-19 Origin: Site
You have a sample on your desk. It connects to Wi-Fi and registers with your SIP platform. What should you try next?
Start with the things a family will actually do: call a parent, receive a return call, change a contact and reconnect after the router restarts.
This guide covers the main checks for KAER KS21 and KS22 before a pilot. KAER also provides demo software for sample testing, so you can begin evaluating the supported functions before finishing your own parent app.
Test real incoming and outgoing calls, not just SIP registration.
Use the same core checks for both models, with separate usability checks for their controls.
Verify contact permissions and independent operation after setup.
Check that calling recovers after a device or network restart.
The KAER KS21 and KAER KS22 connect to a compatible SIP service over Wi-Fi. Parents or administrators manage supported settings, while children use physical controls for everyday calls.
Their main difference is how the child selects a contact and places a call.
| Model | Interface | Usability Check |
| KS21 | Physical keypad with LED contact labels of up to three letters | Can the user recognize labels such as “MOM” and “DAD” and reach the right contact? |
| KS22 | Physical push-button keypad without a display | Can the user enter the intended number correctly and try again after a mistake? |
If you are comparing both samples, use the same SIP platform and test contacts where practical.
Prepare the samples, supplied power adapters, Wi-Fi network, configuration phone and SIP test accounts. Have the receiving devices or mobile numbers ready, too.
Confirm the demo software version and supported settings with KAER. Share your SIP platform requirements and a short list of expected calling rules: who the child can call, who can call back and which calls should be blocked.
Follow the supplied instructions to identify the device, connect through the configuration phone, and enter the Wi-Fi and supported SIP settings.
Check that you can:
Select the correct sample.
Connect it to the intended Wi-Fi network.
Register the correct SIP account.
Understand whether setup succeeded or needs attention.
Try the sample on the kind of Wi-Fi network your customers will use. Test each Wi-Fi band supported by the supplied model and firmware.
Test every calling route your service needs. This may include another kids phone, a parent's ordinary mobile or a family member overseas.
For each route, check that the correct device rings, both people can hear each other clearly, and either person can end the call. Place another call afterward to confirm that normal operation continues.
Test the parent's return call separately. The child being able to call a mobile does not confirm that ordinary mobile callback is ready.
That return path needs an incoming telephone number, routing to the kids phone and permission for the caller. Once configured, call from the parent's mobile and check ringing, answering and audio.
For more about the different calling routes, see Kids Wi-Fi SIP Phones: Device-to-Device, Mobile and International Calling.
Add a few contacts and configure their intended permissions. Then test incoming and outgoing calls separately.
| Test | What to Confirm |
| Call a permitted contact | The outgoing call is allowed |
| Receive a permitted caller's call | The incoming call is allowed |
| Test calls to and from an unapproved contact | The results match the configured incoming and outgoing restrictions |
| Change or remove a contact | The updated rules take effect |
After changing a contact, repeat the affected call. This confirms that the device follows the new settings, rather than simply showing the change in the app.
Disconnect Bluetooth and move the configuration phone away. Make and receive a call to confirm that the kids phone continues working independently over Wi-Fi and SIP.
Ask a first-time user to choose or dial a contact, answer a call, adjust the volume and hang up. For KS21, pay attention to contact-label recognition. For KS22, check whether the user can enter numbers on the physical push-button keypad and try again after a dialing mistake.
Use the instructions you expect to provide with the product. Any hesitation can help identify where clearer guidance or different prompts would help.
Restart the device and router separately, then try a temporary internet interruption.
After each test, check that the phone reconnects, registers with the SIP service and retains its essential settings. Complete an incoming and outgoing call to confirm recovery.
Note how long this takes and whether anyone needs to intervene manually. These details help you prepare customer instructions and support procedures.
Keep a short record of the sample model, firmware, demo software, SIP platform and test results. If a problem appears, note the steps needed to repeat it.
Once the main checks pass, try a small pilot in the homes or other settings where the phones will be used. This gives you a chance to assess setup instructions, everyday operation and support needs before a larger rollout.
Yes. KAER provides demo software for sample testing. Our technical team can explain the supported functions and help plan checks with your SIP system. Requirements for your own app can be discussed separately.
Most checks apply to both. Add separate usability checks for KS21's keypad and LED contact labels, and for number entry using KS22's physical push-button keypad.
Yes, when the required incoming number, routing and calling permissions are configured. Include a separate mobile-to-device call in your sample tests.
Ready to test with your SIP service?
Contact KAER to request KS21 or KS22 samples and demo software. Share your target market, preferred model, calling requirements and estimated quantity. Our team can help plan the evaluation and discuss the customization or integration your project needs.
