Avaya D100 Base Won't Connect 1

[DrewNapa]

Hello guys, I've been digging around the forums here trying to figure out how to get a D100 base that I recently purchased two of second hand, to work on our Avaya system. I followed the instructions as far as setting up a Line/User/Extension in IP Office Manager and set it to DHCP for the IP Config part of the base. I can register my D160 to the base but the phone always says No Config when we try to use it. Also, when I go to System Status in IP Office, it can't detect the base's Firmware version, so I know it's not seeing it.

I couldn't connect to the Web Interface when hooking it up to our normal network switches that the Avaya is on along with our computer that can access IP Office, so I factory reset the base a few times now by holding the registration button and putting a pin into the reset hole. I then took the base and hooked it up to our wireless router and told the router to assign a static IP to it via the MAC address to the default IP address of 192.168.1.100 and eventually I could finally connect to the Web Interface. I then changed the settings in the web interface from the information that was in there still even after having factory reset it several times, to DHCP.

I then put it onto the network again that the Avaya IP Office computer and Avaya system was on and tried to get it to connect again with no success. I tried to access the Web Interface from the computer and couldn't get it to connect to it either. It seems the only time I can access the Web Interface is when I plug it into a router that assigns it a static IP and even then when I save the setting for DHCP, it doesn't seem to work right once on the network.

 

[redswine]

This is the guide I always use. It was written by someone on here awhile back. These things are finicky, and I have found that sometimes I have to factory default them multiple times to get working. Good luck...



TO PROGRAM A D100 BASE INTO THE IP OFFICE MANAGER:

1. Go to System/LAN1/VoIP and check the box for SIP Registrar Enable.

2. Go to the LINE menu, right click and select new -> SIP DECT Line.

3. Enter a Base Name.

4. Enter the MAC address of the D100 base.

5. Check the box for Configure Base IP.

6. Uncheck the box for DHCP Client.

7. Put in the IP address the d100 base will use, the subnet mask and the gateway of the network.

8. Set the Provisioning Server as the IP Office’s LAN address.

9. On the VoIP tab, leave all settings default.


TO CREATE EXTENSIONS AND ASSOCIATED USERS:

1. Go to the EXTENSION menu, right click and select new -> SIP DECT Extension.

2. Put in the Base Extension Field an extension that will match your user’s extension number.

3. On the SIP DECT base tab, select the D100 base that this extension will be associated with.

4. Click OK and click YES to create an associated user.

5. You will automatically be placed into User programming for the user created.

6. Set the name and other common settings.

7. Go to Telephony/Supervisor Settings tab and assign the user a Login Code.

8. Merge the settings in the IP Office.


TO ASSIGN THE D100 BASE AN IP ADDRESS:

**NOTE: The D100 base stations seem to not always respond correctly to reboots or re-initialization.

1. Re-Initialize the D100 base by simultaneously holding down the reset button and the

registration button, both located on the front of the base, for 5 seconds. A quick green flash

seems to indicate that you’ve held it down long enough, you can then let go of the two buttons.

2. Connect to the defaulted base at its default IP address of 192.168.1.100. The username and

password is d100.

3. Change the IP address settings to what static IP address the base should be.

4. Change your PC’s IP address to be on the same subnet of the base and make sure the base

responds to a ping.

5. If it responds to a ping, move the base to the actual network that the IP Office resides on.

6. The base should see the IP Office and have solid blue and green lights.


TO REGISTER AN AVAYA D160 HANDSET TO THE D100 BASE:

1. While connected to System Status, go to the d100 base and click on allow registration.

2. On the d160 handset, click Registration.

3. It will ask to enter PIN, enter 3100 (for d100)

4. Press Login, and enter the extension the d160 should be.

5. Enter the password for the extension. (in Manager/Users/Telephony/Supervisor Settings/Login

Code)

6. The d160 should now work!

 

[DrewNapa]

I definitely appreciate the help, these were the instructions I've been trying to follow somewhat. I was trying to get around assigning it a static IP address since I wasn't entirely sure I knew enough to do it properly but I ended up trying it again and was finally able to assign it a static IP that I can connect to using the Web Management page on the computers with access to Avaya and the IP Office program.

So now it has the static IP and matches IP Office's information about the static IP, but that's about it. I can connect to the Web Management page via the IP address that I assigned it that is also the same as in IP Office, but when I look at System Status of the Base, it still doesn't show what firmware it's using and the handsets still say No Service. I'm not entirely sure what to do next now.

 

[snowman50]

There were some issues on loading the firmware files to the d100 on some versions of Ipo.

So can you please provide this information software version etc.

Did you try a google search for this.

 

[TouchToneTommy]

Browse to the D100 Base
Go to “Update Firmware of Base Station” > “Check Firmware update”
Confirm if there is a newer version of firmware available from your IP Office
If so, click the button for Firmware Update
When it finishes, it will be back on DHCP mode, so you may have to run something like Advanced IP Scanner to find it, or use the paper clip to return it to 192.168.1.100 and go back and set to the desired default IP

 

[snowman50]

thread940-1748603

Check this thread

 

[DrewNapa]

I'm running IP Office 8.1 and when I go to update firmware on the D100's Web Management page, it says it's running D100_0.9.6_0.9.6 and that the newest one is the same number. I googled the problem and came across ton's of different threads with D100 problems, usually with people responding that the D100 is junk or listing different answers that didn't quite apply to my situation, or if it did I wasn't smart enough to know it. I'll read the listed thread next and see if that will shed some light on what to do next. Thanks again for the help so far, I haven't worked on IP Phones or Avaya much at all besides tinkering around in IP Manager for simple things so I'm not an expert by any means.

Also, another question I have is about the "Licenses" for Avaya needed to run these D100's. Is there a way to know if I have enough licenses on our system already or if this is part of my problem? I pulled the System Log from the D100, but I'm not sure if it's telling me anything of value.

[2000/01/01 02:18:49.825] 2483 [D100_Spanish.lng] reading.
[2000/01/01 02:18:49.841] 2484 Date: Wed, 23 Sep 2020 23:48:12 GMT
[2000/01/01 02:18:49.842] 2485 Server: IPOffice/8.1(73)
[2000/01/01 02:18:49.843] 2486 Content-Length: 15080
[2000/01/01 02:18:49.844] 2487 Last-Modified: Mon, 12 Aug 2013 19:34:28 GMT
[2000/01/01 02:18:49.845] 2488 Content-Type: text/plain
[2000/01/01 02:18:50.727] 2489 - finished.
[2000/01/01 02:18:50.728] 2490 [D100_French.lng] reading.
[2000/01/01 02:18:50.745] 2491 Date: Wed, 23 Sep 2020 23:48:12 GMT
[2000/01/01 02:18:50.746] 2492 Server: IPOffice/8.1(73)
[2000/01/01 02:18:50.746] 2493 Content-Length: 15036
[2000/01/01 02:18:50.747] 2494 Last-Modified: Mon, 12 Aug 2013 19:34:30 GMT
[2000/01/01 02:18:50.748] 2495 Content-Type: text/plain
[2000/01/01 02:18:51.625] 2496 - finished.
[2000/01/01 02:18:52.503] 2497 - succes.
[2000/01/01 02:18:52.504] 2498 Try to Connect SIP Server...
[2000/01/01 02:18:52.506] 2499 [E] HTTP Client Return Error:-1
[2000/01/01 02:18:52.507] 2500 [E] No Connection SIP Server.
[2000/01/01 02:21:52.508] 2501 Try to Connect Configuration Server...
[2000/01/01 02:21:52.508] 2502 [/D100.cfg] reading.
[2000/01/01 02:21:52.565] 2503 Date: Wed, 23 Sep 2020 23:51:14 GMT
[2000/01/01 02:21:52.566] 2504 Server: IPOffice/8.1(73)
[2000/01/01 02:21:52.567] 2505 Content-Length: 803
[2000/01/01 02:21:52.567] 2506 Last-Modified: Tue, 22 Sep 2020 01:40:43 GMT
[2000/01/01 02:21:52.568] 2507 Content-Type: text/plain
[2000/01/01 02:21:52.579] 2508 - finished.
[2000/01/01 02:21:52.579] 2509 [/D100prov.txt] reading.
[2000/01/01 02:21:52.636] 2510 Date: Wed, 23 Sep 2020 23:51:14 GMT
[2000/01/01 02:21:52.637] 2511 Server: IPOffice/8.1(73)
[2000/01/01 02:21:52.637] 2512 Content-Length: 224
[2000/01/01 02:21:52.638] 2513 Last-Modified: Tue, 22 Sep 2020 01:40:43 GMT
[2000/01/01 02:21:52.639] 2514 Content-Type: text/plain
[2000/01/01 02:21:52.643] 2515 - OK. There is no difference between Provisioning File and current settings.
[2000/01/01 02:21:52.644] 2516 [/D100settings.txt] reading.
[2000/01/01 02:21:52.733] 2517 Date: Wed, 23 Sep 2020 23:51:14 GMT
[2000/01/01 02:21:52.734] 2518 Server: IPOffice/8.1(73)
[2000/01/01 02:21:52.735] 2519 Content-Length: 326
[2000/01/01 02:21:52.735] 2520 Last-Modified: Mon, 12 Aug 2013 19:34:28 GMT
[2000/01/01 02:21:52.736] 2521 Content-Type: text/plain
[2000/01/01 02:21:52.742] 2522 - finished.
[2000/01/01 02:21:52.793] 2523 [D100_Italian.lng] reading.
[2000/01/01 02:21:52.811] 2524 Date: Wed, 23 Sep 2020 23:51:14 GMT
[2000/01/01 02:21:52.812] 2525 Server: IPOffice/8.1(73)
[2000/01/01 02:21:52.813] 2526 Content-Length: 14870
[2000/01/01 02:21:52.814] 2527 Last-Modified: Mon, 12 Aug 2013 19:34:28 GMT
[2000/01/01 02:21:52.814] 2528 Content-Type: text/plain
[2000/01/01 02:21:53.730] 2529 - finished.
[2000/01/01 02:21:53.730] 2530 [D100_German.lng] reading.
[2000/01/01 02:22:12.913] 2531 Date: Wed, 23 Sep 2020 23:51:15 GMT
[2000/01/01 02:22:12.914] 2532 Server: IPOffice/8.1(73)
[2000/01/01 02:22:12.914] 2533 Content-Length: 15085
[2000/01/01 02:22:12.915] 2534 Last-Modified: Mon, 12 Aug 2013 19:34:30 GMT
[2000/01/01 02:22:12.916] 2535 Content-Type: text/plain
[2000/01/01 02:22:13.619] 2536 - finished.
[2000/01/01 02:22:13.620] 2537 [D100_Spanish.lng] reading.
[2000/01/01 02:22:13.697] 2538 Date: Wed, 23 Sep 2020 23:51:35 GMT
[2000/01/01 02:22:13.698] 2539 Server: IPOffice/8.1(73)
[2000/01/01 02:22:13.699] 2540 Content-Length: 15080
[2000/01/01 02:22:13.699] 2541 Last-Modified: Mon, 12 Aug 2013 19:34:28 GMT
[2000/01/01 02:22:13.700] 2542 Content-Type: text/plain
[2000/01/01 02:22:14.627] 2543 - finished.
[2000/01/01 02:22:14.627] 2544 [D100_French.lng] reading.
[2000/01/01 02:22:14.645] 2545 Date: Wed, 23 Sep 2020 23:51:36 GMT
[2000/01/01 02:22:14.645] 2546 Server: IPOffice/8.1(73)
[2000/01/01 02:22:14.646] 2547 Content-Length: 15036
[2000/01/01 02:22:14.647] 2548 Last-Modified: Mon, 12 Aug 2013 19:34:30 GMT
[2000/01/01 02:22:14.648] 2549 Content-Type: text/plain
[2000/01/01 02:22:15.534] 2550 - finished.
[2000/01/01 02:22:16.414] 2551 - succes.
[2000/01/01 02:22:16.414] 2552 Try to Connect SIP Server...
[2000/01/01 02:22:16.416] 2553 [E] HTTP Client Return Error:-1
[2000/01/01 02:22:16.417] 2554 [E] No Connection SIP Server.

 

[DrewNapa]

I read through the other thread posted and it mainly talks about updating the firmware on the D100 while using IP Office 9.1 or so. My D100 shows it's currently running the latest firmware offered by my IP Office Manager, but again my IP Office Manager is still at 8.1. Is there a way to know if it's a licensing problem or something else?

The D100 is now on the same network as the IP Office Manager and I can login to the Web Management page via the static IP address I assigned it and I'm also able to successfully ping it. However, IP Office Manager's System Status still doesn't show the base's Firmware version, so I'm guessing that's why the cordless D160 that's registered to the base still says No Service, meaning they're still not linked together somehow. I've followed the instructions to the letter this time, which is how I can finally access the Web Management page on the same computer that has IP Office but now I'm at a loss as to how to get the base and system to link.

 

[hotelmotelpatel]

Are the D100 base's R1.1? If your using IP Office 8.1, you will need the d100 base to be a 1.0 to properly connect to the IPO.

 

[DrewNapa]

