Cannot bind additional Yealink DECT handset to 3CX extension

[Blutarsky]

Hello,
I am dealing with 3CX systems for the first time, so be patient!

We have a 3CX cloud setup, a local SBC with a bunch of Yealink W78P DECT and W73H DECT-IP Handsets
I have successfully paired 3 handsets to the same DECT base, however, the third handset is not bound to the 3CX extension 306 as it should be, but it will show on the display "Handset 3".
When calling someone using this misconfigured handset, it will appear as if the call was made by the "master" DECT handset with extension 301.

Within the admin console Apparently, the fault handset is correctly paired to the extension 306...
What am I missing?

 

[Les Webb]

You can try logging in the DECT base and running an autoprovision. This has worked for me in the past with similar issues

 

[Blutarsky]

Not sure why, but the base will refuse the standard admin admin username & password...

 

[Les Webb]

When you provisioned the base in the 3cx system, it gave it a password. I usually work from the Management Console so I don't know where it is in the Webclient.

Edit: found it in the webclient