Cordless Phones on Hosted PBX: 2026 Setup Guide
- stfsweb
- 6 hours ago
- 13 min read
You've probably got the main pieces already. A Hosted PBX service is live, the internet works, and the cordless handsets look simple enough to plug in and use. Then practical problems start. Calls ring but audio drops one way. A handset works near reception but struggles in the back office. Everything looks fine until someone starts a large download and the phones turn choppy.
That usually points to the network edge, not the phone system itself. With cordless phones on Hosted PBX, the Asus DSL-AC68U can either keep voice traffic steady or present an obstacle. The difference comes down to setup. If you treat the router, DECT base station, and cloud PBX as one system instead of three separate purchases, call quality improves and support becomes much more straightforward.
The Foundation for Flawless Cordless Calls
Australian businesses have shifted hard toward IP-based communications. A useful benchmark comes from the United States, where the CDC reported that 75.2% of adults lived in wireless-only households by late 2023 in its wireless substitution release. That doesn't measure Australia directly, but it reflects the same practical change local businesses have already felt. The old assumption of fixed-line telephony as the centre of communications is gone.
That's why cordless phones on Hosted PBX make sense now. A hosted platform gives you PBX features without on-site PBX hardware, and a DECT handset gives staff the freedom to move around the office, clinic, showroom, or warehouse while staying on the same business phone system.
Why the router decides whether VoIP feels reliable
A Hosted PBX call relies on two kinds of traffic. SIP handles the setup. It's the signalling that tells the system who's calling whom. RTP carries the actual voice audio once the call is live.
Your router sits in the middle of that conversation. If it rewrites the traffic badly, delays it, or gives it the same priority as every other device in the office, you get the familiar symptoms: failed registration, one-way audio, dropped calls, and handsets that seem random in their behaviour.
Think of the Asus router as the front desk in your building. If the receptionist writes the wrong suite number on a parcel, it still arrives in the building but never reaches the right person. That's what bad NAT handling does to VoIP.
Practical rule: If a cordless handset works perfectly on one network and poorly on another, start with the router before blaming the handset or the PBX.
DECT handsets are radio devices, not magic phones
A lot of small businesses buy a cordless system assuming “wireless” means the network side is simple. It isn't. The handset talks by radio to the DECT base, and the DECT base talks by IP to the Hosted PBX. So you've got two layers to get right: radio coverage inside the site and clean VoIP transport through the router.
That's why generic buying guides often leave people short. They tell you the phone is “compatible” with cloud telephony, but compatibility doesn't tell you whether your building layout will support clean roaming or whether your router will mishandle SIP. If you want broader background on hosted systems in plain business terms, Blowfish Technology has an essential guide for UK SMEs that frames the operational side well.
For the access side, your internet service matters as much as the phone system. Different NBN and business internet setups behave differently under load, so it's worth checking the main internet connection types used by Australian businesses before you start tuning voice settings.
What works and what doesn't
A few patterns show up again and again in small business deployments:
Works well: A DECT base placed centrally, away from dense metal shelving and heavy Wi-Fi congestion, with the router handling VoIP traffic cleanly.
Works poorly: A base tucked into a comms cupboard beside electrical noise sources, with default router settings left untouched.
Works well: Treating cordless phones on Hosted PBX as part of a managed business phone system.
Works poorly: Buying a handset first and figuring out capacity, coverage, and call routing later.
Initial Asus DSL-AC68U Setup and Security
A clean setup beats a clever repair. If the Asus DSL-AC68U has been used before, reset it first so you're not inheriting someone else's test rules, Wi-Fi tweaks, or half-finished firewall changes.
Start with cabling and a known baseline
For a fresh install, connect the router to power, then connect a laptop by Ethernet if possible. Wired setup removes one variable while you're getting the basics right.
Use this order:
Connect the WAN side correctly: If the Asus is handling the internet connection directly, connect it to the incoming service as required by your provider. If another modem is already doing that job, connect the Asus on the routing side instead.
Connect a laptop by cable: Don't rely on Wi-Fi for the first login if you can avoid it.
Power up fully: Let the unit settle before opening the web interface.
Then browse to the Asus management page and run the initial wizard.
Lock down admin access first
The first change should be the administrator password. Don't leave the router on a default or easily guessed login. If someone gets into the router, they can change DNS, open services, alter firewall rules, and break the phone system without touching the phones.
Use a password policy that your business can maintain. Strong is good. Memorable and documented in your internal records is better than “strong” but forgotten.
A practical baseline:
Change the admin username if the interface allows it: Leaving a default username makes guessing easier.
Set a strong admin password: Use a unique password that isn't shared with email or other business tools.
Store it securely: Keep it in your approved password manager or internal documentation.
A stable VoIP deployment usually starts with boring housekeeping. Fresh firmware, known login details, and no mystery settings.
Choose the right internet mode
The Asus DSL-AC68U can be used in different ways depending on how your internet service is presented. For many small businesses, the two common scenarios are direct connection with provider credentials, or use behind another modem in a bridged or pass-through arrangement.
If your provider uses PPPoE, enter the credentials exactly as supplied. If another device already terminates the service, avoid double-handling the same connection on both devices. That tends to create confusion later when troubleshooting voice traffic.
A simple comparison helps:
Setup style | Best fit | Main risk |
|---|---|---|
Asus as primary router | Small sites wanting one box to manage routing and VoIP priorities | Mis-entered WAN settings can stop internet access entirely |
Asus behind another modem | Sites where the upstream device is provider-managed | Double NAT can complicate voice behaviour if left unchecked |
After the internet is up, name your networks clearly and separate staff Wi-Fi from guest access if your office uses both. Keeping guest traffic away from business devices reduces contention and makes phone issues easier to trace.
Later in the setup, it helps to see the interface flow in action:
Before you plug in the DECT base
Don't connect the cordless base station yet if the router still has default settings or uncertain WAN behaviour. Get the router stable first, then add the phone endpoint. That way, if registration fails, you know the issue is in VoIP handling rather than basic internet setup.
Disabling SIP ALG and Configuring Port Forwarding
If there's one change that fixes more Hosted PBX headaches than any other on an Asus router, it's disabling SIP ALG.
SIP ALG was meant to help VoIP traffic traverse NAT. In practice, it often rewrites SIP packets badly, breaks registration, or causes one-way audio. It's the networking equivalent of a staff member “tidying up” your paperwork by changing details they don't understand. The form still exists, but the important fields are now wrong.
The technical reason this matters is simple. Enterprise DECT IP systems need stable handling of data rates from 192 to 3200 kbit/s, and proper NAT behaviour matters. The IMDA cordless telephony specification is a useful technical reference on that point in its cordless system requirements document.
Where to find SIP ALG on the Asus DSL-AC68U
Open the Asus web interface and inspect the WAN, NAT, and firewall-related areas. On Asus models, the exact menu wording can vary a little by firmware version, but SIP passthrough or SIP ALG options are typically found in the WAN or NAT-related settings.
Use this process:
Log in to the router interface: Use the admin account you created earlier.
Open the WAN or NAT settings area: Look for items related to SIP passthrough, SIP helper, or ALG behaviour.
Disable SIP ALG or SIP passthrough if it interferes: Save the change.
Reboot the router if prompted: Some firmware versions apply this cleanly only after restart.
Restart the DECT base station afterward: That forces a fresh registration attempt to the Hosted PBX.
If your handset system still won't register, check the PBX provisioning details next. This overview of how Yealink phones connect seamlessly to a Hosted PBX is useful for understanding what the endpoint is trying to do at registration time.
Don't test ten changes at once. Disable SIP ALG, reboot, retest registration, then move to the next step.
NAT and port forwarding without guesswork
Most Hosted PBX systems work best when outbound traffic is allowed cleanly and the router doesn't interfere. Some environments still benefit from explicit port handling, especially if a base station or provider expects consistent paths for SIP and RTP.
The standard ports people look at first are SIP on 5060 and the RTP range used by the provider or device. The exact RTP range can vary by platform, so use the values supplied by your Hosted PBX provider or handset manufacturer rather than guessing.
A safe workflow looks like this:
Start with provider guidance: Use the SIP server details and recommended port handling supplied for your service.
Create only the rules you need: Opening unnecessary ports makes troubleshooting harder and increases exposure.
Match the rule to the device: Forward traffic only to the DECT base station if that's the endpoint registering to the PBX.
Retest both directions of audio: Successful ringing doesn't prove RTP is flowing correctly.
Symptoms that point back to this section
Use the symptom, not the guess:
Symptom | Likely cause |
|---|---|
Phone shows offline or won't register | SIP ALG interference, wrong NAT behaviour, or incorrect provisioning |
You can hear them but they can't hear you | RTP path issue, often tied to NAT or port handling |
Calls connect then behave oddly after a short period | Session handling problem, conflicting router feature, or unstable registration |
If your goal is clean voice, disable the “helpful” router features first. On Asus gear, VoIP usually behaves best when the router stops trying to outsmart the phone system.
Prioritising Voice with Quality of Service
Once calls connect reliably, the next problem is usually contention. The phones don't fail all the time. They fail when the office is busy. Someone uploads design files, a cloud backup kicks in, a staff member starts streaming training video, and the voice path gets stuck in the same queue as everything else.
That's where Quality of Service, or QoS, earns its keep. On the Asus DSL-AC68U, QoS lets you tell the router that voice traffic matters more than a large download. It doesn't create more bandwidth. It decides who gets served first when the connection is busy.
Think of QoS as an express lane
Without QoS, every packet joins the same motorway. Voice packets are small and time-sensitive. If they sit behind bulky transfers, people hear stutter, clipping, or delay.
With QoS, the router creates an express lane for voice. Web browsing can wait a moment. A phone conversation can't.
Two ways to set it on the Asus
The DSL-AC68U generally gives you an easier automatic approach and a more deliberate rule-based approach. The best one depends on how much control you want.
Adaptive QoS is the faster option. It's suitable when you want the router to identify common traffic classes and push voice higher without building detailed rules.
Manual or traditional QoS rules are better when the cordless base station is a known device on the network and you want clear control over how its traffic is treated.
A practical comparison:
QoS approach | Best when | Limitation |
|---|---|---|
Adaptive QoS | You want quicker setup and broad application awareness | The router may classify some traffic less precisely than you'd like |
Manual QoS rules | You want the DECT base or VoIP traffic handled in a predictable way | Takes more setup and cleaner documentation |
How to configure it cleanly
In the Asus interface, look for the QoS menu and enable the feature before tuning priorities. Then work in this order:
Enter realistic bandwidth values: If the router asks for upload and download rates, use realistic figures from your service under normal conditions. If you exaggerate them, QoS becomes less effective.
Prioritise voice applications or VoIP class traffic: If the interface provides a VoIP category, use it.
If needed, build manual rules for the DECT base: This is useful when one business-critical endpoint needs special treatment.
Apply and test during normal office activity: A quiet network won't tell you much.
If call quality falls apart only when staff are using the internet heavily, QoS is where I'd spend time before changing handsets.
What QoS can and can't fix
QoS is excellent at protecting voice from internal competition. It does not fix every voice issue.
It can help with:
Choppy audio during busy periods
Voice delay caused by large uploads
Inconsistent quality when guest traffic shares the same service
It won't fix:
Poor DECT radio coverage inside the building
Broken SIP registration
Bad port handling or ALG interference
Internet outages or upstream provider faults
For cordless phones on Hosted PBX, that distinction matters. If the call goes bad when someone starts a big transfer, think QoS. If the handset loses registration or audio breaks in one direction, think NAT and SIP handling instead.
Firmware and Advanced Security Recommendations
A phone system isn't only a voice service. It's part of your business perimeter. If the router is unstable or exposed, the phone system suffers with it.
That's why firmware and security settings deserve the same attention as SIP and QoS. Businesses often skip these steps because they don't look VoIP-specific. In practice, they're often the difference between a setup that operates smoothly for months and one that develops strange faults after a routine internet change or a failed auto-open service.
Keep firmware current and deliberate
Check for Asus firmware updates on a planned basis, not only after something breaks. Firmware updates can improve stability, compatibility, and security. They can also change the interface slightly, so don't update in the middle of the busiest trading window.
Use a simple process:
Check release notes before updating: Make sure the update is intended for your exact model.
Save the current configuration first: If the update behaves unexpectedly, you'll want a quick rollback path.
Update during a maintenance window: Don't cut over while reception is taking customer calls.
Retest phone functions afterward: Registration, transfer, hold, and voicemail access should all be checked.
Turn off features that create unpredictable openings
For small business VoIP, convenience features can cause more trouble than they solve. UPnP is the classic example. It allows devices to request automatic port openings. That sounds handy until a device creates a rule you didn't expect and your troubleshooting turns into guesswork.
Remote management also needs caution. If you don't need to reach the router from outside the office, leave that access disabled.
A good hardening baseline includes:
Disable UPnP: Open ports intentionally, not automatically.
Disable remote administration unless there's a real business need: Fewer exposed services means fewer ways in.
Review firewall defaults: Block unwanted inbound traffic and only allow what your phone deployment requires.
Separate guest Wi-Fi from business devices: Don't let public traffic sit beside your DECT base and PCs.
Security settings don't just protect data. They protect reliability. A router full of auto-open exceptions is harder to secure and harder to diagnose.
Keep the firewall strict, not complicated
You don't need a maze of custom rules for most Hosted PBX deployments. In fact, overly creative firewall setups often cause the very faults people blame on the phone provider.
A better approach is simple: keep inbound traffic restricted, allow only what the phone deployment needs, and avoid stacking overlapping rules. If you've already handled the VoIP-specific behaviour properly, the firewall should act like a disciplined gatekeeper, not a second PBX.
Testing Your Setup and Troubleshooting Common Issues
A phone system isn't finished because the handset shows registered. It's finished when staff can use it under normal pressure without surprises.
That means testing cordless phones on Hosted PBX the way your business works. Don't stop at one outbound call from the front desk. Walk the site. Transfer calls. Leave voicemail. Put the office internet under load. Make the setup prove itself.
A practical acceptance checklist
Run these tests in business hours if possible:
Range test while on a live call: Walk from reception to the furthest work area and listen for dropouts, clipping, or dead spots.
Inbound and outbound call check: Confirm the business number rings correctly and outbound calls hold steady.
Transfer and hold test: Move a call between handsets or extensions and check that the audio path survives the handoff.
Voicemail and email workflow: Leave a message and confirm the business process around message delivery works as expected.
Peak-use retest: Repeat the audio test while normal office traffic is active.
If poor audio appears only in certain rooms, suspect radio coverage or building materials before changing router settings. Independent deployment guidance notes typical indoor range of about 30 to 50 metres per base station, outdoor line-of-sight range up to 300 metres, and that thick walls or metallic construction may require base stations every 20 to 30 metres in practice, as outlined in this cordless coverage planning guide.
Don't confuse capacity with coverage
A lot of reception and admin teams assume that if multiple handsets are registered, they can all be on live calls at once. That isn't always true. On a typical Grandstream DECT IP system, the reference specification shows up to 10 SIP accounts, up to 10 lines per handset, but often only up to 5 concurrent calls across the DECT system, according to Grandstream's DECT cordless product specifications.
That matters in real offices. Five registered handsets doesn't guarantee five external calls plus an attended transfer plus a spare path for overlap. If calls fail during busy periods, test concurrent call load before assuming the router is the problem.
Match the symptom to the likely fault
Use the simplest diagnosis first:
Problem you see | First place to check |
|---|---|
One-way audio | NAT and SIP ALG settings |
Calls degrade only during busy internet use | QoS rules and WAN congestion |
Handset drops in one part of the building | DECT base placement and site coverage |
Phones register but busy periods cause failed calls | DECT concurrent call limits |
Random odd behaviour after months of stability | Firmware changes, new router features, or accidental config drift |
For audio problems in particular, this step-by-step Hosted PBX poor audio quality guide is a useful companion when you want to isolate whether the fault is network-side, endpoint-side, or environmental.
If the symptom appears at the same time every day, look for a usage pattern. If it appears in the same physical spot every day, look for a coverage pattern.
The best troubleshooting habit is to change one thing, test it properly, and document the result. That's how you stop chasing ghosts.
If you want help setting up cordless phones on Hosted PBX without spending your week inside a router menu, Hosted Telecommunications provides Australian-based Hosted PBX support, setup guidance, and SIP-compatible handset advice for small businesses that want reliable business calling across office, remote, and multi-site teams.
Comments