Jump to content

Logicwrath

Customers
  • Posts

    578
  • Joined

  • Days Won

    21

Posts posted by Logicwrath

  1. This was resolved.  There was some kind of issue/error when activating the device in the mobile app and a required call flow was not created.  If you see the "Repair" button in the mobile app it means something is wrong and you should press it to fix the device.  After using the repair button, the call flow that was required was recreated and now I can add the device to users.
  2. As of right now, I see the following benefits for using mobile.

    1. Presence
    2. Call recording
    3. Outbound caller ID
    4. Reliability (Internet outage/power outage)
    5. Call flows, inbound routing, and other misc PBX features
    6. Easily add multiple inbound DID's

    However, as far as replacing handsets, there are some limitations.  No hold or call transfer seem like big ones.  I also wish everything 3 digits or more got sent to 2600hz instead of 4 digits or more.

    An OTT app along with this service to facilitate things like real-time call control, voicemail, BLF, and other advanced things would be great and it could be sold in the app store.  I suspect an app could be developed that would work with any Kazoo installation.  This has some revenue potential for whoever develops something.

    One more thing to note is that Sprint pricing is already very low.  They are offering 4 lines unlimited for $30/each and for a limited time they are including a 5th at no additional charge.  http://prntscr.com/f3cw6r

    Comcast is also providing a competing solution integrated with their voice products back ended with Verizon.  I think they are charging $45 or $65 / phone depending on which Internet/TV plan you have with them.  I believe their offering will have a pretty handy app involved as well.

    I have been thinking about what types of businesses would benefit from using a cell over a wireless handset.  The lack of basic call control seems like the biggest hurdle at the moment.
  3. Hello,
    First, is there a mobile related forum?  If yes, can I get added to it?

    I activated a mobile device last night.  However, when I try to add the device to a user in SmartPBX the action is not saved.  I tried adding the device to more than one user.  In all cases the save button never actually saves the change.  Is this a bug?

    Is it possible to use features like hold and transfer on the mobile device?  If yes, how is this done?
  4. We will be pitching our services to school's and I suspect one issue that might arise will be what happens when the power goes out etc..

    I suspect this questions might come up.

    Is there some kind of edge device that will keep local extensions and paging working in an emergency?

    Any plans on building a Raspberry PI type device that syncs with the cluster for this type of thing?  I suspect that would be a huge undertaking.
  5. Hello Matt,
    This has been discussed on the community in the past.  Create a call flow with a number of *98### where ### is the voicemail box number.  Then drop in the Voicemail object and select the same voicemail box.  On the phone side create a BLF key with the same value as the call flow number *98###.

    This will will monitor the voicemail box.  The only issue here is that if you assign the VM box to one of the users and they transfer someone to the VM using the BLF key it will send the caller to the voicemail box to review their messages and actually have the external caller logged into the voicemail box to edit and make changes etc..

    I suspect one way to work around this is not to assign the VM to any of the users with the BLF key.
  6. I was recently told from an insider that Comcast runs their "nodes" at 87-92% utilization and that they intermingle residential and business accounts.

    I believe WOW runs closer to 65% utilization and does not intermingle business and residential.  I don't have all the details or a complete understand on how this stuff works but I figured I would share it anyways.
  7. We are seeing the same issue.  I tried to add a caller id pre-pend on a monster group and it is telling me "The value for the field "children._.time_limit" must not be more than 600."

    I would still like to add the pre-pend if this gets fixed can you update the thread so I know to check?
  8. It would be great if we could have a recurring phone meeting or webinar once a month or quarter where we have the opportunity to provide feedback.  I am sure there is a huge amount of feedback we could provide that is not getting put on these forums.

    I see this as an opportunity for re-sellers and community members to submit their most important concerns or issues.  I would gladly join a recurring discussion and communicate the items that are most important to me.

    Another thought, could be a monthly/quarterly recurring thread requesting feedback.  This would work even better with a reddit style voting system where top issues get upvoted.  If you were requesting the feedback, I suspect more partners would provide it as they would not feel like they are complaining.  It would be more of an open discussion.  It would also give 2600 the chance to respond and/or fix any misconceptions.

    I think something like this would strengthen vendor/client relationship and help steer innovations/improvements that the community wants most.

    Just a thought.
  9. Rick,
    At least for now, after you submit the port you can request that they manually make the numbers available for configuration.  This is usually good enough to get things configured.

    My biggest complaint is that there seems to be 2 ways to make the number available.  One way makes it "local" and when it is local you can't configure E911.

    The other way, they complete the port makes it more official and all configuration options are available.  I would very much prefer to be able to configure E911 on local numbers or just get rid of the "local" status all together and stick them in like normal numbers.

    In any case I want to be able to configure E911 right away without having to configure a temp number and then later configure the actual number. 
  10. I was reviewing a configuration created by Advanced Provisioner and I see that you are setting the following field:

    ### It enables or disables the phone to protect personalized configuration settings even after auto provisioning.### If it is set to 1 (Enabled), personalized configuration settings via web/phone user interface will be protected and remained after auto provisioning.
    ### 0-Disabled, 1-Enabled. The default value is 0.

    auto_provision.custom.protect = 1

    Is this new or was this always there?  Any idea when this setting was added?  I suspect this setting should solve the issue of provisioner overwriting manually changed settings.
  11. #1 This is something we are very excited about.  Are you willing to give any kind of loose timing on this?  I assume this would be released after support for T46S and T48S phones in provisioner.  Any kind of timing or update on that these fronts is appreciated.

    #2 I have immediate use cases where I will have to make some decisions about pulling phones off Advanced Provisioner.  I would much rather keep the device in Advanced Provisioner, configure the phone and keep your "certified/tested" settings, and then just download the configuration file to my web server with 1 or 2 tweaks.  In the future when #1 comes out, I can easily re-integrate the phone back into Advanced Provisioner without doing as much work.  If you like this idea, is it something we could see in the next week or so?

    #3 Are you thinking about essentially providing some kind of online text editor, with default configuration and perhaps some variables like %sipusername% or %sippassword% etc.?

    When you are ready to do something about #3 I suspect we would all have some good input or ideas on what would actually solve problems or save time.  Honestly, it sounds like #1 would eliminate the need for #3 as being able to merge in a second configuration that overwrites the Advanced Provisioner configuration in certain areas would most likely solve the issues.

    I am very confident that the community would be willing to do an online meeting and discuss ideas or limitations with provisioning.  That type of discussion might save you some time or prevent you from having to develop something that is not as critical or important.
  12. Hello,
    I know there has a been talk recently about the Advanced Provisioner.  We are running into limitations with it frequently when settings we need to use are not available.

    Our most recent case is where we need to configure Remote Phone Book on Yealink phones.

    I don't expect 2600hz to have to test and provide the ability to configure every single setting on a Yealink phone as this would be a huge project.  I also understand the position of not wanting to create a bunch of support tickets if partners break their phones trying to do something advanced or screwing up a field name or something.  However, these limitations are costing us a lot of time and support tickets.  Pulling phones off the provisioning system to allow a feature creates a huge amount of manual work when we need to update those phones in the future.

    1. It would be great if we could merge a second custom configuration file with the configuration file the Advanced Provisioner uses.  I think Polycom has this ability already, and the new Yealink firmware is probably setup to support this.

    2. Can you please add a download configuration link to the Settings button next to the phone in the Advanced Provisioner?  In cases where we need to remove phones from the 2600hz provisioner because of limitations it would be great if we could just download a properly formatted and named cfg file for use on our own web servers.

    3. Can you setup Advanced Provisioner not to configure settings or keys that are not explicitly configured?  If I want to manually set a DSS key to "remote phone book" and that setting is not configured in Advanced Provisioner I don't want the manual setting to get overwritten by the provisioner.  One easy way to do this might be a new option for the key type named something like "Do Not Configure" or "Excluded" etc.  Where the field does not get specified in the configuration file at all and thus would not overwrite anything manually created.

    This is a big pain point for us.  A combination of having to spend a lot of time creating similar configurations by hand (we even use macro recording software to try and automate some of it, it still takes us time and is not perfect) and the inability to configure important settings is always on my mind.
×
×
  • Create New...