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!

hipath4000v6 vbz config

wanyin

Technical User
Jul 18, 2022
50
0
6
CN
The extension is divided into two parts(itr0&&4/itr5), each limited to the other
The problem is that the newly added extension 3254, no matter itr set 5 or 6, can always get through to the extension of itr0, can not get through to itr 5e
Is there a solution that doesn't stop the phone service
REG-VBZ;
H500: AMO VBZ STARTED
CHANGE-VBZ:00&&15,AX,00&&15;
CHANGE-VBZ:0,DX,5,Y;
CHANGE-VBZ:1,DX,5,Y;
CHANGE-VBZ:2,DX,5,Y;
CHANGE-VBZ:3,DX,5,Y;
CHANGE-VBZ:4,DX,0&5,Y;
CHANGE-VBZ:5,DX,0&1&2&3&4,Y;
<dis-scsu:3254;
DIS-SCSU:3254;
H500: AMO SCSU STARTED

------------------------------- USER DATA -----------------------------------
STNO =3254 COS1 =21 DPLN =1 SPDI =0
PEN = 1- 4-121- 0 COS2 =23 ITR =6 SPDC1 =
DVCFIG =ANATE LCOSV1 =1 COSX =0 SPDC2 =
INS =YES LCOSV2 =6 RCBKB =NO
PMIDX =0 ALARMNO =0 LCOSD1 =2 HMUSIC =0 RCBKNA =NO
SSTNO =NO COTRACE =NO LCOSD2 =1 SPEC =
COFIDX =0 DIAL =DTMF PULSTYPE= PULSLEV=
CCTIDX = ACKST = TEXTSEL=ENGLISH
DHPAR = NEONMWI=
CONN =DIR FLASH =YES DTMFBLK =NO WITKEY :NO
------------------- ACTIVATION IDENTIFIERS FOR FEATURES ---------------------
DND :NO CWT :NO
HTOS :NO HTOF :NO HTOD :NO VCP :NO
--------------------- FEATURES AND GROUP MEMBERSHIPS ------------------------
PUGR : HUNTING GROUP : NO
NIGHT OPTION : NO
------------------------- STATION ATTRIBUTES (AMO SDAT) ---------------------
NONE
-----------------------------------------------------------------------------

AMO-SCSU -111 STATION CONFIGURATION OF SWITCHING UNIT
DISPLAY COMPLETED;
 
Your SCSU shows that extn is ITR 6, and ITR 6 is not denied in any direction in VBZ, so it's normal ITR 6 can call ITR 0.

If that extn was ITR 5, I would expect that it cannot call ITR 0.

It's possible to forward into a denied ITR, depending on ZAND ALLDATA ITRFWD parameter, perhaps your call scenario is more than simple call.
 
<cha-vbz
ITRSRC = 6
ITRGR = ?
ITRGR : INTERNAL TRAFFIC RESTRICTION GROUP
CHARACTERISTIC : REQUIRED
POSS. VALUES : AX ALLOWED:SOURCE -> DEST., DEST.->SOURCE UNCHANGED
DX DENIED:SOURCE -> DEST., OTHER DIRECTION UNCHANGED
AD ALLOWED:SOURCE -> DEST., DENIED: DEST. -> SOURCE
DA DENIED:SOURCE -> DEST., ALLOWED:DEST.-> SOURCE
AA ALLOWED IN BOTH DIRECTIONS
DD DENIED IN BOTH DIRECTIONS
ITRGR = aa
ITRDEST = 5;
CHA-VBZ:6,AA,5;
H500: AMO VBZ STARTED

AMO-VBZ -111 INTERNAL TRAFFIC RESTRICTIONS
CHANGE COMPLETED;
<reg-vbz;
REG-VBZ;
H500: AMO VBZ STARTED
CHANGE-VBZ:00&&15,AX,00&&15;
CHANGE-VBZ:0,DX,5,Y;
CHANGE-VBZ:1,DX,5,Y;
CHANGE-VBZ:2,DX,5,Y;
CHANGE-VBZ:3,DX,5,Y;
CHANGE-VBZ:4,DX,0&5,Y;
CHANGE-VBZ:5,DX,0&1&2&3&4,Y;
i need stn3254 can call with itr5,but it seems no effect
 
