SIP/2.0 606 Not Acceptable [...] but it is not configured for the user Avaya Equinox Mobile 2

[bdeltp]

I stuck on a problem for some time.
The account is fully functional on Windows, but when I put it on my Android smartphone (certificate installed), I get the following SIP error:
SIP/2.0 606 Not Acceptable

SIPDialog f7361558 created, dialogs 1 txn_keys 1 video 1 presentation 1 camera 1 unsupp audio 0
[...]
Sip: (f7361558) SendSIPResponse: REGISTER code 401 SENT TO 200.200.200.200 39999 ([COLOR=#EF2929]Public IP Android[/color])

Here I got some HTTP/1.1 401 Unauthorized exchanges between system and my phone, then the REGISTER request and after that :

Sip: SIP REG: 123 +sip.instance="<urn:uuid:///>"
Sip: SIP REG: 123 reg-id=1
Sip: ProcessNewRegistrationRequest name <> extn <123> cfg_extn 0 cfg_user f6f11c50
Sip: ... is_flare 0 (centr 0) is_oneXmobile 0 is_XMSI 0 is_WebRTC 0 equinox_softphone 0 equinox_mobile 1 csdk_softphone 0 csdk_mobile 0  IsSimultaneousClient 0
Sip: cfg_extn 0 vpnn_resilience f658f4a0
Sip: 123 temp_cfg_user->IsHomePbxActive() 0
Sip: SIP FindUserFromAuthentication, <123> cfg_user f6f11c50 from_unregister 0 is_ipo_behind_nat 0 is_phone_behind_nat 1
Sip: authenicateChallengeRtn 1 cfg_user f6f11c50
Sip: SIP REG: user 123 authenticated
Sip: SIP REG: phone is 123@100.100.100.100 ([COLOR=#EF2929]Public IP IPO Server Edition[/color]) client, but it is not configured for the user Avaya Equinox Mobile
Sip: (f7361558) SendSIPResponse: REGISTER code 606 SENT TO 200.200.200.200 39999
SIP Reg/Opt Tx: phone
                 SIP/2.0 606 Not Acceptable

I found articles about this famous error 606, but nothing about the error above.

Yet the remote worker user licenses are well defined ...

 

[critchey]

Sip: SIP REG: phone is 123@100.100.100.100 (Public IP IPO Server Edition) client, but it is not configured for the user Avaya Equinox Mobile

Do you have the checkbox Enable Mobile VOIP client checked on the user?

The truth is just an excuse for lack of imagination.

 

[bdeltp]

Thank you for your answer critchey !

I saw the error, doubting it was a license issue without really understanding it.
I changed the title of the topic for others to find this error.

So to correct this error,
- Choose a "Power User" user profile
- Enable "Mobile VoIP Client"
- Enable "Remote Worker

 

[critchey]

You are welcome and thanks for the pink. I did the exact same thing honestly. I configured the Windows client first and it worked. I configured the Android client and it didn't login and I couldn't figure out why till I saw it in monitor.

The truth is just an excuse for lack of imagination.