Cisco 7920 Configuration Utility
Cisco’s ACU Client Utility (CCU) software has a series of commands for configuring and managing the Cisco 7920. The CCU communicates with the Cisco 7920 to retrieve a list of available services. The CCU can be downloaded from the Web site at the address
It is recommended to download the latest version of the CCU software. The CCU has a standard set of commands that the administrator can use to configure the phone. If your access point, remote access server or voice over IP (VoIP) phone uses a non-standard configuration, then you may need to contact your VoIP service provider for the standard configuration.
When the CCU is installed on the Cisco 7920, it does not replace the phoneâ€™s default configuration or network settings. If your ACU installation does not appear to be working correctly, follow the instructions for troubleshooting in the 7920 Reference Manual.
â€¢ Access Point: This displays the access point’s current configuration.
â€¢ Security: This displays the security settings that the access point has on different ports.
â€¢ Services: This displays the current services enabled on the access point.
â€¢ Users: This displays all users on the access point.
â€¢ Wireless Network: This shows the wireless network device and the wireless network encryption settings.
â€¢ Wireless Network Security: This displays the authentication and encryption settings for the wireless network.
â€¢ Security Settings: This displays the specific security settings for the access point’s wireless network security.
â€¢ Wireless Network Information: This displays the wireless network information for the access point’s wireless network.
â€¢ Basic Information: This displays the access point basic information such as the SSID, encryption type, and antenna.
â€¢ Wireless Network Information: This displays the wireless network information for the access point.
â€¢ Configuration Status: This displays the access point configuration status.
If the phone is connected to the access point, you can use the command to download and display a list of all or some of the remote services provided by the access point.
If the phone is not
no. 10 Cisco 7920 Wireless Communications Services, ip 15 ip ip
â€¢ Wireless Foundations for Businessâ€“Voice Solutionsâ€“Combining Voice and Wi-Fiâ€“Developing the Network for the New Business Environmentâ€“Systemâ€™s Connectivity Capabilitiesâ€“New Business Models for Voice and Video Deliveryâ€“The Future of Telephony and Mobility.
Ethernet switch 102 contains four component cards 102_1â€“102_4. These component cards (102_1â€“102_4) have a maximum of two ports on each card. For example, if component card 102_1 has ports P1â€“P2, then port P1 is the Ethernetâ€“MAC address component card port, and port P2 is the MAC address component card DTE port.
Simultaneously, if a second component card 102_5 has ports P3â€“P4, then port P3 is the Ethernetâ€“MAC address component card port, and port P4 is the MAC address component card DTE port. In the above-described example, port P1 and port P2 are component card ports P1 and P2, and port P3 and port P4 are component card ports P3 and P4.
Also, a computer having ports PC1â€“PCn may have a component card with multiple ports. For example, if component card 102_1 has ports P1â€“P2, then port P1 is the Ethernet port of the computer. If component card 102_5 has ports P3â€“P4, then port P3 is the Ethernet port of the computer. If the computer has ports PC1â€“PCn, then ports PC1â€“PCn are ports of the computer.
Also, the computer port PC1 may also be a component card port PC1. Or the computer
This is a quasi-dupe of this question. Based on the links there, I’ll update the following.
Your operating system is CentOS 5.4 (released 2008-06-26), so this is the latest version of CentOS supported by the OP, which is irrelevant, I suppose.
If this question is migrated to ServerFault, please ping me.
This is not a fully vetted solution, there may be holes.
Copy from this question:
The information available from the support site is not entirely consistent with the information in the FAQs. I think I have my “working” solution, but I’d like to hear what others think…
Using a traceroute command, I used the following output to determine that I was on the right path.
[root@localhost ~]# traceroute ipv4.opennic.net
traceroute to ipv4.opennic.net (184.108.40.206), 30 hops max, 60 byte packets
1 220.127.116.11 (18.104.22.168) 0.714 ms 0.612 ms 0.581 ms
2 22.214.171.124 (126.96.36.199) 0.778 ms 0.652 ms 0.670 ms
3 188.8.131.52 (184.108.40.206) 0.721 ms 0.702 ms 0.734 ms
4 220.127.116.11 (18.104.22.168) 0.723 ms 0.709 ms 0.729 ms
5 22.214.171.124 (126.96.36.199) 0.782 ms 0.724 ms 0.735 ms
6 188.8.131.52 (184.108.40.206) 0.762 ms 0.731 ms 0.754 ms
7 * * *
Thanks to Zoredache, I discovered that “* * *” means “it works”. Since I’m not getting any responses for the rest of the network, it appears that 220.127.116.11 is the gateway for the rest of the network.
Next, a few traceroutes on that IP address yielded the following.
[root@localhost ~]# tracer