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!

D100 (POS IMO) not working on 9.1 1

Status
Not open for further replies.
ipandy

ipandy

Technical User
Joined
Dec 9, 2010
Messages
30
Location
US
So I've read the different posts in here about how to make the D100 work but i am still getting a No Service message on the D160 handset. I've got the IPO set as file server, no d100 files on the SD card, downgraded to 9.0.6, tried to upgrade firmware to 2_0.9.6 from 1_0.9.6 (it won't upgrade firmware). Everything I've read says it should be good to go. I am currently downloading 9.0.5 bin files to downgrade even further. What else am I missing? Thanks
 
Sort by date Sort by votes
Same here. Wasted the whole day today on this. Please share if you figure it out.
 
Upvote 0 Downvote
I get Article Not Found or no longer available when I click the link...
 
Upvote 0 Downvote
IP Office : 9.1 : IP500v2 : D100 Base station will not connect, new out of the box installation




Doc ID: SOLN264719
Version: 3.0
Status: Published
Published date: 04 Mar 2015
Updated: 09 Mar 2015


Author:
Danny Lollo





Details


D-100 Base stations do not connect to 9.1, testing has duplicated this failure and what was found was that in the failing scenario the firmware D100_BS_SL_0.9.6.bin times out when trying to transfer on the 9.1 software.


Problem Clarification


This only happens on new base stations being added or installed on IP500v2 9.1 and the D100 attempts to upgrade the 2 base station firmware files D100_BS_MS & D100_BS_SL The MS completes but the SL times out and reboots, then loops.


Cause


TFTP transfer timeout issue on the IP Office 9.1


Solution


Using a 9.0.5 system will upgrade the firmware and then the D100 can be moved to a 9.1 system with no issues. You can also host the files on an external HTTP server and point to in from Manager.

The fix for this issue will be included in the next SP on 9.1


ACSS (SME)
APSS (SME)
 
Upvote 0 Downvote
Here is what I did to get the D100 working on v9.1.1.0 build 10:

Copied these auto generated files and bin files by loading them in my web browser and saving locally:
D100_BS_MS_1.2.2.bin
D100_BS_SL_0.9.6.bin
D100.cfg
D100prov.txt
D100settings.txt

I put them in the root directory of another web server accessible to the D100. I then configured the D100 with a static IP and set the configuration server IP to that of the web server. I then rebooted the D100 and let it sit and watched the access log of the web server. The D100 pulled the config files and successfully updated both bin files. It then registered with the IP500v2 as that address was in the D100settings.txt file. In manager, I have the D100 line "Configure base IP" checked with the appropriate settings and the provisioning server set to the IPO, not the web server used to do the update. This way future updates will hopefully work without intervention.

Thanks Bob for the idea to use another web server to do the update.

 
Upvote 0 Downvote
Perhaps it is part of the new security options in R9.1 where different "insecure" interfaces like TFTP are disabled. Did anyone check these setting in security to get D100 to work?
 
Upvote 0 Downvote
You have to manually configure the d100 from its web interface. Setup your pc with HFS server and point the d100 to it to download its firmware. After upgrading you can change the call server address back to the IPO. This works for 9.0 problems too.

If vegetarians love animals so much, why are they eating all of their food?
 
Upvote 0 Downvote
I first tried pointing the D100 to a local TFTP server, but it didn't connect. I then pointed it to a local http server, and it pulled the files that way.
 
Upvote 0 Downvote
Where can I get D100prov.txt file please? It's not on the SD card or in my Manager folder
Thanks
 
Upvote 0 Downvote
I didn't search but usually you will find such files in your manager program folder.
 
Upvote 0 Downvote
Just use a web browser and go to of IP500>/D100prov.txt and it will be displayed for you. Same for the other files.
 
Upvote 0 Downvote
OK, I have a new IPO with v9.1.2.0.91 and I´m still
having this issue with getting an D100
(Firmware Version D100_1.2.2_0.8.6 Hardware Version 4)
to work.
In SystemStatus I see the D100 only with IP 0.0.0.0

Before I try to downgrade, I try using HFS as Webserver instead of IPO
but has no success yet.

All three Files exist on the IPOs Webserver:

My question now:
How can I delete this files, as I cant find them on the SDCARD,
or please point me to the location on the SD-Card where I can find them.

btw. I include System.log and Critical.log which just endless repeatedly show this:

Critical.log
[2000/01/01 00:01:38.214] HttpServer resetFlag ON. Reboots itself.
[2000/01/01 00:01:38.349] System goes down... (Use WatchDog timer for reset: 1)
[2000/01/01 00:00:12.712] *** Execute Firmware Update.
[2000/01/01 00:01:00.419] *** Firmware Update Success. Reboot Base Station.
[2000/01/01 00:01:00.557] Initialize D100 Base System Finish.
Firmware Version : D100_1.2.2_0.8.6
Hardware Version : 4
NV Version : 16
Firmware Side : 2 - 1
[2000/01/01 00:01:00.730] Synchronization_main() : System Reset.
[2000/01/01 00:01:00.887] System goes down... (Use WatchDog timer for reset: 6)
[2000/01/01 00:00:12.706] *** Execute Firmware Update.
[2000/01/01 00:01:00.420] *** Firmware Update Success. Reboot Base Station.
[2000/01/01 00:01:00.556] Initialize D100 Base System Finish.
Firmware Version : D100_1.2.2_0.8.6
Hardware Version : 4
NV Version : 16
Firmware Side : 2 - 1
[2000/01/01 00:01:00.730] Synchronization_main() : System Reset.
[2000/01/01 00:01:00.890] System goes down... (Use WatchDog timer for reset: 6)
[2000/01/01 00:00:12.827] *** Execute Firmware Update.
[2000/01/01 00:01:00.521] *** Firmware Update Success. Reboot Base Station.
[2000/01/01 00:01:00.659] Initialize D100 Base System Finish.
Firmware Version : D100_1.2.2_0.8.6
Hardware Version : 4
NV Version : 16
Firmware Side : 2 - 1


System.log
[2000/01/01 00:00:55.414] 0010 [E] HTTP Client Return Error:260
[2000/01/01 00:01:00.419] *** Firmware Update Success. Reboot Base Station.
[2000/01/01 00:01:00.553] 0011 - succes.
[2000/01/01 00:01:00.555] Initialize D100 Base System Finish.
Firmware Version : D100_1.2.2_0.8.6
Hardware Version : 4
NV Version : 16
Firmware Side : 2 - 1
(Base Information)
Serial ID : SID:78E7D183877C124EEE9EE861
MAC Address : 00:E0:11:0B:17:B3
RF ID : 01:85:80:4E:18
CLOCK ADJUST : 11:03:04
BANDGAP ADJUST : MST-09, SLV-08
MARKET(0:GL/1:EU): 1
UserAgent(0:D100): 0
BootStrap(0:Normal): 0
Number of Regist : 2
(Handset Information)
LOGIN MAP : 0x00
REGISTRATION INFO:
[1] 018570170a0185804e18018570170affffffffffff
[2] 0169d117f7f92939cba0d6a20cf5014254e58cb798
[3] ffffffffffffffffffffffffffffffffffffffffff
[4] ffffffffffffffffffffffffffffffffffffffffff
[5] ffffffffffffffffffffffffffffffffffffffffff
[6] ffffffffffffffffffffffffffffffffffffffffff
[7] ffffffffffffffffffffffffffffffffffffffffff
[8] ffffffffffffffffffffffffffffffffffffffffff
USER INFO :
[1] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[2] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[3] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[4] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[5] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[6] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[7] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[8] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[2000/01/01 00:01:00.730] Synchronization_main() : System Reset.
[2000/01/01 00:01:00.890] System goes down... (Use WatchDog timer for reset: 6)
[2000/01/01 00:00:00.374] 0000 HS9 EVENT_ENTER_TESTMODE
[2000/01/01 00:00:02.015] 0001 [NetStack Initialize] Stored IP address(172.24.2.103) assigned.
[2000/01/01 00:00:09.183] 0002 HS2 [PRESS] RADIO_DISC
[2000/01/01 00:00:12.016] 0003 Try to Connect Configuration Server...
[2000/01/01 00:00:12.141] 0004 [/D100.cfg] reading.
[2000/01/01 00:00:12.315] 0005 - finished.
[2000/01/01 00:00:12.315] 0006 [/D100prov.txt] reading.
[2000/01/01 00:00:12.478] 0007 - OK. There is no difference between Provisioning File and current settings.
[2000/01/01 00:00:12.479] 0008 [/D100settings.txt] reading.
[2000/01/01 00:00:12.641] 0009 - finished.
[2000/01/01 00:00:12.689] *** Execute Firmware Update.
 
Upvote 0 Downvote
As pointed out above, this issue is fixed in 9.1.3.
 
Upvote 0 Downvote
Oh sorry. I mixed up some things while looking for the actual firmware for the IPO.

On the above Link:
was a hotfix for v9.1.1 and this was before "my" version v9.1.2 which I thought was the actual IPO version
and SP3 only release for Server Edition yet.

But after your note I found SP3 / v9.1.3 and after Installation I get an Login Config on the D160 Handset
so it looks good. Seem I just have to complete the User Login.

Thank you very much!
 
Upvote 0 Downvote
... Update for:
Luzie67 said:
"Seem I just have to complete the User Login."
Click to expand...
...:

Yes, after creating an SIP DECT Extension following the AVAYA manual
"Avaya D100 Installing and Administering IP Office D100 100174766.pdf"
the D100 / D160 combination works well.
 
Upvote 0 Downvote
Maybe the problem is back with IPO 9.1 SP4 ?
So it looks for to me today.

Have to test on another IPO which I upgrade from SP3 to SP4
to verify this and then report this back here ...

Update: With an IPO updated from SP3 to SP4 there seem to be OK:
I can delete and create D100 without problems.
(Three Config-Files D100.cfg, D100settings.txt and D100prov.txt
are not deleted when I delete the SIP DECT-Line / SIP-DECT-Extension and User)

But I have another IPO updated yesterday from SP2 to SP4
and there I have to investigate further because I have trouble getting D100
to work there...
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

bwbwbw
  • Question Question
VM Pro Failure Fallback not working
Replies
1
Views
122
derfloh
derfloh
claudiotele
  • Locked
  • Question Question
Sip Trunk over TLS not working
Replies
7
Views
796
Mo. Abdullah
Mo. Abdullah
William C290
  • Locked
  • Question Question
Authorization Codes Not Working on SE Expansion L
Replies
4
Views
632
sizbut
sizbut
AndoverService
  • Locked
  • Question Question
SCN 9.1 closes after save
Replies
2
Views
574
Mo. Abdullah
Mo. Abdullah
Rhinorhino
  • Locked
  • Question Question
Time & Date 9.1
2
Replies
20
Views
3K
comfortinntechci.com
comfortinntechci.com

Part and Inventory Search

Sponsor

Back
Top