It’s a Siemens 2G MSC manual dated 2002.
D 9 0 0 Mobile Communication System
Task Manual
TML Version SR10.0 - Innovation
Configuration: 2G MSC
APS-ID: UMRCBK1V.3510
Well, it seems not all commands are implemented between different APS versions… but it was worth a try. In some cases with other telecommunication equipment, engineering commands are hidden from “customer” manuals.
Reversed the time signal on the serial line (IOPTA) today. EWSD is juggling with RTS and CTS signals to talk to the clock. Clock and EWSD have to respond within milliseconds.
nice, I don’t know this RCI, siemens resold quite expensive devices with their firmware, see photo. Unfortunately, I don’t have a working piece yet. That’s why only a few of the biggest operators in CZ bought it. Therefore, a colleague wrote a replacement that emulates the protocol on a PC and forwards it to IOPTA via the computer’s RS232. For inspiration it would be possible to provide
I would like to see that emulation. Can you provide the source code?
you have PM
I am still working on EWSD commissioning, but I make progress. Meanwhile I want to know how to add announcements ocaneq card. it has 10/100baseT port.
The eth port is only used for recording new voices…if you don’t have the programs mentioned below, you will only be able to use what is already in the card for now.
New recording and creation of voices if the record does not have them is quite complicated.
3 programs are needed, see part of the documentation, two of which were heavily licensed for PC hardware.
http://archiv.pabx.cz/f100.pdf
I only have the old “service PC” version
Anyway, if ocaneq is OK, those basic sounds present after the operator will be there. However, these boards are extremely defective and sometimes get erased.
If your board is up (all LEDs must not light up), write DISPANLN:TGNO=X; if there is something there and try if ocaneq plays them.
Look on your acquired NT4 windows PC for those service programs.
I’ll probably get them in some time, but it hasn’t been possible yet. (the operator probably only had two licenses)
That’s why I also installed the old DAS, where management is easy.
Anyway, if you have an OK board, I assume that everything will be preserved on it (voices and possibly speaking clock)
if you want to have ocaneq in a new location, you can find out where it was from DISPANLN, and before you delete the old LTG, you need to set it up in a new position… write down what you have there now…
First call made with EWSD today:
analog phone <-> V52 (Fastlink) <-> EWSD <-> PBX line (PASLAVE) <-> (Jolly’s PBX) <…> T* in Berlin
Jan, can you provide the commands you needed to configure SS7 link to Laforge’s PBX? I want to do configure the same. (Different point codes of course!)
Is it possible to run CSS7 link and PASLAVE PBX on same LTGN? I have LDPARP=22. It uses CRMOD=0 and CRMOD=1 with TYPE=CRPC;
Hi,
I am preparing how to set up the ss7, I will send in about an hour…
for ss7 type=LTGC,ldparp=12
for subscribers such as PBX, paslave, DLU, type=LTGB,ldparp=11.
I don’t combine, it doesn’t have to be something, but in LTGB, 11 you will probably manage to set it up, you can try. But loadtype 12 is made for it.
As for the hardware, all the main 11 and 12 can be uploaded to the LTGN without any problems. But I recommend one LTG on the PBX (PRI, CAS, DLU), and the second on the trunks, and the third possibly on the V5.2 LTGB, ldparp=52.
If it’s not a typo and you have ldparp=22, you have a completely different loadtype than I know…it was not used in our APS.
What must be in the trunk LTG, I will write…
sending how to set up a c7 line, as I have it now with laforge. It is an international ISUP in INAT0. Try it out, but later I recommend you set the national one between you. You can transfer within Germany in the national form, and EWSD is also more benevolent, as we found out for example with screeening indicators.
I will supply the national parameters if necessary.
It’s worth it, if you don’t know, ask, I could have left something out or not written exactly…
create own pointcode:
CRC7OP:SPC=x-x-x,NETIND=INAT0,STPI=STP;
create linkset
CRC7LSET:LSNAM=namelset,SPC=0-0-1,NETIND=INAT0,LSK=0;
create dest pointcode
CRC7DP:DPC=0-0-1,NETIND=INAT0,PRD=name
CRC7USER:USNAME=ISUP,DPC=0-0-1,NETIND=INAT0,PCMTYP=DIU30;
CONFC7DP:DPC=0-0-1,NETIND=INAT0,OST=ACT;
CRTGRP:TGNO=name,OPMODE=BW,GCOS=CCS7IUP;
CRTGRP:TGNO=names,OPMODE=IC,GCOS=CCSLGRP;
ENTRC7TGREL:TGNO=name,DPC=0-0-1,NETIND=INAT0;
CRC7LINK:LSNAM=namelset,LCOD=0,SILTNO=1,LTYPE=D64BWM;
CONFC7LINK:LSNAM=namelset,LCOD=0,OST=ACT;
cr sig line in ch 1
CRTRUNK:TGNO=nameS,LNO=1,LTG=0-xx,LC=diunumber-1,LCOS=DIGSIG13;
cr speech chnnels
CRTRUNK:TGNO=name,LNO=2,CIC=0-2,LTG=0-xx,LC=nrdiu-2,LCOS=DIGSIG14;
CRTRUNK:TGNO=name,LNO=3,CIC=0-3,LTG=0-xx,LC=nrdiu-3,LCOS=DIGSIG14;
and so on to 31
nuc(parameters hardware positions SILT boards table in doc):
CRNUC:NUC=namenuc,LTGIC=useltg,LCIC=diu-1(first chan),LTGOG=(from table hw),LCOG=(from table hw),TYPE=MUX;
ACTNUC:NUC=namenuc;
CANTRDAT:TGNO=name,CIC=0-2,BLK=ADMIN;
CANTRDAT:TGNO=name,CIC=0-3,BLK=ADMIN;
and so on to 0-31
parameters I have now,change (ENTR/CANTGDAT,MODTGRP):
orig1 what you see here in the different statements not use - you have to use the ones you have with you ewsd to call it
DISPTGRP:TGNO=SSGER;
TGNO = SSGER OPMODE = BW MASKNO:06349
GCOS = JSUBORD &NOZON &C7GLARE &CCS7IUP &SEQBKWD MASKNO:06348
&INTLTRK &PROP11 &USVERS1
ORIG1 = 1168 MASKNO:06346
PROTTAB = INTV2 MASKNO:06347
SIGVAR = VAR1 MASKNO:08467
in INTV2 is:
DISPPROTTAB:NAME=INTV2; EXEC'D
PROTOCOL TABLE
NAME : INTV2
SERV : CFW & APPTP & CLIR & CUG & UUS1I & PRI &
COLR & DROV & UUS1E & UUS2 & UUS3 & VPN &
LOCNUM & CCNR & MLPP & HOPCO & ATP & CLIP &
CLIRS & DCT & COLP & DIVCA & ECTR & ECT &
REMO & APPPSS1& APPCRG & APPCTX & CTC & CHEMSG &
FU58 & FU59
DISPTRUNK:TGNO=nameS;
it must look like this if the NUC is OK
TGNO = SSGERS OPMODE = IC LNO = 1 MASKNO:09988
LTG = 0-11 LC = 2- 1 MASKNO:09989
LCOS = DIGSIG13 MASKNO:09998
TSTTYP = 0 MASKNO:09991
CONN = NUC
LTG:
create first
CRLTG:LTG=0-xx,TYPE=LTGC,LDPARP=12;
CRCRMOD:LTG=0-xx,CRMOD=0,TYPE=RMCTC;
CRLTU:LTG=0-xx,TYPE=D30,APPLIC=CCSCCS;
nothing other are required, just CCSCCS D30
Maybe I forgot to write something, set everything to act state…LTG, ports, etc…
and routing:
DISPCPT:CODE=004930;
CODE POINTS FOR DEST
DEST CODE MFCAT ORIG1 LAC SYM- AM-
ROUTYP ZDIG CON BIG
------------+-------------------+-----------+-------+---------+----+---
SSGER 004930 1 - 1 NO NO
DISPDEST:DEST=SSGER;
DESTINATION NAMES AND STANDARD ROUTING PARAMETERS
TYP
DEST : MINMAX DEFEAT TLIM
--------------+-+------+---------+------------------------------
SSGER 3-20 DIALTM1& RINGTM1& CLEATM1&
OFFCALL& RELTM3
DISPROUTE:DEST=SSGER;
DACT
TGNO DEST ROUTE DINO SSDI EOS LNDES TRACA :
----------+------------+------+----------+----+----+---------+-------+--
SSGER SSGER 1-Y ENBLOC 1 SIGN CLEARBA & NAT
PRIM
ZDIG DACT
TGNO DEST ROUTE STAT : DICON :
----------+------------+------+----+--+-------------------------------+-
SSGER SSGER 1-Y 0 0 0
what I didn’t write or some typos, ask if it doesn’t work
If you would like, I would also like to connect with you. We will have setting up overlap dialing and other services between two EWSDs.
The line could be even more stable if we turn on cyclic retransmission between them.
but there is no rush to get to know EWSD calmly… but I would be happy 
I have two problems with activation:
CRC7LINK:LSNAM=JOLLY,LCOD=0,SILTNO=1,LTYPE=D64BWM; EXEC’D
CONFC7LINK:LSNAM=JOLLY,LCOD=0,OST=ACT; NOT EXEC’D
REJECTION CAUSED BY OPERATOR INPUT ERROR
REASON:
ADJACENT DESTINATION POINT NOT CREATED OR NOT ACTIVE
POSSIBLE ACTION:
CREATE/CONFIGURE DP
CRNUC:NUC=SILT1,LTGIC=0-10,LCIC=1-16,LTGOG=0-1,LCOG=0-16,
TYPE=MUX; EXEC’D
ACTNUC:NUC=SILT1; NOT EXEC’D
REASON: TRUNKPORT INC BLOCKED
Is this really required?
CRCRMOD:LTG=0-xx,CRMOD=0,TYPE=RMCTC;
I have PBX line on DIU 0 and SS7 on DIU 1. Maybe this is not a good idea. Can I configure LTGN:YE as TYPE=LTGC? Then i can use LDPARP=3, which is used on all the SS7 LTG. I don’t have them, because I removed all LTG shelfs except one.
Tomorrow I will wire up another LTG to my patch panel and try the load 3.
collisions on LTGB because there are other CRPCs…on LTGC I have them like this. Feel free to try without and see if you have other CRPC there try what it does. I would use the second LTG for trunks, I have never tried to put ss7 on LTGB.
GPNYE is not a problem for both C and B, but your LDPARPs are completely different than mine, probably just a different market.
So try next LTG to give LTGC:
CRLTG:LTG=0-xx,TYPE=LTGC,LDPARP=12;
and if LDPARP=12 does not work for you, try LTGC ldparp=3. But it’s a different loadtype, so it may behave differently than mine, and some parameters may not know it
CRC7DP:DPC=0-0-1,NETIND=INAT0,PRD=name
CONFC7DP:DPC=0-0-1,NETIND=INAT0,OST=ACT;
this commands ok?
yes, do this only after the PCM is UP, I forgot that it has to be done when it is in ACT on LTG diu and confport in act
All 32 ports are up now, but still:
ACTNUC:NUC=SILT1; NOT EXEC’D
REASON: NO ACKNOWLEDGEMENT FROM USER
The H4 lamp on the SILTD is on.
Jan, I think we should meet on video chat with screen sharing, so you can help me and I can type…
is silt in act? statccnc:unit=silt-x;
do you have any IM chat? Telegram or Messenger? It will be more operative…we probably wouldn’t agree in voice communication, by English is bad, but we can possibly try
orange lights may not always be a fault
Thanks to Jan! It works now. I need digsig8 for SS7 signaling with my APS, not digsig13. SS7 link is up. Next weekend I will continue…