Adtran 908e and CS1000 PIR problem

[gndsystems]

We are having problems after switching telcos, the new telco is providing 2 PRI via an adtran 908e and we are having intermittent call failures both inbound and outbound.

Any ideas of what to tell telco to change to make this work properly?

Greg D

 

[KCFLHRC]

It could be any number of things. First of all you need to make sure the protocols match. B8ZS/ ESF for example. Also Make sure how the ISDN is set up, NI2 for example on the D-Channel. You also need to make sure they are passing clocking through to you and that your clock is tracking and not in free run. Lots of possibilities here but without knowing what you have it would just be a guess. A good place to look for call failures is with D-channel messaging. I would also look at the counters in LD 60 and see if the Span is taking error's.

Ld 60 This is for error's
LCNT

LD 60 This will query your clock controller
SSCK 0

 

[gndsystems]

KCFLHRC

Do the following two statements mean anything to you as far as the adtran configuration is concerned?


[highlight #EF2929]Switch Engineer[/highlight]
The report back from the switch engineer says that "the far end dch isn't sending the restart all channels command, Our switch is set to auto and your should be also"

[highlight #CC0000]Telco[/highlight]
Yessir, based on the statement from the engineer, "the far end d ch isn't sending the restart all channels command” – The command I listed below restarts inactive b-channels every hour. There is no command to restart the d-channel short of taking down the PRI.

 

[KCFLHRC]

Those statements don't mean much to me in the CS1000 World. Are the B-channels not clearing after a call properly? Basically the tear down of the call? I would need to see print outs of the D-channel config to tell you what to tell the Adtran people. All this crap about restarting B-channels every hour and all that is nonsense. If it is set up properly there shouldn't be a need to do any of this. Sounds like someone is trying to put a band aid fix on it instead of fixing it properly.

 

[gndsystems]

KCFLHRC here is the print out of the 2 d-channels I appreciate your time and help.

ADAN DCH 0
CTYP MSDC
DNUM 10
PORT 2
DES GLOBAL_ACCESS
USR PRI
DCHL 18
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSERV YES
BSRC 2

ADAN DCH 19
CTYP MSDC
DNUM 10
PORT 3
DES GLOBAL_ACCESS
USR PRI
DCHL 19
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSERV YES
BSRC 2

 

[KCFLHRC]

That BSERV set to YES is concerning to me. Default is NO. Also the CTYP prompt says MSDC, I don't even see that listed in the book as an option.



Back to the BSERV set to YES



If I remember right that prompt being set to yes was for what we called back in the day, "Smart Trunks". This is where you had a Master Route and Service Routes pointed to the Master Route. Nortel may have called this Call By Call Routing if I remember right. This was designed to set min's and max's for number of incoming and outgoing calls on a particular Service Route. Is that what you have or what you had before the transition? I have only seen Smart Trunks like this maybe twice in 30 years of Nortel experience.


If the CO isn't set up for this Call By Call Routing and it was like that before that may very well be your issue

 

[KCFLHRC]

Found this in an old AT&T Guide, this may be how you were set up prior to conversion

Dynamic Channel Allocation (DCA)
Allows a customer to designate the quantity of call types to be allocated within previously provisioned
criteria for either Direct Inward Dial (DID) or Direct Outward Dial (DOD) services. In equipped central
offices, this feature will also include Common Line 800, Outward WATS, and tie line services. This
feature is also known in the industry as call-by-call service selection.

https://cpr.att.com/pdf/mo/0017-0002.pdf

 

[gndsystems]

I made a typo, long story but I had to retype output of report.

CTYP MSDL is the current setting

So you are suggesting we change BSERV to NO ?

I believe a couple of providers ago , we had several call paths over different networks depending on in state out of state international etc.

 

[KCFLHRC]

I think this is about to get complicated but I do think we may be onto the problem

Can you go into LD 21 and do a LTM, this will list all of the trunk members

Also do you have a vendor working on this or are you the end user? The reason I ask is if this is headed where I think it is headed you are going to need someone with some experience building trunks, routes , and BARS programming

Also can you ask your current provider if these are plain old National ISDN 2 PRI's or are they offering or doing call by call routing?

 

[gndsystems]

Standard NI2 – We’re taking all the calls and just passing them through to the PBX, no special routing for DIDs that are part of the PRI."

This is the reply back from telco to your question

It will be next week until I am back onsite to run the reports requested.

I am in the middle between the Telco and AT&T who we pay to maintain switch.

 

[KCFLHRC]

I have my suspicions that this was set up before for call by call routing and now that the new PRI's aren't set up that way you are having issues. If you have a Master Route and Service routes and the LTM shows routes with no member's in it than I think we have found your problem. However, it's not going to be as easy as changing BSERV to NO. All the routes, trunks and D-channels will have to be outed and rebuilt as well as BARS touched for the changes.

 

[KCFLHRC]

I have only ever seen this set up for example Radio Stations and TV Stations where if they put a number up on the screen or tell you to call into the radio station, this call by call feature would only allow so many incoming calls to hit the PRI so it didn't use all of your trunks so no one could make an outbound call.

 

[gndsystems]

KCFLHRC

TYPE TLIST
TKTP DID
ROUT 0
DES GLOBAL_ACCESS
TN 018 01 MBER 1 GLOBAL_ACCESS
TN 018 02 MBER 2 GLOBAL_ACCESS
TN 018 03 MBER 3 GLOBAL_ACCESS
TN 018 04 MBER 4 GLOBAL_ACCESS
TN 018 05 MBER 5 GLOBAL_ACCESS
TN 018 06 MBER 6 GLOBAL_ACCESS
TN 018 07 MBER 1 GLOBAL_ACCESS
TN 018 08 MBER 8 GLOBAL_ACCESS
TN 018 09 MBER 9 GLOBAL_ACCESS
TN 018 10 MBER 10 GLOBAL_ACCESS
TN 018 11 MBER 11 GLOBAL_ACCESS
TN 018 12 MBER 12 GLOBAL_ACCESS
TN 018 13 MBER 13 GLOBAL_ACCESS
TN 018 14 MBER 14 GLOBAL_ACCESS
TN 018 15 MBER 15 GLOBAL_ACCESS
TN 018 16 MBER 16 GLOBAL_ACCESS
TN 018 17 MBER 17 GLOBAL_ACCESS
TN 018 18 MBER 18 GLOBAL_ACCESS
TN 018 19 MBER 19 GLOBAL_ACCESS
TN 018 20 MBER 20 GLOBAL_ACCESS
TN 018 21 MBER 21 GLOBAL_ACCESS
TN 018 22 MBER 22 GLOBAL_ACCESS
TN 018 23 MBER 23 GLOBAL_ACCESS
TN 019 01 MBER 24 GLOBAL_ACCESS
TN 019 02 MBER 25 GLOBAL_ACCESS
TN 019 03 MBER 26 GLOBAL_ACCESS
TN 019 04 MBER 27 GLOBAL_ACCESS
TN 019 05 MBER 28 GLOBAL_ACCESS
TN 019 06 MBER 29 GLOBAL_ACCESS
TN 019 07 MBER 30 GLOBAL_ACCESS
TN 019 08 MBER 31 GLOBAL_ACCESS
TN 019 09 MBER 32 GLOBAL_ACCESS
TN 019 10 MBER 33 GLOBAL_ACCESS
TN 019 11 MBER 34 GLOBAL_ACCESS
TN 019 12 MBER 35 GLOBAL_ACCESS
TN 019 13 MBER 36 GLOBAL_ACCESS
TN 019 14 MBER 37 GLOBAL_ACCESS
TN 019 15 MBER 38 GLOBAL_ACCESS
TN 019 16 MBER 39 GLOBAL_ACCESS
TN 019 17 MBER 40 GLOBAL_ACCESS
TN 019 18 MBER 41 GLOBAL_ACCESS
TN 019 19 MBER 42 GLOBAL_ACCESS
TN 019 20 MBER 43 GLOBAL_ACCESS
TN 019 21 MBER 44 GLOBAL_ACCESS
TN 019 22 MBER 45 GLOBAL_ACCESS
TN 019 23 MBER 46 GLOBAL_ACCESS

TYPE TLST
TKTP AWR
ROUT 3
DES AWR
TN 004 1 02 02 MBER 1 AWR

TYPE TLST
TKTP AWR
ROUT 4
DES AWR
TN 004 1 02 03 MBER 1 AWR2

TYPE TLST
TKTP MUS
PAGE 002
ROUT 5
DES MUSIC
TN 004 1 01 07 MBER 1 MUSIC

TYPE TLST
TKTP COT
ROUT 6
DES COT1
TN 004 1 01 00 MBER 1 COT
TN 004 1 01 01 MBER 2 COT
TN 004 1 01 02 MBER 3 COT

TYPE TLST
TKTP RAN
ROUT 10
DES MIRAN
TN 004 1 02 00 MBER 1 MIRAN

TYPE TLST
TKTP DID
ROUT 11
DES OAM
TN 004 1 02 07 MBER 1 CALLRAN

TYPE TLST
TKTP RAN
ROUT 12
DES MIRAN2
TN 004 1 02 01 MBER 1 RAN

 

[KCFLHRC]

Well, it doesn't appear to be what I thought it was, a Smart Trunk. Still, that BSERV set to yes concerns me