Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

j129 Phones issue 4

Status
Not open for further replies.
NYSTECH

NYSTECH

Vendor
May 9, 2008
1,529
US
IPO SE 10.0.3

Installed and have working 30 J129 phones. Until other day everything was going ok. Now all of a sudden I can not connect any new J129 phones they either get stuck on Acquiring Service or No SIP Proxy. And if I power cycle any of the phones that are working they will not connect again.

Customer says nothing changes on network or their DHCP scope. One of the techs working on this tried to upgrade to latest firmware and was not able to get phones to upgraded.

When looking at monitor trace I can see the ip address of the phones performing Http requests for files and it looks like the Server is sending them but I do not see any SIP Traffic for Registration of the phones..

They have h322 phones that work no issues. I have gone through threads on here and see that these are temperamental phones. I have am troubleshooting either a network issue or maybe a DHCP scope issue I think..

Anyone have experience with these phones and can enlighten me on them and maybe pointer on How the DHCP scope should be set up? Is the SIP Proxy server configure in that or in J100settings or 46xxxsetting file.
The Documentation is as always vague at best. any help is appreciated

 
Sort by date Sort by votes
I'm installing 200 of these next week so I'm interested what your solution is.

If vegetarians love animals so much, why are they eating all of their food?
 
Upvote 0 Downvote
I am just starting to play with my first one of these and after skim reading the 128 page Avaya doc on how to install and administer them I am still none the wiser about how they actually work and am thinking the cost savings will be completely eaten up by the time it is going to take to even get one working. Or am I just missing something obvious?

Found another document with a six line setup, still wasnt working so foundI could change the proxy to manual, entered the PBX IP and then it allowed me to connect the phone to the system, but I have a triangle with explanation mark in it on the top right of the screen.

| ACSS SME |
 
Upvote 0 Downvote
same thing with the e-129 phones, cheap cost but they constantly go out of service, now our customers want nothing to do with them. Have a feeling these phones will be the same headache
 
Upvote 0 Downvote
I got them to work.

1. Go to Avaya Support site and download latest 46xxsettings.txt (The one I used is dated June 2017.)
Some older settings file do not support J129 and no fields for them, Even IP Manager 10.0.3 comes with settings file dated 2013 and that was part of the issue and also the docs are not clear when you should use the 46xxsettings,txt vs. J100settings.txt.

2. Once you have the correct 46xxsettings file you can use the install and admin guide for J129.( Mine is date April 2017) and go to appendix and go through configuration parameters and modify the settings. There are specific ones that mention IP office others are optional.

3. You will need the J100Supgrade.txt and modify that to look like (FW version is latest)

IF $MODEL4 SEQ J129 GOTO J129_SW
GOTO GETSET

# J129_SW
SET APPNAME FW_S_J129_R1_1_0_0_15.bin
GOTO GETSET

# GETSET
GET 46xxsettings.txt

4. Load the 46xxseetings.txt, J100Supgrade.txt and the FW_S_J129_R1_1_0_0_15.bin to primary folder

5. Boot phone.

I have attached the file I used . Hope it helps someone.

 
 http://files.engineering.com/getfile.aspx?folder=bda232f1-ec8c-4edb-9622-5e5a240aedf8&file=46xxsettingsNEW_(00000003).txt
Upvote 0 Downvote
[thumbsup2] I was a little worried. Thanks for the info.

If vegetarians love animals so much, why are they eating all of their food?
 
Upvote 0 Downvote
We used this thread to help us get J129's working a few weeks ago after spend a couple of days, however yesterday during a failover test, none of the J129's came over to the Secondary, and when we fellback to the Primary, they still have not come back up. Luckily this is only a small number of phones. Awaiting the customer to tell us what the phones are actually doing, but we noticed on page 4 in the doc dated Dec 2016, "With the support for connectivity in a native IP Office environment survivability is supported with two IP Office SIP proxies. In this case SIPREGPROXYPOLICY must be set to Alternate."

We don't have that enabled and set in the 46xxsettings.txt file, but it is in the J100settings.txt that I believe was autogenerated on the primary and secondary. Wondering if anyone has run into this problem on a failover test, and if changing the #GETSET entry to GET J100settings.txt in the J100Supgrade.txt file could resolve this, or just do it in the 46xxsettings file? Should we disable the simultaenous settings portion in the doc?
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

pontim
  • Locked
  • Question
Avaya SBC delivering Certificate to j129 phones over port 443
Replies
5
Views
427
derfloh
derfloh
sheldoom
  • Locked
  • Question
J129 Disabling DHCP 2
Replies
3
Views
334
sheldoom
sheldoom
NYSTECH
  • Locked
  • Question
IX Workplace and Desk Phones RTP issue 2
Replies
3
Views
454
NYSTECH
NYSTECH
DiscLight
  • Question
Analog Unsupervised Disconnect issue 4
Replies
8
Views
532
Nortel4Ever
Nortel4Ever
tnestel
  • Locked
  • Question
One way audio issue
Replies
8
Views
486
derfloh
derfloh

Part and Inventory Search

Sponsor

Back
Top