IP500v21 R11 and J1xx series http redirection phone binaries to http server not working? 2

[qtelcom]

Hey guys, IP500v2 R11(SP1) and J1xx series, I can't get the J169/179's to pull the update file if I have the Phone File Server Type set to memory card with HTTP redirection on and set to the phone binaries.

The http server field is filled out in Manager and I verified the http server is working, to prove it, I set the Phone File Server Type to "custom" and the J1xx phones update fine then, however I like the IP500v2 to auto generate the 46xxxxx file stuff and leave the http server to just push the big firmware files.

Recap;
Phone File Server Type "Memory Card" with HTTP redirection on ---> J1xx never grab their update file, and they fail to update, I don't even see the request hit my Http server after checking the http server logs.
Phone File Server Type "Custom" ---> J1xx update fine from the HTTP server
Phone File Server Type "Memory Card" with HTTP redirection off, --->J1xx update fine from the memory card

I have done this countless times with 9608's without issue.

Anyone else seen this or having this issue? Ideas? Bug?

 

[kyle555]

I'd be curious to see a pcap of a J1xx and a 96x1 using that redirection. I wonder if there's some HTTP list directory contents step that's happening on the J1xx before and if it doesn't see what it likes, it never makes the next ask for the next file

 

[intrigrant]

This is why it works with 96x1 and not with any other phone:

HTTP Redirection: If HTTP Redirection below is enabled, 96x1 H.323 phone binary file requests sent to the system are redirected to this address.

 

[qtelcom]

Thanks, intrigrant, I figured they hadn't updated the documentation yet, because well of course that makes sense Avaya, give us a way to have 96x1 phones grab large binaries, but no J1xx series phones without an all or nothing pull from the memory card or custom http server. Totally makes sense. Working as designed as they say.

 

[sizbut]

Sorry Intrigant, but with 11.0 is automatically applied to H175 and J139/169/179 firmware requests. That happens regards of the HTTP Redirect setting which is used for 96x1 phone firmware.

http://marketingtools.avaya.com/kno...Projects/manager/Config_forms.sys_system.html

Stuck in a never ending cycle of file copying.

 

[qtelcom]

They specifically mention H175 / Vantage phones, and 96x1 series, but I don't see any specifics for the J1xx series in those links provided.

Curious what you all do for smaller sites; (less than 25 total IP phones)
When using an IP500v2 and J1xx does everyone just let it pull off the memory card or a custom http server? If using a custom http, you have to pull the autogenerated 46xxxxx file, and then copy that over to your custom http server, just another lovely Avaya hoop to jump through.

 

[sizbut]

Bugger. I blame the 7.5% and now 10% ABV beers I've tried tonight as I'm on holiday. But in my defence I offer

http://marketingtools.avaya.com/kno...Projects/sipphoneinst/file_server_options.htm

and several happily working J179 phones.

Stuck in a never ending cycle of file copying.

 

[qtelcom]

thank you sizbut, that link would suggest that these j1xx are supposed to follow the http redirection like the 96x1’s. Enjoy the beer!

 

[tlpeter]

I would set it to custom all the way.
Copy the auto generated files just before that.

BAZINGA!

I'm not insane, my mother had me tested!