Jump to content

Logicwrath

Customers
  • Posts

    578
  • Joined

  • Days Won

    21

Posts posted by Logicwrath

  1. We are seeing some issues with a large ring group.  The end user would like 15 phones to ring for incoming calls.  Should we expect issues with adding 15 phones to a ring group?  We are getting reports of issues where the not all of the phones are ringing.  I suspect part of it might be due to some delay or weirdness with the current call forwarding.  I increased the ring time from 20 seconds to 30 seconds for now to see if that helps.

    Are their any known issues with having 15 phones in a ring group?  I can understand a small call setup delay + a call forwarding delay causing some issues.  However, once the numbers port tomorrow I will need to make sure that all phones ring when a call comes in.
  2. One of my distributors told me about week ago that they were able to procure 600 more T46G's from Yealink.  I thought awesome, based on your volume how long do you expect those to last?  They told me 1-2 months.

    I placed an order today for 1 phone and I got a call.  We only have 1 open box phone left.  All 600 were sold to what I suspect is high volume re-sellers hoarding stock.

    Additionally, I was told that Yealink is on Chinese new year's for 3 weeks and there is no one they can complain too and that Yealink stopped producing these phones 3 weeks ago.

    I have not tried calling other vendors yet as I only needed the one phone for now.  I am however, worried.  Yealink is no treating their US customers and distribution partners correctly with this behavior.

    New phone, New Firmware + Chinese New Years!

    Maybe, I need to get comfortable with Polycom.
  3. Yes, this would be great.  We currently use Yealink RPS to send our phones to our web server first with common configs, which then redirect to 2600hz's provisioning server.  We have done this to work around as many of the "Advanced Provisioner" limitations as we can.  However, it only solves a portion of these limitations.

    It would be great if we could get text based common config support at the account and sub account levels.  I would actually prefer to use text over GUI so I can choose which parameters are important for me to configure.

    Also, selectable firmware would be great too.
  4. Use Postman in chrome.  Create MD5 hash of username:password and submit it with postman.

    {   "data":{
          "credentials":"md5 has here",
          "realm":"client realm to connect too"
       }
    }

    You need to configure the headers to be Content-Type application/json
  5. Hmm, sounds like a Polycom thing!  Custom configs would be a huge quality of life upgrade.  We are running into settings on just about every install we do that are not supported in the provisioner.  Some of the time we can squeeze them in with pre-provisioning, and the other half we have to manually log into the phone.

    I think the new line of firmware from Yealink has some things baked in that might allow something similar to what your talking about with additional custom configurations.
  6. Hello,
    There are new options in Advanced Provisioner for dial plan entries.  I was testing the "Block Out" rules and they are not getting provisioned.

    I tried setting 1 rule and I also tried setting 2 rules, and I even tried factory resetting the phone.  In all cases the block rules are not getting provisioned to the phone.  I suspect there is a bug.

    Rule 1:
    xxxxxxx
    1,2,3,4,5,6

    Rule 2:
    xxxxxx
    1,2,3,4,5,6

    I want to use these rules to block 6 and 7 digit dialing on the phones.
  7. Out of the 3 distributors I called yesterday, 1 is out completely, one had 366, and the other had 50.  

    I talked to another one today and they have 22.

    I am not sure how quickly these phones sell, but my primary distributor was sold out the first day.  Like you said, we may be able to find some distributors that still have stock, but I am already having to call people we would normally not do business with.
  8. Hello,
    Can we please have the W52P firmware updated to v80+ so we can start supporting W56H handsets?

    The base station for the W52H is the same as the W56H, the only difference is v80+ firmware is required for them to co-exist on the same base station.

    According to the FAQ:
    http://download.support.yealink.com/download?path=upload%2Fattachment%2F2016-4-20%2F3%2Fb9f044bb-761...

    After upgrading from V73 to V80, the base will support both the W52 and W56 handsets. Customers can upgrade the firmware in the same way as Yealink IP phone provisioning. Yealink will soon have a release note regarding the upgrade from V73 to V80. The firmware is free of charge.
  9. Hello,
    Yealink has just released some new products.  We are looking forward to using them and wanted to point them out so they can be added to the advanced provisioner.

    We are VERY excited about OPUS support with Yealink and look forward to using it.

    With a new firmware update. the WF40 now supports the T46G as well as the T29G. Please note you will need to be on firmware revision xx.81.0.15 for this functionality to work.  It also works with the T48G with firmware 35.80.0.95 or higher.  I believe the WF40 also works on all the new T4S series phones, but I need to double check.

    --- begin copy paste ---

    The T4S series includes the entry-level T41S and T42S phones, the gigabit color phone T46S, and the gigabit touch screen phone T48S. The series maintains the elegant appearance of the Yealink T4 series and further ensures users a lifelike communication experience, thanks to Yealink Optima HD voice technologies and the addition of Opus -a totally open, highly versatile audio codec. Moreover, the T4S provides enhanced performance and extended hardware functionalities for business customers.

    The upgraded T4S series incorporates the latest advanced components for excellent stability and performance. The phone series delivers a remarkable phone experience with an optimized smartphone-like interface. Integrated cutting-edge features, like Wi-Fi and Bluetooth connectivity and rich one-touch soft keys, brings additional convenience and increased productivity for customers. 

  10. It would be awesome if we could do the following:

    1. Specify a custom DNS domain for each fax box in advanced settings.  Example: (fax.client.com).

    2. Configure a CNAME MX record for the custom domain that is the actual fax box SMTP domain like 1234dxcfd.fax.zswitch.net.

    I am not sure if this is technically possible or not, but it would sure be nice.
  11. Hello,
    If I recall correctly, 2600hz has been taking steps to prepare for offering SMS / Texting services.

    Is there any update or new information about when such services might be ready for production?  We may end up looking at third parties again in 2017.  Any chance now that 4.0 is live we might get SMS / texting soon perhaps via an app?
  12. Actually, I apologize, the devices are showing green in "Users", however, they are one of the extra hidden devices. from view (+2) or (+1).

    So I guess the interesting thing here is that with failover mode enabled, I am unable to call a registered extension and I get the error message I posted earlier:

    "Due to telephone company facility trouble your call cannot be completed at this time."
  13. I actually checked the registration tab in debugging and found that this user did have an extension registered even though his device list under "Users" was showing "RED".  However, his device under devices is showing green.

    Interestingly, another user in this account is showing a registration in debugging but his devices (in "Users") are showing "RED" but in "Devices" are showing green.

    Some interesting things happening.  I called the user without failover mode on and the call was delivered normally.
×
×
  • Create New...