05-11-2021 08:27 AM
Reviewing a configuration of a 2821 and I seeing the following and wanted to confirm I'm reading it correctly:
trunk group TG carrier-id carrier hunt-scheme sequential both up controller T1 0/0/0 clock source line primary cablelength long 0db pri-group timeslots 1-24 trunk-group TG timeslots 1-24 preference 1 ! controller T1 0/0/1 cablelength long 0db pri-group timeslots 1-24 trunk-group TG timeslots 1-24 preference 2 interface Serial0/0/0:23 no ip address encapsulation hdlc isdn switch-type primary-ni isdn incoming-voice voice isdn map address *. plan unknown type unknown isdn supp-service name calling no cdp enable ! interface Serial0/0/1:23 no ip address encapsulation hdlc isdn switch-type primary-ni isdn incoming-voice voice isdn supp-service name calling no cdp enable dial-peer voice 1 pots trunkgroup TG 1 trunkgroup POTS 2 description ** incoming dial-peer ** incoming called-number . direct-inward-dial dial-peer voice 11 pots trunkgroup TG 1 description 11-Digit-Dialing destination-pattern 91[2-9]..[2-9]...... progress_ind alert enable 8 progress_ind progress enable 8 progress_ind connect enable 8 forward-digits 11
dial-peer voice 12 pots
trunkgroup POTS 1
description 11-Digit-Dialing - CENTREX
preference 2
destination-pattern 91[2-9]..[2-9]......
progress_ind alert enable 8
progress_ind progress enable 8
progress_ind connect enable 8
forward-digits all
Inbound calls should arrive on 0/0/0:23 and outbound calls should start being sent out over 0/0/1:23? Outbound calls would start at 0/0/1.23.1 (0/1:1) and increment to 1.23.2 (0/1:2) etc? If both PRIs are down or in use it should fail to the POTs dial-peer which uses FXO ports on the system? If correct, other than an issue upstream w/ the carrier, what would cause inbound calls to arrive on 0/0/1:23 and not on 0/0/0:23?
05-11-2021 08:33 AM
Inbound calls will be determined by the carrier. So you will need to contact them to find out which PRI they are sending the calls to first. No configuration on the router will change that. You're configuration looks good as far as your goals for outbound calls.
05-11-2021 09:52 AM - edited 05-11-2021 10:11 AM
Inbound calls are handled by ISP. if you want all incoming to land only on first port, raise a request with ISP.
Asper your configuration both pri is a part of a trunk group. And trunk group is in sequential.if you want to send outgoing call only through second pri remove the first controller (0/0/0) from the trunk group. And to make the channel as you mentioned you can define the channel selection as ascending.
05-11-2021 10:46 AM
Thanks for this. Yes, it's configured w/ "hunt-scheme sequential up" which should be ascending correct? I'm seeing outbound calls appear to be descending on 0/0/1:23.
With respect to the backup POTS line, is there any feature such as "privacy" that would essentially prevent 2 people from grabbing the same POTS line for an outbound call.
05-11-2021 10:56 AM - edited 05-11-2021 10:56 AM
Hunt sequence is not the factor for pri channel selection.
Use below command on interface for channel selection ascending/decending.
isdn bchan-number-order{ascending |descending}
what you mean by two people grabbing pots? only one call can be made using fxo port
05-11-2021 05:30 PM - edited 05-11-2021 05:33 PM
As @VON CLAWSON mentioned, the heading is bit confusing. You Mentioned MGCP, But Form the controller configuration you are using h323. There is no mgcp service command on controller.
Which protocol you use ? . if its MGCP you need to make the change from CUCM as mentioned below.
05-11-2021 10:59 AM
Nithin's response about isdn bchan-number-order{ascending |descending} is absolutely correct. However, I'm confused about something. Your title says that you are using MGCP. However, your dial-peers and the fact that you are using trunk groups is H.323. So are you using MGCP or H.323. With MGCP the channel selection and the choice of using the PRI vs POTS lines would be done but CUCM. In H.323 your configuration would be good.
05-11-2021 12:30 PM
Exactly what I also thought @VON CLAWSON
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: