Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ISDN Trunk Group Not Descending Calls

Status
Not open for further replies.

SOConnor

MIS
Jan 27, 2004
54
US
I'm working on a G3r running CM1.3 software. We have an ISDN PRI trunk group with 238 channels and 2 D-channels. This trunk group was put into service in 2001 and has worked just fine since. It is programmed for descending on outgoing calls and AT&T sends incoming in ascending.

Last week we started getting some complaints from some users having trouble getting an outside line.

After much testing we have found that there are a number of outgoing calls going out on the first 23 channels of the trunk group. We have been able to duplicate the problem on several VoIP phones and I have seen an outbound call from one of the VoIP tie trunks on one of the upper channels. The testing also showed outbound calls from the same VoIP phone going out one of the button channels as well. We have even had a small group of 84XX phones that have recently complained about the same issue on Friday. They will get a fast busy and after several attempts the call will go out.

I've done list trace on a number of the phones where the complaints came and get a denial event 1195 which indicates glare whenever the test calls receive a fast busy. The next test might go through but usually on a bottom channel.

What is even stranger is that the first 23 channels are the only upper channels taking outbound calls. All on the same circuit board - the 24th channel is a D-channel None of the other upper channels show outbound calls.

The users that had the have the same COR that they have had for years. Those CORs are used extensively throughout our system of almost 6000 phones but we have only received about 10 complaints all Thursday and Friday of last week. There have not been any changes to route patterns, ARS or the trunk programming. I have seen traffic on all but the 10 middle channels as recently as 04/22/08.

Avaya has verified the trunk group programming to be correct and there are no errors in the logs. AT&T has checked their end and verified that all channels are working on their end.

Has anyone experienced a similar situation?
 
The system priorities for outbound calling is to first look for an idle trunk in the port network of the station that originates a call. Based on having the trunk group set as decending it would start at the back of the trunks first. I guess with IP phones it would probably define the home port network as the port network where the C-LAN board is that the phones registered to. You could take the first PRI and put it in a seperate trunk group to protect it from outbound usage.

Kevin
 
Agreeing with Kevin. Split the 238 members into 2 groups, 1st 5 PRI in one (TG1), last 5 PRI in the other (TG2). Change your route pattern to use the TG2 as the 1st choice and the TG1 as your 2nd choice.

-CL
 
This trunk group serves everyone on the system of 36 EPNS and there are only 2 D-channels for the entire trunk group so I cannot really split them. The trunks all come into the site where the PPN is located which is also the location of the C-Lan boards where the VoIP phones are registered. The 84XX phones that reported the problem are also at this location.
 
You can build a 2nd trunk group in the PBX and move half of the members to it. The D channels do not change and you do not modify the signalling group or the provider side (1 trunk group from LEC, 2 trunk groups in the PBX). This is not an issue and has been done this way since the G3si which only supported 99 members per trunk group. Your D channels are not an issue which would effect this change.

-CL
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top