Karl Stallknecht

I'm on 4.1 We can't use account.timezone because the account has phones in different timezones, so we need to use the timezone of the user in question.

KAZOO-5726

I tried that and it didn't work either. Yes, and yes.

We have a few accounts with offices in different timezones and I thought it would be helpful to show the timezone on the voicemail email if they forward the email between offices and are trying to figure out what the actual time when the voicemail was received was. I used the dropdown and added user.timezone but it just doesn't show anything when I left a test voicemail. My full string is: {{date_called.local|date:"l, F j, Y @ g:i A"}} {{user.timezone}} Which when I tested it just now it shows: Monday, October 16, 2017 @ 8:17 PM (simply missing the timezone at the end) Am I doing something wrong or is this a bug?

So I'm curious here... We have some clients who either: a) just want to close the office early some days (meaning they just want to start the normal after hours, or "all other times" TOD, earlier in the day) or b) want to activate an override of all TOD functions until further notice (i.e. a snow day where they record a special holiday voicemail and want all calls to go to that voicemail box until further notice) Does anyone have a good idea on how to accomplish both of these together, with BLF keys that will illuminate simply when the after hours or holiday TODs are active (one for "after hours" and one for "holiday")? The issue with the methods above is that if the client let's say activates their after hours early, they then have to manually reset it in the morning. Also, the BLF key won't illuminate if the system is automatically closing them so having a BLF key is misleading, other than telling them that something out of the ordinary is happening. I'm guessing that two features would need to be added to accomplish this: 1) A way to "schedule" presence updates at certain times, and 2) A way to "schedule" TOD resets to happen when a normal TOD would change the behavior. Does anyone have a programmable thermostat? It would work the same way...you schedule the temperatures you want based on the days and times. If you go and change the temperature with the up/down arrows, it holds the temperature that you set until the next scheduled temperature change and then resets and goes back to what it's scheduled to do (this would be the equivalent of closing the office early). Or if you change the temperature and then press override, it will keep the temperature at the temperature you set until further notice (this would be the equivalent of a snow day). Or maybe all of this is possible and I'm missing something?? :-)

For #2, I actually reported an issue with the slider. Certain resolutions and zoom sizes would make it impossible to show certain times (i.e. you could select 5:05pm but not 5:00pm). @JR^ thought it would be best to replace the slider to alleviate this issue.

If you want to further complicate things haha, you can also assign a BLF key on the phone to monitor the status of each time of day. Basically you'd setup a call flow like Fast Device mentioned, but also have it update a random presence number. Then you'd set a BLF key for each time time of day with the presence number(s) you used, and the one that was active would be lit up. The issue is this wastes BLF keys if you're using a phone that doesn't have many. And then it requires at least four keys (one to update the time of day for A, one to update the time of day for B, one for the light for time of day A and one for the light for time of day B), versus some customers may be used to an older-style PBX system where you simply turn "night mode" on and off with one button, and that same button lights up when it's on. This is one thing I wish we could do that we can't!

Oh okay sorry I didn't know that is what you were referring to. Thanks!

Out of curiosity what is the purpose of changing the local SIP port? We've never done that and haven't had issues, so I'm wondering what could potentially happen.

I can't remember where the screenshots are But here are the instructions from our wiki. These have worked perfectly for us but we don't use them for faxing, just voice. 1. Log into SPA112 (default creds are admin/admin) (to get the IP, plug a phone into port 1 and dial **** and then wait and then dial 110#) 2. Change default password (go to "Administration - User List") 3. Upgrade the firmware ("Administration - Firmware Upgrade" https://software.cisco.com/download/release.html?mdfid=283998771&catid=278875240&softwareid=282463187&release=1.4.1&relind=AVAILABLE&rellifecycle=&reltype=latest (make sure to unzip the file that gets downloaded before you try to upload it to the Cisco device) 4. After firmware upgrade, go to "Voice - Line 1" and then set these credentials: Proxy: (this is actually the account realm) Outbound Proxy: (insert whatever your outbound proxy server is) Use Outbound Proxy: change from "no" to "yes" Display Name: (sip username for the device - i.e. "user_xxxxxx") User ID: (sip username for the device - i.e. "user_xxxxxx") Password: (sip password) 5.. Set the dial plan to the following: (*xxxxxxx|[3469]11|0|00|[2-9]xxxxxx|xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.|**xxxxxxx) 6. Click submit and let the device reboot

We've never been able to get call waiting working. It beeps but you can't pickup the new call. Maybe it's something we are doing wrong?

Never mind my previous post...

I don't have the config file since I don't have any SPA112s that I can connect to right now, but I have screenshots of config. Would that help? Or is there something specific you're looking for?

This is fantastic! Thanks so much! Quick question: what is the difference between ring back timeout and call back timeout? I am guessing ring back is the time it's been in park before it rings back, and call back timeout is how long it rings back the phone before going back to park?

Thanks!!!

FYI I've been using it for over a year. I'm not fighting against using it. I just think it's good to have both options.

I wasn't discouraging him, and I appreciated the tutorial. I was just pointing out the fact that it's still more involved than just logging into the GUI.

So I get that Postman is more powerful and a great application, I just think the beauty of the old developer app was that it showed you the basics right there and gave you samples to play with. It was just easier for super quick and simple things. So I agree with @esoare that it would be nice to bring it back.

@Logicwrath I've read tons of posts from people who had to do this exact thing...we had one customer that we did it for and it worked, but luckily the root issue went away so we could remove the VPN and just go back to the normal setup. I've always been afraid it might start back up at any of our clients though.

Ditto

Ohh right! So then yes, technically functionality was removed lol.

Thanks!

No, sorry Darren. My original post should have been worded to say that I *THOUGHT* the functionality was no longer in Monster. But you/Tuly showed me that it was there all along. But I still think a keyboard shortcut is indeed "hidden" if it's not posted anywhere (that I can find).

In Kazoo you could just go to the account manager and click the account and it would show you the account ID. I didn't realize that feature was still there in Monster, but it was hidden. As for the auth token, I was using the developer app to get that. Like @Tuly mentioned most of the time I need to run a super short and simple API command. I found it annoying (even with Postman) to go through the multi-step process to a) figure out the account ID, b) generate a token, and c) then use that token to run the API command, versus just logging into the GUI and copying and pasting the account ID and auth token. Even though the auth token changes, as long as I just go to the GUI and copy and paste the most recent one then it's fine.

Wow, thanks @Tuly! I was pulling my hair out trying to find the account ID and generate an auth token now that I can't get it from Kazoo :-P Using the API to get those pieces of information was annoying lol.