Cisco WS-X4604-GWY - VoIP Gateway Especificaciones descargar pdf (Pagina 100)

Chapter 4 Gateway Selection

Cisco CallManager Redundancy

4-6

Cisco IP Telephony Network Design Guide

78-11103-03

The following example shows the configuration for H.323 gateway failover:

interface Loopback0

ip address 1.1.1.1 255.255.255.0

voip-gateway voip bind srcaddr 1.1.1.1

dial-peer voice 101 voip

destination-pattern 1111

session target ipv4:10.1.1.101

preference 0

voice class h323 1

dial-peer voice 102 voip

destination-pattern 1111

session target ipv4:10.1.1.102

preference 1

voice class h323 1

h225 timeout tcp establish 3

Note To simplify troubleshooting and firewall configurations, Cisco

recommends that you use the new

voip-gateway voip bind srcaddr

command for forcing H.323 always to use a specific source IP

address in call setup. Without this command, the source address used

in the setup might vary depending on protocol (RAS, H.225, H.245

or RTP).

MGCP Gateway

Adding MGCP to the VG200 and Cisco CallManager allows this standalone

gateway to switch over to a secondary Cisco CallManager in the event

communication is lost with the primary Cisco CallManager. Within the VG200

configuration file, the primary Cisco CallManager is identified using the

call-agent hostname command, and a list of secondary Cisco CallManager

systems is added using the ccm-manager redundant-host command. Keepalives

with the actively associated Cisco CallManager are accomplished through the

MGCP application-level keepalive mechanism, whereby the gateway sends an

empty MGCP NTFY message to the Cisco CallManager and waits for an

acknowledgement. Keepalive with the backup Cisco CallManager(s) is

accomplished through the TCP keepalive mechanism (UDP will be used in a later

version).

1 2 ... 95 96 97 98 99 100 101 102 103 104 105 ... 261 262

Sin comentarios

Cisco WS-X4604-GWY - VoIP Gateway Especificaciones Pagina 100