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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

H. 323 upgrade file location? 12

Rhinorhino

Rhinorhino

Vendor
Joined
Aug 29, 2022
Messages
144
Location
US
After unzipping the H.323 upgrade files what location do I drop them in and do I need to do an Upgrade?

Thanks
 
Sort by date Sort by votes
I'll be over there later today to check on minute.

Shaun E. yes per your original post I did change the J179 to Signaling H.323.

I'll send an update.

Thanks for the help.
 
Upvote 0 Downvote
Hey guys, here is pictures of where I currently am plus a monitor print out the phone is still saying waiting for DHCP after leaving it sitting there for a couple of hours

Currently running by itself as DHCP by the IPO on address 192.168.43.1 .

No other network devices except for Avaya handsets using the Avaya DHCP.

MONITOR:

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********
7451610mS DHCP: DHCP type=DHCPMsgRelease HTYPE=01 H=C81FEAD8F1A9 ReqIP=192.168.43.101 CI=Absent
7451610mS DHCP: DHCP type=DHCPMsgRelease HTYPE=01 ResIP=192.168.43.101
7451610mS DHCP: DHCP::SetState, 192.168.43.101: Bound->Returned

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********
7593726mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01 H=C81FEAD8F1A9 ReqIP=0.0.0.0 CI=Absent
7593726mS DHCP: DHCP type=DHCPMsgDiscover HTYPE=01 ResIP=192.168.43.101
7593726mS DHCP: DHCP::SetState, 192.168.43.101: Returned->Checking

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********
7594226mS DHCP: DHCP::SetState, 192.168.43.101: Checking->Offering
7594226mS DHCP: DHCP::Unsupported option (120) requested, 192.168.43.101
7594226mS DHCP: DHCP::Unsupported option (119) requested, 192.168.43.101
7594226mS DHCP: DHCP::Unsupported option (59) requested, 192.168.43.101
7594226mS DHCP: DHCP::Unsupported option (58) requested, 192.168.43.101
7594226mS DHCP: DHCP::Unsupported option (51) requested, 192.168.43.101
7594226mS DHCP: DHCP::Unsupported option (43) requested, 192.168.43.101
7594226mS DHCP: DHCP::Unsupported option (26) requested, 192.168.43.101
7594226mS DHCP: DHCP::Unsupported option (12) requested, 192.168.43.101
7594226mS DHCP: DHCP::Unsupported option (7) requested, 192.168.43.101
7594226mS DHCP: DHCP::Unsupported option (33) requested, 192.168.43.101
7594232mS DHCP: DHCP type=DHCPMsgRequest HTYPE=01 H=C81FEAD8F1A9 ReqIP=192.168.43.101 CI=Absent
7594232mS DHCP: DHCP type=DHCPMsgRequest HTYPE=01 ResIP=192.168.43.101
7594232mS DHCP: DHCP::SetState, 192.168.43.101: Offering->Bound
7594232mS DHCP: DHCP::Unsupported option (120) requested, 192.168.43.101
7594232mS DHCP: DHCP::Unsupported option (119) requested, 192.168.43.101
7594233mS DHCP: DHCP::Unsupported option (59) requested, 192.168.43.101
7594233mS DHCP: DHCP::Unsupported option (58) requested, 192.168.43.101
7594233mS DHCP: DHCP::Unsupported option (51) requested, 192.168.43.101
7594233mS DHCP: DHCP::Unsupported option (43) requested, 192.168.43.101
7594233mS DHCP: DHCP::Unsupported option (26) requested, 192.168.43.101
7594233mS DHCP: DHCP::Unsupported option (12) requested, 192.168.43.101
7594233mS DHCP: DHCP::Unsupported option (7) requested, 192.168.43.101
7594233mS DHCP: DHCP::Unsupported option (33) requested, 192.168.43.101

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********
7687692mS HTTP: 192.168.43.101(11608) HTTPSession(Secure) (Total = 2)
7687694mS HTTP: 192.168.43.101(11608) HTTPSession: Operational
7688534mS HTTP: Secure Rx Src: 192.168.43.101(11608)
GET /96x1Hupgrade.txt HTTP/1.1
Host: 192.168.43.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/J179-4.0.4.0.10 (MAC:c81fead8f1a9)
Accept: */*
Accept-Language: en
Pragma: no-cache
Cache-Control: no-cache
Expires: 0
7688535mS HTTP: 192.168.43.101(11608) HTTPServerSessionIO: stCreationCallback(7)
7688535mS HTTP: 192.168.43.101(11608) HTTPEmbeddedFileServerSessionIO: stCreationCallback
7688535mS HTTP: 192.168.43.101(11608) HTTPSession: SendErrorResponse Code: 403, Entity: AVAYA 96xx SIP access not enabled
7688536mS HTTP: 192.168.43.101(11608) HTTPSession: Forcing Session Destruction, As Error Handling Not Supported
7688536mS HTTP: 192.168.43.101(11608) HTTPServerSessionIO: SetState GracefulClose
7688537mS HTTP: 192.168.43.101(11608) HTTPServerSessionIO: SetState Delete
7688537mS HTTP: 192.168.43.101(11608) ~HTTPSession: Duration: 845ms (Total = 1)

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********
7750058mS HTTP: 192.168.43.101(56074) HTTPSession (Total = 2)
7750060mS HTTP: 192.168.43.101(56074) HTTPSession: Operational
7750062mS HTTP: Rx Src: 192.168.43.101(56074)
GET /96x1Hupgrade.txt HTTP/1.1
Host: 192.168.43.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0) AVAYA/J179-4.0.4.0.10 (MAC:c81fead8f1a9)
Accept: */*
Accept-Language: en
Pragma: no-cache
Cache-Control: no-cache
Expires: 0
7750063mS HTTP: 192.168.43.101(56074) HTTPServerSessionIO: stCreationCallback(7)
7750063mS HTTP: 192.168.43.101(56074) HTTPEmbeddedFileServerSessionIO: stCreationCallback
7750063mS HTTP: 192.168.43.101(56074) HTTPSession: SendErrorResponse Code: 403, Entity: AVAYA 96xx SIP access not enabled
7750064mS HTTP: 192.168.43.101(56074) HTTPSession: Forcing Session Destruction, As Error Handling Not Supported
7750064mS HTTP: 192.168.43.101(56074) HTTPServerSessionIO: SetState GracefulClose
7750065mS HTTP: 192.168.43.101(56074) HTTPServerSessionIO: SetState Delete
7750066mS HTTP: 192.168.43.101(56074) ~HTTPSession: Duration: 8ms (Total = 1)

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********

********** SysMonitor v9.1.12.0 build 212 [connected to 192.168.2.251 (StAnneCCD_9_1)] **********
 

Attachments

  • 17528664241168179482017972594271.jpg
    17528664241168179482017972594271.jpg
    1.2 MB · Views: 5
  • 17528664637923031195750826665842.jpg
    17528664637923031195750826665842.jpg
    1.3 MB · Views: 5
  • 1752866536570847624058866228616.jpg
    1752866536570847624058866228616.jpg
    2.2 MB · Views: 4
  • 17528665509602996855793961402679.jpg
    17528665509602996855793961402679.jpg
    4.2 MB · Views: 4
  • 17528665650566696355352759607659.jpg
    17528665650566696355352759607659.jpg
    3.3 MB · Views: 3
  • 17528665779815405898323306267627.jpg
    17528665779815405898323306267627.jpg
    3.3 MB · Views: 4
  • 17528666473354563702683687109712.jpg
    17528666473354563702683687109712.jpg
    2.6 MB · Views: 3
  • 1752866838419481990134762930205.jpg
    1752866838419481990134762930205.jpg
    1.4 MB · Views: 5
Upvote 0 Downvote
HTTPSession: SendErrorResponse Code: 403, Entity: AVAYA 96xx SIP access not enabled

IPO declined access to the 96x1Hupgrade.txt file as it recognizes the phone as SIP endpoint.

You origami have to setup another http server to host the firmware.
 
Upvote 0 Downvote
Run HFS Webserver and place the funds there. And set "Phone File Server"to external (or forward or something like that) and ever the computers ip in there. This will force the phone to load the files from there.
 
Upvote 0 Downvote
Shaun E. If your reading, did you need to do this to get your Js to with on 9.1?
 
Upvote 0 Downvote
Rhinorhino said:
Shaun E. If your reading, did you need to do this to get your Js to with on 9.1?
Click to expand...
No I didn't.

Have you uploaded a custom 96xxHUpgrade file, or are you using the auto generated one? I uploaded the one from the firmware package and it worked fine.
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

Michel$
  • Locked
Convert j159 SIP to H.323
Replies
11
Views
1K
William C290
William C290
sheldoom
  • Locked
  • Question Question
H.323 Trunk to SIP Trunk
Replies
4
Views
859
Menniss
Menniss
BrianCosta
  • Locked
  • Question Question
Avaya IPOSE - H.323 - IPO500v2
Replies
1
Views
511
derfloh
derfloh
L
  • Question Question
ERS3500 upgrade
Replies
1
Views
187
biv343
biv343
bignose21
  • Question Question
Release 12 Upgrade
Replies
8
Views
394
bignose21
bignose21

Part and Inventory Search

Sponsor

Back
Top