Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How to erase an analog extension ? 1

Status
Not open for further replies.

MDUserSergey

Programmer
Sep 16, 2002
43
0
0
RU
Hello, professionals. I need help.
I have an MX-One TSW sp6. And it works fine. But one of subscriber tell me Bye! And I need to erase his analog port from my TSW. But it is not erasing ! See it parameters:
<SUDIP:DIR=5730;
DIRECTORY INFORMATION AT 09:16:30 28JUN22
DIRECTORY NUMBER : 5730
TYPE OF DIRECTORY NUMBER : ATS
NAME : Exten
ADDITIONAL NUMBER :

EXTENSION TERMINAL DATA
EQU TERMD ADN
7-1-50-26 0000000

EXTENSION DIRECTORY CATEGORIES
CAT TRAF SERV CDIV ROC TRM ADC CUST LANG BSEC MCOST
4 01040401 0202120000 011131000 000001 0 010000001 4 - 0 -

EXTENSION MULTIPLE DIRECTORY NUMBER DATA
DIR KEY CALALT
*5730 - -
COMMAND LOST

<


And how can I erase it ? It is not work !
 
I will express my opinion on the topic.
A couple of times there were similar problems with the station when the station responded with COMMAND LOST. Both cases occurred after incorrect deletion of data or hardware.
In this case, it is not possible to solve the problem by restarting the program blocks. In one case, only lifting the station from the INL helped. In the second case, the manual correction of the data by the SACOS team helped.
The procedure was led by one respected member of this forum.
I suppose that in this case one of the above operations cannot be dispensed with.
Or, as an option, roll back to a system dump in which this problem has not yet been observed and then add data that has changed since the dump.
Good luck.
 
to ges69: I try. No way - COMMAND LOST ... It's pity.
to vkrt: Thanks. I find SACOS commands ... It's may be correct.
 
In order to carry out data correction by the SACOS command, it is necessary to have a thorough knowledge of the data storage structure in the station. Without this data, it is better not to use these commands.
 
vkrt is absolutely correct. You cannot fix corruption by restarting random program units. If you want to see what unit has corruption, first do HIREI. Then input a command which results in "command lost", then do HIMDP. You will see a lost signal which indicates where the corruption is. To recover the system to normal, you can reload from a system dump which was made before the corruption was caused ( unlikely available) or you must get someone with access to the PLEX data to use SACOS to manually remove the data. Last option is to INL the system and re-input the configuration with pcregen data(difficult if printouts are not working). I discarded my PLEXview years ago so cannot help, but if you are lucky, someone might step in and save the day (whosrdaddy maybe :)
 
to vkrt ; to himdp: Thanks !

Don't know how to start ... Look:

<HIREI;
WAIT
EXECUTED
<EXTEE:DIR=5730;
EXTEE:DIR=5730;
SURE? (YES/NO)
<Y;
NOT ACCEPTED
DIR 5730 IS
MULTIPLE REPRESENTED
<KSMDP:MDN=5730;
KEY SYSTEM MULTIPLE DIRECTORY NUMBER DATA
MDN DIR KEY CALALT
5730 *5730 - -
WAIT
COMMAND LOST

<HIMDP;

DIAGNOSTICS FROM OPERATING SYSTEM
TIME DATE
07:59:27 06JUL22
NO INFORMATION STORED IN LIM 001, LAST HIREI: 07:57:33 06JUL22
NO INFORMATION STORED IN LIM 002, LAST HIREI: 07:57:33 06JUL22
NO INFORMATION STORED IN LIM 003, LAST HIREI: 07:57:34 06JUL22
NO INFORMATION STORED IN LIM 004, LAST HIREI: 07:57:33 06JUL22
DIAGNOSTICS FROM LIM 005, LAST HIREI: 07:57:34 06JUL22

