I resolved a problem for which I had made an earlier posting and wanted to share this with the forum. I had a problem with a small percentage of my IP phones not getting an IP address when using DHCP. New phones would not register but once a phone had been manually configured and had attached properly, I could configure it for DHCP and it would work. There were still a few exceptions to this. I had posted the following snippet from a debug:
DEBUG IP DHCP SERVER PACKET
Jan 17 13:49:58.086: DHCPD: BOOTREQUEST from 0100.06d7.aa8a.06 forwarded to 10.10.125.10.
Jan 17 13:49:58.170: DHCPD: forwarding BOOTREPLY to client 0006.d7aa.8a06.
Jan 17 13:49:58.170: DHCPD: broadcasting BOOTREPLY to client 0006.d7aa.8a06.
Jan 17 13:50:14.087: DHCPD: setting giaddr to 10.10.95.1.
This morning I viewed the output of the SHOW IP INTERFACE command on the local router and I noticed the broadcast address of the VLAN on the trunk was not set to 255.255.255.255. I changed the IP BROADCAST-ADDRESS and all of my problem phones came up. I power-cycled the 3524 switch and all of the IP phones attached promptly.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...