02-09-2011 08:47 PM - edited 03-16-2019 03:22 AM
We are currently running MGCP and plan to change to H.323 on some of our gateways so that we can TDM switch between PRI's using dial-peers. Can someone provide an example on how we can achieve the following:
PRI (telco) -----> Cisco 2811 ------> H.323 -----> CUCM
|
|
PRI (eFAX)
The behavior should be as follows:
1) For calls coming from the telco, route them to CUCM unless a dial-peer is identified that routes the call to the PRI (eFAX)
2) For calls coming in from CUCM, route them to the telco unless a dial-peer is identified that routes the call to PRI (eFAX)
Both CUCM and the telco dial-peers basically need to match all patterns because we have so many DID's on the phone system and they're constantly changing since we're a service provider.
Solved! Go to Solution.
02-10-2011 02:42 PM
Hey, great calls are working without any delay; and the conf looks fine too
Regards
Thomas
P.S. Please rate helpful posts
02-10-2011 01:25 AM
Hi Jordan,
This is possible if you have a set of very specific numbers for the Fax system. You would need to create the following for this to work.
The below dial-peer's are assuming the NANP(North American Numbering Plan)
Dial-Peer's
dial-peer voice 1 voip (Calls to G/W from CUCM)
incoming called-number .
direct-inward-dial
!
dial-peer voice 2 pots (Calls to G/W from Telco or FAX)
incoming called-number .
direct-inward-dial
!
dial-peer voice 3 pots (Local calls to Telco)
preference 1
destination-pattern [1-9]......
forward-digits all
port 0/0/0:23
!
dial-peer voice 4 pots (Long Distance calls to Telco)
preference 1
destination-pattern [1-9]..........
forward-digits all
port 0/0/0:23
!
dial-peer voice 4 pots (International calls to Telco)
preference 1
destination-pattern [1-9]............
forward-digits all
port 0/0/0:23
!
dial-peer voice 5 voip (Calls to CUCM from Telco or Fax)
preference 1
destination-pattern 81....
forward-digits all
session target ipv4:10.254.1.10 (CUCM IP)
!
dial-peer voice 5 pots (Calls to FAX from Telco or CUCM)
preference 1
destination-pattern 67..
port 0/0/0/1:23
forward-digits all
!
dial-peer voice 6 pots (Emergency calls to TELCO)
preference 1
destination-pattern 911
port 0/0/0:23
forward-digits all
!
This is the basic idea, you need to tweak this as per your specific number's but overall this should work.
Regards
Thomas
P.S. Please rate helpful posts
02-10-2011 02:28 PM
Thanks for the info. I used your model and setup the following dial-peers. I don't have any dial-peers setup to route to eFAX yet, but that shouldn't be a problem since the exact DID will be matched.
Do you see any issues with the following setup? It seems to be working fine in both directions with no delay.
dial-peer voice 1 pots
description Enable DID on calls from PRI's to GW
incoming called-number .
direct-inward-dial
!
dial-peer voice 2 pots
description Calls to Telco (Primary)
preference 1
destination-pattern .T
port 1/1:23
!
dial-peer voice 3 pots
description Calls to Telco (Secondary)
preference 2
destination-pattern .T
port 1/0:23
!
dial-peer voice 4 voip
description Default calls to CUCM Publisher (Primary)
preference 1
destination-pattern .......
voice-class codec 1
voice-class h323 1
session target ipv4:x.x.x.x
dtmf-relay h245-alphanumeric
!
dial-peer voice 5 voip
description Default calls to CUCM Subscriber (Secondary)
preference 2
destination-pattern .......
voice-class codec 1
voice-class h323 1
session target ipv4:x.x.x.x
dtmf-relay h245-alphanumeric
!
dial-peer voice 6 voip
description Default calls to CUCM Subscriber (Terciary)
preference 3
destination-pattern .......
voice-class codec 1
voice-class h323 1
session target ipv4:x.x.x.x
dtmf-relay h245-alphanumeric
02-10-2011 02:42 PM
Hey, great calls are working without any delay; and the conf looks fine too
Regards
Thomas
P.S. Please rate helpful posts
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