TIME DATE ERROR CODE
07:59:26 06JUL22 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 02019B5C
BRANCHVALUE = 00000000
ENTER
SWSW B-LEVEL SIGNAL READWRITEBRDRES (H'0070)
FROM DCP (H'07E) EXE A IN LIM 005
TO DCP (H'07E) EXE A IN LIM 005
NUMBER OF DATA BYTES IN SIGNAL = 62
WITH 0 1 2 3 4 5 6 7 8 9
000 01 60 86 01 00 25 12 1E 23 50
010 00 24 00 00 00 00 00 00 00 00
020 00 00 00 0F 7C 00 00 00 00 00
030 09 42 02 02 00 00 02 00 34 CE
040 00 00 00 00 00 00 00 00 00 00
050 20 22 07 06 07 41 34 00 3E 02
060 00 00

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 10 7A

TIME DATE ERROR CODE
07:59:16 06JUL22 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 02019B5C
BRANCHVALUE = 00000000
ENTER
SWSW B-LEVEL SIGNAL READWRITEBRDRES (H'0070)
FROM DCP (H'07E) EXE A IN LIM 005
TO DCP (H'07E) EXE A IN LIM 005
NUMBER OF DATA BYTES IN SIGNAL = 62
WITH 0 1 2 3 4 5 6 7 8 9
000 01 60 86 00 00 25 12 1E 23 50
010 00 23 00 00 00 00 00 00 00 00
020 00 07 00 05 00 00 22 06 00 00
030 03 00 00 00 FE FE 00 FF 88 88
040 02 00 5A 00 00 00 00 02 01 4F
050 2A 02 00 81 D2 00 00 00 4A B1
060 09 08

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 10 7A
NO INFORMATION STORED IN LIM 006, LAST HIREI: 07:57:34 06JUL22
NO INFORMATION STORED IN LIM 007, LAST HIREI: 07:57:34 06JUL22
NO INFORMATION STORED IN LIM 008, LAST HIREI: 07:57:34 06JUL22
NO INFORMATION STORED IN LIM 009, LAST HIREI: 07:57:34 06JUL22
NO INFORMATION STORED IN LIM 010, LAST HIREI: 07:57:35 06JUL22
NO INFORMATION STORED IN LIM 011, LAST HIREI: 07:57:35 06JUL22
DIAGNOSTICS FROM LIM 012, LAST HIREI: 07:57:34 06JUL22

TIME DATE ERROR CODE
07:58:21 06JUL22 H'13
FAULTY POINTER
LOGICAL PROGRAM ERROR ADDRESS = 02044790
ENTER
SWSW B-LEVEL SIGNAL FETDIRIND (H'003F)
FROM KHH (H'1C2) EXE A IN LIM 001
TO DER (H'17D) EXE A IN LIM 012
NUMBER OF DATA BYTES IN SIGNAL = 8
WITH 0 1 2 3 4 5 6 7 8 9
000 FF FF 00 00 23 01 C2 01

NO INFORMATION STORED IN LIM 013, LAST HIREI: 07:57:35 06JUL22

END


And You look that error type COMMAND LOST is earlier than last DUMP !
PBX do DUMP automatically every day (sorry, night). And that error exist any years ago. And it is a problem. Yes, to start-up a multi-LIM PBX - is a correct way. But there are a lot of subscribers in service. And I can't interrupt the service. Where do I begin ?
 
Long time since I was cheking the forum, no on vacation. So first of all, himdp and vkrt are 100% right. DO nOT start with random SACOS commands,or you destrroy everything there. Now, I need to see the PLEX (I think I still have it), but then, if you REALLY want to fix this, prepare for a bunch of traces and this and that. MDN is a very tricky issue, but hopefully it is DER. So I think your problem resides in LIM12 (not sure). If you are ready to work with this, let me know.
BR fcpli
 
to ficpli:
Yes. I ready to work with this. In the end of way I need to delete one of LIM and replace it to another office. It nessesary. And no way wirhout SACOS. But I dont know SACOS commands and no one time work with. And I listen what do You think about.
 
I need to delete 1 LIM from my big PBX. And then relocate it with new NIU to new office.
But in order to remove even 1 LIM, I must first remove all subscribers from this LIM in general.
In a new office it will a new organisation with a new exten numeration and new PBX owner. Not me.
New owner not need to make interLIM GS-lines longer. He need a new TDM-PBX. But in old location a 13-LIM PBX is so bigger than I need.
The new owner needs a 1-LIM PBX. And I need a 12-lim. That's why.
Some analog and digital subscriber ports are removed easily. But a few digital ports don't want to be removed at all. And I'm furious.
 
In that case, I'd rather pick up a 12 LIM station from INL. This will get rid of all current problems and upgrade to TSW sp8.
 
It's hard. In that case I need an INL of TSW sp8. I would like a link to this archive.
 
I unfortunately only have SP8 versions of the two regional versions EX and ST.
The rest were not interesting to me and I did not save them.
 
to vkrt:
Thank You for your link. I got it.
Than I must to read ALEX ...
It is very dangerous for my health to stop PBX for a start-up. In any case, this will be a reason for subscribers to refuse my local communication services.
But technical question is how to install my Ericsson licences from my sp6 packet to new sp8 TSW. I listen that non licensed PBX not work fine. And I have never done anything like this.
I have INL_st_tsw_sp08_r9b. On feb. 2012. By one good specialist. How to check - is it good.
 
I did not save the INL_st_tsw_sp08_r9b version as unnecessary. In the EX version, the r9b correction was absent in principle. The license file during installation is placed in the /SYSN/USR1/SES/LI/ directory. If it is not there, then you can try to request a license file (its copy) from the official distributor. I don't know how to export a license file from a running system. I don't think it exists.
 
Yes, a path to /SYSN/USR1/SES/LI/ is a right path for licenses file. Thanks. But I ask about another thing - I listen that license file for sp6 not work with sp8.
 
All tsw loc is work with sp0 to 8 ...no worries.
And you can message me for convert lic if need
Cyber_city64@yahoo.com

PG4E
 
The current BC13 license file is valid for any version of SP0-SP8.
 
If you can't find the license file, I can extract it from a working system so that it can be reloaded with a new upload.
 
So now you people are creating a new system? Wow....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top