Cisco IOS Voice Troubleshooting and Monitoring -- H.323 Gateway-to-Gateway and Gatekeeper-to-Gateway Security - Revision history

Pzimmerm: added metadata

2012-10-16T17:13:53Z

added metadata

← Older revision		Revision as of 17:13, 16 October 2012
Line 1:		Line 1:
	{{Template:Required Metadata}}		{{Template:Required Metadata}}
		+	<meta name="keywords" content="h323 security, voice, IOS, troubleshooting"></meta>

	{\| align="right" border="1"		{\| align="right" border="1"

Pzimmerm: Added required metadata template

2009-12-17T23:51:17Z

Added required metadata template

← Older revision		Revision as of 23:51, 17 December 2009
Line 1:		Line 1:
		+	{{Template:Required Metadata}}
		+
	{\| align="right" border="1"		{\| align="right" border="1"
	\|align="center"\|'''Guide Contents'''		\|align="center"\|'''Guide Contents'''

Pzimmerm at 22:52, 5 March 2009

2009-03-05T22:52:26Z

← Older revision		Revision as of 22:52, 5 March 2009
Line 1:		Line 1:
-
	{\| align="right" border="1"		{\| align="right" border="1"
	\|align="center"\|'''Guide Contents'''		\|align="center"\|'''Guide Contents'''
Line 9:		Line 8:
	* Intradomain Gateway to Gatekeeper Security -This security is based on H.235, in which H.323 calls are authenticated, authorized, and routed by a gatekeeper. The gatekeeper is considered a known and trusted entity. The gateway does not authenticate it when the gateway tries to register with it.		* Intradomain Gateway to Gatekeeper Security -This security is based on H.235, in which H.323 calls are authenticated, authorized, and routed by a gatekeeper. The gatekeeper is considered a known and trusted entity. The gateway does not authenticate it when the gateway tries to register with it.
	* Interdomain Gatekeeper to Gatekeeper Security -This security covers authenticating and authorizing of H.323 calls between the administrative domains of Internet Telephone Service Providers (ITSPs) using InterZone Clear Token (IZCT). This document covers only the portion of a call where the terminating gatekeeper sends a token in its location confirmation (LCF) message so that it authenticates the answerCall Admission Request (ARQ). Location request (LRQ) validation is not included in this feature. LRQ validation is a feature scheduled for a future Cisco IOS release.		* Interdomain Gatekeeper to Gatekeeper Security -This security covers authenticating and authorizing of H.323 calls between the administrative domains of Internet Telephone Service Providers (ITSPs) using InterZone Clear Token (IZCT). This document covers only the portion of a call where the terminating gatekeeper sends a token in its location confirmation (LCF) message so that it authenticates the answerCall Admission Request (ARQ). Location request (LRQ) validation is not included in this feature. LRQ validation is a feature scheduled for a future Cisco IOS release.
-
-	~~[[Category:IOS Voice Troubleshooting]]~~
-	~~[[Category:H.323]]~~

Pzimmerm: 1 revision

2009-03-05T22:22:56Z

1 revision

← Older revision

Revision as of 22:22, 5 March 2009

Pzimmerm at 00:41, 3 March 2009

2009-03-03T00:41:17Z

New page

{| align="right" border="1"
|align="center"|'''Guide Contents'''
|-
|[[Cisco IOS Voice Troubleshooting and Monitoring Guide#Troubleshooting Cisco IOS Voice Overview|Troubleshooting Cisco IOS Voice Overview]] [[Cisco IOS Voice Troubleshooting and Monitoring Guide#Debug Command Output on Cisco IOS Voice Gateways|Debug Command Output on Cisco IOS Voice Gateways]] [[Cisco IOS Voice Troubleshooting and Monitoring Guide#Filtering Troubleshooting Output|Filtering Troubleshooting Output]] [[Cisco IOS Voice Troubleshooting and Monitoring Guide#Cisco VoIP Internal Error Codes|Cisco VoIP Internal Error Codes]] [[Cisco IOS Voice Troubleshooting and Monitoring Guide#Troubleshooting Cisco IOS Voice Telephony|Troubleshooting Cisco IOS Voice Telephony]] [[Cisco IOS Voice Troubleshooting and Monitoring Guide#Troubleshooting Cisco IOS Voice Protocols|Troubleshooting Cisco IOS Voice Protocols]] [[Cisco IOS Voice Troubleshooting and Monitoring Guide#Troubleshooting Cisco IOS Telephony Applications|Troubleshooting Cisco IOS Telephony Applications]] [[Cisco IOS Voice Troubleshooting and Monitoring Guide#Monitoring the Cisco IOS Voice Network|Monitoring the Cisco IOS Voice Network]] [[Cisco IOS Voice Troubleshooting and Monitoring Guide#Cause Codes and Debug Values|Cause Codes and Debug Values]]
|}

H.323 networks have different kinds of configurations and call flows. See the [http://www.cisco.com/en/US/partner/tech/tk1077/technologies_white_paper09186a0080094a01.shtml Cisco Gateway to Gatekeeper (H.235) and Gatekeeper to Gatekeeper (IZCT) Security Troubleshooting Guide, document 18729] to get information about the following features:
* Intradomain Gateway to Gatekeeper Security -This security is based on H.235, in which H.323 calls are authenticated, authorized, and routed by a gatekeeper. The gatekeeper is considered a known and trusted entity. The gateway does not authenticate it when the gateway tries to register with it.
* Interdomain Gatekeeper to Gatekeeper Security -This security covers authenticating and authorizing of H.323 calls between the administrative domains of Internet Telephone Service Providers (ITSPs) using InterZone Clear Token (IZCT). This document covers only the portion of a call where the terminating gatekeeper sends a token in its location confirmation (LCF) message so that it authenticates the answerCall Admission Request (ARQ). Location request (LRQ) validation is not included in this feature. LRQ validation is a feature scheduled for a future Cisco IOS release.

[[Category:IOS Voice Troubleshooting]]
[[Category:H.323]]