esoare

Above is how you do it. You could do it with a User, or a Device. Whichever suites your fancy. esoare

Do you have access to Advanced Call Flows?

What @Tuly is referencing. Advanced Call Flows. Play Media Select the Media that has the Music. Edit. Upload the new file into the media that is named in all the Ring Groups.

no. it's going backwards. So, from what is visible in advanced provisioner. The Yealink T42S for example. There is only 2 options. "Current" (which by the way, Should the firmware version be placed beside "Current" so it's known which Version "Current" is?) and V81.0.110. While Yealink has had 4 total firmware's for the T42s on Yealink's website. I am suggesting have all the variants available. i/e .25, .60, .70, as well as .110.... It may be to arduous to accomplish, but it would certainly tell us if something broke between firmware's. Perhaps going forward, as new firmware's become available, 2600hz plans on adding all of them to the Advanced Provisioner, and the, "going backwards" won't be of consequence? I just looked at the Yealink T42G and there are 20-24 firmware variants. Obviously some are pretty old....I wouldn't want to pick between all those. I guess it's a matter of policy, and how much Firmware variants to offer... Sorry to bring complication to this. Perhaps I'm overthinking things....

I just had a mind blowing idea! What if you could select any of the firmware's available for the phone? This would be helpful for us to "test" things out, more easily For instance. Right now the Yealink T42S has 4 firmwares on the Yealink website. Yealink T42s Downloads . What if for testing purposes, I want to have 4-6 phones that I can Beta Test stuff with. In advanced porvisioner, I can select the different firmwares, and see if there is a difference, say with "BLF", or the "Call Park" feature!! For instance. In 81.0.70 firmware, Yealink did some Optimization to the "Call Park" function. Well. I am using 81.0.110 and noticed that the Red Light gets stuck on...but I don't have a way to 1: Go back to pre 81.0.70, OR 2: Even better, have 4 phones with various firmware 81.0.110, 81.0.70, 81.0.60, 81.0.25 and because they respond differently, I know that Yealink screwed things up again on firmware 81.0.70 upwards, which killed Call Park/BLF on Production. (This isn't an official report, but I suspect that Call Park is messed up again, it seems to work with BLF and *32, but I got a Stuck "Red light Flashing" with Call Park and *32) Why is Option 2 relevant. Because there wouldn't have to be any booting/rebooting as firmware's are installed. There would be a valid testing of a features, across multiple firmware's in real time! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Yealink firmware Optimization from the PDF "Yealink_SIP_Phones_Release_Note_Of_Version_V81.pdf " "4. Optimized the feature of Call Park. Description: You can enable or disable the IP phone to dial out the call park code/park retrieve code directly when pressing the Park/Retrieve soft key. And you can press the BLF/BLF List key to park the call to the monitored user or retrieve the call parked from the monitored user."

I wouldn't mind having my company "in" the sandbox... Maybe I would if it went down. Lol. But it sure would get me testing new stuff. OR I was playing around with existing phones between production and sandbox. I basically would use Yealink RPS and Grandstream Gaps to change which provisioner to point to, sandbox or production, therefore it just required a "reset to manufacturers settings" the phone would reset and go to RPS or Gaps to get additional provisioner server settings. (question, are the two provisioned totally separate? So I can leave the phones built with the same Mac addresses and it won't cause issues, is my question) If the above answer is, it's OK, then I don't see a need to put my company in sandbox. ***************************************** Please make the newsletter part of the forum also!! That way all the info is in one place. I already asked a programming/api question, which would have been tougher if the smart people where on the Google groups. Being able to see what was released in the sandbox, would be easier to play with, if it was in the forum, versus in an email based newsletter, that we would have to hunt down. There may be a need to lock that topic down since some features won't make it to production or be delayed. But I would suggest the more eyes that are on it the better. Perhaps some of the people running their own cluster want to test out the latest stuff also. Hope that helps. esoare

