The maintenance console software I have installed does work with v6. I do not have the original registration file -- we are the third firm to work on the project. My assumption is that it can be re-registered using the ROM ID.
Thank you. Yes the latest is v6 from what I see in the maintenance console install. Is there a reason not to migrate from v3 to v6? Are there potentially breaking changes that would disrupt the existing programming or potentially require other card updates as dependencies?
Getting closer. The root of the problem is the ksu firmware is not high enough. Currently at v3 but it would appear that the card was introduced with v4 and this is why it is unrecognized and not in the available card options. Now, trying to track down v4 firmware.
Not to my knowledge. If I power down and remove the card, then connect and view slots, it is empty and there is no fault condition.
I then tried to add the card to programming before installing the card, but again, I don’t find the card type in the list. The only one I see that is close is the...
I am using the PBX Unified Maintenance Console 7.8.2.0, but this includes 7 versions for TDA50. When I connected via USB, the console window reported version 3.0.1.24 and this leads me to believe the TDA50 is at 3.0.1.24
I am using the 3.0.1.24 version of the PBX Maintenance Console and after we added the card, there is a fault-unacc error on the slot page. I do not see the IP-EXT4 in the list of available cards to install, but the manual does show this as an acceptable card for this KSU model. The KSU is...
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.