Post a dis-scsu of your calling and called extns, and say which is which.

Post a dis-vbz.
Maybe post a dis actda and sdat for both extns too.
 
Last edited:
DIS-VBZ;
H500: AMO VBZ STARTED
| ITR-GROUPS (DESTINATION)
ITR - |
MATRIX | 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
|
----------|------------------------------------------------
0 | A A A A A D A A A A A A A A A A
1 | A A A A A D A A A A A A A A A A
2 | A A A A A D A A A A A A A A A A
3 | A A A A A D A A A A A A A A A A
4 | D A A A A D A A A A A A A A A A
5 | D D D D D A A A A A A A A A A A
ITR-GROUPS 6 | A A A A A A A A A A A A A A A A
7 | A A A A A A A A A A A A A A A A
(SOURCE) 8 | A A A A A A A A A A A A A A A A
9 | A A A A A A A A A A A A A A A A
10 | A A A A A A A A A A A A A A A A
11 | A A A A A A A A A A A A A A A A
12 | A A A A A A A A A A A A A A A A
13 | A A A A A A A A A A A A A A A A
14 | A A A A A A A A A A A A A A A A
15 | A A A A A A A A A A A A A A A A
 
3254 call 8200 is ok,3254 call 8368 is not ok
<dis-scsu:3254;
DIS-SCSU:3254;
H500: AMO SCSU STARTED

------------------------------- USER DATA -----------------------------------
STNO =3254 COS1 =21 DPLN =1 SPDI =0
PEN = 1- 4-121- 0 COS2 =23 ITR =6 SPDC1 =
DVCFIG =ANATE LCOSV1 =1 COSX =0 SPDC2 =
INS =YES LCOSV2 =6 RCBKB =NO
PMIDX =0 ALARMNO =0 LCOSD1 =2 HMUSIC =0 RCBKNA =NO
SSTNO =NO COTRACE =NO LCOSD2 =1 SPEC =
COFIDX =0 DIAL =DTMF PULSTYPE= PULSLEV=
CCTIDX = ACKST = TEXTSEL=ENGLISH
DHPAR = NEONMWI=
CONN =DIR FLASH =YES DTMFBLK =NO WITKEY :NO
------------------- ACTIVATION IDENTIFIERS FOR FEATURES ---------------------
DND :NO CWT :NO
HTOS :NO HTOF :NO HTOD :NO VCP :NO
--------------------- FEATURES AND GROUP MEMBERSHIPS ------------------------
PUGR : HUNTING GROUP : NO
NIGHT OPTION : NO
------------------------- STATION ATTRIBUTES (AMO SDAT) ---------------------
NONE
-----------------------------------------------------------------------------

DIS-SBCSU:8200;
H500: AMO SBCSU STARTED

----------------------------- USER DATA ----------------------------------------
STNO =8200 OPT =OPTI COS1 =20 DPLN =0
MAINO =8200 CONN =DIR COS2 =20 ITR =1
PEN =1- 1-109- 12 LCOSV1 =2 COSX =0
INS =Y ASYNCT =500 LCOSV2 =2
SSTNO =N PERMACT = LCOSD1 =4 CBKBMAX =5
TRACE =N EXTBUS = LCOSD2 =2 RCBKB =N
ALARMNO =0 DFSVCANA= SPDI =0 RCBKNA =N
HMUSIC =0 FLASH = SPDC1 = CBKNAMB =Y
PMIDX =0 SPDC2 =
SECR =N DIGNODIS=N DSSTNA =N COMGRP =0
STD =60 CALLOG =ALL DSSTNB =Y TEXTSEL =ENGLISH

REP =0 OPTICOM =N OPTIUSB :0 VPI =
IDCR =N OPTICA = OPTIS0A :0 VCI =
APPM =N OPTIDA = OPTISPA :0 PATTERN =
BLF =N OPTIUP0E:0 OPTIABA :0
DIS-SBCSU:8368;
H500: AMO SBCSU STARTED

