Avaya K175

[mohamedmohy365]

i am trying to configure K175 in Avaya IPO and I added the 46xxx file but the phone is stuck in the logging screen Can you help?

 

[Mo. Abdullah]

what are the parameters you added in the 46xxsettings.txt file that you uploaded to the IPO?
did you configured the file server address in the K175 phone settings manually first?
can you verify that the K175 phone reach and connect to the file server from the configuration verifier screen from the phone settings?

 

[mohamedmohy365]

what are the parameters you added in the 46xxsettings.txt file that you uploaded to the IPO?
did you configured the file server address in the K175 phone settings manually first?
can you verify that the K175 phone reach and connect to the file server from the configuration verifier screen from the phone settings?

yes I added it manually from phone setting and I can ping from phone to IPO for the 46xxx file it was auto-generated so I added it manually to the embedded file management

 

[Mo. Abdullah]

you should use the auto generated file settings (copy and paste to new txt file ) and edit or update it with the K175 parameters then upload it to the IPO files system again.

 

[Mo. Abdullah]

as per the settings file you attached.
i have edited it for you. you can upload it directly to the IPO embedded file system. and restart K175 phone.
try to type in the file server setting on the K175 phone the following address:
http://192.168.42.1:80

 

[mohamedmohy365]

you should use the auto generated file settings (copy and paste to new txt file ) and edit or update it with the K175 parameters then upload it to the IPO files system again.

i did the same copy the auto generated file and paste in new file then uploaded to ebeded file but still same issue

 

[mohamedmohy365]

as per the settings file you attached.
i have edited it for you. you can upload it directly to the IPO embedded file system. and restart K175 phone.
try to type in the file server setting on the K175 phone the following address:
http://192.168.42.1:80

thanks so much i will check it and give you feedback really appreciated

 

[sizbut]

None of the above. Remove the manually edited 46xxsettings.txt from the system. Put any custom settings for the phones in a 46xxspecials.txt file. Set the file redirect address for whichever HTTP file server you are using to host the K100 firmware if upgrading. And actually tell us what "stuck in the logging screen" means - which client, shows wrong users/password?, just plain stick, what type of IP Office and what release.

 

[mohamedmohy365]

None of the above. Remove the manually edited 46xxsettings.txt from the system. Put any custom settings for the phones in a 46xxspecials.txt file. Set the file redirect address for whichever HTTP file server you are using to host the K100 firmware if upgrading. And actually tell us what "stuck in the logging screen" means - which client, shows wrong users/password?, just plain stick, what type of IP Office and what release.

i am not make any http file server just add the 46xxxsetting and added it to embedded file

 

[Mo. Abdullah]

None of the above. Remove the manually edited 46xxsettings.txt from the system. Put any custom settings for the phones in a 46xxspecials.txt file. Set the file redirect address for whichever HTTP file server you are using to host the K100 firmware if upgrading. And actually tell us what "stuck in the logging screen" means - which client, shows wrong users/password?, just plain stick, what type of IP Office and what release.

it is working with me perfectly with the 46xxsettings file. and your solution is correct too my friend.
it can work with any of the 2 files 46xxsettings and 46xxspecials . any one of them will do the purpose.

 

[mohamedmohy365]

it is working with me perfectly with the 46xxsettings file. and your solution is correct too my friend.
it can work with any of the 2 files 46xxsettings and 46xxspecials . any one of them will do the purpose.

after adding the file 46xxxsetting.txt still also stuck in logging in page is there anything I can do it

 

[sizbut]

Yes, until you change a setting on the IP Office and the matching setting that needs to be passed to your phones by the 46xxsettings.txt file doesn't change. Or the IP Office team add a new setting to fix an issue or add a new feature in the auto-generated file. Just because you've got it working doesn't mean correct, you solution is more likely to lead to issues somewhere in the future and most certainly isn't an excuse to be telling others to make the same mistake.

 

[Mo. Abdullah]

Yes, until you change a setting on the IP Office and the matching setting that needs to be passed to your phones by the 46xxsettings.txt file doesn't change. Or the IP Office team add a new setting to fix an issue or add a new feature in the auto-generated file. Just because you've got it working doesn't mean correct, you solution is more likely to lead to issues somewhere in the future and most certainly isn't an excuse to be telling others to make the same mistake.

i am not getting info from my mind, it is all what Avaya say's and no issues will happen in the future and i am working this way since 4 years with more than 20 customer and they have no issues. i am not making any mistakes and not having excuses. and this way from the beginning was done by Avaya backbone Engineer when i opened a ticket with Avaya at my first year dealing with Avaya products.

you have recommended your solution way and it is very correct like i said. but my way is very correct too.
it is not my problem that you have faced issues with this way.

 

[Ekster]

4 years aga there was no 46xxspecials.txt support so you had to create a manual 46xxsettings.txt.

"The 46xxspecials.txt file is supported for the Avaya Workplace Client for IP Office R11.1.2.4 and higher."

Now you should use the 46xxspecials.txt, this leaves the 46xxsettings.txt to auto generate and any changes in the future will be populated into it.

 

[sizbut]

i am not getting info from my mind, it is all what Avaya say's and no issues will happen in the future and i am working this way since 4 years with more than 20 customer and they have no issues. i am not making any mistakes and not having excuses. and this way from the beginning was done by Avaya backbone Engineer when i opened a ticket with Avaya at my first year dealing with Avaya products.

you have recommended your solution way and it is very correct like i said. but my way is very correct too.
it is not my problem that you have faced issues with this way.

Show me where Avaya says (spelt correctly) in the IP Office documentation. And don't say an Avaya BBE told you, I've had to school them on how their own products work often enough.

4 years aga there was no 46xxspecials.txt support so you had to create a manual 46xxsettings.txt.

"The 46xxspecials.txt file is supported for the Avaya Workplace Client for IP Office R11.1.2.4 and higher."

Now you should use the 46xxspecials.txt, this leaves the 46xxsettings.txt to auto generate and any changes in the future will be populated into it.

Who said this is anything to do with Workplace? The original poster hasn't answered any questions about the actual client, what they mean by stuck*, the model of K175, or the IP Office.
*what screen cam before, what data did it ask for and what did they enter. Current this whole thread is the blind leading the blind.