Yeah, thanks but that's not going to work for me.. The network security where I work does not allow downloads from sites like this. I would need to be able to download it from Unify. And I can't download it to my personal PC and then transfer it from a thumb drive because all of the desktops do not allow a thumb drive to connect, or any portable media.. It's a real PITA sometimes.!
nope, can't get to either site... They have actually locked down our internet connection to anything not deemed necessary for work.. I was surprised I could still get to this site.. We are doing upgrades to our 4000s this year as soon as the Covid situation allows. I'm guessing I'll get the latest loadware at that time.. My CP200 phone is working now though, so thanks for all the help.
There isn't a public download for the phone firmware but Unify service partners have access to it, it should be no problem for your maintainer to provide you with the firmware.
Alternatively, you could maybe put sbcsu's downloads on a thumb drive and say, mount them on a linux box, and use winscp to bring to your PC.
Bonjour mes chers,
Mes excuses pour mon apparition dans le fil.
Svp aider moi,j'ai un Hipath 4000 v4.
J'ai activé l'AMOS CHESE c'est dire Secrétaire/Directeur pour une direction maintenant on souhaiterait qu'un numéro parmi N puisse joindre facilement le directeur sans passer par le secrétariat tout en gardant l'AMOS activé pour les autres.
L'AMO CHESE fonctionne comme prévu.
Si vous souhaitez outrepasser la fonction, vous pouvez mettre un code dans WABE for FWDIGNOR.
Utilisez ce code suivi du numéro de poste du gestionnaire pour l'appeler - vous devrez tester.
Faites une nouvelle bande de roulement en cas de problème.
Moriendi, I have access to the Unify Customer Portal, Atos / Unify is our provider.. Would I find it there? I was looking in the download area but couldn't find it.. My CP phone is up and working, I just wanted to go through the practice of updating the loadware.. I should mention that we do have a DLS, but it is not operational. After our upgrade to V7 it was moved to a VM and it was never configured.. I had very limited experience with the original DLS and haven't been able to get the new one fired up and functional.. Thanks SBCSU, I was unable to download that last file either..
I'm not sure what you'll see when you login, customer portal is likely different to partner portal, but if you see "Support" at the top, the downloads are in there under "Software Download".
If you post a screenshot of the page after you've logged in it might help.
If you have a service contract with Atos, you should just log a call to get that DLS working. There isn't much to it for 4K, it's more effort for OSV because OSV needs it for SIP mobility and to mass configure the phones. With HFA, the mobility features are a feature of the 4K itself (autoset relocate, mobile HFA etc), and almost all the other info is held in 4K DB so you don't need a DLS, apart from to flash the phones, and from CP phones, you don't even need it for that.
I discovered I do have access to the loadware. I went back and spent a little more time paying attention to details while reading and was able to find the loadware.. So one last question, (well maybe not last) I already have a DLS, and I did some poking around, and it looks like it has some connectivity to the 4000. When I looked under gateways, it did show all of my STMI cards. It does not however seem to have any stations in the database. Now I know that the option 43 setting on our DHCP is wrong, but if the option 43 was pointed to the correct IP of the DLS, would the stations automatically start registering in the database? Or do you need to have the DLS scan the IP range to go out and find the stations? And finally (no really) Would the DLS be a better choice for managing the IP phones compared to the IPSM ? Keep in mind that all of my IP phones that are used are either Optipoint or Openstage 15 phones... Thanks again for everyone's help, this has been really helpful!
You can't use IPSM for Optipoints or OS15 (CP phones only), so you'll have to use DLS. Which is a shame because IPSM is way, way simpler.
DLS syncs to the 4K using the config under "Element Manager", it logs in to the Assistant. You can look in the Element Manager and make sure it's periodically syncing, password is correct, etc. It's no use if it hasn't synced for a year. If the node code (I think) isn't populated in the element manager when you add the 4K, the 4K phones won't appear in the DB, so if you make a sync and nothing appears, check that.
To get the physical phones in the DB, you have to either scan them from DLS, or have the phones register on the DLS by giving them the DLS IP over DHCP. If you have issued the wrong DLS address, you can't then overwrite that by scanning them and telling DLS to give the phones the right one, you'll need to correct it in the DHCP server.
You can get duplicate entries in DLS by resyncing but specifying a different node number in the element manager, specifying a different node number on the phone etc (by that I mean via terminal number, sometimes people enter the full E164 in DLS but a node code+number on the phone terminal number), you have to pay attention. With a small site and one 4K it can be easier to just delete everything and start again, but even then the DLS might have configured some phones with node code+extn, and some with E.164 in the terminal number, so when you scan them again it's still a mess. HFA doesn't use the terminal number for registering on the 4K (like SIP does), HFA uses the system config page for that where you give it the subscriber number, 4K IP etc, but it will use terminal number to create host name and DLS uses it to populate the DB.
If you've never used it, you won't have these problems.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.