coding on T1

[coniglio]

we recently installed a PRI circuit and calls were getting busy signals sporadically. During conference call with carrier and vendor, my carrier to my vendor to change the signalling protocol to 5ESS, which my vendor did later that night. Now I'm getting the below alarm:

alarmRI210 DCH: 10 DATA: 00000001
Alarm Description: Protocol Error: Wrong coding standard.

Does this automatically point to the carrier? I checked circuit and that parameter is set to what my carrier requested, 5ESS. I just need to know who to call first. Thank you.

 

[johnpoole]

the carrier will not know that your geting errors, they will runin bgnd. make sure the rls is right for remote switch on your d, check serv msg,lkd 96 stat serv, may be off and need to beon, on need to be off.

john poole
bellsouth business
columbia,sc

 

[coniglio]

they do know, because I told them already. I know they won't see them so I told them and also told my vendor. I just didn't want this to turn into a finger-pointing scenario. Thanks Johnpoole.

 

[johnpoole]

finger pointing never helps, i do know that the office does not monitor voice ckts for errors. when you get busy outbound what does a load 60 stat show?. and waht does a load 60 lcnt show? both need to be addressed to localize the problem.

john poole
bellsouth business
columbia,sc

 

[coniglio]

T1 stats fine (idle and busy channels). LCNT are all zeroes. i do NOT know much about T1s. the carrier is looking into this so it's just wait and see for now. thanks for your help.

 

[coniglio]

the carrier and vendor are still working on this but now I've received a new alarm:
PRI217 DCH: 10 DATA: 00000006
PRI = Primary Rate Interface Diagnostic/Alarm Description: Protocol Error: General Location not supported.

If anyone knows what "general location not supported" means I would appreciate it. Carrier says the previous PRI210 alarms are due to the PBX programming being incorrect but I haven't had much luck with this carrier so far and am starting to wonder about them. thanks for your help.

 

[unkalary]

How is the DChannel programed. Is it NI2 or NI1(custom). That is determined by how the CO is programed. What type of CO is it. 5ESS DMS100 DMS250 DMS500 etc ??? Does the CO have NI2 capability? Many questions that needs to be answered. Look and ask and then post back

 

[coniglio]

The carrier said to program the route as 5ESS; once that was done we started getting these D-channel alarms. I'll see if I can figure out how to look at the D-channel programming. Never did this before...thanks.

 

[johnpoole]

ld 22
prt
adan dch x

john poole
bellsouth business
columbia,sc

 

[wdhb]

sounds like you have the wrong IFC. PRT your route & see what IFC is set to. Your PBX vendor should be able to advise you what the right setting is for the PSTN switch type

 

[coniglio]

the IFC is set to ESS5. It was set to ESS4 per carrier's request but incoming callers were getting busy signals so per carrier's request vendor changed to ESS5 which solved busy problem but then started generating the D-channel alarms. Carrier says it's not them but if they're the ones who told tech to program as ESS5 doesn't that make this carrier's responsiblity to fix? No-one seems to know what to do next. thanks for your help.

 

[johnpoole]

no if the carrier has ess5 emulation you have to match it, they will not change out there switch. i would try turning service msg off or on in ld 96.. i would try changing vsel form vce to vod or vod to vce on your route. i would try after the change did you do a enl msdl x fdl in 96. if not you firm and soft ware doesn't match. and the guy on the keyboard is ALWAYS the one that has to know (or guess) the correct combination.. don't let your vendor off that easy, this can't be the only pri they have ever installed..have them call nortel ts or dial into a working switch. one good thing about our little company is several 1000 techs and 20,000+ working t1's... what i don't know i can copy

john poole
bellsouth business
columbia,sc