Avaya IPO Rls 11.0 and H.323 J159 2

[BrianCosta]

Hi ...

I have IPO Rls 11.0.0.4 and an Application Server with Media Manager, the client purchased new Avaya J159 IP Phones.
The Phones worked as a Standard SIP, not a Featured SIP, So I converted the phones from SIP to H.323 firmware, and worked fine.
The customer noted something wrong with the phone operation and it's correct. on the Phone directory, if search on the john, for example, the phone display that there a 3 matches but it's only 2 matches on the phone screen, the other problem is that when choosing to call one of john's phones on the list it calls another extension number or call phone's itself.
is there a thing can I do to resolve this and keep it on H.323 firmware or must be upgraded to the latest firmware 11.0.4.7 and back the J159 to SIP firmware if I do this will work as a feature SIP operation?
my concern is the upgrade of the Application Server and damage due upgrade,

Thanks in Advance

 

[tac84]

Well, the J159 needs IP Office running at least R11.0.4.2 (Minimum) to work in supported SIP protocol. According to a couple of websites I've just checked, the J179 will work in SIP on R11 or higher. If you want to avoid the upgrade, maybe swap out the J159 and replace with a J179.

Thanks, Tim
Adelaide, Australia

 

[BrianCosta]

@tac84: The Problem is the customer Like J159, as I tell no problems with me upgrading the IPO, My concern is upgrading the IPO Application Server, The IPO Version is 11.0.4.0.0, if I upgrade it the IPO to 11.0.4.7 and leave the application server, is this will cause problems ?

 

[derfloh]

Upgrading the Application Server is not a big deal. Especially if you stay within the same minor release.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[BrianCosta]

@tac84: Upgrading the IPO to 11.0.4.7, but not worked as a SIP feature, it's still Standard SIP

 

[derfloh]

How is the 46xxsettings.txt and does the phone load it?

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[BrianCosta]

@derfloh: The 46xxsettings is auto-generated and the phone loads it from IPO.
attach all the files attached to the system

Thanks

 

[teletechman]

Clear the phone and try again. Also check to make sure it is pulling the files by using monitor with the HTTP enabled. This will tell if it pulls the 46xxsettings file which it needs to be a feature phone.
Mike

 

[BrianCosta]

Hi ...

I have Upgraded another IPO the same way, and the Feature SIP phone is working fine.
the difference is that after the upgrade, I updated the 46xxsettings and the J100Supgrade and J11settings. and auto-generated from the new updated.
in the previous system, I forget to update the file, so the headline of the autogenerated file is kept at 11.0.4.0.0, is this will cause the problem? I don't test it yet, because I need to know the issues before working on-site.

Thanks