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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Display incorectly

Status
Not open for further replies.

lanpham_imported

Technical User
Nov 26, 2011
71
VN
I have a tieline between an Ericsson MD110 and OPENSCAPE 4000V8 by ISDN Trunk.
Extensions at the Openscape4000v8 (SIP,HFA Extension) call Extensions at MD110 (DTS, ATS, ISDN extension).
Calls from the Openscape4000v8 extensions are display correctly on DTS extensions, ATS extensions. But not correctly on ISDN extension, add to 2 digits “00”. Eg it shows 0040100 instead of 40100 (I don’t want to display 2 digits “00” at pre)
Note: If I use a R2 trunk between MD anh 4000V8, display correctly on all of extension
Help me making this config display extension number on ISDN terminal from 4000v8’ extension.
Please help!
Brs!
 
Activate the DIAGS switch :

CHA-DIAGS:COMP=CP2,S05=ON;
CHA-DIAGS:COMP=CP2,S06=ON;

Simulate the scenario immediately and check HISTA output (F4066)
You can see in which format calling and called pty. is sent.
Deactivate the DIAGS switch after tracing to prevent HISTA flooding.

Check entries in KNFOR for modifying calling pty. display on partner.
This can have impact on other features (e.g. callback)

For example:
CHANGE-KNFOR:DNNO=1-1-315,NPI=ISDN,TONIN=SUBSCR,TONOUT=SUBSCR;

DNNO must be 3 level node (1-1-315).

TDCSU: NNO = 1-1-315
LDAT : DNNO = 1-1-315
 
Dear ADIBV!
Can you say clearly? I only undersatand a liitle!
I enter cha-diags command as you say. But not display corectly
Please help! Thanks
 
What do you mean by "But not display corectly" ?
After you activate DIAGS and simulate the scenario immediately you should see in Hista ( sta-hista:search; ) a similar output like :

F4066 M4 N1175 NO ACT BPA CP ADVISORY 02-05-03 09:36:38
ALARM CLASS:CENTRAL:023
FORMAT:49
TEST: OUT OUT SETUP.CALLING_N.NUMBER
ORIGIN: 1- 1- 100 DESTIN: 1- 1- 400 BITS:0123456789012345
3165 not def not def 1- 1- 100 --012----O------
71903165 unknown unknown


F4066 M4 N1176 NO ACT BPA CP ADVISORY 02-05-03 09:36:38
ALARM CLASS:CENTRAL:023
FORMAT:49
TEST: OUT OUT FACS BILL CHARGED
ORIGIN: 1- 1- 100 DESTIN: 1- 1- 400 BITS:0123456789012345
3165 unknown unknown 1- 1- 100 --012----O------
71903165 unknown unknown


F4066 M4 N1181 NO ACT BPA CP ADVISORY 02-05-03 09:36:39
ALARM CLASS:CENTRAL:023
FORMAT:49
TEST: IN IN ALERT.CONN_N.NUMBER
ORIGIN: 1- 1- 400 DESTIN: 1- 1- 100 BITS:0123456789012345
72703441 unknown unknown 1- 1- 400 --012-----------
3441 unknown unknown


F4066 M4 N1182 NO ACT BPA CP ADVISORY 02-05-03 09:36:44
ALARM CLASS:CENTRAL:023
FORMAT:49
TEST: IN IN CONN.CON.NUMBER
ORIGIN: 1- 1- 400 DESTIN: 1- 1- 100 BITS:0123456789012345
72703441 unknown unknown 1- 1- 400 --012-----------
3441 unknown unknown


F4066 M4 N1183 NO ACT BPA CP ADVISORY 02-05-03 09:36:45
ALARM CLASS:CENTRAL:023
FORMAT:49
TEST: IN IN DISC.CALLED_N
ORIGIN: 1- 1- 400 DESTIN: 1- 1- 100 BITS:0123456789012345
72703441 unknown unknown 1- 1- 400 --012-----------
3441 unknown unknown

After simulating the scenarion and take the Hista output, deactivate the DIAGS switch ( S06=OFF & S05=OFF ) to prevent HISTA flooding !!!
 
My feeling is that you have no OS4k knowledge.

I would suggest to take some proper trainings/courses first via :
as donb01 suggested in "Operating OS4KV8 system" topic.

Also read the documentation/service manuals available on :
Check topic "Siemens: Hicom FAQ":

You canonot make support without at least having a basic course and getting familiar with RMX/Comwin & OS4k Assistant
 
By the way it is possible to have a DPNSS trunk between MD110 and 4K
On the 4K side it is handled by a CDG (Cornet-DPNSS-Gateway) Card
 
Easier to trace the MD?
Trace a good and bad call, post results.
 
Dear all
Many tks adibv, i will try to sign web page which you say
Hi, Moriendi
I Trace the MD as below:

