Unable to register Yealink T21P-E2

[RichardW]

I am trying to register a Yealink T21P-E2 on our 3CX instance which is cloud hosted. I have tried to autoprovision and all the settings showing on the phone's web interface appear to be correct - however it keeps failing to register. I can see the extension number on the phone itself and there is a button labelled '3CX Phonebook' however when pushing this button it tells you that the phone is unable to download the phonebook. Clearly this is 99% of the way there but SOMETHING is stopping the registration succeeding. The firmware on the phone is 52.84.0.35.

52.84.0.35

 

[leejor]

Have you checked the 3CX Activity Log for any clues as to why it can't register, is there even a log showing an attempt? Has the extension option been set to allow WAN registrations?
Are other sets registering just fine? If this is the first, have you run the firewall checker successfully?

 

[Saqqara]

How are you trying to provision the phone - sbc or stun.

Have you check the blacklist and removed any entries.

 

[RichardW]

Trying to register using stun. There is nothing for a few hours in the event log so no clues there. I am trying to register this handset at home so nothin to compare with. When trying to follow 3CX's provisioning instructions - the phone doesn't do what it says its going to do so had to abandon that (it says the phone will ask for a user name and password when booted - but it doesn't).

 

[Saqqara]

Have you factory defaulted the phones, after setting up the phone within 3cx . After entering the details into 3cx, in the activity log you should see info that the phone has been setup for stun (rps)

Are you port forwarding 5001 on the firewall protecting the 3cx server

Does the 3cx server have full internet access ?

 

[leejor]

all the settings showing on the phone's web interface appear to be correct - however it keeps failing to register.

This being the case, I have to assume that the set is either attempting to register to the incorrect location, or, is being blocked by either a firewall setting (incorrect port forwarding?), or 3CX setting.

 

[RichardW]

All resolved - was a small issue on local router.