Setting BLF's

Status
Not open for further replies.

JoeB

Forum User
Basic Certified
Joined
Jul 15, 2020
Messages
35
Reaction score
1
It appears that configuring BLF's by browsing to the phone's IP (.(we use Yealink phones, various models) takes precedence over using the management console.
Is this correct? When I make changes using the BLF tab of an extension, I don't see the changes, so I've started using the browser interface. It's then out of sync
with what's displayed in the management console. The web client does show the BLF's as set on the extension.
Thanks for any assistance.
 
These settings will take effect once the phone has been reprovisioned which happens once a day automatically.

when you make a change you must reprovision the phone to push the new template.
 
I've made changes and not seen them the next day, nor after forcing a reprovision from the management console. The settings I make from a browser are the ones I see.Though it's a very simple process, I want to make sure I'm doing it right.
I'll open a ticket with our hosting service.
 
Can you provide this info:


  • 3CX Version, e.g. Standard Annual 16.0.2.910
  • Server OS, e.g. Debian 9 / Windows Server 2012 R2 / Raspberry Pi
  • Is the 3CX Server Hosted and where?
  • IP Phone Make/Model/Firmware
  • Provisioning Method: Local / VPN / STUN / SBC
  • Trunk Provider or Gateway Make/Model
  • Has the Firewall Checker passed: YES / NO
  • Are custom Phone Templates being used: YES / NO

Sounds like your phones are not on the same subnet as your PBX. In which case it's likely a firewall issue causing you problems or you're not running the latest phone FW.
 
I'll have to drill down through all the settings. I see that this is only phones that I've set up. On a previously installed phone, my changes took immediately.
All the phones except one have current firmware.

Thanks.

3CX Version - Enterprise Annual / 16.0.619
Server OS - Hosted. Assuming Linux OS, as file locations are in Linux format
Is the 3CX Server Hosted and where? - Yes.
IP Phone Make/Model/Firmware - Yealink T46S - 66.85.0.5
Provisioning Method: Local / VPN / STUN / SBC - STUN
Trunk Provider or Gateway Make/Model - CloudCo
Has the Firewall Checker passed: YES / NO -
Do not know. System in service several years, I assume yes.
Are custom Phone Templates being used: YES / NO - No
 
Perform a firewall test from the mgmt console when you can.

Check firewall on the phone end.

1595431063185.png
 
I've been able to modify two phones.The passwords didn't meet the criteria.
One was existing, the other is one of my lab phones. I have three more with changes pending. Sometimes there is a long delay from when I give a provision command to when I see anything.

1595434431389.png

This was 11:57. The two other phones provisioned quickly.
 
Hi Joe,

Whenever you make any changes to the extension (ie names, BLF, provisioning tab options) you need to go to the Phones tab afterwards, select the phone and click reprovision so they phone will be updated.

Is this not working for you? Try factory resetting and reprovisioning the phone as per our guide first
https://www.3cx.com/sip-phones/

If this works, then the reprovision button should also work (although it may take a few seconds before the phone shows the changes on screen)

As for passwords, use the regenerate button in the Extensions tab and this will generate provisioning-server compliant passwords that have already been tested to work before we released the PBX. The phone UI itself may show other password requirements but I can assure you the ones the PBX generates are compliant when using our firmware and out provisioning methods.
 
I've run through the exercise several times. Changing the BLF on one particular phone works consistently now. I may have to run through a stare-and-compare to find out why. It's not critical to our operations, but if I have to do this for someone else, I need to understand why it works when it does and not other times.
Thanks.
 
What I often notice is that not all phone models will be very speedy, some will show the update in 1 second (as soon as you hit reprovision) others may take up to a minute.

This is of course provided that there are no connection/firewall problems etc that would entirely halt the communication between phone and PBX.

Just make sure the phone is factory reset the first time and provisioned automatically, then from this point forward you can do as I described. Note that Yealink phones will also reprovision automatically after this whenever you restart them.

Let us know if you have any more questions and we will be glad to help!
 
I might be guilty of the sin users have been committing for a lifetime - not accurately describing the problem. The changes do reflect on the web client, not the IP phones.
What I'm realizing is that it's not just BLF fields not updating, the phones don't reprovision at all when I make the request, regardless of whether I click on the Phones tab, or use the phone's GUI.
I'll have to approach this from that angle.

1595596787416.png
 
I am still a bit confused on how you are adding the BLF's to the phones. In your first post you mentioned that you are doing this by browsing to the IP of the phone. Is that correct or did i miss something?

Can you explain the process you are following so we can better assist?
 
My issue has more to do with phones not reprovisioning when I select that from the console, or from the phone's GUI. I have been programming the BLF's by browsing to the phone, since the changes don't take, otherwise.I have a ticket open with our hosting service.
If there's a "close thread" option, this can be closed.
Thanks for all the replies.
 
Locking this thread but you can always create a new one if you run into any more issues.
 
Status
Not open for further replies.

Forum statistics

Threads
111,954
Messages
589,924
Members
164,852
Latest member
priya