Phones disconnected on IP406v2

[m1ch1nt3l]

I have 2 ip406v2 systems which are disconnecting the phones at least twice a day. The systems must be rebooting during that time because when the users press the redial button the display shows "no stored number". The systems are running the version R3.2.55. The second system have a Phone8 and DS16 modules. During the event the monitor gives the following messages:

29509995mS PRN: 5>DSPhonePort:isconnectIndication (154089061)
29509995mS PRN: 6>DSPhonePort:isconnectIndication (154089061)
29509996mS PRN: 1>DSPhonePort:isconnectIndication (154089062)
29510008mS PRN: 7>DSPhonePort:isconnectIndication (154089074)
29510011mS PRN: 0>DSPhonePort:isconnectIndication (154089077)
29510017mS PRN: 3>DSPhonePort:isconnectIndication (154089083)
29510018mS PRN: 2>DSPhonePort:isconnectIndication (154089084)
29510724mS ISDNL1Evt: v=6 peb=6,PHDI
29510724mS ISDNL3Evt: v=6 p1=6,p2=1001,p3=5,p4=127,s1=
29510724mS PRN: T4 Timeout
29510996mS PRN: 5>DSPhonePort:ownGlitch timeout (154090062)
29510996mS PRN: 6>DSPhonePort:ownGlitch timeout (154090062)
29510996mS PRN: 1>DSPhonePort:ownGlitch timeout (154090062)
29510997mS CMExtnRx: v=205, p1=6
CMPhoneStatus
Line: type=NoLine 0
Call: lid=0 id=-1 in=0
Product Unknown
Cause=18, No user responding/No response from remote device
29511001mS CMExtnRx: v=206, p1=7
CMPhoneStatus
Line: type=NoLine 0
Call: lid=0 id=-1 in=0
Product Unknown
Cause=18, No user responding/No response from remote device
29511006mS CMExtnRx: v=201, p1=2
CMPhoneStatus
Line: type=NoLine 0
Call: lid=0 id=-1 in=0
Product Unknown
Cause=18, No user responding/No response from remote device
29511012mS PRN: 7>DSPhonePort:ownGlitch timeout (154090078)
29511012mS CMExtnRx: v=207, p1=8
CMPhoneStatus
Line: type=NoLine 0
Call: lid=0 id=-1 in=0
Product Unknown
Cause=18, No user responding/No response from remote device
29511020mS PRN: 0>DSPhonePort:ownGlitch timeout (154090086)
29511020mS PRN: 3>DSPhonePort:ownGlitch timeout (154090086)
29511020mS PRN: 2>DSPhonePort:ownGlitch timeout (154090086)
29511021mS CMExtnRx: v=200, p1=1

 

[gmgbg]

Had a similar problem, the problem was the service provider, they did maintenance during night. IP Office lost it's clock and started disconnect DS ports with same message as in your trace.

 

[aarenot]

Check times of reboots for a time pattern, Telcos often have this for there functions.

Go to your VMPRO AA if you have one, and press DTMF which is invalid for that menu, if it reboots add $ as an option in the menu, and route it somewhere.

I assume you have a good ground on the system.

 

[m1ch1nt3l]

The problem exists for 3-4 months. What I have to say to the provider to solve the problem? About the clocking?

 

[gmgbg]

In my case, the provider started a trace and then they say what happend, then they turned of the maintenance they were running.

 

[ProviderReborn]

You dont have a duff phone do you. Have seen this on our own in house system which was due to one of the phones loosing its config. I realise the a 5410 is not IP but we had to enable to TFTP server which then downloaded a file from the manager directory onto the phone and all was then ok.

 

[technicaluser4]

Hi there, I think I can help with this problem because I have already passed through this.

I had a problem when I had ISDN BRI installed on the system and it was a timing problem on the ISDN connections.

Make sure that your telecom provider has got his ISDN configuration set to point to point and not point to multipoint. This is what avaya recommends.

If you notice the ISDN LEDs going off then your ISDN circuits are dropping.

Then check the clock quality setting on the ISDN form. Only nne should be network, the others fallback and the unused ones should be unsuitable.

The above have solved my issue which was exactly the same.

 

[m1ch1nt3l]

Thank you technicaluser4. I assumed that it was something wrong with the ISDN configuration. I will follow your recommendations.