Cisco Systems 30 VIP manual Cisco CallManager Registration Process

Page 57

Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)

routing the call to a Cisco IP Phone located in Cluster 1, then the following messages would help you find the cause of the problem.

16:02:51.671 CCMRouteGroup - DeviceName=’’172.16.70.245’’

16:02:51.671 CCMRouteGroup -AllPorts

Part of the initialization process shows that Cisco CallManager is adding “Dns” (Directory Numbers). By reviewing these messages, you can determine whether the Cisco CallManager has read the directory number from the database.

16:02:51.671 CCMNodeId: 1, EventId: 1540 EventClass: 2 EventInfo: Call control started

16:02:51.843 CCMProcessDb - Dn = 2XXX, Line = 0, Display = , RouteThisPattern, NetworkLocation = OffNet, DigitDiscardingInstruction = 1, WhereClause =

16:02:51.859 CCMDigit analysis: Add local pattern 2XXX , PID: 1,80,1 16:02:51.859 CCMForwardManager - Started

16:02:51.984 CCMCallParkManager - Started 16:02:52.046 CCMConferenceManager - Started

In the following traces the Device Manager in Cisco CallManager is statically initializing two devices. The device with IP address 172.17.70.226 is a Gatekeeper and the device with IP address 172.17.70.245 is another Cisco CallManager in a different cluster. That

Cisco CallManager is registered as an H.323 Gateway with this Cisco CallManager.

16:02:52.250 CCMDeviceManager: Statically Initializing Device; DeviceName=172.16.70.226

16:02:52.250 CCMDeviceManager: Statically Initializing Device; DeviceName=172.16.70.245

Cisco CallManager Registration Process

Another important part of the SDI trace is the registration process. When a device is powered up, it gets information via DHCP, connects to the TFTP server for its .cnf file, and then connects to the Cisco CallManager specified in the .cnf file. The device could be an MGCP Gateway, a Skinny Gateway, or a Cisco IP Phone. Therefore, it is important to be able to discover whether or not devices have successfully registered on the Cisco AVVID network.

In the following trace, Cisco CallManager has received new connections for registration. The registering devices are “MTP_nsa-cm1” (MTP services on CCM1), and “CFB_nsa-cm1” (Conference Bridge service on CCM1). These are software services running on

Cisco CallManager but are treated internally as different external services and are therefore assigned a TCPHandle, socket number, and port number as well as a device name.

16:02:52.750 CCMStationInit - New connection accepted. DeviceName=, TCPHandle=0x4fbaa00, Socket=0x594, IPAddr=172.16.70.228, Port=3279, StationD=[0,0,0]

16:02:52.750 CCMStationInit - New connection accepted. DeviceName=, TCPHandle=0x4fe05e8, Socket=0x59c, IPAddr=172.16.70.228, Port=3280, StationD=[0,0,0]

16:02:52.781 CCMStationInit - Processing StationReg. regCount: 1 DeviceName=MTP_nsa-cm1, TCPHandle=0x4fbaa00, Socket=0x594, IPAddr=172.16.70.228, Port=3279, StationD=[1,45,2] 16:02:52.781 CCMStationInit - Processing StationReg. regCount: 1 DeviceName=CFB_nsa-cm1, TCPHandle=0x4fe05e8, Socket=0x59c, IPAddr=172.16.70.228, Port=3280, StationD=[1,96,2]

© 2000 Cisco Systems, Inc.

57

