Serious IP Office 406V2 issue 2

[mikem501]

I have an IP Office 406V2 with an Quad BRI card in slot B and a 4VCM Card, Phone 8 expansion and an SCN networked with an IP SMall Office edition.
I am running 3.1(56) on both boxes.

My problem is that at some point in time the 406V2 disconnects Digital extensions with the following error in the monitor:
DSPhonePort:ownGlitch timeout

It is like someone is pulling out all the extensions at once and then back in. This is causing a big headache as the active calls on DS extensions are disconnected.

I have replaced the 406V2 unit and the problem is still there. Does anyone knows what the problem can be?
If there are any problems on the ISDN network (like disconnections etc) can these cause internal problems?

Any help will be appreciated.

 

[IPGuru]

what lead are you using to connect your DS unit to the IP406?
if you do not use the 1M screened cable as supplied then all sorts of strange things can happen

 

[mikem501]

I am using the supplied lead and the expansion is a phone 8 (analog). The DSs disconnecting are the 8 on the 406.
I have also noticed that on a normal system with the same firmware I never get such an error.
The only combination that generates exactly the same error is when you unplug a DS and put it back in. Therefore I am thinking that the main problem is like the cabling is being disconnected. However given the environment it is impossible and cannot understand why this is happending at the same time.
The cabling is a structured Cat6 cabling and properly tested, however what I am suspecting now is that it can be some alien cabling interference on the cable bunch somewhere in the route that is intermittently causing signals on the digital extension cables to loose track.
My next test it to connect a DS directly to the IP406 without using the structured cabling plant and check if the directly connected DS will restart like all others.

 

[crashtest1000]

We had a simalr issue on a DS30 and it was the power pack.

Atr a guess try a new power pack.One you know is OK

 

[mikem501]

It makes lot of sense that it can be a power problem ,however I have changed the power supply, connected the system with a UPS and still gives me this connectindication as if someone disconnected the phone.

Immediately before the DS error I noticed this one:

981844mS ISDNL1Evt: v=6 peb=6,F6 F3
981904mS ISDNL1Evt: v=6 peb=6,F7 F6
981905mS ISDNL1Evt: v=6 peb=6,PHAI
981905mS ISDNL1Evt: v=6 peb=6,Locked
981916mS ISDNL3Evt: v=6 p1=6,p2=1000,p3=0,p4=0,s1=

Can anyone interpret the above ISDN error?
If you have a problem on your ISDN lines, can it affect your internal extensions?
Can it be an incompatibility with the Digital Extensions - I am using 5402 and 5410 models.Are the Digital Extensions upgradeable?

 

[mikem501]

Have noticed the same error:

DSPhonePort:ownGlitch timeout (one DS extension after the other)

On an IP Small Office edition with a Quad BRI Card.
Does anyone have an idea of the setting for clocking setting for Quad BRI Cards?
Could this be the setting of all the problems that I am getting?

Any comments?...

 

[intrigrant]

v=6 //physical linenumber, i.e. slot 6
peb=6 //hardwarebuildnumber

981844mS ISDNL1Evt: v=6 peb=6,F6 F3 //State change from deactivated (F3) into activated (F6)

981904mS ISDNL1Evt: v=6 peb=6,F7 F6 //State change from activated (F6) into synchronized (F7)

981905mS ISDNL1Evt: v=6 peb=6,PHAI //Bri or Pri in connected state

981905mS ISDNL1Evt: v=6 peb=6,Locked //Bri or Pri synchronized and ready for use

981916mS ISDNL3Evt: v=6 p1=6,p2=1000,p3=0,p4=0,s1=
v=p1 //physical line number
p2=1000 // line is connecting to CO (1001 = disconn)
p3=0 // Tei value
p4= // not used
s1= //not used

Put one line as "Network" and all the others as "Fallback", this will prevent IPO to switch synchronizing between active lines. Usually you will hear a "click" during the conversation when there is a synch switchover.

 

[mikem501]

Thank you very much intrigant. Very good explanation. It means therefore that this was a call being connected.
I have changed the clocking setting as you indicated now, I had all of them getting clocking from the network.


Can my ISDN lines affect the error the disconnection error that I am getting on the system?
i.e.