CTDEI:DIR=42600;
CALL TRACE
INITIATED ON DIR: 42600 EQU: 003-3-72-00
EQU: 003-3-72-01
DEVICE TYPE ITL PTR: H'013F
MP-IN EQU MP-OUT EQU DEV EQU DEV DIR EQU
* NO-CON *
SL60 ***** 003-2-40-18
EXECUTED

SUSIP:DIR=42600;
STATUS INFORMATION AT 16:29:11 28MAR20
DIR TYPE TRAFFIC STATE/PTR LINE STATE/PTR DIV STATE ADD INFO
42600 ITS B1-FREE #013F FREE #0304
B2-BUSY
END

The call connection is very well, good speed but display incorectly on ISDN extension. It adds 2 digit "00" at first calling number!
Brs!
 
I mean the messaging on the trunk. What is the 4K sending to the MD. If you can't trace from 4K side, trace from MD. We are interested in the calling party, NPI/TON, any other classmarks. I don't see any calling info on what you supplied. Maybe the call is marked International and it makes MD apply 00 prefix.

What is the 4K trunk? Example, 1-2-8-0.
Send DIS-TDCSU:1-2-8-0;

In that display, there is a COT number. Example, 1.
Send DIS-COT:1;

Maybe LINO can help here, I don't know.

Send the TDCSU and the COT for your trunk.
 
Hi Moriendi!
Tks very much
note that:
Calls from the 4K'extensions are display correctly on DTS extensions, ATS extensions (belong to MD110)
But not correctly on ISDN extension, add to 2 digits “00”. Eg it shows 0040100 instead of 40100 (I don’t want to display 2 digits “00” at pre)

And note: If I use a R2 trunk between MD and 4KV8, display correctly on all of extension

I am going to go the office tomorrow, i will send you the commands of 4K about the TDCSU and the COT for my trunk.
Brs!
 
Dear Moriendi!
These are parameters of TDCSU, COT, ODR...
Please see:

<DIS-TDCSU:1-1-1-0;
DIS-TDCSU:1-1-1-0;
H500: AMO TDCSU STARTED
+------------------------ DIGITAL TRUNK (FORMAT=L) -------------------------+
| DEV = S2COD PEN = 1-01-001-0 TGRP = 1 |
|---------------------------------------------------------------------------|
| PROTVAR = ETSI INS = Y SRCHMODE = CIR |
| COTNO = 30 COPNO = 30 DPLN = 0 |
| ITR = 0 COS = 200 LCOSV = 32 |
| LCOSD = 32 CCT = DESTNO = 10 |
| SEGMENT = 1 DEDSCC = DEDSVC = NONE |
| FACILITY = DITIDX = SRTIDX = |
| TRTBL = GDTR SIDANI = N ATNTYP = CO |
| CBMATTR = NONE NWMUXTIM = 10 TCHARG = N |
| SUPPRESS = 0 DGTPR = CHIMAP = N |
| ISDNIP = ISDNNP = |
| PNPL2P = PNPL1P = PNPAC = |
| TRACOUNT = 10 SATCOUNT = MANY NNO = |
| ALARMNO = 2 FIDX = 1 CARRIER = 1 |
| ZONE = EMPTY COTX = 30 FWDX = 5 |
| DOMTYPE = DOMAINNO = TPROFNO = |
| INIGHT = CCHDL = |
| UUSCCX = 16 UUSCCY = 8 FNIDX = 1 |
| CLASSMRK = EC & G711 & G729AOPT SRCGRP = ( ) |
| TCCID = SECLEVEL = TRADITIO |
| HMUSIC = 0 CALLTIM = 60 WARNTIM = 60 |
|---------------------------------------------------------------------------|
| BCNEG = N BCGR = 1 LWPAR = 0 |
| LWPP = 0 LWLT = 0 LWPS = 0 |
| LWR1 = 0 LWR2 = 0 |
| VNNO = |
| SVCDOM = |
| BCHAN = 1 && 30 |
| |
+---------------------------------------------------------------------------+
AMOUNT OF B-CHANNELS IN THIS DISPLAY-OUTPUT: 30

AMO-TDCSU-111 DIGITAL TRUNKS
DISPLAY COMPLETED;


<DIS-COT:30;
DIS-COT:30;
H500: AMO COT STARTED

