[asterisk-users] Polycom UC 4.x Unreachable
gary.reuter at gmail.com
Thu Aug 24 23:42:45 CDT 2017
Turns out UCS Polycoms are quite picky about blank callerids, to the
extant they ignore those packets completely.
My global "callerid=" in sip.conf was intentionally blank. In ten
years, in never caused a problem.
By setting to 0, the Polycoms that didn't respond to SIP OPTIONS (nor
the NOTIFY for waiting messages) now work fine.
If anyone is curious, the problem is easily reproduced in the dialplan
by setting the callerid there to blank, then the UCS polycom will
ignore that INVITE as well. Set the callerid to anything else and
On 23 August 2017 at 19:29, John Covici <covici at ccs.covici.com> wrote:
> I always set it to no, but set the registration time to 60 seconds,
> and that has always worked for me.
> On Wed, 23 Aug 2017 17:23:38 -0400,
> Gary Reuter wrote:
>> We've had dozens of Polycom 3.x firmware phones deployed and working
>> great for years.
>> Now I've finally been charged with the long-overdue task of figuring
>> out why newer Polycom devices with 4.x firmware register fine but do
>> not respond to SIP OPTIONS request and therefore always become
>> UNREACHABLE if the sip qualify setting is set to yes.
>> To my dismay, searches for solutions from others who have encountered
>> this problem have given zero results.
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> Check out the new Asterisk community forum at: https://community.asterisk.org/
>> New to Asterisk? Start here:
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
> Your life is like a penny. You're going to lose it. The question is:
> How do
> you spend it?
> John Covici
> covici at ccs.covici.com
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> Check out the new Asterisk community forum at: https://community.asterisk.org/
> New to Asterisk? Start here:
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
More information about the asterisk-users