Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations dencom on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ISDN BRI on IP500 "PHDI" issues 1

Status
Not open for further replies.

technicaluser4

Technical User
Dec 28, 2006
310
MT
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?
 
Usually, we set all BRI lines to clock from the network. This has caused us no problems.

Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 
Yep ive got the same issue.

with systems set the same as Matt

and now trying just one BRI set to clock


Thought i was going mad


 
Always set ONE for sync (clock) and ONE for fallback !!!

Here some info about isdn

Value Message
F1 Inactive
F2 Sensing
F3 Deactivated
F4 awaiting signal
F5 identifying input
F6 synchronized
F7 activated
F8 lost framing


ISDNL1Evt: v=[line_no.] peb=[hardware device no.], [message]

Where BRI L1 sates value is as follows :-

Message Description

PHAI Physical Activate Indication (i.e. Line is UP)
PHDI Physical Deactivate Indication (Line is DOWN)
T3TO T3 timeout has occurred
TxErr A Transmit error has occurred
UnLocked The IP Office is not able to lock its clock to this line.
Locked The IP Office and the clock extracted from this line are locked together.


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!
 
Oh Dear,

i have just put a BRI card in about an hour ago and realised i may be popping back into site tomorrow to change the clocking.

Schoolboy error

 
>>i have just put a BRI card in about an hour ago and realised i may be popping back into site tomorrow to change the clocking.

Can you not dial in via ISDN modem?

ACA - IPOffice implement
ACA - IP Telephony
CCNA - Passed at last
 
could do, but they are just down the road, the receptionist is sexy and my dinner is nearly done

 
>>the receptionist is sexy

Enough said.

ACA - IPOffice implement
ACA - IP Telephony
CCNA - Passed at last
 
Tom

Is your Mum cooking dinner again :) Its about time you found the cooker.

He He

 
i am cooking all by myself, honest.

i am actually very proud of my culinary skills, and wireless means i can surf the web from next to the hob

 
Hi, had a similar issue once.
Turned out that the service provider was running maintenace tests during the night. That was IPO sw 3.0 or 3.1, the IPO freaked out, had to reboot it to get it work.
Monitor traces looked similar then.
 
This is what I have here...I mean
Line 5 - network clocking
Line 6 - fallback
Line 7 - unsuitable
Line 8 - unsuitable

Calls keep dropping out. Therefore the conclusion is that it seems that I am prefectly set up and the calls are dropping due to provider problems although they are not catching them!

What do you think?
 
Did you try to put them all on networking?
I normaly put them on networking and had no problems, only Mobile Gateway's and other ISDN hardware who do not provide a clock.


Greetzzz...Bas

y1pzZTEUdok1vrI5cLb3FdPX4PgTPlSONkb5WPjz0x50etSujaMSmhdRCbOx9vASnrRNzzXv0IxNQA

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
If you can get the service provider to run a trace that they can look back to when it happens it would be good.
The must see something, even if it's the IPO that's causing this they should see it
 
Thanks guys! even if we went through all the subjects such as sexy receptionists, mummies, cooking. I think there is some truth in all this!
 
The only way I got the system working without errors until now is to disable all clocking from all lines (suppose that IP Office is using its internal clock).

I just want to hear whether someone here that have an IP500 and a BRI8 card inside (runnning 4.1.12) without any dropped calls problems.
If yes, please, how are you set
up? point to point or point to multipoint? and then what clock source are you using.

I am getting clock changed alarm in system status all the time when i put one line as network and another one as fallback.


 
That alarm must be in black with 8kh has changed

This is normal because you did a reboot after the change
You need synchronisation so disabling all will give problems


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!
 
hi tlpeter,
I can see the alarm in the system status and it does not appear only following a reboot. I can see it increasing with time. Clock switching is happening all the time.

Everytime the alarm comes in system status I notice a PHDI event in monitor and another user complaining that his call just dropped.

I changed the circuits to point to multipoint with provider but the problem did not disappear.

I have also noticed this error in monitor:
31453mS PRN: +++ START OF ALARM LOG DUMP +++
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 +++
31621mS PRN: ObjectMemoryPool: SSIComponentId, filled 4 times
32453mS PRN: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
32453mS PRN: + loader: 1.1
32453mS PRN: + cpu: id 2 board c0 pld 17 type c10 options 802
32453mS PRN: + fpga: id 1 issue 0 build 5e
32453mS PRN: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
32453mS PRN: ++++++++++++++++++++ LIST OF MODULES ++++++++++++++++++++
32453mS PRN: +------------------------------------------------------------
32454mS PRN: + Slot 1: Base PHONE8 Board=0x03 PLD=0x03
32454mS PRN: + Mezzanine ATM4 Board=0x02 PLD=0x07
32454mS PRN: +------------------------------------------------------------
32454mS PRN: + Slot 2: Base DIGSTA8 Board=0x12 PLD=0x06
32454mS PRN: + Mezzanine BRI8 Board=0x01 PLD=0x08
32454mS PRN: +------------------------------------------------------------
32454mS PRN: + Slot 3: Base VCM32 Board=0x05 PLD=0x11
32455mS PRN: + Mezzanine NONE
32455mS PRN: +------------------------------------------------------------
 
Oke that is a different alarm
This is monitor and it remembers 20 alarms

But when your alarm keeps increasing there is still a problem !

I will explane your trace a bit

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

peb=7 means the isdn line 7
F3 F7 means Activated(F7) and then deactivated (F3)
This is always the last one first and then the first one
T4 started means that it is trying to get synchronised again
peb=5 unlocked meand it is locked to the clock anymore
peb=6 locked means the clock is locked
This will give a reboot because you can not be called anymore and you can not make external calls anymore

You realy have a problem with the line(s)

What you need to do is go in to monitor
Go to filter -> trace options -> isdn
Press clear all and select all the isdn settings except for the "trunk packets(ip401 only)"

Let that race run and show it when it goes wrong again


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!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top