02-06-2009 03:19 PM - edited 03-15-2019 04:03 PM
We are turning up a new PRI on a shared tenant phone system. This is our first H.323 gateway. We have a very large number of DID's on the system. We currently have the following patterns (which is not working):
dial-peer voice 1 voip
preference 1
destination-pattern .......
voice-class codec 1
voice-class h323 1
session target ipv4:10.10.10.10
incoming called-number .
dtmf-relay h245-signal h245-alphanumeric
no vad
!
dial-peer voice 2 voip
preference 2
destination-pattern .......
voice-class codec 1
voice-class h323 1
session target ipv4:10.10.10.11
incoming called-number .
dtmf-relay h245-signal h245-alphanumeric
no vad
!
dial-peer voice 10 pots
destination-pattern .T
incoming called-number .
direct-inward-dial
port 1/0:23
forward-digits all
The problem is that when a call comes in, the POTS dial peer is picking it up and sending the call back out the PRI.
How can we configure the dial peers so that anything coming from the VoIP side gets directed out the POTS peers and anything from the POTS side gets directed to the VoIP peers?
Solved! Go to Solution.
02-06-2009 04:56 PM
Hi Jordan,
You can using corlists and do something like this:
dial-peer cor custom
name a
name b
dial-peer cor list a
member a
dial-peer cor list b
member b
dial-peer voice 1 voip
destination-pattern ....
session target ipv4:1.1.1.1
incoing called-number .
corlist outgoing a
corlist incoming b
dial-peer voice 10 pots
destination-pattern .T
session target ipv4:1.1.1.1
incoming called-number .
direct-inward-dial
corlist outgoing b
corlist incoming a
You may want to come up with something easier to manage. Possibly set up prefixes that you use for routing, etc.
Example of that would be marking inbound voip calls with the prefix 1#, and then setting the destination-pattern on the pots dial peers to be 1#.T.
The config would look like this:
translation-rule 1
rule 1 /\(.*\)/ /1#\1/
translation-profile 1
translate called 1
dial-peer voice 1(and/or 2)
translation-profile incoming 1
dial-peer voice 10 pots
destination-pattern 1#.T
A couple options to wrap your mind around. You may find it easier to have the voip systems prepend a certain prefix before it gets to this gateway as well.
hth,
nick
02-06-2009 03:26 PM
How the number thta you gave to tenants looks like ?
02-06-2009 04:19 PM
We have various, non-contiguous blocks. And as we add new tenants, we may port individual numbers onto our network. So, they can vary greatly.
02-07-2009 03:05 AM
Seems like you would have a distinct advantage in using MGCP in this case then.
02-06-2009 04:56 PM
Hi Jordan,
You can using corlists and do something like this:
dial-peer cor custom
name a
name b
dial-peer cor list a
member a
dial-peer cor list b
member b
dial-peer voice 1 voip
destination-pattern ....
session target ipv4:1.1.1.1
incoing called-number .
corlist outgoing a
corlist incoming b
dial-peer voice 10 pots
destination-pattern .T
session target ipv4:1.1.1.1
incoming called-number .
direct-inward-dial
corlist outgoing b
corlist incoming a
You may want to come up with something easier to manage. Possibly set up prefixes that you use for routing, etc.
Example of that would be marking inbound voip calls with the prefix 1#, and then setting the destination-pattern on the pots dial peers to be 1#.T.
The config would look like this:
translation-rule 1
rule 1 /\(.*\)/ /1#\1/
translation-profile 1
translate called 1
dial-peer voice 1(and/or 2)
translation-profile incoming 1
dial-peer voice 10 pots
destination-pattern 1#.T
A couple options to wrap your mind around. You may find it easier to have the voip systems prepend a certain prefix before it gets to this gateway as well.
hth,
nick
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: