Cisco Signaling Controllers

telnet  hsi1
SunOS 5.8

login: mgcusr
Password: ***
Sun Microsystems Inc.   SunOS 5.8       Generic February 2000
mgcusr@hsi1% mml
Connecting to port 10129 on host hsi1


Welcome to the GoldWing H323 Signalling Gateway.

gw mml> prov-sta:srcver="active",dstver="test15"
   H323 Signalling Gateway   Sat Jul 24 14:21:31 2004
M  SUCC

Successfully started provisioning session "test15" from "active".
Note: This provisioning session has not been verified.

gw mml> prov-add:name=SYS_CONFIG_STATIC, RaiSupported=enabled
   H323 Signalling Gateway   Sat Jul 24 14:21:46 2004
M  SUCC

Successfully added provisioning element(s):
MML Name :    SYS_CONFIG_STATIC.
Parameter:    RaiSupported.
Value    :    enabled.

gw mml> prov-cpy
   H323 Signalling Gateway   Sat Jul 24 14:22:10 2004
M  SUCC

Successfully activated provisioning session test15.

gw mml> quit

Exiting GoldWing MML.
mgcusr@hsi1% 

!--- Issue this command in order to restart the application 
!--- under directory/etc/init.d: 


# ./CiscoGW stop
Signalling PMmain to shut down
Signalling GWmain[27287] to shut down
Process 'PMmain' not found
Process 'GWmain' not found
...shutdown complete
# ./CiscoGW start

Application started
# 


!--- You can run on the Cisco IOS® gatekeeper 
!--- the show gatekeeper gw-type-prefix command.

#show gatekeeper gw-type-prefix 

GATEWAY TYPE PREFIX TABLE
=========================
Prefix: 71*
  
  Zone cisco-1 master gateway list:
      10.48.84.180:1720 HSI01
		10.48.84.190:1720 HSI02 
		
If you see :
#show gatekeeper gw-type-prefix 
GATEWAY TYPE PREFIX TABLE
=========================

Prefix: 71*
  Zone cisco-1 master gateway list:
      10.48.84.180:1720 HSI01
		10.48.84.190:1720 HSI02 (out-of-resources)
		

!--- HSI, which plays the role of a H323 gateway, appears as 
!--- Out of Resources in the gatekeeper when HSI has sent 
!--- a RAI message to the Gatekeeper with a Resource Unavailable
!--- indication. This happens any time HSI cannot handle 
!--- calls for any reason: not all processes are started, 
!--- HSI goes to 100 percent CPU, faulty IP connectivity.

Capturing Cisco IOS debug Logs
!--- When you capture the logs that includes debugs on the Cisco IOS 
!--- gateway/gatekeeper, it is important to configure the router 
!--- such that timestamps are present on the logs and debugs. 
!--- Also, it is imperative that no logs get dropped. Logging 
!--- to the console can cause logs and/or debugs to get 
!--- discarded from the output. This configuration statements turn on
!--- log timestamps, and direct the log output to a buffer.

config terminal
   service timestamps debug datetime msec
	service timestamps log datetime msec
	no logging console
	logging buffer <Logging buffer size>
	debug
	end


!--- Turn on the Cisco IOS debug for H225 ASN
!---  on the Cisco Gatekeeper in order to check 
!--- that the feature works correctly.


Cisco_Gatekeeper#debug h225 asn1


!--- Run the Cisco IOS show debug command in order to check
!--- if the debug is activated. Before you make reproduce the problem, 
!--- make sure that you clear the log buffer.clear loggingReproduce 
!--- the problem.  You can do a commanding links IS/OOS 
!--- on the Cisco PGW2200 or command EISUP destinations 
!--- IS/OOS on the Cisco PGW2200 or physically remove or 
!--- re-plug IP links between Cisco HSI  and the Cisco PGW2200. 


H.225 ASN1 Messages debugging is on.


You can do a commanding links IS/OOS on the Cisco PGW2200 -or- 
command EISUP destinations IS/OOS on the Cisco PGW2200 -or- 
physically remove or re-plug IP links between Cisco HSI  and the Cisco PGW2200. 

!--- When the Cisco IOS debug  h225 asn1
!--- are activated on the Cisco Gatekeeper, you can run 
!--- the show log | include resourcesAvailable command to verify
!--- if the resourceAvailable message is logged on the gatekeeper 
!--- with the Cisco IOS logging buffered command.

Cisco_Gatekeeper#show log | include resourcesAvailable
Output of the Cisco Gatekeeper debug log information:

value RasMessage ::= resourcesAvailableIndicate: 
value RasMessage ::= resourcesAvailableConfirm: 


!--- If the ResourceAvailable message is available on 
!--- the Cisco Gatekeeper log, you can check 
!--- the content of this H225 debug message.


!--- The content of this debug message is:

<snip>
value RasMessage ::= resourcesAvailableIndicate: 
    {
      requestSeqNum 10103
      protocolIdentifier { 0 0 8 2250 0 4 }
      endpointIdentifier {"822C71A000000015"}
      protocols 
      {
      }
      almostOutOfResources TRUE
    }


14203224: Jul 12 10:25:54.095: RAS OUTGOING PDU ::=

value RasMessage ::= resourcesAvailableConfirm: 
    {
      requestSeqNum 10103
      protocolIdentifier { 0 0 8 2250 0 2 }
    }
<snip>

!--- Note: You do not see the logs since 
!--- logging to the console was turned off through the previous command. 
!--- But, the logs and debugs are captured in the 
!--- log buffer. In order o see them, set the terminal length 
!--- to 0 and show the log buffer. If you set the terminal 
!--- length to 0, this causes the output to scroll continuously, 
!--- for example, without the --More-- prompt.

no debug all
terminal length 0
show logging