
Neighbored Cisco IOS and Polycom CMA Gatekeepers
Polycom, Inc. 71
!
! - One network interface (Ethernet or Loopback) must be designated as the source interface.
! - This ensures that all H.323 gatekeeper traffic originates from the same address
! - for each call.
!
interface FastEthernet0/1
ip address 10.232.253.253 255.255.255.0
h323-gateway voip interface
h323-gateway voip bind srcaddr 10.232.253.253
!
!
! - The command "gatekeeper" puts the router into GK configuration mode
!
gatekeeper
!
! - The first local zone created must contain the IP address of the network interface on the
! - IOS device to which H.323 has been bound. This establishes the address of the gatekeeper.
! - The zone name and domain name are requirements for each zone to help the GK manage
! - endpoint registrations properly. The "enabled-intrazone" is required to allows devices in
! - each zone to call each other. The remote zone must use the IP Address of the CMA as
! - that is the point to which all Polycom devices attach.
!
zone local cucm company.com enable-intrazone
zone remote video company.com 192.168.51.1 1719
!
! - Zone prefixes are required to properly route calls into CUCM as CUCM does not register
! - E.164 prefixes or extensions. Therefore, by adding a zone prefix, we are telling the GK that
! - any Call Admission Request (ARQ) looking for an extension starting with 1,and is x digits
! - long, gets routed to the CUCM zone, and eventually the CUCM itself. A "*" represents a
! - multiple digit wildcard match (i.e. 123456). The use of the "*" is required
! - as the IOS GK uses this to route all cucm zone calls to the registered CUCM cluster.
!
zone prefix cucm 1*
zone prefix video 2*
!
! - The remote and zone session bandwidth should be be set (even in small environments)
! - to prevent potential overloading of the CUCM H.323 interface or other network segments.
!
bandwidth remote 5000
bandwidth session zone cucm 5000
!
!
Komentarze do niniejszej Instrukcji