Error on PRI2 NORTEL Option61

[RV482]

Hi!

I have this error code from pbx about clocking. The impact is after sometimes the channels on that loop goes mbsy…, any advise? See details below...Thanks!

The system is an Option61 with PRI2 connection to an IP router.

 

[Firebird Scrambler]

Problem based on a Option 11c system
DTA300 on Euro Isdn (I421) link.

Solution
Check CC clocking from Primary Ref.

Full details
DTA300 output from switch every 5 minutes or so.

SSCK 0 showed CC as;

.ssck 0
ENBL
CLOCK ACTIVE
CLOCK CONTROLLER - DTI061
PREF - 1
SREF - FREE RUN
AUTO SWREF CLK - ENBL
NO ERROR
IP DB PORT 1 DSBL
IP DB PORT 2 DSBL
IP DB PORT 3 DSBL
IP DB PORT 4 DSBL
CABINET CLK SRC: CC

Swapped CC to track in free run mode & then swapped back to Primary clock.

SSCK 0 now shows as;

.ssck 0
ENBL
CLOCK ACTIVE
CLOCK CONTROLLER - LOCKED TO SLOT 1
PREF - 1
SREF - FREE RUN
AUTO SWREF CLK - ENBL
NO ERROR
IP DB PORT 1 DSBL
IP DB PORT 2 DSBL
IP DB PORT 3 DSBL
IP DB PORT 4 DSBL
CABINET CLK SRC: CC

And now all is well with the world...





Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[RV482]

Thank you very much for the reply but we are using PRI2 (30channels) on an Option61 with rls. 18 only so we don't have any IP application, the PRI2 is connected to the Cisco router.

 

[RV482]

Hi!

The procedure was tried but the error still persist.. any thoughts?

Attached is the log events for reference.

Again thank you!

 

[bignose21]

You say it is connected to a Cisco router I would presume that you have links to the PSTN and you use them as your clock source, if that is the case look at the clocking on the Cisco is it from you (the 61) or if from somewhere else is it still good? Could also confirm the CRC4 settings on both ends but that is normally only an issue on initial setup if there is a mismatch.

 

[phones1]

I had an 81 with the same issue, the clock provided was from a cisco E1 I/f in a ISR3925 which put all channels to MBSY after a short while, you'll have to RCNT in 60 to bring it back online but this wont solve the issue.

as said in above messages, check CRC is the same at both ends & that their clocking for the connected I/f is set to network (assuming your still USR), or you can try re-configuring the circuit for standard EURO ETSI if using EURO I421 or vice versa. If they make any changes to the cisco end make sure they shut/ no shut the I/f to force any changes & fully down both the DCH & the loop then bring back up on the M1 around the same sort of time.

I did come across a known issue at the time on the cisco side that if your M1 isn't plugged in to the same gateway as the cisco PSTN primary clocking source then it will still slip too much for the M1 to handle & you'll be back square 1


As luck would've had it I was using a DDP2 card, which I configured the other side up as a standard EURO ETSI & I plugged this on to a cancelled ISDN30 trib. set the M1 to use this as the secondary clock source which locked in & has been error free for months now.

Good Luck (happy new Year)

Scott

Remember if it doesn't work hit it harder

Scott UK

 

[phones1]

as luck would have it found this in my notes from setting this up with the cisco guys.

controller E1 0/1/1

pri-group timeslots 1-16
description BT 15 Channels
!


interface Serial0/1/1:15
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
!


voice-port 0/1/1:15
cptone GB
music-threshold -70
bearer-cap Speech

sh isdn timers

Timers

ISDN Serial0/1/1:15 Timers (dsl 1) Switchtype = primary-net5
ISDN Layer 2 values
K = 7 outstanding I-frames
N200 = 3 max number of retransmits
T200 = 1.000 seconds
T202 = 2.000 seconds
T203 = 10.000 seconds
ISDN Layer 3 values
T301 = 180.000 seconds
T303 = 4.000 seconds
T304 = 30.000 seconds
T305 = 30.000 seconds
T306 = 30.000 seconds
T307 = 180.000 seconds
T308 = 4.000 seconds
T309 Disabled
T310 = 40.000 seconds
T313 = 4.000 seconds
T316 = 120.000 seconds
T318 = 4.000 seconds
T319 = 4.000 seconds
T322 = 4.000 seconds
T3OOS = 5.000 seconds
TGUARD= 8.000 seconds, Expiry = REJECT_CALL
T-activate = 4.000 seconds

Can't find the clocking part which is annoying but if I find I'll post.


Remember if it doesn't work hit it harder

Scott UK

 

[bignose21]

so if I do a "show run" on one of our Ciscos that is connected to a CS1K i see this:

controller E1 0/0/0
framing NO-CRC4
pri-group timeslots 1-31
description ;PABX
!
controller E1 0/1/0
pri-group timeslots 1-31
description ;PABX
!

also see:

network-clock-select 1 E1 0/1/0
network-clock-select 2 E1 0/0/0

Also see:

interface Serial0/0/0:15
description ;Link to PABX
no ip address
encapsulation hdlc
no logging event link-status
isdn switch-type primary-qsig
isdn overlap-receiving
isdn incoming-voice voice
isdn bchan-number-order ascending
isdn sending-complete
no cdp enable
!
interface Serial0/1/0:15
description ;Link to PABX
no ip address
encapsulation hdlc
no logging event link-status
isdn switch-type primary-qsig
isdn overlap-receiving
isdn incoming-voice voice
isdn bchan-number-order ascending
isdn sending-complete
no cdp enable
!


so from that I know I have 2 x 30 channel E1 circuits and can see that CRC4 is enabled on one and disabled on the other, and they are QSIG.
then if I do "show network-clocks"

#sh network-clocks
Network Clock Configuration
---------------------------
Priority Clock Source Clock State Clock Type

1 E1 0/1/0 GOOD E1
2 E1 0/0/0 GOOD E1
10 Backplane GOOD PLL

Current Primary Clock Source
---------------------------
Priority Clock Source Clock State Clock Type

1 E1 0/1/0 GOOD E1

I can see that the Cisco is clocking from the E1 connected to the CS1K and its good.

 

[phones1]

Bignose I think you've answered your own question, when the Cisco gateways clock from the Nortel all is fine. If your gateway is now connected to the pstn & the M1 is behind it having to clock from the cisco the clock source is no good.

Also your using Qsig which needs different option enabled on the DCH.

Remember if it doesn't work hit it harder

Scott UK

 

[AvayaHE]

Should activate crc on Nortel and Cisco

"controller E1 0/0/0
framing NO-CRC4
pri-group timeslots 1-31
description ;PABX"

Cs1000 Slave of Clock from Provider
and Master in direction of Cisco
That works