Page 56 Page 58
Image 57
Page 56 Page 58
Contents SDI Trace Output Configuring Traces Reorder Tone Through Gateways Gateway Registration Problems Page Purpose Documentation Checklist Channel Calling Search Space CCAPi Acronym/Term Cnf Law mu-lawCisco IOS Cluster Codec ChannelFlow Full duplex 711 729 225 245 323 Half Duplex Hookflash Jitter Law mu-lawPartition 931 Route Filter Route Group Route List Route PatternSilence Suppression Voice Activation Detection Voice Activation Detection Silence Suppression VoIP Translation PatternCisco CallManager Administration Details View Report Microsoft PerformanceMicrosoft Event Viewer SDI Trace Configuring Traces SDL Trace Page SDLTraceDataFlag Value SDLTraceTypeFlag Value DefinitionCall Detail Records CDR and Call Management Records CMR Sniffer TraceSelect Service Service Parameters CDRs Voice Quality Problem CategoriesPage Packet Number Time absolute ms Time delta ms Button Help John Check Your Loads Phone Resets Dropped Calls Page Page Cisco CallManager Feature Issues Locations Conf Bridge Region1 Region2 MTP Resource Problems MTP Dial Plans Dialing DOES-NOT-EXIST Page DialPlanWizardG Clause NamePattern Device Name Device Description Usage Pattern PartitionReorder Tone Through Gateways Slow Server ResponseGateway Registration Problems Module.port CFG Booting Dhcp for dynamic configurationTracyclose mod port tracystart mod port TaskID Cmd show dhcp Gmsg ***TFTP Error File Not Found Gmsg CCM#0 CPEvent = Loadid -- CPState = LoadResponse Gatekeeper ProblemsRegistration Rejects RRJ Cisco IP Phone Initialization Process Sample TopologyPage Skinny Station Registration Process Message Description Station Register Station ResetStation IP Port AcknowledgePage Cisco CallManager Initialization Process Self-Starting Processes Cisco CallManager Registration Process Cisco CallManager KeepAlive Process Cisco CallManager Intra-Cluster Call Flow Traces Cisco Systems, Inc CCMStationD stationOutputStopTone tcpHandle=0x4fbbc30 Cisco Systems, Inc Call Flow Traces Page Cisco Systems, Inc Following debug messages show that the call is in progress Gatekeeper Endpoint Registration Debug Messages and Show Commands on the Cisco IOS GatewayCisco Systems, Inc Page Cisco IOS Gateway with T1/PRI Interface Cisco IOS Gateway with T1/CAS Interface Cisco Systems, Inc Inter-Cluster H.323 Communication Call Flow Traces Failed Call Flow Cisco Systems, Inc Reading Records Writing RecordsRemoving Records Table SchemaFields in a Call Detail Record Known IssuesDeciphering the Time Stamp Origination leg call identifier Global Call IdentifierDate/time of call origination Originator’s node IDCalling party cause Of call termination Isdn location valueIP address for the originator’s media connection Port for the originator’s media connectionIP address to which the call was delivered unsigned integer Destination span or portIP port to which the call was delivered Called party’s partitionCodec type used by the destination on sending side IP address for the destination outgoing media connectionDate/time of connect Date/time of disconnect unsigned integerCisco CallManager node identifier Global Call Identifier for this callCall Identifier Directory number used on this callLost RTP packets during this connection Interarrival jitter during this connectionLatency experienced during this connection Normal Calls Cisco IP Phone-to-Cisco IP Phone Call Management Records Logged By Call Type Codec Cause Codes Description Codec Types Compression / Payload typesNumber changed Alarms Calling Cisco Technical Assistance Center TAC Index Debug messages and show commands Page Topology

30 VIP specifications

Cisco Systems has been a leading company in networking technology, and its suite of products is continually evolving to meet the demands of modern digital infrastructure. One of the latest introductions is the Cisco Systems 30 VIP, a highly advanced solution designed to enhance network performance and security for businesses of all sizes.

The Cisco Systems 30 VIP stands as a cornerstone for next-generation networking features, providing organizations with significant advantages in speed, reliability, and scalability. At the heart of the 30 VIP are key technologies such as advanced routing protocols and enhanced security measures that ensure seamless data transfer across multiple devices.

Main features of the Cisco Systems 30 VIP include its high throughput capabilities, which support accelerated data processing and lower latency. This is crucial for businesses that rely on real-time data exchange and cloud applications. Additionally, the device incorporates Multi-Protocol Label Switching (MPLS) technology, which optimizes data flow between networks and significantly enhances overall performance.

Another notable characteristic of the 30 VIP is its integrated security features, including advanced threat detection and prevention systems. These are designed to protect sensitive business data from cyber threats, ensuring operational continuity and compliance with industry regulations. The Cisco 30 VIP also supports secure access protocols, allowing for secure remote connections, which is increasingly vital in today’s hybrid work environment.

The adaptability of the Cisco Systems 30 VIP is another of its standout aspects. It offers compatibility with existing Cisco infrastructure, making it easier for businesses to adopt new technologies without overhauling their entire system. This modular approach allows for easy upgrades and integration of future technologies, ensuring long-term viability and investment protection.

Furthermore, the Cisco Systems 30 VIP is powered by intelligent network management software that simplifies monitoring, configuration, and troubleshooting processes. This software enhances network visibility, allowing administrators to identify and address potential issues proactively, thereby reducing downtime and enhancing user experience.

In summary, the Cisco Systems 30 VIP represents a significant advancement in network technology with its high throughput, integrated security features, adaptability, and intelligent management capabilities. These elements combine to provide a robust solution that meets the evolving needs of modern businesses while ensuring secure and efficient operations. As organizations continue to navigate an increasingly complex digital landscape, the Cisco Systems 30 VIP offers a future-proof option designed to facilitate growth and resilience.
Top Page Image Contents