Cisco Systems 30 VIP Message Description Station Register, Station Reset, Station IP Port, Date

Page 53

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

The primary messages in the Skinny Station registration process are described in the following table.

Skinny Station Registration Process Descriptions

Message

Description

Station Register

The station sends this message to announce its existence to the

 

controlling Cisco CallManager.

Station Reset

Cisco CallManager sends this message to command the station to reset

 

its processes.

Station IP Port

The station sends this message to provide Cisco CallManager with the

 

UDP port to be used with the RTP stream.

Station Register

Cisco CallManager sends this message to acknowledge the registration

Acknowledge

of a station.

Station Register Reject

Cisco CallManager sends this message to reject a registration attempt

 

from the indicated phone.

 

char text[StationMaxDisplayTextSize];

 

};

 

Where:

 

text is a character string, maximum length of 33 bytes, containing a

 

textual description of the reason that registration is rejected.

Station Capabilities

Cisco CallManager sends this message to request the current

Request

capabilities of the station. Station capabilities may include compression

 

standard and other H.323 capabilities.

Station Version Request

The station sends this message to request the version number of the

 

software load for the station.

Station Version Response

Cisco CallManager sends this message to inform the station of the

 

appropriate software version number.

Station Capabilities

The station sends this message to Cisco CallManager in response to a

Response

Station Capabilities Request. The station’s capabilities are cached in

 

the Cisco CallManager and used to negotiate terminal capabilities with

 

an H.323 compliant Terminal.

Station Button Template

The station sends this message to request the button template

Request

definition for that specific terminal or Cisco IP Phone.

Station Button Template

Cisco CallManager sends this message to update the button template

Response

information contained in the station.

Station Time Date Request

The station sends this message to request the current date and time for

 

internal usage and for displaying as a text string.

Station Define Time and

Cisco CallManager uses this message to provide the date and time

Date

information to the station. It provides time synchronization for the

 

stations.

Cisco IP Phone-to-Cisco IP Phone Call Flow within a Cluster

This section describes a Cisco IP Phone (directory number 1000) calling another Cisco IP Phone (directory number 1001) within the same cluster. The cluster is a group of Cisco CallManagers having one common Publisher SQL database and many Subscriber SQL databases.

In our sample topology, CCM1 is the publisher and CCM2 is a subscriber. The two

Cisco IP Phones (1000 and 1001) are registered to CCM1 and CCM2, respectively. The call flow is shown in the diagram below. The two Cisco CallManagers within a cluster communicate with each other using Intra-Cluster Control Protocol(ICCP). When a Cisco IP Phone goes off-hook , it opens a control Skinny Station session (with TCP as the underlying protocol) with the

Cisco CallManager. After call control signaling is established between the two Cisco IP Phones

© 2000 Cisco Systems, Inc.

53

Image 53
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 ChannelPartition Flow Full duplex 711 729 225 245 323 Half Duplex HookflashJitter Law mu-law Silence Suppression Voice Activation Detection 931Route Filter Route Group Route List Route Pattern 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 callLatency experienced during this connection Lost RTP packets during this connectionInterarrival jitter 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