01-13-2009 03:44 PM - edited 03-15-2019 03:29 PM
Below is the current config of the gateway a client's Call Manager 3.3 is connected to. I have a pending raid failure on the publisher, and want to ensure callers can still dial out and recive calls if the publisher fails completely and it is being rebuilt.
I am really rusty with gateways so please bear with me. If I add the following to the config of the gateway, will it be sufficient to ensure call processing if the publisher fails?:
dial-peer voice 20 voip
incoming called-number .
destination-pattern 3...
preference 1 <---Add
progress_ind setup enable 3
session target ipv4:10.1.24.24 <-----assumimg this is the Publisher's ip address
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 21 voip
incoming called-number .
destination-pattern 3...
preference 2 <---Add, higher value than that of the PUB
progress_ind setup enable 3
session target ipv4:10.1.24.25 <----assuming this is the Subscriber's s ip addess
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
Current Config of gateway:
Password:
PSTN_Gateway#sh run
Building configuration...
Current configuration : 2271 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname PSTN_Gateway
!
boot-start-marker
boot system flash c1700-ipvoice-mz.123-8.T.bin
boot-end-marker
!
enable secret 5 ************
tdm clock T1 0/0 both export line
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
voice-card 0
!
voice-card 1
!
voice-card 2
!
no aaa new-model
ip subnet-zero
ip cef
!
!
ip tcp synwait-time 5
!
!
no ip domain lookup
no ftp-server write-enable
isdn switch-type primary-ni
!
!
!
!
!
!
!
!
!
!
!
!
ccm-manager redundant-host 192.168.10.1
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 192.168.10.1
ccm-manager config
!
!
controller T1 0/0
framing esf
linecode b8zs
pri-group timeslots 1-24 service mgcp
!
!
!
interface FastEthernet0/0
ip address 192.168.10.4 255.255.255.0
speed auto
!
interface Serial0/0:23
no ip address
no logging event link-status
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.10.213
no ip http server
!
!
!
control-plane
!
!
!
voice-port 0/0:23
!
voice-port 1/0
timing hookflash-out 50
!
voice-port 1/1
timing hookflash-out 50
!
voice-port 2/0
timing hookflash-out 50
!
voice-port 2/1
timing hookflash-out 50
!
mgcp
mgcp call-agent 192.168.10.2 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp package-capability rtp-package
no mgcp package-capability res-package
mgcp package-capability sst-package
no mgcp package-capability fxr-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax t38 inhibit
mgcp rtp payload-type g726r16 static
!
mgcp profile default
!
!
!
dial-peer cor custom
!
!
!
dial-peer voice 10 pots
application mgcpapp
port 0/0:23
!
dial-peer voice 99910 pots
application mgcpapp
port 1/0
!
dial-peer voice 99911 pots
application mgcpapp
port 1/1
!
dial-peer voice 99920 pots
application mgcpapp
port 2/0
!
dial-peer voice 99921 pots
application mgcpapp
port 2/1
!
!
line con 0
line aux 0
line vty 0 4
01-13-2009 05:27 PM
u have done the right way by using tow voip dial-peer for same destination with diffrent session targets and perefrence
however, You might need to adjust the default timers when using multiple CallManagers, especially if the gateway has a PRI connection for inbound calls. When a call comes in that should be forwarded to a CallManager, the router attempts to set up an H.225 TCP session to its preferred VoIP dial peer. The TCP session must time out before it will try another dial peer. This takes 15 seconds by default. ISDN Q.931 has a Call Proceeding timeout of 10 seconds. A call that comes in over a PRI line will time out before the router can fail over to an alternate CallManager. Even without a PRI connection, 15 seconds might be longer than you want to wait
To remedy this, change the H.225 TCP session establishment timer. The voice class h323 10 command creates a voice class in global configuration mode that reduces the timer to three seconds
voice class h323 10
h225 timeout tcp establish 3
then apply it on ur dial-peer
dial-peer voice 20 voip
voice-class h323 10
dial-peer voice 21 voip
voice-class h323 10
good luck
if helpful Rate
01-13-2009 06:47 PM
Thank you very much for your help. I will be trying this in the bnext couple of days and will rate if successful!
01-13-2009 05:28 PM
Hi James,
The more pertinent part of your configuration is already there:
!
ccm-manager redundant-host 192.168.10.1
ccm-manager mgcp
This will allow your router to register via MGCP to the publisher. If for whatever reason the MGCP connection breaks, you could use H323 through the dial peer you have configured. You would want to add this command as well "ccm fallback-mgcp".
hth,
nick
01-13-2009 06:47 PM
Thanks, I will do that. Thanks Again!
01-15-2009 10:59 AM
Hi Nick,
Question:
if the currently configured dial peers are pots, how will adding the below affect the gateway, as I see in the current config, no incoming call numbers are listed in the current pots dial peers?
01-15-2009 11:27 AM
Your question doesn't really make any sense. Can you try re-wording?
-nick
01-15-2009 11:40 AM
Sorry, should have clarified more.
The change I was going to make was this:
dial-peer voice 20 voip
incoming called-number .
destination-pattern 3...
preference 1 <---Add
progress_ind setup enable 3
session target ipv4:10.1.24.24 <-----assumimg this is the Publisher's ip address
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 21 voip
incoming called-number .
destination-pattern 3...
preference 2 <---Add, higher value than that of the PUB
progress_ind setup enable 3
session target ipv4:10.1.24.25 <----assuming this is the Subscriber's s ip addess
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
In their current config, the dial peers are configured as follows:
dial-peer voice 10 pots
application mgcpapp
port 0/0:23
dial-peer voice 99910 pots
application mgcpapp
port 1/0
dial-peer voice 99911 pots
application mgcpapp
port 1/1
dial-peer voice 99920 pots
application mgcpapp
port 2/0
dial-peer voice 99921 pots
application mgcpapp
port 2/1
I was wondering if I added what I specified above, which calls for an incoming called number, how that would affect the current POTS dial peers, if at all, or am I misunderstanding what this means:
dial-peer voice 20 voip
incoming called-number .
destination-pattern 3...
preference 1 <---Add
progress_ind setup enable 3
session target ipv4:10.1.24.24 <-----assumimg this is the Publisher's ip address
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 21 voip
incoming called-number .
destination-pattern 3...
preference 2 <---Add, higher value than that of the PUB
progress_ind setup enable 3
session target ipv4:10.1.24.25 <----assuming this is the Subscriber's s ip addess
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
I have very little experience when it comes to CCM and gateways, so please forgive my
inexperience, thanks.
01-15-2009 12:33 PM
No problem.
It is impossible to match a voip dial peer when the call comes in on a pots circuit, and vice versa.
This link will help:
http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml
hth,
nick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide