NFAS group issues.....

[DavidNe]

I'm having issues with my Bchannels going into LCKO state.

Here is the scenario.....I've created 3 PRI's for one route. here is my route and DCH information.....

ROUT 5

TYPE RDB
CUST 00
ROUT 5
DES GSX_PGCC
TKTP TIE
ESN NO
CNVT NO
SAT NO
RCLS EXT
DTRK YES
DGTP PRI
ISDN YES
MODE PRA
IFC D100
SBN NO
PNI 00000
NCNA YES
NCRD NO
CHTY BCH
CTYP UKWN
INAC YES
ISAR NO
TGAR 1
ADDP NO
DSEL VOD
PTYP PRI
AUTO NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 1905
TCPP NO
TARG
BILN NO
OABS
INST
IDC YES
DCNO 1 *
NDNO 1
DEXT NO
DNAM NO
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096
TFD 0
CDR NO
MUS YES
MRT 30
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0


PAGE 002

FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
TTBL 0
ALRM NO
ART 0
AACR NO



ADAN DCH 59
CTYP MSDL
GRP 1
DNUM 10
PORT 1
DES GSX_PGCC
USR PRI
DCHL 59
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC D100
SIDE USR
CNEG 1
RLS ID **
RCAP
PRI INTERFACE ID
053 2
060 3
T200 3
T203 10
N200 3
N201 260
K 7


for some reason when I place a call across the PRI's when it hits loop 60 (third PRI) and 53 (2nd PRI) all BCH's go into LCKO state but the call completes on the first T1 (Loop 59) on the 23rd channel.

I've had my carrier do some traces and they have advised this is an NFAS group issue..... that everytime I send a call out that I'm sending them nfas id of 0 for all the interfaces on the nfas.

How does the NFAX numbering work in my Option 81 with regards to an NFAS group of 3? is it 0,1 and 2 or is it 1,2 and 3.

Any help on this would be very greatful.

 

[bhassell2000]

do you have a backup D in the group?

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[DavidNe]

No there is no bakcup Dch programmed.

 

[drifter56]

Your carrier is referring to interface ID's, on the Meridian 1 system any primary d-channel is automaticlly id 0 and any back up d-channel is id 1. You set the other t-1 loops id by the PRI Interface ID prompt in the d channel data block. Yours are currently set for loop 53 id 2 and loop 60 id 3. You may want to check with the carrier to be sure they set their id's that same as yours, also be sure that the spans you have loop 53 and 60 connected to have the correct id's at the CO's end, if they are reversed that could cause your issue.

 

[RickyPone]

You can check the pri inerface id by rolling the cables on loops 52 and 60.

 

[DavidNe]

I checked the cables and they are correct, I disconnected Loop 60 from my end had the carrier check on their end and they advised that the 3rd PRI was down....

as per the carrier he has has advised that his NFAS ID's are setup as 0, 2 and 3

When I bring up all 3 PRI's the carrier sees only interface 0 in all of his ISDN traces.

 

[RickyPone]

Sounds like a vendor meet is needed. Can you get a tberd? If you could then you could set it up on one of the pris and see if you can place a call. But that is alot of trouble when this seems to be a protocol problem. And I'll have to say that you programming looks fine to me. I had a trouble like this once and I had to blow it all away and rebuild to correct it. Built it back exactly the same. First and only time that has ever happened to me. If you have enough hardware and network space you could try to build another trunk group and see if you have the same trouble.

 

[DavidNe]

after opening up the DCH messaging here is what I get (obviously I am not going to paste all the failed calls from Loop 60 CH24 as it's pretty much all the same.......until it gets to the 1st PRI and the call completes...

DCH 59 OMSG SETUP REF 00000033 CH 53 3 TOD 15:42:52
CALLING #:4058000 NUM PLAN: PRIVATE
CALLED #:15146947242 NUM PLAN: PRIVATE

DCH 59 IMSG REL COMP REF 00000033 CH 53 3 TOD 15:42:52 CAUSE :REQ CIRC NOTAVAI

DCH 59 OMSG SETUP REF 00000032 CH 53 2 TOD 15:42:52
CALLING #:4058000 NUM PLAN: PRIVATE
CALLED #:15146947242 NUM PLAN: PRIVATE

DCH 59 IMSG REL COMP REF 00000032 CH 53 2 TOD 15:42:52 CAUSE :REQ CIRC NOTAVAI

DCH 59 OMSG SETUP REF 00000031 CH 53 1 TOD 15:42:52
CALLING #:4058000 NUM PLAN: PRIVATE
CALLED #:15146947242 NUM PLAN: PRIVATE

DCH 59 IMSG REL COMP REF 00000031 CH 53 1 TOD 15:42:54 CAUSE :REQ CIRC NOTAVAI


DCH 59 OMSG SETUP REF 00000017 CH 59 23 TOD 15:42:54
CALLING #:4058000 NUM PLAN: PRIVATE
CALLED #:15146947242 NUM PLAN: PRIVATE

DCH 59 IMSG CALLPROC REF 00000017 CH 59 23 TOD 15:42:54

DCH 59 IMSG ALERT REF 00000017 CH 59 23 TOD 15:42:56
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 59 IMSG CONNECT REF 00000017 CH 59 23 TOD 15:42:56

DCH 59 OMSG CONN ACK REF 00000017 CH 59 23 TOD 15:42:56

 

[yyrkroon]

Had the same problem once, turned out Telco had us programmed as 3 seperate loop with seperate dch and we had the same setup as you 1 dch running 3 loops...just something to think about