Are you referring to the software of the base or a hardware version of the base? I wasn't aware there was different hardware versions. Software wise, it says it's running D100_0.9.6_0.9.6 and that my IP Office Manager has that as the newest version available. I'm unsure how to "delete" the d100.cfg files or similar ones off of the SD Card in order to possibly make the D100 reinstall the current firmware from the IP Office.

How can I tell if my problem is a licensing problem? It never gave me an error when I tried to install the line or anything like that in IP Office but I have no idea what licenses our system has since it was bought by the previous owner of the business here from long ago.

 

[hotelmotelpatel]

On the base itself,you will see the release of the base, 1.0 or a 1.1, This is a issue that many techs have had. If your using any thing lower than a 9.1 IPO, you will need to use a hardware version of 1.0. I have set many of these up. For licensing, all you need is IP Endpoint, and some type of VCM channels, (VCM 32, VCM 64, or Combo card). Also make sure you set the file server type to memory card in your system Tab. You can always put it back to manager or custom after it downloads it files into the base.

 

[DrewNapa]

I definitely appreciate the help hotelmotelpatel, I know my way around computers but I've never really worked on Avaya or IP Phone systems in general and so I'm trying to my best to learn it as quickly as I can but obviously I have a long ways to go yet.

The base has a sticker on it that says 1.0, so I assume that's the release version you were referencing. So the license I have on IP Office Manager says it's an Essential Edition license. Unfortunately I have no idea about the VCM channels part, but the IP Office Manager says in the System tab that the Phone File Server Type is already set to Memory Card.

 

[hotelmotelpatel]

Not a problem, everyone goes through a learning process. The first step is to login to manager, check your license's, along with the essential license, you will require a IP endpoint license. The VCM channels, you can check your control unit tab, you will see what cards are inserted into the system. You need to look for a VCM 32, VCM 64, or a Combo card. All three cards supply VCM channels. Once you confirm if you have available IP endpoint license and have a card that supplys VCM channels. We can take it to the next step. The good thing is that the 1.0 base you have will work fine with your IPO R8.1.

 

[DrewNapa]

Okay so I looked at the Licenses which says (1) next to it and only displays a tab which says Essential Edition under it, so I must be missing an Endpoint License. Under the Control unit tab, it lists (1) IP 500 V2, (2) Combo6210/ATM4 V2, (3) Combo6210/ATM4 V2. I've been trying to look online for an Avaya IP Office 8.1 IP Endpoint License to purchase and there seems to be very few vendors with any at all. But since I didn't see anything that talked about VCM channels under the Control Unit Tab, would getting a license be pointless even if I could somehow find one?

 

[TouchToneTommy]

In 9.1, the SIP Registrar box on the VoIP tab of the LAN port came unchecked. I know I wasted an entire day checking all of my D100 programming before finding that, and although you're on 8.1, confirm that your SIP Registrar is checked.

 

[DrewNapa]

I appreciate the tip, the weird part is when I went to set up the SIP Registrar box at the beginning, the box was already checked and enabled. Yet it appears I don't have the licenses for making a D100 work possibly so I have no idea why it was already enabled.

 

[hotelmotelpatel]

You can not buy a IP endpoint for 8.1 anymore, Avaya Did away with the ADI license. They want everyone to upgrade to R10/R11. But to get around this, You can Purchase a VCM 32 V1 or a VCM 64 V1. They will create virtual IP endpoints. This will give you your IP endpoint you need with out upgrading your system. TouchToneTommy is right, that the SIP register box in the Voip tab has to be checked. But before you do all your programming, you need your Prerequisites. Do not get a VCM 32 or VCM 64 V2, they do not create virtual IP endpoints. Avaya IP500 VCM 32 Base Card (700417389)is what you need.

 

[DrewNapa]

Thank you very much hotelmotelpatel, I'm going to do some searching online for 700417389 to see if I can purchase one. If I find one and purchase it, will the installation to my current system be somewhat simple or would that require me having to reprogram IP Office altogether for this new card?

 

[hotelmotelpatel]

Power down the IPO, insert the VCM V1 card into an available slot, power up the IPO. If you look at your license's, you will now have 12 Virtual IP endpoint license's.

 

[DrewNapa]

Amazing, thank you so much for your help. I'll find one of those parts and get it installed and hope that my D100 FINALLY connects. Thank you so much again.

One last question though, did my system definitely not have the capability already for the vcm based off what I said was in the controllers tab and so buying this part is definitely my problem and won't work with the D100 otherwise?