Jump to content

Rick Guyton

Customers
  • Posts

    628
  • Joined

  • Days Won

    41

Posts posted by Rick Guyton

  1. I wish SmartPBX could support clients with multiple locations. It'd be very nice to be able to group a bunch of phones up into a location and have them automatically use the main number for their location to call out on, call 911 over and use a certain "location prefix" for their extensions. 
  2. Hi Jr,
         It used to be that simply going to the URL would crash the integrated iOS browser on iPad and the iPad chrome browser. Now it just makes the tablet run like hell. after I load the interface, there's a 10-20 second delay from when I tap a key to when it populates in the field.
  3. Replication:
    - Create an account
    - Put a device into the account
    - Delete the account
    - Put same device into another account

    Expected Result:
    - The phone shows up in Advanced provisioner after being added to SmartPBX.

    Actual Result:
    - The phone will not show in Advanced provisioner in the new account.

    Diag:
    It seems that the provisioning profile is never deleted when you delete an account. If I check https://p3.zswitch.net/MAC.cfg the old config is still there from the old account. I'm assuming advanced provisioner in the new account sees this and therefore blocks it on the new account.
  4. If we are talking mobile apps, I'd personally much rather see a client access app. Something that shows call logs for that user, shows voicemail box messages, fax box, busy status of other users in the system and a dialer that allows you to dial off your cell phone like you would off your desk phone. 

    For management, I've just been RDPing into one of my servers to use the interface. According to Katie, the webUI should work on mobile devices, but it always crashes for me. Haven't tried it on the new Monster release yet though...
  5. @Karl: this is an example of a PIVOT call flow. What you are seeing is PHP code that resides on your server somewhere. So basically, if you setup a PIVOT callflow, 2600hz queries your webserver for a callflow and you can dynamiclly create one. In this example, the code above evaluates the callerID of the incoming call. If the first 3 numbers are 486, it gives a busy signal. If not, it tells 2600hz to go follow another callflow.

    @Ralley: Thanks for the example. That's awesome.
  6. Sure Karl, we recommend currently that clients that get bombarded with robocalls simply put a menu item at the beginning of their call flow. Even if they don't really need one, they can just make two menu items like "press 1 for sales and 2 for service" even if they ring the same phones. Sure, that won't stop real person sales, but it will prevent the robodials since they won't press 1.
  7. I'm curious about this too. Darren mentioned he wanted us to start using the MonsterUI exclusively, and I want to be using it aswell. But because there's issues going back and forth between KazooUI and Monster and my clients still have to login via KazooUI, I'm forced to do all of my production work in KazooUI still. :(
  8. It would be nice to have API access to the Reseller Accounting tool. I know Darren commented that the Reseller tool simply accesses existing APIs and that's probably true. But, I'd bet there's a heck of a lot of API calls and logic applied. It'd be extremely convenient to be able to make a single API call and get a nicely formatted JSON back that I can use a tool like Zapier to auto-generate invoices into my quickbooks online.
  9. I just wanted to say that I love the new provisioner. I've been playing with it pretty much all day and I am so excited about being able to deploy this to all my clients. It is going to save me so much time it's ridiculous. 90 percent of my support time on this service is dedicated to walking clients through getting me remote access to their computers, then gaining web GUI access to the phones to modify one thing or another. now, I'll be able to just log into the provisioner make the change and ask the client to reboot their phone. WOOT!
  10. Correct, It'd be nice if BLF could be set account wide. Often, clients want all the same BLF keys across all the phones. In almost all scenarios, there are a few BLF keys that they want across all phones (Like the front desk, owner, manager, ect) then a few customizations on individual phones. Also, I just found out that on the T46G, all of the buttons are considered "BLF" buttons. So, I have to set BLF key 1 to "line" on every phone. (Pictures below so you know what I'm talking about there)

  11. I'd be very helpful if "Line Keys" were available in the "account settings". Often, my clients will want the same BLF keys across all their phones. I'd be very nice if I could do this via account settings instead of setting each phones line settings through the advanced provisioner. That said, this is a hell of a lot better than logging into each phone and doing it through the WebGUI.
×
×
  • Create New...