04-05-2007 05:52 AM - edited 03-14-2019 08:51 PM
Hello everyone --
We have deployed numerous CCMEs in the past , most using FXO ports. In order to be customer friendly, we would create a number of dial-peers for each local area code with a preference for each port. For example:
dial-peer voice 1000 pots
destination-pattern 9407.......
port 0/1/0
forward-digits 10
!
dial-peer voice 1001 pots
preference 1
destination-pattern 9407.......
port 0/1/1
forward-digits 10
!
dial-peer voice 1002 pots
preference 2
destination-pattern 9407.......
port 0/1/2
forward-digits 10
!
dial-peer voice 1003 pots
preference 3
destination-pattern 9407.......
port 0/1/3
forward-digits 10
!
dial-peer voice 1100 pots
destination-pattern 9321.......
port 0/1/0
forward-digits 10
!
dial-peer voice 1101 pots
preference 1
destination-pattern 9321.......
port 0/1/1
forward-digits 10
!
dial-peer voice 1102 pots
preference 2
destination-pattern 9321.......
port 0/1/2
forward-digits 10
!
dial-peer voice 1103 pots
preference 3
destination-pattern 9321.......
port 0/1/3
forward-digits 10
Once you add on long distance and 911 this can be a management headache. We have also tried using 9T with a 2 sec Interdigit timeout, but customers give us grief about that, and we still have to create dial peers for X11 and long distance.
What do you guys do? Is there a cleaner method of creating dial-peers.
Thank you.
Solved! Go to Solution.
04-05-2007 06:55 AM
Absolutely, trunk groups is the solution.
1 - associate the pots line to a trunkgroup:
voice-port x/y (or int x/y for ISDN port)
trunk-group
2 - in the dial-peer, use it instead of port:
dial-peer voice XX pots
trunkgroup
3 - optionally, define preference for the individual port inside the trunk-group in step 1
4 - optionally, define multiple trunkgroups with preference in step 2
5 - optionally, define an hunt-scheme for the trunkgroup:
trunk group
hunt-scheme least-used
Hope this helps, if so please rate post!
04-05-2007 06:55 AM
Absolutely, trunk groups is the solution.
1 - associate the pots line to a trunkgroup:
voice-port x/y (or int x/y for ISDN port)
trunk-group
2 - in the dial-peer, use it instead of port:
dial-peer voice XX pots
trunkgroup
3 - optionally, define preference for the individual port inside the trunk-group in step 1
4 - optionally, define multiple trunkgroups with preference in step 2
5 - optionally, define an hunt-scheme for the trunkgroup:
trunk group
hunt-scheme least-used
Hope this helps, if so please rate post!
04-05-2007 07:59 AM
Very cool, this is what I needed.
Thank you.
04-05-2007 08:01 AM
Thank you for the nice rating and good luck!
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: