46xx VPN phone boot file. Is there an update? 2

[oscar01]

I have a pair of 8700s running CM3.1.2 and have some 4621SW phone sets with the VPN firmware on them for home use. I notice on the VPN firmware that the boot file is b20d01b2_3.bin but the same phone on my desk has the latest boot file of b20d01b2_8_3.bin. Is the older boot file specific to make the VPN phone work or can I upgade it on my VPN phones to the lastest and leave the application file alone? I guess I'm asking if the VPN phone will work with the latest boot file and.

Thanks

 

[Mitch672]

there was a slighlty newer 46XX VPN firmware, but it is still based on R2.3, and reports as R2.3 The only difference in the new firmware is, it does not require the WebLM server for the VPN phone license.

http://support.avaya.com/japple/css...eID=317892&temp.bucketID=108025&PAGE=Document

mitch


AVAYA Certified Specialist

 

[oscar01]

Mitch672 - Yea that's the one I have and don't have a WebLM server. Someone was complaining that they dropped a call and the phone rebooted so I was just wondering if the 2_8_3 boot file would "enhance" or even work with the VPN application.

Thanks

 

[Mitch672]

I would not do it; you wil lprobably break the VPN phone, possibly requiring it to be replaced. You can't mic and match "a" an "b" files (Application and Boot). You can't partially update the phones firmware. The call probably dropped due to a crappy ISP, most likely.\

mitch


AVAYA Certified Specialist

 

[oscar01]

Ok thanks. I agree but try telling the sales employee whose "office" is out on their deck and wants to have their VPN phone wireless (which I am about to accomplish with a PoE wireless bridge)and insists that there isn't anything wrong with their 7Mb up and down stream internet connection. (Sorry did that sound cynical?)

 

[Mitch672]

you know, I have said this before, sometimes, you need to stop the inmates from running the assylum. If he wants to use a VPN phone, the minimum would be a HARDWIRED connection. tell him to get a cable wired out to his deck, or work inside like a normal person.

mitch


AVAYA Certified Specialist

 

[n25]

Mitch672,

You mentioned a new FW which doesn't require a WebLM server for the VPN phone license. Does that mean that it's now possible to use VPN phones without licenses or will it only get the licenses on a different source other than a WebLM server?

 

[oscar01]

n25 - Officially you don't need a WebLM server and you still need to pay Avaya per license. Unofficially it works without a license and I don't know how Avaya would be able to tell if you have 1 or 100 VPN phones out there so you are supposed to either not know this or be on the honor system. If you plan on having integrity and paying for the licenses a good question would be should you now have to pay for each license or just pay for concurrent used licenses like with Softphone and IPAgent.

 

[Mitch672]

you still need to "officially" buy the VPN client license, however, if you use the R2.4 VPN firmware, it doesn't check, and it won't give the user the 15 day warning, and stop working after 30 days, without WebLM access.

their official policy is, you need to still sell the licenses, but they really don't enforce it any longer. If you are a reputable Business Partner, you will keep selling the licenses to the customers. Even though WebLM isn't required, it still does work, if you already have it setup. Once thing thats an issue is, if you have NEVER setup WeBLM, then you order the customers first VPN phone license, no problem... then, you order an additinal license, well, your AVAYA supplier (Catalyst or VodaOne) is going to want a SID to attach that license to and create and RFA Transaction for you. Without actually installing WebLM, there is no real way to order additional licenses, really... because you won't have a SID to generate the new XML license file...

mitch


AVAYA Certified Specialist

 

[n25]

Thanks guys! Well that's kind of odd... what's the use of the license if the hardware won't check for it? Not to mention that you really can't give them an SID since we won't be needing a physical WebLM server anymore.