COT: 30 INFO:
DEVICE: INDEP SOURCE: DB
PARAMETER:
RECALL IF USER HANGS UP IN CONSULTATION CALL RCL
TRUNK CALL TRANSFER XFER
TRUNK SIGNALING ANSWER ANS
UNRESTRICTED SUFFIX DIALING USD
CHANGEOVER FROM HOLD TO RING TONE CHRT
KNOCKING OVERRIDE POSSIBLE KNOR
CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC
TIE LINES TIE
INTER-SYSTEM TRANSIT TIES ITT
DON'T RELEASE CALL TO BUSY HUNT GROUP BSHT
CAMP-ON ON DID CALLS KNDI
DESTINATION NUMBER WITH PREFIX DIGITS TO CDR DPRE
SEND NO NODE NUMBER TO PARTNER LWNC
INCOMING CDR BY ZONE OR FROM LINE ICZL
ANSWER BEFORE POSTDIAL OR ANNOUNCEMENT ABPD
WAIT ANNOUNCEMENT WAAN
USE DEFAULT NODE NUMBER OF LINE DFNN
UUS SERVICE CLASS 1 (CONNECTION SETUP BASIC CALL) UUS1
UUS SERVICE CLASS 3 (CONNECTION RELEASE BASIC CALL) UUS3
INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR (DATA) NLRD
TRANSFER BEFORE ANSWER ON DSS1 TRBA
CONTROLLED TRUNK AND LINE SELECTION CTLS
NETWORK CALL TRANSFER, EXPLICIT CALL TRANSFER NCT
NO TONE NTON

AMO-COT -111 CLASS OF TRUNK FOR CALL PROCESSING
DISPLAY COMPLETED;

<DIS-LDPLN:TYPE=LDP,LDP=42-6X;
DIS-LDPLN:TYPE=LDP,LDP=42-6X;
H500: AMO LDPLN STARTED
+--------------+-------------------------------------------------+
| | |
| DIPLNUM: 0| |
| LDPNO :7 | LDP : 426-X |
| | SPC : 22 |
| | FDSFIELD : 0 SDSFIELD : 0 PINDP : N |
+------+-------+-------------------------------------------------+
| DPLN | LROUTE| LAUTH |
|------+-------+-------------------------------------------------+
| 0 | 1 | 1 |
| 1 | 2 | 1 |
+------+-------+-------------------------------------------------+

AMO-LDPLN-111 ADMINISTRATION LCR DIALPLAN
DISPLAY COMPLETED;
<DIS-LDAT:LROUTE=1;
DIS-LDAT:LROUTE=1;
H500: AMO LDAT STARTED
+------------------------------------------------------------------------------+
| LROUTE = 1 LDPLN NAME = TO MD SERVICE = VCE |
| TYPE = LCR DNNO OF ROUTE = 1 |
| SERVICE INFO = |
+------+-----+-----+----+-----+----------+-----------+----------+------+-------+
| | | | | | SCHEDULE | CARRIER | | | |
|LRTEL | LVAL|TGRP | ODR|LAUTH| ABCDEFGH | ZONE| LATTR | LDSRT|COTIDX |
+------+-----+-----+----+-----+----------+-----------+----------+------+-------+
| 1| 1| 1| 3| 1 | ******** | 1 EMPTY| WCHREG | | 0 |
+------------------------------------------------------------------------------+
| 2| 1| 3| 3| 1 | ******** | 1 EMPTY| WCHREG | | 0 |
+------------------------------------------------------------------------------+

AMO-LDAT -111 LCR-DIRECTIONS
DISPLAY COMPLETED;
<DIS-LODR:3;
DIS-LODR:3;
H500: AMO LODR STARTED
+-------------------------------------------------------+
| ODR POSITION CMD PARAMETER |
+--------+----------------------------------------------+
| 3 | 1 ECHOALL |
| | 2 END |
+--------+----------------------------------------------+
H03: THE NEXT FREE ODR IS 1

AMO-LODR -111 ADMINISTRATION OF LCR OUTDIAL RULES
DISPLAY COMPLETED;
You study and give me help!
Tks and Brs!
 
Make a test with PROTVAR = PSS1V2 and also with ECMAV2 on TDCSU (instead of ETSI) and compare some test results.
 
Yes.

You have configured TDCSU as central office (S2COD, ETSI). I would have expected S2CONN and some variation of ECMA1/ECMAV2/PSS1V2. Not sure if this would cause your problem though, it depends on the configuation of the MD. 4K will still have sent private network indicator. 4K just thinks the MD is public CO.

You don't need half those COT parameters that are in there but again, I don't see how they'd cause the problem.

Make a test call with LINO in the COT.

cha-cot:30,cotadd,LINO;
make the test, then take it out.
cha-cot:30,cotdel,LINO;

It will force the call to NPI/TON unknowm/unknown. The S2COD config might be causing an ISDN/INTERNATIONAL NPI/TON, which is why I asked for a trunk trace, but you did not supply.
 
Hi Adibv and Moriendi!
Many, many thanks
I will to change those parameters when i come back my office. I am having 15 day off because CORONA virus. So i am going to enter that command later!
Please wait me!
Brs!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top