02-21-2019 03:10 PM
Approximately 60 phones are operational on one switch stack; well over 2000 phones are deployed at multiple sites. We have a number of CP-79xx phones that will not register confirmed in CallManager (CM). To eliminate any DHCP problem IP addresses were reserved after registration failed with leased addresses. We are running Network Access Control. Questionable phones provide network connectivity for connected PCs confirmed by ARP tables, authenticated sessions showing PC MAC and IP addresses, response to ping and user functionality confirmation.
The phone instrument in some cases is assigned a DHCP IP address and in others seems to be assigned the reserved address; both cases are confirmed by the authenticated session showing the phone MAC and assigned IP as listed in the Cisco Network Regietrar (CNR) scope. There is the appropriate arp entry until it ages out, but no response to ping. In some cases CM list the IP address and Status as unregistered; in other cases the IP and Status are both "none". In all cases the IP address in the phone's Network Configuration is 255.255.255.255 (IPv4 global broadcast). All problem phones were reset to default configuration at least twice with the same individual results. Is the phone's IP address 255.255.255.255 sufficient to conclude that the audio processor is now defective or are there other tests ?
02-23-2019 05:13 AM
02-25-2019 09:32 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide