D- channel or signal group issue help?

[heathersue]

Hello,

Looking for advice here, we have a new PBX with 2 new PRI's for local and LD. Teh PRI's are 23 b+D, Dchannel on the 24th member of each trunk and. The first trunk had the primaray D channel and the second trunk group has the backup d channel.

When we place a call to the site about a quarter of the time the call will drop right away - before anyone picks it up. the connection just dies. since the call gets there we figure this is a signal group or Dchannel issue where maybe the cables were flipped or the Dchannels were put in backward - we tried just about everything to get this to work - confirmed we have the right cables in the right places, verifid D-channels were where we thought they should be...etc. anyone ever have this happen to them before - if so what steps did you take to resolve? thanks.

sincerely,
dazed and confused in NJ

 

[98Converter]

Did you build individual signal groups for each T1? Sounds like your using 1 signaling group for both...

Thanks,
CJH

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[nohuhu]

heathersue,

1. list trace tac, try to catch a dropped call.
2. disp events for isdn denial events.
if it is d-channel issue, there must be some record of it.

 

[1a22ip]

To use primary and secondary D channel arrangements you must have one signal group defined like Below:
SIGNALING GROUP

Group Number: 7 Group Type: isdn-pri
Associated Signaling? n Max number of NCA TSC: 10
Primary D-Channel: 03A1724 Max number of CA TSC: 23
Secondary D-Channel: 04B1824 Trunk Group for NCA TSC: 4
Trunk Group for Channel Selection: 4 X-Mobility/Wireless Type: NONE
Supplementary Service Protocol: a

Trunk Brd Interface ID Trunk Brd Interface ID
1: 03A17 0 11:
2: 04B18 1 12:

The signal group must match the Telco. If the signal group comes active then they match. I had a similar problem and the problem was the setting on the trunk group form for Trunk Hunt: was set to Ascend and the two PBX's could not reset the channels fast enough. I changed this to cyclical and problem was solved.

Hope this helps
ED

1a2 to ip I seen it all

 

[heathersue]

UPDATE:

I wanted to let everyone know we found out the issue. I stopped responding when we saw one of the strangest symptoms ever - on an inboundcal we though the call was dropping since we heard silence, but - if we take one of the 'silence' calls and try to transfer it to another extension it then worked fine. Worked with Avaya on this up to what they call the 'green room' with tier 4 engineers. Wound up that the CM 3 software load we had installed had some known issue with the function of the DSPs and we had to have an untested patch applied. Issue all fixed.