Solved Registration fails with 404

[cerien]

Hello
I am trying to register a simple softphone (linphone) to a 3CX hosted on amazon, plain basic & fresh installation.
I've created an extension, 101, I am using the FQDN, and the authentication ID and password from the Phone provisionning tab,
I've unchecked for the extension: Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked)
Network interface for registration and provisioning is the FSQN (mydomain.my3cx.us)
Network Settings / FQDN / Allow calls from/to external SIP URIs is checked

Yet, when linphone sends a registration, it ends with a 404 - the user looks correct (its the extension authentication id) from the sip trace

What am I missing !!!

Thanks for the help

J.

 

[JohnS_3CX]

Hi @cerien

We would recommend that you use the 3CX Softphone instead, just send yourself a welcome email and you will receive links for the Windows app,Android app or iOS app. Or you can use the Webclient or Chrome extension if you wish to access it over your desktop browser.

Otherwise, the sip user ID is is the extension number, the authID and password are the ones in the extension's Phone Provisioning tab. 404 means the user was not found, if you know the SIP protocol well should be easy to troubleshoot. If not then we strongly recommend using our apps or webclient which are very user friendly and more secure than a 3rd party app, due to the 3CX tunnel protocol that encrypts your traffic to and from the PBX.

 

[cerien]

I do have extensive knowledge of SIP. I've successfully configured a 3CX app - but I'd like to use another softphone as the agents are already using it. I've tried using the extension and the authID for the registration, still getting a 404. I am guessing some option must be incorrect somewhere, and prevents the phone from registering, even though the credentials are correct

 

[Alphabetic]

I've found when using 3rd party phones the "name" field must be the ext # if that helps you.

 

[JohnS_3CX]

In this case we will not be able to provide further assistance since the 3CX app was confirmed working.
Perhaps reconsider by comparing the features our app gives, VS a generic app that was not tailor made for 3CX.

Given your extensive knowledge, this should however be of assistance in figuring out what was missing if you still wish to use a 3rd party app:

- The PBX has the Activity Log page, which has settings on the top right allowing you to enable Verbose logs

- It also has a Capture feature so you can catch the registration and analyze the pcap

- You can register a local Windows app based extension and compare that registration, vs the one on your 3rd party app (use the same extension for both to simplify)

- From there you can see the differences and adjust your own SIP client to your needs

 

[cerien]

I've found when using 3rd party phones the "name" field must be the ext # if that helps you.

Kudos to you !!!! You saved my day !
The FROM field must be set to the extension number, while the authentication username is set to the authID.

So a register will look like this:

REGISTER sip:mydomain.my3cx.us SIP/2.0
....
From: <sip:[email protected]>;tag.....
....
Proxy-Authorization:.... username="AuthID"
....

Many Thanks