Genesys Cloud - Main

 View Only
Discussion Thread View
  • 1.  Polycom VVX 401 Registration / PureCloud Provisioning / DHCP

    Posted 08-01-2019 17:55
    Hi All... really struggling with this. We do quite a bit of ip phone registration using dhcp, but this one isn't adding up. 

    Trying to register a Polycom VVX 401 to my purecloud voice instance using the purecloud provisioning service. I have the base phone set up per the config note, and my dhcp pool on my l3 switch has option 160 configured as so:  option 160 ascii http://phonediscovery.mypurecloud.com

    Doesn't work. The admin section on the phone has a default dhcp boot sever of "custom+opt66", which I can't find anything about on the interweb. It has a second entry for BootSrv Opt: with a default value of 161, but configuring option 161 for the phone discovery url doesn't work. 

    I tried the manual setting per another doc, entering the discovery url manually, etc... and that doesn't appear to do anything either. 

    The phone doesn't seem to go through a dhcp process... it gets an ip address in my vlan for that network, but i don't see it trying to look up a boot server like you'd see a cisco or avaya phone do. It defaults to a "user credentials" or "web credentials" page. 

    Any thoughts? 

    #Telephony

    ------------------------------
    Dean Thames
    Koch Business Solutions
    ------------------------------


  • 2.  RE: Polycom VVX 401 Registration / PureCloud Provisioning / DHCP

    Posted 08-02-2019 08:40
    If you browse to phonediscovery.mypurecloud.com, what should be seen? I'm getting a 404 back... I suppose that could be normal but not sure: 

    {
    • status: 404,
    • code: "not found",
    • message: "HTTP 404 Not Found",
    • contextId: "a947f76c-24b7-42b4-90f9-c7971858ccbc",
    • details: [ ],
    • errors: [ ]
    }

    ------------------------------
    Dean Thames
    Koch Business Solutions
    ------------------------------



  • 3.  RE: Polycom VVX 401 Registration / PureCloud Provisioning / DHCP

    Posted 08-02-2019 11:16
    Dean,

    First, i assume you are a US East PureCloud Org as that phone discovery URL for US Phones.  

    In case you are not a US East Org, here are the other provisioning URLS:
    Region Phone Discovery Address
    US East http://phonediscovery.mypurecloud.com
    EU West http://phonediscovery.mypurecloud.ie
    EU Central http://phonediscovery.mypurecloud.de
    APNE http://phonediscovery.mypurecloud.jp
    APSE http://phonediscovery.mypurecloud.com.au

    Second, The Custom + Opt66 will prefer whatever DHCP option is defined as Custom Option (i.e. 161) and then fallback to DHCP option 66.  if only option 160 is defined in DHCP, then you may want to reset the phone to 160 (that is the Polycom default.  161 is not standard)

    If all else fails, you can format file system on your phone and it will default to Custom+Opt66 and restore any other non standard settings back to factory default.  there could be something in the Ethernet menu that is preventing you from getting a solid connection to the network.

    Also, i believe the polycom phones "USER AGENT" string includes the MAC address and the provisioning service uses that to respond with config files.  using a browser probably isnt supported.

    Thanks, and good luck!

    ------------------------------
    Joshua Davis
    Solution Engineer
    Altivon
    ------------------------------



  • 4.  RE: Polycom VVX 401 Registration / PureCloud Provisioning / DHCP

    Posted 08-02-2019 12:05
    Thanks Josh. Yes US East. That part is clear enough... and thanks for the clarification on Opt+66. 
    I was just browsing to the website to get a read on if it was accessible or not. Cisco and Avaya phones will tell you if the boot or provisioning server that it's trying to reach is unavailable, this phone doesn't really tell you anything. 
    At this point I'm going with a firewall issue on port 8061.
    Will update when I know more.

    ------------------------------
    Dean Thames
    Koch Business Solutions
    ------------------------------



  • 5.  RE: Polycom VVX 401 Registration / PureCloud Provisioning / DHCP

    Posted 08-21-2019 14:32
    So, this is, in fact firewall related. The issue is that we are seeing hard ip addresses come back instead of dns entries. For example, ec2 instances, not their dns entry. This causes our firewalls (palo alto) some heartburn. It's difficult to whitelist ip addresses....

    Has anyone worked through this?

    ------------------------------
    Dean Thames
    Koch Business Solutions
    ------------------------------



  • 6.  RE: Polycom VVX 401 Registration / PureCloud Provisioning / DHCP

    GENESYS
    Posted 08-21-2019 15:41
    I should not presume...

    Have you gone through this article in the Resource Center?

    https://help.mypurecloud.com/articles/purecloud-ports-services/

    ------------------------------
    George Ganahl GCP (PureCloud) ICCE CCXP
    Principal Technology Consultant
    Genesys
    ------------------------------



  • 7.  RE: Polycom VVX 401 Registration / PureCloud Provisioning / DHCP

    Posted 08-21-2019 16:17
    Yeah. We have the domains all whitelisted and we have the ip address json reference. 
    Issue is that after you get to the url that's whistled ... the provisioning one, you get directed to an ip address that doesn't have a domain attached to it that starts trying to pass out the logs and whatnot. And that ip address in turn refers the phone client to another ip address that's often different from the ip url: 

    snip 1
    What my security guy is looking for would be an ip address with a domain on it, like so: 

    snip 2






    ------------------------------
    Dean Thames
    Koch Business Solutions
    ------------------------------



  • 8.  RE: Polycom VVX 401 Registration / PureCloud Provisioning / DHCP

    Posted 09-06-2019 09:25
    Ok... I was able to negotiate a peace agreement with my sec ops guys. They're really down on the aws whitelist for port 80, but we agreed to lock the policy down to the specific vlan that the phones will be on (not everyone who uses aws is a good actor, btw...). 

    Things are working except for the dag-gum sntp override on the polycom. The phone won't register unless it has the correct time, but the settings file keeps reverting back to override the sntp server that it picks up in dhcp option 42. We use our own, so the phone doesn't have access to the time.windows.com alternate address. 

    Grrr... is there a way to set this override to false in dhcp? I can do it manually, but that's no way to do a deployment for 50 folks in a foreign land. 

    sntp


    ------------------------------
    Dean Thames
    Koch Business Solutions
    ------------------------------



Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources