Solved SOLVED - CISCO SPA112 ID since V15-SP6

[AWS2P]

Hi ,
i'm using a CISCO SPA112 gateway on 3CX V15, since 3CX updated to SP6 ID , Password etc ..... have been changed to alphanumeric 10 caracters instead of numeric extension number.

I know this device is unsupported by 3CX but do you have already tested with 10 alphanumeric ID, for me it's impossible to register to 3CX after that setting change.

if i remove alphanumeric and reset to previous in 3CX console and SPA112 side it register directly.

If there is a hack, i'll be pleased to know.

 

[craisondigital]

I was having issues too. I ended up deleting the extension completely and recreating it and it has been registered ever sense.

 

[AWS2P]

Ok thanks, i will try this

 

[AWS2P]

Hi, i' ve tried today creating two new extensions and set it in SPA112 with no more success, just if i remove alphanumeric ID and set it with 3CX extension number it register .

can you show me informations about SPA 112 FW and also portion of settings concerning authentication for line1 and 2 on yours?

 

[leejor]

if i remove alphanumeric ID and set it with 3CX extension number it register .

Are you saying that the User ID (which is normally a phone number, or the extension number), had been changed to some seemingly random alphanumeric string? Or...do you mean that the password had changed?

 

[craisondigital]

The userID needs to be set to the extension, then you need to change the drop-down to use authorization ID to yes. Then you put the AuthID (random alpha-numeric) in the box below. I'm using the latest firmware.

 

[AWS2P]

Are you saying that the User ID (which is normally a phone number, or the extension number), had been changed to some seemingly random alphanumeric string? Or...do you mean that the password had changed?

With V15 SP6 all credentials have to be set according new 3CX policy, so if you regenerate credentials user ID become a 10 alphanumeric caracters. It's not necessary to force the settings change but in that csae you have a red warning triangle in front of each line meaning your are not good with new policy.

 

[AWS2P]

The userID needs to be set to the extension, then you need to change the drop-down to use authorization ID to yes. Then you put the AuthID (random alpha-numeric) in the box below. I'm using the latest firmware.

i will try that, for my try i've set in user ID and auth ID the new alphanumeric

 

[AWS2P]

The userID needs to be set to the extension, then you need to change the drop-down to use authorization ID to yes. Then you put the AuthID (random alpha-numeric) in the box below. I'm using the latest firmware.

you are right on target, i've made settings change like you explain me to do and now SPA112 is registered again with new credential format.
Nice job

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.