Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Configure Cisco 2801 H.323 gateway on CM5 network

Status
Not open for further replies.

r1214

Technical User
Jun 2, 2009
5
US
I have a Callmanager 5 based VoIP deployment that is about 99% complete with about 15 locations. Each of these sites sits in a couple of local calling areas and utilize 4 PRI trunks for all inbound/outbound calls (all sites connected via Metro Ethernet LAN or private fiber network). Each site has a 2800 series router with FXO card and configured as a basic MGCP gateway for handling 911 calls out the local office so 911 service gets the correct physical address of that office. Other than that, I don't have much experience setting up voice gateways using FXO. I have this one remaining office which is on the MetroE LAN and can get to our PRI gateways, but their local calling area is outside of the other groups and uses a small-town Telco, so they can't route their local calls to our PRI gateways (and their local public number needs to remain the same and tied to that Telco). So, I put two 4-port FXO cards in their 2801 to handle their 6 POTs lines, and set it up as a MGCP gateway. Then I discovered inbound caller-ID doesn't work with MGCP gateways and FXO ports and that you need to setup as a H.323 gateway. I would love to see some sample configs on how to go about doing this.

The only outbound calls on these FXO ports will be the ones with a dial pattern 9846xxxx, which is their local prefix, and of course 9911 for 911 calls. Everything else should route out our PRI gateways. I have made the necessary route patterns in Call Manager and will point the 9846xxxx to the H323 gateway I setup in CM as well. I'm just not sure how to setup the H323 stuff in IOS on the router or create the appropriate dial peers for inbound calls coming to the POTs/FXO ports at the local site.

Any help greatly appreciated. This is the first time I believe I have posted (at least on this username, lost my username before and only posted once) but have used Tek-Tips many many times to gain lots of useful answers to other problems! thanks
 
place your voice-ports in a trunk group, and setup dial-peers
for starters... Do you need config examples for router and Call Manager?



[americanflag] Go Army!
Tek-TIP Member 19,650
 
Yes that would be very helpful, thank you. At the moment I can't even get the router to show up as status registered in Call Manager under the Gateways list. I set it up as a H323 instead of typical "2801 -> MGCP" and then put the IP address of the router as the name. Next I added these statements that I found in some other posts on the Net

voice class h323 1
h225 timeout tcp establish 3
!
interface FastEthernet0/1.2 <-- this is my voice vlan int
encapsulation dot1Q 2
ip address 172.25.199.254 255.255.255.0
h323-gateway voip interface
h323-gateway voip bind srcaddr 172.25.199.254 <-- IP I put in CM
!
!
dial-peer voice 3000 voip
preference 1
destination-pattern 168.
progress_ind setup enable 3
progress_ind progress enable 8
voice-class h323 1
session target ipv4:172.25.2.11 <--- my subscriber
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 3001 voip
preference 2
destination-pattern 168.
progress_ind setup enable 3
progress_ind progress enable 8
voice-class h323 1
session target ipv4:172.25.2.10 <-- publisher
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
 
You won't see the router registered wit ccm if using h323. With h323 protocol ccm has no control over the router so it will not register. It is a peer to peer relation as opposed to MGCP where the call manager is the master and the router the servant.
 
Ahh okay, I did not realize that. Jeter, do you have any sample configs I could play with based on what I'm trying to accomplish? thanks for both of your help, I really appreciate it.
 
I can post one tomorrow.


[americanflag] Go Army!
Tek-TIP Member 19,650
 
Thanks Jeter- that would be greatly appreciated
 
Here are few dial peers that examples of calls going out a PRI... Your port will be setup for a trunk group or individual voice-ports

dial-peer voice 100 pots
description ****Local Calls****
destination-pattern 9[2-9]......
port 0/1/0:23
forward-digits 7
!
!
dial-peer voice 101 pots
description Long Distance
destination-pattern 91[2-9].........
port 0/1/0:23
forward-digits 11
!
dial-peer voice 103 pots
description 9911
destination-pattern 9911
port 0/1/0:23
forward-digits 3
!
dial-peer voice 104 pots
description 911
destination-pattern 911
port 0/1/0:23
forward-digits all
!
dial-peer voice 102 pots
description 011 International
destination-pattern 9011T
port 0/1/0:23
forward-digits 0
!
dial-peer voice 105 pots
description 118 Time and Temp
destination-pattern 118
port 0/1/0:23
forward-digits all
!
dial-peer voice 177 pots
incoming called-number .
direct-inward-dial
!


