two trunk groups combined to one trunk group?

[piken]

our isdn-pri was split into two trunk groups, one designated as inbound only (DNIS #'s directed here) and one group as two-way.

Our new LD provider says they can't do that and all channels will be one trunk group configured as two-way.

So I'm trying to see if I'm missing anything by thinking I can just drop the inbound group and add members to the two-way group.

Neither group has anything special in the incoming Call handling table. DNIS #'s are direct ext. #'s

They have diff. cor's, but nothing special in either cor.

Of coarse diff. TAC's.

Inbound has Night service ext., easy enough to add to remaining trunk group.

Service type is Diff. inbound = tie / two-way = cbc
Seems strange, don't know why they're both not cbc.

Is there anything I'm missing or am I just being paranoid?

 

[4merAvaya]

I think the only thing that is accomplished by using 2 trunk groups is to prevent outbound traffic from using all of the trunks. By using a separate group for incoming calls you are reserving that many trunks at a minimum. If the number of incoming calls exceed the members in the first trunk group they will automatically flow to the second trunk group.

Kevin

 

[orypecos]

Beings how u are dropping the inbound trunk, and not the two way trunk, the outgoing ARS route patterns shouldn't have to be changed, but it wouldnt hurt to make sure that end of it is set up correctly. Sometimes when I get looking at some old programing I find that it was programed wrong or less effective than possible. When u get the channels moved over to the two way trunk, and everything is working fine, remove the old trunk to avoid confusion. Many times I have dialed into a system to do troubleshooting and spend time troubleshooting a trunk that is no longer used.

 

[piken]

yea, I know the reasoning behind having two trunk groups, but without the new carrier being able to make thier own groups to match mine, inbound calls will come in on all channels, when previously they only came in on channels we designated. Seemed like a simple request to carrier, but they said they couldn't do it. Oh well.

So it really seems like a pretty simple matter of just moving the trunk group members from the inbound group to the existing two-way group and after testing drop the old inbound group. As long as the old inbound group had nothing special in its incoming call handling table, which it doesn't.

 

[Bobg1]

Its not that they can't.
It's either they don't want to be bothered or they don't have someone with the knowledge of setting it up properly.