Microsoft Teams Integration
Hikvision Intercom Integration
ISDN Switch-off Migration
All materials to evaluate Yeastar as a PBX vendor on products, solutions, partner program, support, learning resources, etc.
I have an S20 scheduled for auto reboot. I noticed that the extensions BLF buttons are not working property. The only solution is to also reboot all Realink T29G phones.
Anyway to also send a reboot command to all extensions after the S20 reboots?
Date
Votes
12 comments
-
Larry Neblett No, there is no command that will cause a batch reboot to the phones. They would have to be done individually or , if connected to a PoE switch, you might be able to toggle the switch power which would cause all PoE devices to reboot.
You can also find info on the methods to do a remote reboot in the following link -
http://forum.yealink.com/forum/archive/index.php?thread-40801.html
The question that arises, if why is there a need to reboot the S20, and what is the cause of the BLF issues?
The issue is that the phones register to the server and in doing so are assigned an expiry time. This is the time period by which when the expiry occurs, the phone should re-new its registration period. In the meantime, the phone is idle and may never know about the PBX going off-line while rebooting, so whatever status they had when the system went off is the same status they will have when the PBX comes back on-line.
The BLF function is a subscribe/notify mechanism.
The phone will send a SUBSCRIBE message to the PBX informing the PBX of the extension it wants to monitor and for how long (another expiry) for the BLF function. If successful, the PBX will then send a 200OK and then send a NOTIFY about any state occurring on a monitored phone back to the subscribing phone(s) as they occur. Both the SUBSCRIBE and NOTIFY will elicit an 200OK upon either side seeing the aforementioned to confirm that whatever the message, that it was seen and acted upon.
The absence of a 200OK to a NOTIFY, DOES NOT cause the PBX to resend the NOTIFY. Instead, the RFC indicates that the subscription should be removed. This is somewhat under the assumption that the subscribing phone is no longer reachable due to the lack of a request and that if the phone did not respond to the NOTIFY, then it likely will not on subsequent messaging and the re-sending of same is nothing but extraneous traffic. The phone needs to resubscribe, which is what I assume you hope to achieve by rebooting the phone.
Additionally, there is a bug reported in the Asterisk forums that Yealink made some changes in their v82/83 firmware that impacts how it works and I assume it possible that this could be involved in your case and which may be exacerbated by the reboot of the PBX. You may need to setup a syslog and do captures to find the real reason.
In any event, you might reconsider the scheduled reboot need to see if this averts the issues as reported in the Asterisk forum. As an aside, I have a number of PBX systems in my office of various makes and models besides Yeastar and I reboot none of them unless it is required after doing some type of upgrade.
-
Abelaguilar Larry:
Thank you for the explanation. I thought I read somewhere that a scheduled reboot was a good way to clear up anything that may bog the system down, however, I will stop this.
Thanks again for taking the time to explain further.
-
Riddhe M I have seen several issue of the BLF error in the forum. Maybe a bug that Yeastar is trying to fix.
-
Larry Neblett Riddhe, it would be good to have some context to the statement. Not that I do not believe that there aren't or have not been some issues, but rather that it takes three things to tango - PBX, network and phone. All of which may have variables that can be the source of the issue.
I won't say that there may not be a need to do a reboot at some point, and perhaps my upgrading and tinkering has provided the needed reboots to prevent any issues from arising, but if there is a need to do, I suggest that the reboot frequency be extended out as much as possible. It would be nice if YS could have a schedule that would handle the reboot schedule similar to the time condition settings so that you could exert more control over when a reboot would occur. As it is now, when setting for a monthly reboot, you can only select the date which means that the reboot may occur on any day of the week as long as the date matches.
-
Abelaguilar I wanted to post an update on my progress. Turns out the BLF buttons do send the correct feature code, however, the status light on my yealink T29G does not update. I should say they update sometimes and at other times pressing the button does not change its light status, but the feature code is initiated correctly. I can tell because when I log in and look at the inbound route the time condition is correctly checked.
Not sure what I can do to fix this.
-
Larry Neblett A feature code has nothing to do with the "then current" BLF status indication. The feature code is nothing more than a code that is sent to the PBX telling the PBX to either pickup/intercept a call on a monitored extension if ringing or to dial the monitored extension if not ringing.
A button when pushed, may cause a status indication to change as a result of the feature code action and the resulting NOTIFY that is sent from the PBX, but as indicated, the NOTIFY is sent from the PBX.
So, while the action of sending a code should change a status on a monitored extension, it is the NOTIFY message received by the phone from the PBX that actually tells the phone what the condition is related to the BLF indication. So, the question is whether or not you saw a NOTIFY and what the contents were of same (the entire header) as it may be related to the earlier post where I indicated:
Additionally, there is a bug reported in the Asterisk forums that Yealink made some changes in their v82/83 firmware that impacts how it works and I assume it possible that this could be involved in your case and which may be exacerbated by the reboot of the PBX. You may need to setup a syslog and do captures to find the real reason. Please read the below link. Yeastar's underlying core telephony aspect is Asterisk.
A Wireshark capture may show the issue. While a syslog might help, I think the capture should be the starting point.
-
Abelaguilar ok maybe i'm just expecting the BLF to perform a function its not designed for or not ready for based on current bug reports.
The initial intent was to have staff members press the Open BLF when they come in the morning, then Lunch BLF for Lunch voice mail and Closed BLF for closed voice mail.
I may work on a wireshark capture. given time constraints may be easier to just eliminate this for now and revisit in the future.
-
Larry Neblett Perhaps I am not getting the full picture. You initially indicated that you were rebooting the PBX in the hopes that doing so would cause the extensions' BLF button displays to synchronize. You then asked about rebooting the phones for the same purpose as you had indicated that rebooting the phone solved the problem - "The only solution is to also reboot all Realink T29G phones."
Can you explain in some detail what you are actually trying to do?
A BLF in the typical sense is a function where a button is assigned to monitor a given extension. If the monitored extension is connected to the system and available to take a call, the indicator assigned to that extension will show "green". If the extension is currently ringing, the indicator will show "blinking red". If the extension is engaged in a call, the button will display "solid red".
When green, pushing the button will cause the phone to dial the monitored extension and presumably the extension will ring.
When blinking red, pushing the button will cause this phone to intercept the call that is ringing at the monitored extension.
When solid red, pushing the button will dial the extension, same as it does when the button is green, but the call will be handled according to how the phone's rules are established - voice mail, call waiting, forward, etc., as the phone is already engaged.
Now then, different manufacturers refer to these type of buttons with different nomenclature - DSS keys, VMPK keys, BLF keys/buttons, etc., but all essentially mean the same. These buttons, by whatever their name, can be set to perform different functions.
What you seem to be attempting to do is to use the buttons to set in- and out-office-status via the time override function, which does not cause a change in indication. The function is merely a dial code that is sent when the button is pressed. So, it is not clear to me the desire and the expectation as of yet and how this relates to extension;s BLF status indications.
Assuming the hours are set, you could have the system invoke whatever settings you like automatically based upon the time.
-
Abelaguilar Yes the idea was to trigger the time override for the time condition via the BLF button. It works fine, however, the light indicator on the BLF button does not always indicate the current time condition.
For example pressing the Lunch BLF triggers *803 which is the Lunch IVR
Office closed BLF triggers the *804 which is connected to the office closed IVR
If we don't do anything the time condition does its thing as programmed. The idea for us was to have a visual at any given time of where the current time condition is and trigger a time override via the BLF button if for example we decide to go to lunch early. Of course we can just pick up a hand set and dial the feature code.
Hopefully , i'm explaining this correctly.
So, the rebooting of phones was in a failed effort to try to solve this issue, however, that does not address the root cause of the problem.
-
Larry Neblett OK, now I understand, but sadly the light aspect has nothing to do with it and will not work the way you had hoped. There is no extension to monitor, it is simply a command that is executed by pushing the button, the same as if you had picked up the handset and dialed the same code.
-
Riddhe M Just checked again in the knowledge base, I found a useful article for the time condition.
https://support.yeastar.com/hc/en-us/articles/360013149733-Time-Condition-Extended-Understanding
You need to notice if the time condition is in override mode or not.
It's kind of confusing for the design of BLF state regarding to time condition.
-
Abelaguilar Well this is what i'm trying to accomplish. I'll keep playing with this. Great articles though. Thank you for the information. This helps. I'm assuming no one else here is successfully using the BLF keys in this manner to trigger time override conditions.
Please sign in to leave a comment.