Avaya and SIP Doorphone registration loss

[Vejsel]

Hi everyone
I work for a Doorphone Company, and we have three Customers that have the same Problem.
I can register our Doorphone System to the Avaya IP Office and it works fine.
But after a period of time (1-3 Days) the Doorphone loses the registration and i have to restart the Doorphone to re-register again.
I dont have any trace that shows why the unregister happens.
Does anyone have a clue?

Here the Avaya Settings and status:

Here the Doorphone Settings:

 

[holdmusic34]

Go to the extension/VOIP tab of the doorphone extension 1590

Make sure force authorization is unticked.

A madman with a taste for speed.

 

[Vejsel]

Thank you for the response.
We will test this.
I will give feadback if it helped.

 

[VoIP Numpty]

Make sure force authorization is unticked.

Sounds like scarily dangerous advice to me - why allow a device on to the system with no credentials?

A sysmon trace is what's needed - get the BP of one of your customers to help.

 

[Vejsel]

Hallo VoIP Numpty

i've already asked the BP's for a trace but no awnser til now.
I have next week a meeting with one of them. We'll see how it goes.

 

[Vejsel]

@holdmusic34

We deactivated Force Authorisation last week on Thursday, from then till now the doorphone has not lose the registration.
Thank you.

 

[amriddle01]

That's why he's not called Numpty...

 

[VoIP Numpty]

but running without Authorisation is not any kind of solution, it needs diagnosing properly.
I'm very surprised it is an available option, and unless I need more coffee it has been removed in R11.0 anyway (or maybe earlier and I didn't notice but there's an ominous gap in the R10.1 manual on the KB

http://marketingtools.avaya.com/kno...ergedProjects/manager/Config_forms.extn.html)

 

[janni78]

I don't see which version the IPO is on, but I had an issue in 9.x where randomly the IPO wasn't able to process the re-register answer something like "Server Unavailable" causing the endpoint to stop trying.
Restarting the endpoint solved the issue, haven't seen that happening in 10.x.

"Trying is the first step to failure..." - Homer