Yealink Provisioning Template

[tony28]

I was browsing and found this old post. Should I be concerned about this? Am using latest version of 3CX v16.
https://www.3cx.com/community/threads/yealink-provisioning-template.49792/

 

[SweetAction]

The template sets the password for those 2 users to the same password as the admin account. If you have weak admin passwords, then it will be weak there as well. if using 3cx generated passwords, likely not an issue.

Why is your phone open to the world? Your firewall should stop these attacks before they hit the phone.

 

[tony28]

I am guessing SIP phones were configured using STUN otherwise you cannot access the phone, correct?
Should SIP ports 5060 be locked only to trunk provider?
3CX softphone, are using https port, right so I can only lock down port 5060.

 

[JohnS_3CX]

I am guessing SIP phones were configured using STUN otherwise you cannot access the phone, correct? This depends on your network security and how good it is at keeping outsiders out.

Should SIP ports 5060 be locked only to trunk provider? Please read here, look at 5060 https://www.3cx.com/docs/ports/

3CX softphone, are using https port, right so I can only lock down port 5060. As above, depends if you use webclient and STUN phones

 

[tony28]

I am using 3CX client for Android and they are roaming around. How can it be secured when they will have dynamic IPs?

 

[Evolute IT]

I am using 3CX client for Android and they are roaming around. How can it be secured when they will have dynamic IPs?

The 3CX client uses the 3CX Tunnel. No need to "secure" the port.