Thanks for the reply
I am afraid that the client is running some older firmware on the various
different SIP phone models.  Most are at version 11-5-1SR1-1
As for Cisco documentation, it is becoming somewhat less useful as time
goes on.
My pet peeve is searching through Bug Search and finding nothing.  Then
involving TAC and being pointed to a Bug ID that should have shown in my
search.
Not sure if my search fu is bad or the Bug Search tool is "not helpful". (A
nice way of saying not worth shit).

Russell Goings (AM)
IPT Engineer – Dimension Data
Direct Line 571-203-4021
russell.goi...@dimensiondata.com
Monday – Friday 8:00 – 5:00 EST

On Fri, Apr 6, 2018 at 12:10 PM, Charles Goldsmith <wo...@justfamily.org>
wrote:

> Anthony, it doesn't help that the SRND is also lighter in terms of total
> number of pages than it used to be.  Back in the 8.x days, it was over 1400
> pages.  With all of the new technology and features added through to
> version 12.x, you would expect it to get larger, not smaller.
>
>
> On Fri, Apr 6, 2018 at 10:31 AM Anthony Holloway <
> avholloway+cisco-v...@gmail.com> wrote:
>
>> I'm a little surprised that the spec for DNS support is not well
>> documented.  It should be in the SRND.  Especially since DNS + Certificates
>> are more common place today.
>>
>> On Fri, Apr 6, 2018 at 9:03 AM Wes Sisk (wsisk) <ws...@cisco.com> wrote:
>>
>>> Looks like it was known broken at one point:
>>>
>>> The DNS Query Response TTL of the secondary DNS server is not being
>>> respected by the 9971/9951/8831 phones if the primary server goes down
>>> after the first request.
>>> Resolution Summary
>>> CSCut29536 for 8831 IP Phones
>>> CSCut29519 for 99xx IP Phones
>>> CSCut75647 for 8811/51 IP phones
>>>
>>> So versions and deeper dive required.
>>>
>>> -Wes
>>>
>>>
>>> On Apr 5, 2018, at 3:14 PM, Russell Goings <russgoi...@rgoings.com>
>>> wrote:
>>>
>>> Hi all
>>>    I have a client who was doing some network mucking around and part of
>>> that maintenance caused the two DNS servers used by a group of IP phones to
>>> go unavailable.  Some of these phones went unregistered with a reason code
>>> 13 - TCP KeepAlive Timeout.
>>>
>>> What I (OK not me.  Just the client.  Well maybe I am interested as
>>> well) would like to know is how do the Cisco SIP phones, particularly the
>>> 8851 model, deal with the TTL from the DNS response.
>>>
>>> Does the phone honor the DNS TTL and cache the response for 24 hours?
>>>
>>> Does the phone have a different cache time for the DNS response?
>>>
>>> Does it make a new DNS query every time it sends a keep-alive?
>>>
>>> I have never looked into this before and on this Thursday afternoon my
>>> Google-fu is weak.
>>>
>>> And the incident was over a week ago so not much from the phone logs to
>>> help.
>>>
>>> Thanks
>>>
>>> Russell Goings (AM)
>>> IPT Engineer – Dimension Data
>>> Direct Line 571-203-4021 <(571)%20203-4021>
>>> russell.goi...@dimensiondata.com
>>> Monday – Friday 8:00 – 5:00 EST
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip@puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip@puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to