C:\Users\Administrator.VIA>esentutl /g c:\windows\NTDS\ntds.dit /!10240 /8 /o
Initiating INTEGRITY mode...
Database: c:\windows\NTDS\ntds.dit
Temp. Database: TEMPINTEG2872.EDB
Checking database integrity.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................
Integrity check successful.
Operation completed successfully in 2.188 seconds.
file maintenance: info
Drive Information:
C:\ NTFS (Fixed Drive ) free(44.2 Gb) total(98.8 Gb)
DS Path Information:
Database : C:\Windows\NTDS\ntds.dit - 34.1 Mb
Backup dir : C:\Windows\NTDS\dsadata.bak
Working dir: C:\Windows\NTDS
Log dir : C:\Windows\NTDS - 30.0 Mb total
edbres00002.jrs - 10.0 Mb
edbres00001.jrs - 10.0 Mb
edb.log - 10.0 Mb
file maintenance: Recover
Initiating RECOVERY mode...
Log files: C:\Windows\NTDS.
System files: C:\Windows\NTDS.
Performing soft recovery...
Database recovery is successful.
It is recommended you run semantic database analysis
to ensure semantic database consistency as well.
C:\Users\Administrator.VIA>esentutl /ml c:\Windows\NTDS\edb
Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.1
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Verifying log files...
Base name: edb
Log file: c:\Windows\NTDS\edb.log - OK
No damaged log files were found.
Operation completed successfully in 0.282 seconds.
C:\Users\Administrator.VIA>esentutl /p c:\Windows\NTDS\ntds.dit /!10240 /8 /o
Initiating REPAIR mode...
Database: c:\Windows\NTDS\ntds.dit
Temp. Database: TEMPREPAIR3184.EDB
Checking database integrity.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................
Integrity check successful.
Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
repair, the database will be rolled back to the state
it was in at the time of that backup.
Operation completed successfully in 1.812 seconds.
C:\Users\Administrator>repadmin /syncall
CALLBACK MESSAGE: SyncAll Finished.
SyncAll terminated with no errors.
C:\Users\Administrator>repadmin /replsummary
Replication Summary Start Time: 2020-09-11 16:37:13
Beginning data collection for replication summary, this may take awhile:
....
Source DSA largest delta fails/total %% error
Destination DSA largest delta fails/total %% error
[trunk-bitrix]
exten => _X.,1,Noop(------Incoming-Call-From-Bitrix------) ;;; просто вывод для дебага в консоли
same => n,Set(CALLERID(num)=${PJSIP_HEADER(read,X-Extension-Number)}) ;;; назначение переменной
same => n,Goto(from-internal,${EXTEN},1) ;;; прыгает в контекст по умолчанию для обработки транков
[from-internal-custom]
Стандартный контекст FreePBX from-internal включает в себя контекст from-internal-custom. Создайте контекст с таким именем в файле extensions_custom.conf
и заданный там диалплан будет выполняться, как диалплан FreePBX.
# так срабатывает, но значение пустое
#exten => _X.,1,Set(CALLERID(num)=${PJSIP_HEADER(read,X-Extension-Number)})
#так не срабатывает
#exten => _300,1,Set(CALLERID(num)=${PJSIP_HEADER(read,X-Extension-Number)})
# а так пишет Executing [200@from-internal:1] Verbose("PJSIP/300-00000075", " VAR 600") in new stack
VAR 600
exten => _X.,1,Verbose( VAR ${PJSIP_HEADER(read,X-Extension-Number)} headers