Jump to content

Karl Stallknecht

Customers
  • Posts

    1,154
  • Joined

  • Days Won

    21

Posts posted by Karl Stallknecht

  1. 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!

  2. You definitely don't want to mix the two together! Use 100% SmartPBX or 100% Advanced CallFlows and Advanced Provisioner.

    They're both APIs on top of the same underlying system, and SmartPBX is meant to do a lot of things in an easy format. So if you go in and change something underneath it, weird things will break.

  3. Hi Tim,

    SmartPBX and Advanced Provisioner are indeed connected and they use the same provisioning URL.

    SmartPBX is great, but very limited and you have to use it exactly as it wants you to use it. Any customizations or changes aren't going to work well with it. We've found that customers who need logins should only have access to SmartPBX, but sometimes then they are disappointed that they can't get some of the more complex functionality.

    For provisioning specifically, with SmartPBX you can't do a ton other than just set the line keys/feature keys. For most people this is fine, but some customers (especially those who want an environment that is more similar to an old style PBX system) they will want a ton of things customized beyond the defaults that SmartPBX has to offer. Advanced provisioner allows you to modify a ton of settings, as well as specify custom config too. But there's no way I would let customers touch it (at least with our customers).

    The question I think comes down to who us going to be using it? Your technically trained employees, or customers that may not have technical skill sets?

  4. I can't remember where the screenshots are :P

    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

  5. 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?

  6. 4 minutes ago, FASTDEVICE said:

    @Karl Stallknecht Once configured as I'm showing, Postman becomes simple to use. Actually, it will be easier than the GUI and much more extensible. All that is being asked, is give it a try.  

    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.

  7. 1 hour ago, Tuly said:

    The reason why im excited about it,  when I have to do a quick API, lets say change The park ring back or change the outbound caller ID, in order to get the token I have to put in the username and password of an extension,  hash it then copy paste a few times to get the token, (Maybe there is an easier way,  I don't know ) 
    I do it just on a Linux server, 

    Ditto

  8. 1 hour ago, FASTDEVICE said:

    right, I'm aware there are two, but related topics, here. The ability to view the account and auth string, and then using the token somewhere in the UI. Where are they using the token?   Karl referenced a "developer's app."  I see no such app.

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

  9. 1 minute ago, Darren Schreiber said:

    Got it. So my point in my reply was that nothing was taken away from Kazoo UI, nor intentionally hidden. All the things available in Kazoo UI are still available in Monster UI, and have infact been enhanced to make it easier (hence the 'd' key to get the data with one push). So hopefully you see this as an improvement. Your original post seemed to imply we took something away that was there before - we did not.

    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).

  10. 9 hours ago, Darren Schreiber said:

    What do you mean "now that I can't get it from Kazoo"? The Account ID is available in both the account manager and the currently logged in user's control center, and the auth token was never available in the old Kazoo UI. It's the same as it has always been?

    The only thing the debug option allows for is retrieving the auth-token, which has never been exposed previously.

    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.

  11. Travis: I don't think we've had ANY of those issues at all. But we use 100% Polycom. Have you tested with other brands to see if those issues are Polycom specific? We change those settings at the provider level and account level all of the time and have never seen inheritance issues, other than with one minor thing. I'm totally shocked reading this!

    Actually I need to correct myself: the selection of http/https seems to be ignored, and the Polycoms at least always use https regardless.

×
×
  • Create New...