Karl Stallknecht

See here: https://helpcenter.2600hz.com/2600hz/topics/time-formatting-incorrect-in-fax-voicemail-email-templat...

Wow, I learn something new every day! Thanks for explaining this Baze! I had no idea we could let clients enable/disable this by themselves without logging into the UI. Now the only other thing that would be helpful and help mimic an analog system would be a way to setup a BLF key so that it could light up to show that the system was in "night mode" like a standard PBX will let you do so that the receptionist will see it when he/she comes in every morning as a reminder to take the system off of night mode.

Wow, thanks!!! This works! I am thrilled! Our clients are going to be SO happy! I am upset though that 2600hz did not tell anyone this...

Oh, good thinking! I'll try this on Monday and see if it works. Thanks!

Looks like that was the problem. We are using advance callflows for this account so we had never assigned an extension in SmartPBX since it didn't matter. Thanks!

In SmartPBX under users and user features, you can no longer enable inbound call recording. When you click the icon nothing happens. I use to be able to use this, but it no longer works.

Very good write up Vern!!

None of our medical offices have asked us about HIPAA compliance for the phone side of things. Faxing comes up quite frequently though...see this article I posted and never got a response on: https://helpcenter.2600hz.com/2600hz/topics/hipaa-compliant-fax-option

Confirmed

Not sure, sorry :-/ We're using 4.16 for our clients at the moment.

Hmm you might need to use a newer version. Try 4.16

What I was curious about was if non-2600hz firmware was causing issues. I would recommend doing a reset file system and then using voipt2.polycom.com as the provisioning server to put older firmware on (try 4.04). Then once it has downloaded that, update the provisioning server to 2600hz and see what happens.

Michael, Can you please clarify the software versions? Are you referring to firmware 4.1.8.0628 loaded by 2600hz? Or are you getting the firmware directly from Polycom?

Sorry to be the bearer of bad news but I'm pretty sure you can't do this (but I could be wrong).

I need to be careful saying this since we rarely use Yealinks, but I am about 80% positive that the 2600hz provisioning files will NOT overwrite the BLF keys on Yealinks, so if you set them in the web UI for the Yealink phone it should stick without an issue. That being said, it isn't the best method and is not recommended. I did it about 6 months ago and had no problems. Something Darren mentioned in the same breakout session Anthony is referring to was that 2600hz will be adding a way for you to tweak or upload your own custom config via Monster. This way even if they have not added the feature in, you can still set it from Monster and then have it provision automatically without needing to go into the web UI. This would eliminate the issue you mentioned.

FYI you can make it easier on yourself by selecting "call park" instead of "BLF" on the line key type menu. This avoids you having to press transfer. On Polycoms, this option is called "automata" when you set up a BLF option. See below:

Are you using a "landline" type device? If so, it shouldn't be costing you anything.

Out of curiosity is this so that their employees can't stalk customers or something? haha Smart idea though, I like it. In Kazoo caller ID prepend works fine for us, as long as we are using SIP devices with it. 2600hz: is there a way to disable incoming caller ID? I can see how this would be useful with certain customers. I know you can disable incoming CNAM dips, but I'm not sure about the number portion.

A potential customer is currently using Ring Central and wanted to know if we have this ability: they said that Ring Central has the ability to prepend digits before or after the caller ID when a call is forwarded from their office to an external number. The idea is that a customer calls the office and presses the extension for employee A. Employee A has a call flow that rings their desk phone for 10 seconds and then rings their cell phone for 10 seconds. Employee A wants to know that it is a forwarded call though if they get it on their cell phone, so the cell phone shows "0(xxx)xxx-xxxx" and the employee can answer the phone differently. Currently the only two ways I know of right now to tell someone that it is a forwarded call are: a) Set the external device settings to not pass through caller ID, so the caller ID shows the office number - the problem with this is that the customer can't look at their cell phone call log to get the caller ID of the caller. Plus, then the employee might think another employee from the office is calling. or b) Set the external device settings to "press 1 to confirm pickup" - the problem with this is that you don't know until you have already answered and it also slows down the answer time, so you have to add more rings in order to allow time for the employee to listen to the prompt and then press 1. As for as I know, no other method exists. If it does though I'd love to know about it! And if it doesn't, are you able to add this caller ID prepend method? I tried setting up a call flow to prepend the caller ID before the call goes to an external landline type device, but it didn't work. The prepend feature only appears to work with SIP devices.

This has been in place for a few months :-) https://helpcenter.2600hz.com/2600hz/topics/faxbox-send-settings?topic-reply-list%5Bsettings%5D%5Bfi...

We use Grandstream ATAs. They've been ROCK solid for us. The only thing we've noticed is that some of them seem to stop sending caller ID information through to the analog phone once and a while, and you have to reboot the ATA to fix the problem. Not sure whether that's a 2600hz problem or Grandstream. I would love auto provisioner though, as the Grandstreams require a lot of tweaking to the settings to get them to register and work well. We saved screenshots of all of the config pages so that we can go back and reference it, but auto provisioner would make our lives much easier.

Marie: We noticed the same things. FYI for the first point you mentioned about logging into Monster, I found that the only way to get rid of the getting started screen is to go through the welcome process. Once you go through it, it stops coming back up.

Thanks Katie, we are glad to see all of these updates. Do you know when provisioner will receive some of its long overdue fixes though? We are anxious to start using it but can't due to several major issues. Thanks!

Ditto!

Aaron, We received a success message back, but the phone number we added still is able to dial DIDs on that account: {"page_size":0,"data":[],"revision":"undefined","request_id":"05769ba5bde5862240291107d2fbf0aa","status":"success","auth_token":"xxxxx"}*  We might be doing something incorrectly, but to us it appears that this is not working.