ISDN Recovery on Timer Expiry

[JameyC]

I'm trying to set up an NFAS group on a DEX600E connecting to a Spectra ACD. I have the primary D up and everything looks ok, but 1 out of 5 calls fail to Ring No Answer. The ACD never sees the call. The messaging is below...Any help would be appreciated!


³ ..1..... ³ InterfaceType..... ³ PrimaryRateInterface ³
³ .1...... ³ Interf IDPresent.. ³ InterfaceExplicitlyIdentified ³
³ 1....... ³ ExtensionBit...... ³ Last Octet ³
³ .0000111 ³ InterfaceIdent.... ³ 7 ³
³ 1....... ³ ExtensionBit...... ³ Last Octet ³
³ ....0011 ³ Channel/MapType... ³ B-ChannelUnits ³
³ ...0.... ³ ChanlNum/SlotMap.. ³ ChannelIndicatedByTheNumber ³
³ .00..... ³ CodingStandard.... ³ ITU-T StandardizedCoding ³
³ 1....... ³ ExtensionBit...... ³ Last Octet ³
³ 1....... ³ ExtensionBit...... ³ Last Octet ³
³ .0010011 ³ ChannelNumber..... ³ 19 ³
³ octet020 Information Element................................................³
³ 00011110 ³ Info Element...... ³ ProgressIndicator ³
³ 00000010 ³ LengthOfElement... ³ 2 ³
³ ....0001 ³ Location.......... ³ PrivateNetworkServingTheLocalUser ³
³ ...0.... ³ Spare............. ³ 0 ³
³ .00..... ³ Coding Standard... ³ ITU-T StandardizedCoding ³
³ 1....... ³ Extension Bit..... ³ Last Octet ³
³ .0000011 ³ ProgressDescrption ³ Origination Address Is Non-ISDN ³
³ 1....... ³ Extension Bit..... ³ Last Octet ³
³ octet024 Information Element................................................³
³ 01101100 ³ InfoElement....... ³ CallingPartyNumber ³
³ 00001100 ³ LengthOfElement... ³ 12 ³
³ ....0001 ³ Numbering plan.... ³ ISDN/TelphonyNmbrngPlan(REC.E.163/164 [19]) ³
³ .010.... ³ Type of Number.... ³ National number ³
³ 0....... ³ Extension bit..... ³ Octet Continues Through Next Octet ³
³ ......01 ³ ScreeningIndicator ³ User Provided,Verified and Passed ³
³ ...000.. ³ Spare............. ³ 0 ³
³ .00..... ³ PresentationInd... ³ Presentation Allowed ³
³ 1....... ³ Extension bit..... ³ Last Octet ³
³ ........ ³ Digits............ ³ 423(omitted) ³
³ octet038 Information Element................................................³
³ 01110000 ³ InfoElement....... ³ CalledPartyNumber ³
³ 00000101 ³ LengthOfElement... ³ 5 ³
³ ....0001 ³ Numbering Plan.... ³ ISDN/TelphonyNmbrngPlan(REC.E.163/164 [19]) ³
³ .011.... ³ Type of Number.... ³ Network specific number ³
³ 1....... ³ Extension bit..... ³ Last Octet ³
³ ........ ³ Digits............ ³ 6599 ³
³ octet045 Information Element................................................³
³ 10010110 ³ InfoElement....... ³ LockShift-Codest6:InfoEleForLocalNetwork ³
³ octet046 Information Element................................................³
³ 00000000 ³ InfoElement....... ³ SegmentedMessage ³
³ 00000001 ³ LengthOfElement... ³ 1 ³
³ .0000000 ³ NumberOfSegments.. ³ 00 ³
³ 0....... ³ 1stSegmentIndctr.. ³ Subsequent Segment To First Segment ³
³ Checksum ³ CRC 16............ ³ 1111100111001110 hex=f9ce ³

³ Ch#:RD3 ³CCITT LAPD DSS1 ³Flg:3361 Cnt:1 Time:23:53:41.774 ³
³ .......0 ³ EA Bit (ISDNccitt) ³ 0 ³
³ ......1. ³ C/R Bit........... ³ 1 ³
³ 000000.. ³ SAPI.............. ³ CCP CallControlProcedures ³
³ .......1 ³ EA Bit............ ³ 1 ³
³ 0000000. ³ TEI............... ³ 0 ³
³ octet002 LAPD Frame format identifier.......................................³
³ .......0 ³ FrameIdentifier... ³ I InformationFormatFrame ³
³ 0000000. ³ N(S).............. ³ 0 ³
³ .......0 ³ P Bit............. ³ 0 ³
³ 0000000. ³ N(R).............. ³ 0 ³
³ octet004 Protocol Discriminator Contents....................................³
³ 00001000 ³ ProtocolDisc...... ³ Q.931/I.145 user-ntwkCallControlMssges ³
³ octet005 Call reference information element.................................³
³ ....0010 ³ LengthOfValue..... ³ 2 ³
³ 0000.... ³ SpareBits 4MSB.... ³ 0 ³
³ 0....... ³ ReferenceFlag..... ³ FROM callReference originator ³
³ .0000000 ³ ReferenceValue.... ³ 0 ³
³ 00011100 ³ ReferenceValue.... ³ 28 ³
³ octet008 Message type Information element...................................³
³ 01011010 ³ MessageType....... ³ RELEASE_COMPLETE ³
³ octet009 Information element ...............................................³
³ 00001000 ³ InfoElement....... ³ Cause ³
³ 00000101 ³ LengthOfElement... ³ 5 ³
³ ....0011 ³ Location.......... ³ TransitNetwork ³
³ ...0.... ³ Spare............. ³ 0 ³
³ .00..... ³ CodingStandard.... ³ ITU-TStandardizedCoding ³
³ 1....... ³ ExtensionBit...... ³ Last Octet ³
³ .1100110 ³ CauseValue........ ³ RecoveryOnTimerExpiry ³
³ 1....... ³ ExtensionBit...... ³ Last Octet ³
³ octet013 DIAGNOSTIC : [RecoveryOnTimerExpired]...........................³
³ ........ ³ TimerNumber....... ³ 3 ³
³ octet014 DIAGNOSTIC : [RecoveryOnTimerExpired]...........................³
³ 00110000 ³ TimerNumber....... ³ 0 ³
³ octet015 DIAGNOSTIC : [RecoveryOnTimerExpired]...........................³
³ 00110011 ³ TimerNumber....... ³ 3 ³
³ Checksum ³ CRC 16............ ³ 0000111110001011 hex=0f8b ³


 

[ISDNman]

Well the cause code is coming form the transit network.

But usually this cause indicates tha tthe destination did not send a ALERTing before the timer expired or becuase it rang too long without answering.

Are you sure that calls that work and those that fail have the same Called Party Address?

If so, does the route for the number have the ability to handle the number of calls arriving. In other wards are you filling an internal group with no overflow path?

Another possibility is that the system is bogged down and just not fast enough?

 

[JameyC]

Thanks for your reply. It turns out the end user had clock priority off AT&T instead of us. Not sure how that works because they initially told me they clock off Bell...

Unfortunately another problem

We have it set up as an NFAS group...problem is if you disable the primary D channel, the secondary D channel only sees the B channels on its own span and will not use any other spans. Also, the primary D channel cannot use B channels on the same span as the secondary D channel...

I think its customer equipment though as I see the no circuit available coming from them...

Maybe we will get this figured out soon...or convince them to go to SS7