Recent content by lisluk

You can try to use the ECMA1 protocol, instead of the ECMAV2.

AFAIK, all the OpenStage T phones models should work connected to H4kV4R4, without additional patches, etc.

@sbcsu See the attached file - I hope it helps you. BR

cd /opt/pal/bin ./lan

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)...