3CX softphone for iPhone: what works with Callmar

Start with the official 3CX iPhone path

The documented mobile setup for a 3CX V20 user is the official 3CX app. Install it, open the 3CX web client or desktop app, select the QR code and scan it from the iPhone. This 3CX QR provisioning profile configures the extension and the vendor’s remote connection automatically.

The official 3CX iPhone manual also covers calls, transfer, conferences, Siri, widgets, status and 3CX messaging. If those features or vendor support are the goal, there is no reason to translate the QR profile into a third-party account.

Why 3CX is different from a normal SIP account

3CX is built around its own provisioning and remote-phone architecture. The QR code is not a generic SIP URI: it can carry the information the official app needs to find the system and use 3CX services. Remote desk phones generally sit behind a 3CX SBC or router phone instead of registering as arbitrary Internet clients. Those paths carry more policy than a server, username and password.

Callmar is an independent SIP client. It does not consume the 3CX provisioning file, use the 3CX Tunnel or become a phone behind a 3CX SBC. This is why a QR code that works in the 3CX app is not enough to configure Callmar, and why a remote manual phone example is not automatically a supported iPhone configuration.

Compare the official app and Callmar

The decision is therefore architectural, not a preference for one dial pad. Callmar is worth testing only when its local notes or CRM workflow matters and the administrator can provide a plain SIP path without removing the organisation’s required 3CX features.

The username limitation to check

Current 3CX documentation shows an Extension Number and an Authentication ID as separate values. Some deployments set them to the same value; others do not. Callmar currently has one SIP username field, so a setup that requires two different values cannot be represented correctly.

The official manual IP-phone guide displays Extension Number, Authentication ID, Password and the 3CX FQDN/port. For a remote phone it also points to an SBC or router phone. Those details describe a supported phone topology; they do not promise that an unrelated iOS SIP app can use the same route.

Ask the administrator one direct question: Can this extension register with the same value as both its SIP address user and authentication username? If the answer is no, stop there and use the official 3CX app.

Compatibility checklist for the administrator

All of the following need a clear yes before a useful test:

• The extension may be used by a manually configured, independent SIP client.
• One username value works for both the SIP identity and authentication.
• The administrator provides the server, port, transport, password and any required encryption settings.
• The extension is reachable from the iPhone’s network without relying on the 3CX Tunnel or a phone behind the 3CX SBC.
• The deployment allows this additional registration and has an incoming and outgoing route for it.
• The TLS certificate is valid for the supplied FQDN, and the same TLS/SRTP combination is configured on both sides.
• The administrator accepts that a 3CX update or policy change may affect this nonstandard path and will retest it.

A separate test user is preferable to reusing the daily 3CX mobile user. It prevents a manual REGISTER from replacing a live contact or changing where business calls ring.

Define success and rollback before testing

Write down the 3CX version, test user, approved FQDN and port, network being tested and every device already attached to that user. This turns a one-off registration into a reproducible test and makes it clear whether a later 3CX update changed the result.

A successful trial must cover more than a green status: one internal call, one permitted external call, two-way audio, one incoming call while Callmar is open, one while the iPhone is locked, and a repeat after moving between Wi-Fi and cellular. The existing official app or desk phone must continue to receive calls if the design says both should remain active.

Agree on rollback as well. Remove the Callmar test account, delete or disable the separate test user and restore the official QR provisioning if another device is displaced. Do not keep a partly working manual registration on a production user while investigating it.

Configure Callmar only when the test is approved

1. Create a separate 3CX test user or extension so an existing desk phone and official app are not disrupted.
2. In Callmar, add an account and choose 3CX PBX or Custom / Other. The preset is only a starting point; it does not import a 3CX profile.
3. Enter the exact FQDN, port, compatible Username and Password provided by the administrator. Replace the preset’s TLS, SRTP or port defaults if the approved endpoint uses another combination.
4. Save and confirm a fresh registration. A saved form is not evidence that 3CX accepted it.
5. Place one internal and one permitted external call, then confirm caller ID and two-way audio.
6. Call the test user while Callmar is open. Only after that passes should you close the app, lock the iPhone and test the approved background path.

A successful registration in one test network does not prove that the account will work while roaming between Wi-Fi and mobile data. Treat that as a separate test.

Understand remote and lock-screen limits

A local manual test may reach the 3CX FQDN directly while the iPhone is on the office LAN. That does not create a remote path. If external phones must use an SBC, router phone or the 3CX Tunnel, Callmar cannot substitute its relay for that architecture.

Callmar’s push relay can keep a compatible standard SIP registration reachable and wake the app through CallKit, but the relay itself must be allowed to reach the approved 3CX endpoint. The administrator must test registration and incoming routing from that path; a green local test is insufficient.

Verify separately on office Wi-Fi, an outside Wi-Fi network and cellular data. Then repeat an incoming call with the iPhone locked. If only the official app works remotely, that is evidence that the deployment depends on the vendor path, not that the Callmar password field is wrong.

Fix common 3CX and Callmar test failures

The QR code will not import

This is expected. A 3CX QR profile is for the official app, not a standard SIP account import. Request manual values only if the administrator supports that design.

Registration fails with 401 or 403

Compare the Extension Number with the Authentication ID. If 3CX requires different values, Callmar’s one-username model does not fit. Also check password, source policy and whether this user may register another contact.

TLS fails before registration

Use the 3CX FQDN covered by the certificate and the exact TLS port. An IP address or privately signed certificate can reach the server but still fail identity validation.

It works on the office LAN but not remotely

The test may depend on local DNS or direct LAN access. Ask whether remote phones are required to use a 3CX SBC, router phone or Tunnel. Callmar does not implement those vendor paths.

Outgoing works but incoming does not

Check the user’s active contact and inbound destination. Then test while Callmar is open. If the open test passes but the locked test fails, investigate the separately approved relay and push path.

The call connects without two-way audio

Compare SRTP and codec policy, then inspect the SDP and RTP addresses selected by 3CX. Registration success cannot prove the media route through NAT.

The official app or desk phone stops ringing

The manual registration may have replaced another contact or changed routing. Remove the test account and restore the supported 3CX provisioning before changing production user settings.

A 3CX update breaks the manual setup

Retest against the current 3CX documentation. Because this is not the normal mobile path, do not assume an old workaround is a stable contract across upgrades.

When the official 3CX app is the right answer

Use the official 3CX app when the organisation provisions users by QR code, requires the 3CX Tunnel, depends on 3CX chat or presence, or expects support from 3CX for the complete mobile experience. That is the normal and documented path.

The official app is also the safer choice when the administrator cannot expose a compatible manual SIP path or when the Authentication ID differs from the extension identity. A shorter setup that follows the vendor architecture is better than a longer unsupported setup that happens to register today.

What Callmar can add after a verified setup

Once registration, outgoing and incoming calls work reliably, Callmar can present those SIP calls through CallKit and optionally create on-device transcripts for calls handled inside the app. Recording and transcription are off by default.

Callmar 1.4 can send call details and transcript text to a configured CRM. The audio recording is not sent. See the private call-notes guide and CRM setup guides. These features do not change the underlying 3CX compatibility requirement: the SIP connection has to work first.

“3CX” is a trademark of its owner. Callmar is an independent product and is not affiliated with or endorsed by 3CX.