This requirement make sense with analogue lines using FXO. And we use this concept reserving some port for some users and other ports for another users.
But with e1, all you DID is mapped with your subscribed channels. AFAIK it’s not possible to select the channels as your client request.
Your requirements is clear, but as @Nithin Eluvathingal already answered it’s not possible to do this.
What is your customers reason for wanting to do this?
To be clear you can absolutely configure different access codes for the different directory numbers that you might have on a device. It’s just a matter of using the line calling search space instead of the device calling search space for these call scenarios.
However AFAIK you can not absolutely control what channel that the call uses.
I assume that should work, remove the port command from dial-peer and use only trunk-group. This is not a common scenario so not sure about the behaviour. Theoretically it should work. I have no access to test these commands on my lab now.Will try this tomorrow and will post the behaviour.
It a new information for me...
I don’t think that this would work as there is only one control channel and you can not share that across multiple trunk groups.
Also another benefit of using trunk groups is that it will reduce the number of outbound dial-peers I would have to create and I can directly control the hunting scheme as to which ISDN Channel or FXO port will be chosen first as well as the ability to dedicate some channels of ISDN circuit to particular dial-peers.
https://www.globalknowledge.com/ca-en/resources/resource-library/articles/trunk-groups-why-bother/
The referenced configuration is for FXO ports.
But for sure used correctly trunk group(s) can definitely lower the number of dial peers used. Just as server groups would do the same thing for SIP connections.
Your above configuration will work, remove the port0/1/0:15 from dial-peer. we can select the channels. Here is my test configuration and the result. Its a possible solution.
Router configuration which i tested.
trunkgroup 1
trunkgroup 2
controller E1 0/1/0
clock source line primary
pri-group timeslots 1-10,16
trunk-group 1 timeslots 4-5
trunk-group 2 timeslots 7-8
dial-peer voice 10 pots
trunkgroup 1
destination-pattern 3........
dial-peer voice 20 pots
trunkgroup 2
destination-pattern 4........
When making calls using 3, call is send through channel 4.
When making calls using 4, call is send through channel 7.
But, i don't see this as a useful feature for the customer.
Absolutely interesting, did not even think about that the pri-group and trunk-group are two different configuration elements altogether. I stand corrected about the control channel as that’s defined on the pri-group.
One thing observed, if the shared configuration is indeed the entire thing you have there is only one trunk group defined and to truly know for sure that it would work you should configure multiple trunk groups under the same controller. Otherwise your not testing the entire thing.
About remove of port from dial peers, it’s not actually possible to have both configured at the same time on a dial peer AFAIK.
