Search results for query: *

From the https://www.tek-tips.com/threads/openscape-4000v10-cdr-local-unanswered-calls-are-missing-in-cdr.1828243/: "Either SELG (SELT) THRGCON setting to N (Y means 'only through connected', so setting N collects more, not less), or ZAND CCD CDRRINGB to YES (cdr for ring back), or setting both...

Changing time directly on Linux-Host command line, if duplex do on both processors: # date -s 17:25 or # date -s "YYYY-MM-TT hh:mm:ss" # date -s "2012-12-31 09:51:24" => date & time. changed

The LOGBK does not contain any informations about the logon attempts (successful nor unsuccessful) - only the entered AMOs are visible.

Is there any possibility to see logon attempts from ComWin inside RMX?? In HistaFile or LogBK there aren’t such informations available. Any ideas?

In our case, the problem was solved after the parameter "ZAND/ALLDATA2/CONFTONE" has been set to "NO" (workaround solution). The official solution ( provided from product house) is included in the OpenScape4000 RMX-Hotfix 8 for V10 R1.42.0.

Try with: "vk_activate -c AScol".

One of the OS4kV10R1 duplex node, reports the problem as in the title (see attached file for more details). What can/should be done in such situation?https://files.engineering.com/getfile.aspx?folder=2acc5872-9c62-46d9-9054-b4f59c2076ec&file=Node2.txt

We have noticed some problems with the HD. Furthermore - there are some AMOs that can be executed on the APE (for ex. UPDAT, HISTA...)

We have old system with APE module (HiPath 4000 V5). We have to check HD (AMO DVU) but this AMO can't be run on CC-AP. "THE CALLED AMO ACTION IS NOT ALLOWED TO RUN ON CC-AP" Is there any hint to force CC-AP to run AMOS?

Our customer need a following solution: after an identification with a PIN of a virtual subscriber, the SRCGRP of this virtual subscriber will be taken into account, and not the SRCGRP of the home subscriber. At present, the OS4k takes into account the KNNR/NNO of the virtual subscriber, but...

I would do what you write (raise a ticket with Unify) but it is OS4kV8 (end of support)...

After activation of the A9.115 loadware, there was a flood of F5870 messages from EnterpriseGWs - for example: F5870 E8 N5220 NO ACT BPA BOARD LW EXCEPTION 22-10-17 09:28:47 ALARM CLASS:CENTRAL:002 P919:LTG1 :LTU19:007: 00 : 0 Q2347-X EntGW/1 BST:01...

Try with the "CALLTYPE" parameter (AMO SDAT) set for the CMI DECT phone.

In our case it was definitely related with the AFR2 service and the ":PAS:FBT/FAULTFILE2" file, not with the HISTA and its tasks/files, as described in the documentation above. It was solved with: [ol 1] DEACTIVATE-AFR:LDU=AFR2,TYPE=PROT&LDU; STA-DEL:":PAS:FBT/FAULTFILE2"...

What H4k/OS4k version is it?

I think that in our case it is related with the AFR service and the ":PAS:FBT/FAULTFILEx" file, not with the HISTA and its tasks/files, as described in the documentation above.

Does anyone can say me something more about such error: F6524 E8 N1631 NO ACT A1 SM-AM MAINTENANCE 23-04-17 22:54:21 ALARM CLASS:CENTRAL:029 FORMAT:33 WARNING BY AFR TASK: FAULTFILE DAMAGED FAULTFILE WAS NEW INITIALIZED Many thanks in advance!

Found in the Unify Knowledge Base.https://files.engineering.com/getfile.aspx?folder=02bfa139-dba2-4fef-ae87-c179a2578274&file=After_installing_Java_version_1.8.0_351,_access_to_Assistant_Configuration_Managemen,is_blocked,_client_preparation_blocks_at_the_Java_related_step_(KB000105286).pdf

Ad.1 You can try with: "START-HISTA:RTYPE=SEARCH,CONTEXT=MID,MID=FM,NUM=2750;

I recommend: "dis-wabe:gen,,0&&15;" or "reg-wabe:,0&&15;