Search results for query: *

Happen to me on a couple of systems. Following the below solved the issue. https://support.avaya.com/ext/index?page=content&id=SOLN364398&viewlocale=en_US

Hi all, It seems that the issue is only on J100 series phones as H323 phones are not having this issue. I have upgraded the J100 phones to the latest 4.1.1 two days now and customer didn't make any complains yet.

I have the same issue with one customer and i have upgrade to 11.1.3 and the problem is not solved.

I have android 13 and if you remove the permissions the app stop to work.

Try disabling check OOS in sip trunk settings

Unfortunately i didn't try that.

From the web :7070 go to actions restore and then choose to restore only the one-x portal.

Yep it was a physical server. On virtual i didn't had any issues also.

Happened to me also. The reason was that one-x was reset to default. I had a backup and i restore the one-x and it worked.

I had the same issue. I uninstall manager, delete the ipoffice folder in program files, reboot my pc and install manager again and it worked.

Check your 46xxsettings file under # J129AUTOGENERATEDSETTINGS for the following options. J129 take the auto time settings manually all other J phones takes the time directly of the system. SET GMTOFFSET +2:00 SET SNTPSRVR "" SET DSTOFFSET 1 SET DAYLIGHT_SAVING_SETTING_MODE 2 SET DSTSTART...

From waht's new WebLM Enhancement Previously the WebLM service run on IP Office primary servers has only been officially supported for the licensing of IP Office servers. It is now supported for the licensing of other Avaya servers and services being used by the same IP Office server, for...

Just a general question If customer has a private certificate isn't that secure? Also noticed that if you change port 5060 to a random port helps a lot

My mistake your release is 10 So try J100settings.txt

Go to system settings and disable Avaya http clients only

The 46xxsettings.txt file is auto generated by the system. In order to edit that file open http://x.x.x.x/46xxsettings.txt copy to a txt file edit the settings needed rename the txt file to 46xxsettings.txt and upload that file to the primary folder.

Look in the 46xxsettings for the SET PHNMOREEMERGNUMS and check which numbers are assigned. These are the emergency numbers for the local you specified for your system.

After further testing separated customer network with voip network and the problem disappeared. After this we reconnect the networks and the problem came back. Any ideas on what in the customer network only affects J129 phones?

ipo v2 R11.4 I have a very strange one with one customer. Customers has 16xx phones and j129 phones. Every couple days J129 looses network and goes to acquiring service. Strange thing is that only J129 phones do that, 16xx phones works fine. When J129 goes to acquiring service you can not ping...

I have opened a ticket with avaya for this. Is a known issue with R11.1