[americanflag] Go Army!
Tek-TIP Member 19,650
 
Thanks Jeter. I ended up having to get some additional help from a local Cisco resource but the system is up and running. I was *real* close to having it going based on your help and what I'd found in other forums. Here is the router config I ended up with (at least the pertinent items) in case it could help anyone else:

!
!
trunk group AnalogFXOPorts
!
voice-card 0
!
voice class h323 1
h225 timeout tcp establish 3
!
!
!
interface FastEthernet0/0
description "Connected to MetroEthernet LAN"
ip address 172.25.100.199 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/1
description "Connected to POE switch"
no ip address
duplex auto
speed auto
!
interface FastEthernet0/1.1
description "Data VLAN"
encapsulation dot1Q 1 native
ip address 172.16.199.254 255.255.255.0
ip helper-address 172.16.10.5
!
interface FastEthernet0/1.2
description "Voice VLAN"
encapsulation dot1Q 2
ip address 172.25.199.254 255.255.255.0
h323-gateway voip interface
h323-gateway voip bind srcaddr 172.25.199.254 <-- bind H323 to Voice VLAN IP
!
!
!
voice-port 0/0/0
trunk-group AnalogFXOPorts 6 <--the # sets preference. I wanted outbound calls to start on port 0/1/1
timing hookflash-out 50
connection plar opx 8853 <-- points to CTI Route Point DN in CM that fwds to a Unity auto attendant
caller-id enable
!
voice-port 0/0/1
trunk-group AnalogFXOPorts 5
timing hookflash-out 50
connection plar opx 8853
caller-id enable
!
voice-port 0/0/2
trunk-group AnalogFXOPorts 4
timing hookflash-out 50
connection plar opx 8853
caller-id enable
!
voice-port 0/0/3
trunk-group AnalogFXOPorts 3
timing hookflash-out 50
connection plar opx 8853
caller-id enable
!
voice-port 0/1/0
trunk-group AnalogFXOPorts 2
timing hookflash-out 50
connection plar opx 8853
caller-id enable
!
voice-port 0/1/1
trunk-group AnalogFXOPorts 1
timing hookflash-out 50
connection plar opx 8853
caller-id enable
!
voice-port 0/1/2
timing hookflash-out 50
shutdown
!
voice-port 0/1/3
timing hookflash-out 50
shutdown
!
!
!
dial-peer voice 301 pots
trunkgroup AnalogFXOPorts
destination-pattern 9[2-9]......
no digit-strip
forward-digits 7
!
dial-peer voice 302 pots
trunkgroup AnalogFXOPorts
destination-pattern 9[2-9]..[2-9]......
no digit-strip
forward-digits 10
!
dial-peer voice 303 pots
trunkgroup AnalogFXOPorts
destination-pattern 91[2-9].........
no digit-strip
forward-digits 11
!
dial-peer voice 305 pots
trunkgroup AnalogFXOPorts
destination-pattern 9911
no digit-strip
forward-digits 3
!
dial-peer voice 306 pots
trunkgroup AnalogFXOPorts
destination-pattern 90
no digit-strip
forward-digits 1
!
dial-peer voice 307 pots
trunkgroup AnalogFXOPorts
destination-pattern 91411
no digit-strip
forward-digits 4
!
dial-peer voice 308 pots
trunkgroup AnalogFXOPorts
destination-pattern 91611
no digit-strip
forward-digits 4
!
dial-peer voice 3000 voip
preference 1
destination-pattern [1-8]...
progress_ind setup enable 3
progress_ind progress enable 8
voice-class h323 1
session target ipv4:172.25.2.11 <-- CM subscriber
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 3001 voip
preference 2
destination-pattern [1-8]...
progress_ind setup enable 3
progress_ind progress enable 8
voice-class h323 1
session target ipv4:172.25.2.10 <-- CM publisher
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
!
!
call-manager-fallback
secondary-dialtone 9
max-conferences 8 gain -6
transfer-system full-consult
ip source-address 172.25.199.254 port 2000
max-ephones 30
max-dn 150
default-destination 1685
alias 1 8853 to 1685 <-- this was important to allow calls to make it to a front desk phone DN while in SRST mode when the newtork connection was down
!
!
!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top