Jump to content

sporkman

Members
  • Posts

    26
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by sporkman

  1. 26 minutes ago, Karl Stallknecht said:

    We had a similar problem. The smoking gun was that somehow "https" got introduced into the mix. Make sure that https is NOT used anywhere and make sure that your web server where the files are hosted, do not have https redirection enabled. As much as I do not like this solution, it seems like the only way to make the things you are referring to, work.

    WTAF... How did you stumble on this? It looks like we've had https for some time (because why wouldn't you in this day and age??). Did it happen on a firmware update or any other change?

    Just tried this on a non-essential phone at this site - changed the "additional config" and the "contacts dir" to http and here we go:

    x.x.x.x - - [30/Jan/2022:15:59:59 -0500] "GET /phonebase/xxxx/contacts/0004f27xxxx-directory.xml HTTP/1.1" 404 248 "-" "FileTransport PolycomVVX-VVX_300-UA/5.9.6.2327 (SN:0004f27xxxx) Type/Application"
    x.x.x.x - - [30/Jan/2022:16:00:01 -0500] "GET /phonebase/xxxx/misc.cfg HTTP/1.1" 200 734 "-" "FileTransport PolycomVVX-VVX_300-UA/5.9.6.2327 (SN:0004f27xxxx) Type/Application"
    x.x.x.x - - [30/Jan/2022:16:00:03 -0500] "GET /phonebase/xxxx/contacts/000000000000-directory.xml HTTP/1.1" 200 11039 "-" "FileTransport PolycomVVX-VVX_300-UA/5.9.6.2327 (SN:0004f27xxxx) Type/Application"

    Another oddity - clearly the phone is on 5.9.6, but Advanced Provisioner says it's on 5.9.3.  ¯\_💩_/¯ 

     60451807_ScreenShot2022-01-30at4_08_39PM.png.75e24422f3b9ff491c721f9d3b1e9ace.png

  2. We've had some basic overrides in our config for some time that allowed us to serve up a basic company directory.

    We set "Custom Config File URL" in the Advanced Provisioner to point to a file on one of our web servers, eg: "hxxp://phonedir.example.com/phonebase/customername/misc.cfg"

    That file has some basic overrides related to directories, polling (to ensure we don't have stale directories when we make changes to the XML directory), and some customer requests that can't be set in the provisioner:

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <!-- see https://documents.polycom.com/bundle/trio-c-ag-7-1-0/page/c-ucs-ag-local-contact-directory.html -->
    <PHONE_CONFIG>
            <ALL
                    softkey.feature.directories="1"
                    softkey.feature.doNotDisturb="0"
                    feature.doNotDisturb.enable="0"
                    feature.directory.enabled="1"
                    divert.dnd.1.enabled="0"
                    video.enable="0"
                    dir.search.field="1"
                    dir.local.readonly="1"
                    prov.polling.enabled="1"
                    prov.polling.mode="rel"
                    prov.polling.period="3600"
                    voIpProt.SIP.specialEvent.checkSync.downloadDirectory="1"
            /> <!-- end ALL -->
    </PHONE_CONFIG> <!-- end PHONE_CONFIG -->

    We also set "Custom Contacts Directory URL" in the Advanced Provisioner to point to a directory on our web server, eg: "hxxps://phonedir.example.com/phonebase/customername/contacts/" and we place a "000000000000-directory.xml" file in the /contacts/ directory.

    We periodically make changes to 000000000000-directory.xml when the customer has staffing changes.

    This worked well for the better part of the last year. The phones pulled the "misc.cfg" file, the "000000000000-directory.xml" file, and displayed the directory. We could make changes to the directory XML file and within the "prov.polling.period" phones would check the file for changes.

    What's happening now is that the "misc.cfg" file is being fetched (can see it in our web server's logs), but the directory file is not - not a single attempt in the last month of logs I have from ANY phones.

    Is there anything new that rolled out in the hosted kazoo service in the past few months that might alter this behavior?

    Our phones are running both 5.9.3 and 5.9.6 - same behavior on both.

    Really stumped as this was working, and then it wasn't, and with no changes on our end.

  3. 22 minutes ago, vladimir_2600hz said:

    @Karl Stallknecht when using this feature all the Poly phones in the account will be have their custom_contacts_dir_url automatically set to an auto generated XML file, that would be the intention of the Contact List tab. 

     

    @sporkman that's interesting! we tested with VVX400 series and a reboot was enough to apply the new contact list, we will keep an eye on the usability.

    Can you tell me what version you're running? I have a VVX410 running 5.5.1.15937.

    This article was updated to note some issues were corrected after 5.4.0:

    https://community.polycom.com/t5/VoIP-SIP-Phones/FAQ-How-can-I-create-a-local-directory-or-what-is-the/m-p/74922/highlight/true#M14125

    The old behavior was for the phone to copy the global directory to the personal directory, making them semi-permanent.

  4. 54 minutes ago, Karl Stallknecht said:

    This requires you to manually apply it on each phone, and manually create XML files though, which can be a huge hassle. Plus then every time an employee leaves, you have to remember to update all of the phones and XML files.

    I have a phone sitting here and both it's shared directory file (000000000000-directory.xml) and the per-phone directory file (64167f94XXXX-directory.xml) are empty and after multiple reboots, the phone just holds on for dear life to the previous contents of those files. Going to try different levels of phone resets to see which one finally makes it ask for either of those files again.

    Trying to imagine doing a reset on an office with like 50 phones just to update the contacts...

  5. And if anyone was wondering, I was going to try the "learn by doing" approach, but whatever I was putting in for names/numbers was just always giving me an error. I assume I'm misunderstanding what goes in what field or what's allowed in each field.

    Anyhow, I guess this was taken away as the option no longer shows up:

     

    Screen Shot 2020-12-03 at 1.19.10 PM.png

  6. 2 minutes ago, Darren Schreiber said:

    That's unfortunate. While there was an issue last Monday/Tuesday, it was resolved. I would not agree that this should stop you from mission critical clients in the future, but it sounds like the timing on this did kill it for this customer.

    Yes, the call center issue.  It's a very large ob/gyn office.  I mean, not having ladies in labor being able to reach their nurse or doctor is a really big deal - in many ways this client is probably more demanding than an office full of traders.  Total disaster.  And the hours spent convincing our reseller there was a problem, just painful.  Even after the fix, there are still ongoing issues that I suspect don't show up in lower call-volume queues, and definitely some browser-specific issues with the web app that we never really nailed down.

  7. Just wanted to pop in on this one again, as we're seeing issues with people using sidecars.  I have to dig again to find the Polycom thread, but there's a bug in older versions that causes the sidecar to lock up, so I want to get those customers running something with that fixed.

    Any other insight onto where the "default" comes from?  Would love to be able to set that on a per-site basis.

  8. On 12/17/2017 at 7:05 PM, Karl Stallknecht said:

    @sporkman I love your optimism with the dollar symbols lol.

    Yeah, maybe misplaced.  It's a huge ob/gyn office and the call center app is hugely not functioning.  You want to up the stress level in an office like that?  Get your phone system dumping calls from ladies in labor.  Huge black eye for us and a bit of a "is this ready for prime time" sort of moment.

  9. 1 minute ago, Darren Schreiber said:

    Nope, not if they load known files perfectly.

     

    I think I see what you're looking at then - an unprovisioned phone is going to be generating many more 404s than a provisioned phone?

    When we bring up a large number 40-100, is there a batch size we can work with that won't trigger this?  The method of having the DHCP server set the boot server saves literally hours of work compared to entering stuff by hand on every phone, especially if you're going into an office and transferring phones from another provider.

    DDoS generator attached:

    IMG_20171215_155737.jpg

  10. 3 minutes ago, Darren Schreiber said:

    Yup, that's what you hit. Basically don't plug in the phones until they're configured, as a rule, and it should be fine. And don't try to load configs from a browser.

    I can unblock you manually if you msg me your IP.

     

    Thanks!

    So my remaining question is what happens in a more normal situation like a power outage where you similarly have an inrush of phones looking to hit the server?  Will they be blocked?

  11. We use DHCP option 66 to provision new phones to the zswitch server.  This is obviously way faster than manually keying the provisioning server into each phone and it works great with new phones.  For used phones, we similarly point all the phones at Polycom's boot server which clears and updates them if necessary.

    Today we were on site with 70 phones to provision.  After a round of 30 or so phones, we found no further phones could be provisioned.  After much troubleshooting, we realized that "p3.zswitch.net" was not reachable from our public IP at this site.  We flipped to another public IP and were able to do another batch of phones.  Then same thing, "p3.zswitch.net" becomes unreachable.

    My spidey sense says that there's some kind of DDoS protection in place and turning up an office full of phones at once is triggering it.  This is worrisome in that a) we should be able to bulk provision phones and b) would this same thing happen if, say a large office lost power and then all the phones hit the server at once when the power returned we'd be in a similar situation

    Thoughts?

  12. Thanks - found that.  I do frequently get lost in the UI, so maybe I'm missing it, but after some hunting, I'm not seeing a place to set the default.  I checked at the main "advanced provisioner" level, nothing there. Also looked all over at the account level and didn't find anything.

    That said, any good reason to be running something this old?  Does the use of this old version imply that after testing 5.4.x is what's best or just what was out when the account was setup?

  13. When brining in a new phone and having issues, is there a recommended version of the Polycom software we should be starting with?  I see the most current if 5.6, and there seem to be quite a few 5.5.x releases.  What version does the provisioning server serve up and when (if ever) do you push upgrades?

    Of note, a phone I"m working with now in the lab is at 5.4.0.5841, which is relatively old and I'm wondering if this is why I see the phone complaining about invalid params in kazoo.cfg - perhaps the platform is too far ahead of the phone.

  14. Mark - yes please!  I'm slogging through the Polycom admin guide and it's a beast.  I was looking for macro information a few weeks back and just kept finding snippets with no context or format.  If you have a references that's something of an alternate HOWTO for macros, that would be great.

  15. I'm not sure how useful this would be to advanced users or how often it would be useful, but in trying to sort out all the various config files served up, overrides in the Advanced Provisioner, etc. I find I can waste an ungodly amount of time doing something simple like trying to grab all the config files a particular phone wants to load.  For troubleshooting, I find it useful to grab the configs sometimes.  For the learning process, seeing a list of the files (and the order they're loaded) is handy. I'm talking all Polycom here, but I assume other phones are similar.

    What I'd like to see in the Advanced Provisioner is some data that's probably already there being exposed on one of the config tabs. Mainly a list of config files, in the order they're read, all with hyperlinks to the actual config files.  Make sense?

  16. OMG, that avatar is frightening.

    So I did figure this out and have 50+ phones running with this.  Be aware that some of the Polycom info is way out of date.  I mostly used the Freeswitch guide.

    I do wish those little help popups would have some more info or that there was an actual set of docs for the product.  I ended up using "Custom Config File URL" and loading a config there that defines an LDAP server.  Not sure if that's better or worse than the directory override as it seems like either would work.

    Another total bummer here is that this has to be done for EVERY SINGLE PHONE.  This should really be a company-wide setting.

    I'm new to the platform, is there any good option for documents outside of the forum?  Is there any interest in feature requests/feedback from users that come in here via a reseller?

    Next up - softkeys!  I hope in the future we see the advanced provisioner turn lots of these config items into clickable GUI bits and pieces.  The Polycom guide is great, but it can be pretty time-consuming to find the info, load it on the phone, make a change, reboot the phone, etc.  I probably clocked a good hour just waiting on phone restarts while troubleshooting LDAP.  I did not have an anime hentai helper though. :)

×
×
  • Create New...