The OS4k IP Solutions manual contains this scenario.
You need to add a MEK manually for the new AP in Assistant (exact option was mentioned by adibv above) and then add the same MEK on the NCUI. The MEK is any 16 characters string.
Moriendi - you are right, also, if it were the date bug, the year should be 2014 -not 2012- and only on the ADP&SWU, not in Assistant. The exe-date workaround still makes sense imo in this case to have a correct date on the phones and in charging records. Of course, setting an NTP server is...
Once you change the location to testlab, it's exe-date, not cha-date, if you want to set a separate date and time in the ADP. Make sure to set the last parameter to NOSYNC, otherwise the ADP will still get the (wrong) date from the 4k linux platform. But this is just a workaround. For V6 R2.17...
The feature is rather well described in the 4k service manual (feature usage examples).
Calling party needs the attribute BROADCST. It has to dial the WABE BROADCST code or press the BROADCST key, followed by the number of a keyset that has an appearance on up to 40 other keysets. You need to...
The standby CC restarts are indeed related to the missing attendant group configuration, the user address is the same in the advisories.
On the active side you only get a DBAR as CP tries to handle a call for which interception to attendant group would make sense, but on the standby side when...
These messages might be related, but they are not showing the cause of the restart, you need to take a larger portion of the Hista around the time of the restart, usually the relevant messages are marked accordingly with something like HARDREST or SOFTREST right before the name of the SWU...
Ok, this means that FAMOS was locked - if it was done by the system, then you should see in the Hista a related advisory. Also, there is a V6 R2 patch that prevents the automatic blocking of FAMOS, included in RMX-HF11 for V6 R2.17.
Assuming you are talking about a HiPath/OpenScape 4000, if you are using PTIME block 87 for your trunks, with parameter S12 you can have an automated release of connection after a certain time, but this will happen regardless of state, so it might interrupt an ongoing call.
Otherwise, the...
Try first act-famos:famos;
If after this you still cannot connect with ComWin, then restart the ADP.
You have a dual system (ADP and SWU running in separate machines), so an ADP restart doesn't impact telephony, but CSTA applications (like OSCC, UC, DTB, BLF) will be (shortly) disconnected.
You should be able to connect to the ADP via telnet on the Atlantic LAN.
Connect via ssh (using PuTTY for example) to the OS4k Assistant, and run from there
telnet 192.0.2.3
After inputting the credentials, run
TSN;
You'll get a list of active connections, if you see 12 connections for logical...
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.