1668592mS PRN: Monitor Status IP 406 DS 3.1(56)
1668592mS PRN: LAW=A PRI=0, BRI=4, ALOG=0, ADSL=0 VCOMP=4, MDM=0, WAN=0, MODU=1 LANM=0 CkSRC=7 VMAIL=1(VER=2 TYP=1) CALLS=0(TOT=53)
1674505mS ISDNL1Evt: v=7 peb=7,F3 F7
1674515mS ISDNL1Evt: v=7 peb=7,UnLocked
1674515mS ISDNL1Evt: v=6 peb=6,Locked
1674524mS PRN: 4>DSPhonePort:isconnectIndication (1696328)
1674525mS PRN: 6>DSPhonePort:isconnectIndication (1696329)
1674525mS PRN: 2>DSPhonePort:isconnectIndication (1696329)
1674538mS PRN: 7>DSPhonePort:isconnectIndication (1696342)
1674542mS PRN: 0>DSPhonePort:isconnectIndication (1696346)
1674546mS PRN: 1>DSPhonePort:isconnectIndication (1696350)
1675255mS ISDNL1Evt: v=7 peb=7,PHDI
1675255mS ISDNL3Evt: v=7 p1=7,p2=1001,p3=5,p4=127,s1=
1675255mS PRN: T4 Timeout
1675524mS PRN: 4>DSPhonePort:ownGlitch timeout (1697328)
1675526mS PRN: 6>DSPhonePort:ownGlitch timeout (1697329)
1675526mS PRN: 2>DSPhonePort:ownGlitch timeout (1697330)
1675538mS PRN: 7>DSPhonePort:ownGlitch timeout (1697342)
1675542mS PRN: 0>DSPhonePort:ownGlitch timeout (1697346)
1675546mS PRN: 1>DSPhonePort:ownGlitch timeout (1697350)
1676336mS ISDNL3Evt: v=6 p1=6,p2=1001,p3=5,p4=0,s1=
1680530mS PRN: 4>DSPhonePort::ConnectIndication (1702334)
1680532mS PRN: 6>DSPhonePort::ConnectIndication (1702336)
1680532mS PRN: 2>DSPhonePort::ConnectIndication (1702336)
1680545mS PRN: 7>DSPhonePort::ConnectIndication (1702349)
1680551mS CMExtnTx: v=407, p1=5
CMVoiceMailStatus
Line: type=DigitalExtn 3 Call: lid=0 id=-1 in=0
Calling[00000002] Type=Default (100)
Product Unknown
UUI type=Local [....] [0x03 0x01 0x02 0x00 ]
Display [Kathleen Msgs=2]
Timed: 25/04/06 08:59
1680556mS PRN: 0>DSPhonePort::ConnectIndication (1702360)
1680557mS PRN: 1>DSPhonePort::ConnectIndication (1702361)
1684380mS ISDNL1Evt: v=8 peb=8,F3 F7
1685130mS ISDNL1Evt: v=8 peb=8,PHDI
1685130mS ISDNL3Evt: v=8 p1=8,p2=1001,p3=5,p4=127,s1=
1685130mS PRN: T4 Timeout

 

[intrigrant]

Well, there is definetly something wrong in the system but i'm not sure what causes the problem.

Try to remove the VCM card first and see how it is going, this card can ruin up your whole system if it's broken.

If that doesn't help then replace the trunk cards and check all physical connections because the ISDN seems to have a problem with keeping the connection up with IPOffice.

If that doesn't help i advise you to contact Avaya.

 

[IPGuru]

1675255mS ISDNL1Evt: v=7 peb=7,PHDI
PHDI is Physical Hardware Disconnect Indicator

Your ISDN circuit has dropped

PHDI is it reconnecting.

I cant say whether this is the cause of you DS problems or or is caused by the DS issue but it is worth a look

try leaving the ISDN disconneted for an hour or so overnight to prove.

 

[mikem501]

Could it be something related to the ISDN setup such as point to point or point to Multipoint?
What is recommended by Avaya, or what do you recommend on this parameter which can be set up by the Tel Provider?

 

[mikem501]

Can I downgrade the system to the initial relase and start over from scratch? I am afraid that it is a software issue.

I am running 3.1 (56). Can I go somewhere below 3.0?

 

[bryce21]

Hello

I have exatly the same problem with one 406V2 (+dsp8) and one DS16.
I have open a case to Avaya.

 

[mikem501]

Hi Bryce21,
Do you have any trunk cards installed?
If yes - do you notice any ISDN PHDI logs?

 

[bryce21]

He Mikem501,
Yes, I have a BRI8 trunk card and I have PHDI messages

 

[mikem501]

I would like to thank IPguru and Intrigant for the help given. I have solved my problem by putting the ISDN circuits from the provider side to a point to point setup instead of point to multipoint. The PHDI errors have disappeared together with the downgltich and connectindication errors that I was experiecing.

Bryce21 - set your ISDN circuits to point to point and you will see your problem disappearing. Still cannot understand how the external lines can affect the internal extensions and only DS but anyways, another problem solved and filed.
Took me 2 days standing infront of monitor to identify the cause.

 

[JeSTeROCK]

Set the TEI on the line to 127 if using point to multipoint.

Good work boys

 

[mikem501]

I have tried that but still encountered problems, however it might solve the problem as this depends on the country you are located in.

 

[bryce21]

Hello,
I've try to change the TEI on my IPOFFICE but nothing change.
I try to contact my provider (I'm in France) but I don't think that he change the configuration of the line for me !

 

[mikem501]

Changing the TEI did not solve the problem for me.

I have noticed that when I had the problem, the trunk ISDN lines front LED (SLOT A/B) were not always on when not in use. Sometimes the LEDs go off.

Changing ISDN circuits to Point to Point is the only way how I solved the problem at least for me worked on 2 different systems, one is IP 406 with 4xBRI and the other is Small Office with 3xBRI.

In any case I am checking with Avaya about how such an issue is giving me disconnect indication on Digital Extensions.