SIP Settings for Desk Phones, Adapters and PBX Systems
Any SIP-compatible desk phone, analogue adapter or PBX can connect to Click2Call. Use the settings below for any device we don't have a step-by-step guide for. The device must support SIP version 2.
Last reviewed: October 2026
What settings do I enter?
| Setting | What to enter |
|---|---|
| Username / User ID / Login | Your number exactly as shown in Voice → Line Manager, e.g. 61370500989 (no +, no leading 0). For an extension, use its Login from the User Extensions table. |
| Authentication name | Same as the username |
| Password | The line password from the Password box on that number's row in Voice → Line Manager — not your portal login. New numbers have no password until you set one and click Save Changes. |
| SIP server / Proxy / Domain / Registrar | sip.click2call.com.au |
| Outbound proxy | sip.click2call.com.au (or leave blank if your device doesn't need one) |
| Transport | TLS (recommended), TCP or UDP |
| Port | 5060 for UDP or TCP · 50600 as an alternative to 5060 · 5061 for TLS |
| DTMF (keypad tones) | RFC 2833 (sometimes called AVT or out-of-band). SIP INFO also works. |
| Voice codecs | G.722 (best quality), G.711 A-law, G.711 µ-law, G.729 |
| Packet time (ptime) | 20 ms. 10 ms is not supported. |
| STUN server | Not required |
Why TLS is recommended
TLS encrypts the call setup between your device and Click2Call. Routers can't read or rewrite encrypted traffic, so TLS avoids the most common cause of one-way audio and failed registrations (a router feature called SIP ALG — see Fixing One-Way Audio and Dropped Registrations). If your device can't use TLS, try port 50600 instead of 5060: routers don't recognise it as a SIP port, which has a similar effect.
Where the port goes
Most devices take the port on the end of the server address, e.g. sip.click2call.com.au:50600. Some have a separate Port field. Enter Click2Call's port there, not your device's own local SIP port.
Do I need firewall rules?
Usually not. Click2Call handles devices behind NAT and most firewalls, and you should never need to forward ports 5060 or 5061 to your phone or PBX. If your firewall blocks outbound traffic by default, allow your devices to reach sip.click2call.com.au (103.55.116.140) on the ports above. Call audio uses UDP to the same address.
Can I encrypt the audio too? (Secure RTP)
TLS encrypts the call setup; Secure RTP (SRTP) encrypts the voice itself. To require it on a line: Voice → Line Manager → click the number → Other Settings → Voice Quality & Codecs → turn on Secure Encrypted RTP → Save. Only do this if your device is set up for SRTP — calls will fail otherwise. The same page lets you force a particular transport or restrict codecs. Leave codecs alone unless you have a reason; the defaults suit nearly everyone.
Registration, peering or IAX2 — which connection type?
Each line's connection type is set in Voice → Profiles.
- SIP Registration (the default): your phone or PBX logs in with the username and password above. Right for almost everyone.
- SIP Peering (Direct IP): your PBX and Click2Call trust each other by IP address instead of a login. Needs a static public IP. Useful for PBXs that route many numbers.
- IAX2: for Asterisk-based systems (FreePBX and similar). Uses one port for signalling and audio, which can make firewalls simpler and uses less bandwidth per call.
Not sure which you need? Use SIP Registration.
Still not registering?
See Setting Up a Softphone and Fixing Registration Problems for the checklist, and Fixing One-Way Audio and Dropped Registrations if calls connect but audio fails.
Related Guides
Still need help?
Our Australian support team is available to assist you.