Well. Tell them it's in Beta and unavailable. lol.

Definitely Excited over here!! That is totally awesome!! esoare

I would agree with your statement of nervouseness being do to past burns and scarring. I guess something that wasn't mentioned, and I just thought of since you posted your reply Darren, is the following: There would be an announcement of the new firmware available in advanced provissioner. Reseller's would have an opportunity to select a few customers with various needs to upgrade their phones. If there are reports with said customer's we open service tickets that could be tracked to the new firmware. The Current wouldn't be forced without those being closed. (I'm not making a rule here, just a suggestion.) Obviously a "bad firmware" wouldn't be forced as current. If no reports, then the Firmware Current change is announced. And we move on with life.

I happily gave you the "feel good"

After the minimum week (perhaps more) and the new "current" firmware is rolled out. What if a huge bug gets identified? i/e: the Yealink BLF fun we had a few firmware's back. Can you make a mechanism that would be able to allow us (or you the provider) to roll back easily? I would recommend that. Just in Case. esoare

TrueDat!

What about email signatures? esoare

Question on this. With the e911 CLID, would we want that DID (which should probably be different than a: the main account number, b: the location number) to ring ALL the phones at that location? Kinda, like a default e911 group for that DID number, would always ring all phones. An alternative, but more complex. would be to do what Cisco does. Have 1 or 2 DID's set for a location, with the addresses programmed. When a device dials 911, it picks the first DID for outgoing CLID, and dials 911. If the call gets disconnected, the 911 operator can call back the DID, and it will RING that specific Device. If a second person call 911, the same is accomplished... My reasoning suggesting the default e911 DID ring Group, is that customers usually have a Menu Call flow for their main number, and it would be difficult for a dispatcher to reach whoever called 911, if the 1st call to 911 was disconnected.

It's in Beta. U must have missed the email for the invitation? esoare

I am really liking the new Forum!! Most Awesome is the "Unread Content" that allows us to peruse what we missed in a short amount of time!! I like that the heavy hitters (Developers that have clusters are posting here) since that allows us small fry's the ability to see what is being discussed. Keep up the great work! Another + to the design, layout + the Point system! esoare

FASTDEVICE, Sounds good. Looking forward to your product...like within a month or so. es

To explain a little bit better. So with Monster UI, I can download a CSV. For the Whole Month. The data is in the CSV program. So the curiosity question that I am asking about, is there a program to take that CSV info. Tabulate and a: put it into a new database to run reports from, or b: just run the reports from this CSV only. I am looking for the least complicated way of doing this, and wasn't sure if someone has a python script with a PDF creator to do this already. esoare

I can probably close on a customer, but I need this "I need to be able to tell by extension/person, number of inbound/outbound calls." Anything BASIC out there that people are using? Would appreciate more info. esoare

When I noticed the W56P was in the New UI (What are we calling that again?) I programmed the MAC in Yealinks RPS, did a factory reset on the unit, and the phone went/stayed at Firmware Version 25.73.0.40.. Thanks for working on the firmware updates!! es

Great, please keep us updated...rather not open a ticket on my end. 

Would like to see the option of "Also Ring VoIP Phones" in the Call Forwarding of Users in the Admin Interface not only the User Portal interface. 

experienced this also. must be a bug.

Vern from Telnexus came up with something for those of us that haven't the brainpower to do it. https://helpcenter.2600hz.com/2600hz/topics/new-billing-service is the post for that. 

I posted this in another thread. "https://helpcenter.2600hz.com/2600hz/..." Looking to spread the idea. ~~~~~~~~~~~~~~ I wonder if a record then play option would work? (then they wouldn't notice the delay) There are devices out there, that are made specifically to cancel out screaching of speakers, when a phone is next to one. So the Idea is. Hit Page. Hear a Tone. Record the message. Hang Up. The Kazoo platform "pages all the phones" The recorded message Play's across all the phones Kazoo hangs up. ~~~~~~~~~~~~~~~