----------------------------- USER DATA ----------------------------------------
STNO =8368 OPT =OPTI COS1 =121 DPLN =1
MAINO =8368 CONN =DIR COS2 =23 ITR =5
PEN =1- 3-115- 7 LCOSV1 =4 COSX =0
INS =Y ASYNCT =500 LCOSV2 =4
SSTNO =N PERMACT = LCOSD1 =1 CBKBMAX =5
TRACE =N EXTBUS = LCOSD2 =1 RCBKB =N
ALARMNO =0 DFSVCANA= SPDI =0 RCBKNA =N
HMUSIC =0 FLASH = SPDC1 = CBKNAMB =Y
PMIDX =0 SPDC2 =
SECR =N DIGNODIS=N DSSTNA =N COMGRP =0
STD =60 CALLOG =ALL DSSTNB =Y TEXTSEL =ENGLISH

REP =0 OPTICOM =N OPTIUSB :0 VPI =
IDCR =N OPTICA = OPTIS0A :0 VCI =
 
<reg-actda:stn
STNO = 3254&8200&8368;
REG-ACTDA:STN,3254&8200&8368;
H500: AMO ACTDA STARTED
ADD-ACTDA:STN,8200,VCR;
ADD-ACTDA:STN,8368,VCR;
ADD-ACTDA:STN,8368,OPTISET,4,4,2,7,7,NORMAL,2,3,2;
ADD-ACTDA:STN,8368,INHUNT,VCE;
 
So 3254 cannnot call 8368.
3254 is DPLN 1, ITR 6. 8368 is DPLN 1, ITR 5. They have difference COSs, and also different COS1/COS2.

I don't see a reason for this problem. ITR 6-> 5 is not blocked. Does not look like an ITR problem. Are you using any time of day switching/berum/beruz. Are you using VNR.


For testing..
- is 8368 definitely in service READY? (dis-sdsu)
- have you taken 8368 out of the hunt group
- have you deleted and re-added 8368
- can 8368 call 3254
- can any other extn call 8368. does this work if calling extn is also dpln 1 / itr 5.
- 3254 can call 8200, which is ITR 1. Can you call 8368 if you make 8368 ITR 1.

Maybe there is some corruption here. Maybe it needs a reload or a gendb.

Are you able to mail me a complete regen ? if so send it to itsjustasmallproblem at gmail. also send a dis-aps:,psgl,y*;
 
1. 8368 is ready
2. not yet
3. not yet
4. 8368 can't call to 3254
5. yes ,other itr 5 extension call to 8368 is ok, itr 1 extension to 8368 is blocked
6. not test yet,but 3254 call the other itr0-4 extension is ok
it seems althought i change setting 3254 from itr0 to itr5 or 6 ,it keep working in itr0.
 
<dis-aps:,psgl,y*;
DIS-APS:,PSGL,Y*;
H500: AMO APS STARTED
ADINIT STARTED
PROGRAM SYSTEM : Y0-E30YC
VERSION NUMBER : 60
CORRECTION VERSION NUMBER : 001
PART NUMBER : P30252N4802B00017|V6 R2.17.0
PROGRAM SYSTEM WITH CODE SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

DIR SUBSYSTEM | | OMF SUBSYSTEM
-----------------------+-+-----------------------
ZMITSC00.Y0-EM0.10.001 |*|ZMITSC00.Y7-PMT.10.001

PROGRAM SYSTEM : Y7-P3TYT
VERSION NUMBER : 60
CORRECTION VERSION NUMBER : 001
PART NUMBER : P30252N4802U00251|V6 R2.51.0
PROGRAM SYSTEM WITH TEXT SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

DIR SUBSYSTEM | | OMF SUBSYSTEM
-----------------------+-+-----------------------
ZMITSC00.Y7-PMT.10.001 | |ZMITSC00.Y7-PMT.10.001

ADINIT COMPLETED
STATUS = H'0000
AMO-APS -111 SOFTWARE LOAD UPGRADE
DISPLAY COMPLETED;
<
 
regen file
 

Attachments

  • ALL20240823.txt
    636.4 KB · Views: 4
I tried your DB on V6 R2.17, and it works as expected. 3254 can call 8368, and 8368 can call 3254.

Myabe you have some corruption.

You could try
- soft/hard restart the processor
- reload the processor
- update the HF level (you are HF0, I am HF29)
- GENDB the database.
 
yes,i will try hard restart the system。Is there any necessary preparation work to be done before hard restart?
 
Not really, other than exe-updat:bp,all; It's not needed, but, I'd do it anyway,
 

Part and Inventory Search

Sponsor

Back
Top