Karl Stallknecht Posted October 31, 2016 Report Share Posted October 31, 2016 You're right about the NAPTR records not being supported on DNS Made Easy.I figured that between our own DNS and DNS Made Easy, the likelihood of specifically 2600hz's east coast proxy having an outage at the same time as our own DNS servers is pretty low so I just took a chance when setting it up. So technically speaking if our DNS servers go down then the NAPTR records won't work, but Polycoms at least will fall back to A records, which WILL be up via DNS Made Easy:http://support.polycom.com/global/documents/support/technical/products/voice/SIP_Server_Fallback_TB5...(see page 5)If other phones such as Yealinks or Cisco don't fail back to A records then that would cause a problem of course. And if 2600hz's east coast proxy went down when our DNS was also down, then it wouldn't fail over to central or west coast. But again, the likelihood is all of those things happening at once is pretty low.All of this being said, we aren't even using hostnames yet for any live clients. But once we get transitioned to Monster then what I have mentioned above will apply. Link to comment Share on other sites More sharing options...
esoare Posted November 2, 2016 Report Share Posted November 2, 2016 BLF issues again.... Ran a flush on a bunch of the presence...will see if it fixes it. Link to comment Share on other sites More sharing options...
Logicwrath Posted November 2, 2016 Report Share Posted November 2, 2016 Are you using Yealink? Did you have the Out Dialog BLF set to enabled on the handsets? Were the presence value for users/lines or were they for "Call Park" DSS Keys? Link to comment Share on other sites More sharing options...
Recommended Posts