Hi raulbal
How big is Your system?
Send printout of command SYECP
If it is big system, changing the extensions numbers is a hard work.
I see that now You can have ca. 400 extensions
To change numbers you need PC-regen Excel and many time.
----------------------------------
If anything can go wrong, it will. (Murphy's Law)
;Initiate 70xxx excluding 70399 as extension number series.
nansi:numtyp=ex,numse=70000&&70398&70400&&70999;
;Initiate 70399 as new operator number nansi:numtyp=oi,numse=70399;
;only necessary parameters are stated in this example)
operi:dir=70399,equ=,prg=,traf=,type=;
;Change all extension numbers:
; this can be a lot of work depending on the amount
; of extensions.....so for a big site
; I would make a pcregen ini file
; where I'd use a text editor to
; put 70 in front of the existing numbers
KSDNCIROLD,DIR=;
EXDNCIROLD=,DIR=;
;Delete the old now unused extension number series:
nanse:numtyp=ex,numse=300-398;
nanse:numtyp=ex,numse=400-499;
nanse:numtyp=ex,numse=800-992;
nanse:numtyp=ex,numse=994-999;
;Initiate the common operator number:
nansi:numtyp=oc,numse=9;
opcoi:coacc=9;
Now also mind NUTRI as the incoming number on DID lines has changed.
But for now I think you 'll have enough work already!
______________________________
"Reload and Restart Requested
System Initiated"
Hi summerdike
Command
KSDNCIROLD,DIR=;
EXDNCIROLD=,DIR=;
are not recommended, very oft this command is blocked or erased from system.
After this command data corruption is guaranty
I never use this commands
What happened ( after xxDNC command ) with groups (GH GP etc) or RODNx DAY= NIGHT=’?
In CDINx DIV will be changed too?
----------------------------------
If anything can go wrong, it will. (Murphy's Law)
<SYECP:LIM=1;SYSTEM EQUIPMENT CONFIGURATION
INITIATED LINE INDIVIDUALS IN LIM 1
INTERNAL LINES: ANALOGUE 288
DIGITAL 28
CAS
POTS
ITS
OPERATOR 1
DATA
DUAL
PUBLIC LINES: ANALOGUE 8
DIGITAL
ISDN S0
ISDN S2M 60
H.323
PRIVATE LINES: ANALOGUE
DIGITAL
APNSS
DPNSS
ISDN S0 7
ISDN S2M
H.323
END
<
I don't think its advisable for Pcregen- INL keeping in mind the level of expertise raulbal has...
Summerdike has given all the commands in sequence which are good enough for him to do the changes for the time being...In case of KSDNc errors he can fix it by
KSEQC: New vacant position & back
KSEQC:Old position...
It will not disturb any other traffic only the problematic extension will be handled out...
Raulbal: Once you are confident making up a LIM from scratch then you can think about INL procedure...
Cheers,
""The truth about action must be known and the truth of inaction also must be known; even so the truth about prohibited action must be known. For mysterious are the ways of action""
I change my mind about copy configuration MD data for editing.
You MUST use PC-regen to collect and store configuration in human language.
But I see a big problem (maybe I’m wrong) you have old version of SAM (probably 3.6) and BC 12 or higher (12.1) in consequence not correct version of PC-regen. My investigation
You send a printout of command SYECP and
1
in this printout public and private line have position H.323. This option is available from BC 12
2
<SYECP:LIM=1;SYSTEM EQUIPMENT CONFIGURATION
Command and answer in this some line. It was a problem with WinFiol from SAM 3.6 and BC 10 (or higher) with NIU and connection via Ethernet.
And now is my test after this test I always thing that command xxDNC is wrong and data corruption is guaranty
I crate two extensions KS 2012 and EX 2046
Than make diversions and GP group and after change number using command xxDNC
[tt]
<KSEXIIR=2012,CAT=21,EQU=1-0-22-04,ITYPE=26;
EXECUTED
END now all is OK Numbers changes
<ksdnc:dirold=2012,dir=2013;
EXECUTED
<exdnc:dirold=2046,dir=2047;
EXECUTED
<sudip:dir=2012&2046;
NOT ACCEPTED
DIR=2012
DIRECTORY NUMBER(S) NOT ASSIGNED
<sudip:dir=2013&2047;
DIRECTORY INFORMATION AT 22:03:21 31JUL05
DIRECTORY NUMBER : 2013
TYPE OF DIRECTORY NUMBER : DTS
NAME :
Regarding your test changing numbers with EXDNC and KSDNC:
All I see in the printouts is that after the number changes the diverison data are gone. This to me sounds like a minor problem, if it is a problem at all.
I assume you tried to print out the call pick up group data with the command GHDAP but that is the Group Hunting Data Printout .
For Call Pick Up data the command GPDAP applies.
MD110 shows in the printout SUDIP that number change is followed correctly by Group Call Pick up.
______________________________
"Reload and Restart Requested
System Initiated"
Engineering the Md110 requires a group of programs called SAM toolbox.
One program in there is called PCregen (from PC regeneration).
It can make a back up off all the Exchange data in the MD110.
A complete backup (including program units) is available on the HDU or NIU2. It is called REL1 directory.
You can make a copy of this backup with the means of a an FTP client program (like Win commander or another).
This operation requires NIU/NIU2 (the FTP server part).
In the ftp client program connect by ip address to the MD110 (requires username password of a certain level, mostly level 5).
Path on HDU to Rel1 is //usr1/ses/dr/Rel1
______________________________
"Reload and Restart Requested
System Initiated"
COMMAND:> LIST
STATUS:> Connecting FTP data socket 172.24.177.231:2565...
150 Opening data connection for (Opening data connection for (Opening data co) (172.24.177.231,2565).
226 Closing data connection.
STATUS:> Getting listing "/ USR1"...
COMMAND:> TYPE A
200 Command okay.
COMMAND:> CWD / USR1
521 "/ USR1" is not a directory
ERROR:> Permanent completion problem reply.
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.