ISDN BRI on IP500 "PHDI" issues 1

[technicaluser4]

I have an IP500 with BRI 8 Card and 4 BRI lines connected.
I am set up was point to point configutation with my provider and got 1 line set to (network clock) another as (fallback) and the other 2 set to (unsuitable)

Calls are dropping off during conversations and I noticed the following in montior:


663284mS RES: Tue 22/4/2008 16:39:33 FreeMem=79019952(25) CMMsg=4 (5) Buff=200 961 999 7166 5 Links=20600
665211mS CMExtnTx: v=506, p1=0
CMVoiceMailStatus
Line: type=DigitalExtn 6 Call: lid=0 id=-1 in=0
Called[Extn506 Msgs=0 Old=0 Sav=0] Type=Default (100) Reason=CMDRdirect Calling[00000000] Type=Default Plan=Default
Display [Extn506 Msgs=0]
Timed: 22/04/08 16:39
760756mS ISDNL1Evt: v=7 peb=7,F3 F7
760756mS PRN: T4 Started
760951mS ISDNL1Evt: v=5 peb=5,F3 F7
760951mS PRN: T4 Started
760961mS ISDNL1Evt: v=5 peb=5,UnLocked
760961mS ISDNL1Evt: v=6 peb=6,Locked
760961mS PRN: BRI: LockToPeb 5
761284mS RES: Tue 22/4/2008 16:41:11 FreeMem=79018908(24) CMMsg=4 (5) Buff=200 961 999 7166 5 Links=20602
761506mS ISDNL1Evt: v=7 peb=7,PHDI
761506mS ISDNL3Evt: v=7 p1=7,p2=1001,p3=5,p4=127,s1=
761506mS PRN: T4 Timeout
761701mS ISDNL1Evt: v=5 peb=5,PHDI
761701mS ISDNL3Evt: v=5 p1=5,p2=1001,p3=5,p4=127,s1=
761701mS PRN: T4 Timeout
898727mS CMExtnRx: v=503, p1=0


Have noticed also the follwing error in System status:
Alarms in the Service Section:
Occurences: 40
Error Description: 8Khz clock source changed, Previous source was Line6: Slot: 2 Port: 2


My IPO was running (4.0)after that I read that there were some issues with ISDN lines going out of service I have upgraded to 4.1.12, but the problem persists.

My hardware conists of:
IP500
Slot1 = 8port analog analog extension+4-port analog trunk card
Slot2= 8-port digital extension+8BRI trunk card
Slot3= VCM32 extension card
Expansion 1=Digital Exp DS30.

Anyone met this?

 

[groundedagain]

We are having exactly the same error on a site and set the same as technicaluser4.

Jason Wienert
Brisbane, Australia

http://www.centralcity.com.au

GoldMine, Avaya, ACCPAC CRM

Please remember to thank preople for their valuable input.

 

[technicaluser4]

Hi Jasonwienert,

do you mean that you are set up without clock or with one clock on 1 line?

if you are set up with no clock did you managed to eliminate the problem?
and what platform and software version are you running?

Thanks,

 

[Bas1234]

technicaluser4,

761506mS ISDNL3Evt: v=7 p1=7,p2=1001,p3=5,p4=127,s1=

Did you set the tei to 127?
Leave that on 0.



Greetzzz...Bas

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________

 

[Belrick]

The sooner you get your telco provider onto this the sooner this line fault will be fixed.
p.s: Insist that they don't waste the customers time doing a bit error rate test(bert test). (ask them to check the configuration, slippage, crc checking etc) or to use a third party ISDN analyser)

Thats the real battle.

 

[technicaluser4]

HI bas,

I changed the lines to point to multipoint to check if it makes any difference. But it did not make any difference at all.

I asked them to change the lines to a point to point config and set the TEI to 0 back again.

I tried everything. The provider is not noticing any errors from his end unfortunately. This is a brand new IP500 system and I am going to try to use 2 x BRI4 cards instead of 1 x BRI8 card to check whether it will make any difference.

 

[technicaluser4]

Does anyone know what this alarm is on the IP500?

31453mS PRN: ALARM: 16/04/2008 09:29:26 IP 500 4.0(7) <TLB Data > CRIT RAISED addr=020102e7 d=5 pc=f0096a88 00000014 f0096bd8 f009622c f016c98c f016ac8c
31453mS PRN: +++ END OF ALARM LOG DUMP +++


Is it related to config or shall I remove all the firmware and reload it from scratch?

 

[TomMills]

send it to avaya through whatever channels you have. TLB errors are not a good thing.

i have only seen them after an unexplainable reboot

 

[tlpeter]

Why sending this to avaya ?
4.0.7 and 4.0.10 had many many many reboot issues
Upgrade and then see what happens !


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[TomMills]

Point taken

 

[groundedagain]

technicaluser4, this has only started since upgrading to the MR for 4.1, prior to that we were on four and had the intermittent BRI issue. It is an IP500 with a 8BRI, point-to-point.All four BRI's connected
BRI1 - Network Clock
BRI2 - Fallback
BRI3 - Unsuitable
BRI4 - Unsuitable

We upgraded to get over the other intermittent BRI issue of one BRI "going out of service" and blocking all incoming and outgoing calls.

Jason Wienert
Brisbane, Australia

http://www.centralcity.com.au

GoldMine, Avaya, ACCPAC CRM

Please remember to thank preople for their valuable input.

 

[technicaluser4]

Just want to add a concluding comment. I have asked my provider to change 2 of the circuits on which I was getting the disconnections.

As soon as this was done by the provider the problem disappeared. The issue was within the provider's ISDN circuits.

Thanks a lot.