Hip4advs BR

s
HiPath 4000 V6.0

Treinamento Avanado (Customer)
CH4KV6ADVS
CONTEDO
BR0039HIPATH4000Avanado
1 - Configurao de Troncos 2 - LCR 3 - Grupos de Atendimento 4 - Ramais IP 5 - Key System 6 - FlexRouting 7 - Uw7 Assistant 8 - HiPath 4000 Assistant 9 - Diagnsticos 10 - Backup and Restore
Configurao de Troncos
1. Configurao de Troncos
Contedo
1 2 3 AMOS para troncos ............... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Configuraes Centrais . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Configurao de troncos digitais . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.1 STMD: S0-trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.2 S0 - tronco tie-line digital com protocolo ECMAV2 . . . . . . . . . . . . . . . . . . . . 17 3.3 S0 - tronco digital com a cent ral pblica . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.4 DIUN24: S2-tronc o . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.4.1.S2 - tronco digital tie-line com protocolo ECMAV2 . . . . . . . . . . . . . . . . . . . . 21 3.4.2 S2 - troncos digitais com a c entral pblica. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.
CTIME
temporiz. DH p/ X21, DIGITE, troncos, tie line, TMOM temporizador DH para taxas gerais, fazer/interromper
DTIM1 COSSU
classe de servio descritor de protocolo No. TGRP No. BL No. COS No. COP No. COT classe de parmetros classe de troncos grupos de troncos parm. de loadware para rede
DTIM2 COT PROD E

tabela do clock de referncia No. PROT PRIO
PTIME
temporiz. p/ SLMA, TMCOW, TMEMW
temporiz. p/ CP, circuitos, AC, PSE
WABE
VBZ
COP
REFTA
BUEND
LWPAR
ZAND
COFEA
dados de converso de dgitos
restries para trfego interno
AMOs para troncos
No. ITR
facilidades dados do CO dos tronsistema cos RDSI central EREFPEN TGR P ALL
DESTNO
TACSU
circuitos troncos digitais STMD, TGRP
TDCSU
TSCSU
circuitos troncos especiais TMOM,
circuitos de tronco analgicos TMCOW, TMLRB,
KNMAT KNDEF
cd. do no. de DPLN
MFCVAR
RICHT LODR
MFCTA
tabelas de cdigo multifrequencial
DIMSU
capacidades p/ facilid.
restries entre trfegos para rede
cdigo para uma/diversas rotas
LSCHD
LDAT LDPLN
LDSRT LPROF
1.1.1
1.1.1.1
Relao de AMOs para troncos

AMO BUEND Grupos de troncos Especificao do tamanho mximo e nome para grupo de troncos
1.1.1.2
AMO COP Classe de parmetros Classificao dos parmetros relacionados a troncos em categorias, as quais so atribudas pelos AMO TACSU/TSCSU aos troncos.(parametros de linha).
1.1.1.3
AMO COT Classe de troncos Classificao das facilidades de linha relacionadas ao processamento de chamadas em categorias, as quais so alocadas pelos AMO TACSU/TDCSU/ TSCSU aos troncos
1.1.1.4
AMO PTIME Tabelas padro para troncos Especificao de tabelas padro para definir e ou modificar temporizaes (p.ex.: tempos de pulsos E&M) e parmetros de funcionamento (p.ex.: bloqueio de chamadas a cobrar DDC para troncos analgicos (CAS)
1.1.1.5
AMO TACSU Configurao de troncos analgicos e digitais com sinalizao associada a canal (CAS) e tie lines utilizando mdulos como TM2LP, TMLRB, TMEW2 e DIUN2. Alocao de endereos de HW e de parmetros para os troncos e para as linhas, e colocao dos mesmos em operao.
1.1.1.6
AMO TSCSU Configurao de troncos especiais para TMOM2, SLMD, servidores integrados e TMX21. Alocao de endereos de HW e de parmetros para troncos e para linhas, e colocao dos mesmos em operao.
1.1.1.7
AMO TDCSU Configurao de troncos digitais com interfaces S0 ou S2utilizando mdulos como STMD e DIUN2 e STMI4. Obs: Configura-se tambem os troncos IP! Interface S0. Alocao de endereos de HW e de parmetros para os dois canais B de um circuito S0, e colocao dos troncos em operao. Interfaces S2. Alocao dos endereos de HW e de parmetros para os 30 canais B de um circuito S2, e colocao dos troncos em operao.
1.1.1.8
AMO RICHT Rota alocada uma rota para: - um ou diversos cdigo(s); - um ou diversos grupos de sada / bidirecional dependendo de DPLN, CPS e SVC.
1.1.1.9
AMO PRODE Descritor de protocolo. (Proticolos ISDN (CCS) Normalmente no so necessrias alteraes de protocolo, pois os protocolos so pr-inicializados para todos os troncos conhecidos. Obs: Por default no vem habilitado na central! Tem que ser habilitado!
1.1.1.10
AMO LWPAR Parmetros de loadware (Ex: Mestre/Escravo , com ou sem CRC-4) Parametrizao do loadware para troncos analgicos e digitais da rede. Atribuio de tabelas para os troncos da rede analgica e adaptao das mesmas, se for necessrio, atravs deste AMO. Os blocos de parmetros para os circuitos DIUS2 esto atribudos de forma permanente, porm possvel efetuar mudanas.
1.1.1.11
AMO COFEA Exibio das facilidades de servio dos troncos ISDN para a CO (Central Pblica). A informao de estado dos troncos ISDN disponveis na CO (Central Pblica) mostrada no terminal de servio.
1.1.1.12
AMO REFTA Tabela de clock de referncia Todos os sistemas com conexes digitais a outros sistemas Hicom ou central pblica precisam ter um clock sincronizado. Por esta razo, todos os sistemas Hicom possuem um gerador de clock que sincronizado aos circuitos de linha, que por sua vez oferecem o clock com a maior qualidade.
1.1.1.13
AMO MFCTA Tabelas de MFC Definio de tabelas padro com sinais MFC e sua interpretao com possibilidade de modificao. Obs: Troncos R2 Digital!
Configuraes Centrais
1) CHA-ZAND
TYPE = ALLDATA PNNO =
(nmero do n fsico; Todo o sistema com todos os Access Points (APs)
PNODECD =
(Cdigo de n fsico para otimizao de rota)
ROUTOPTP = Yes/No
(Otimizao de rota smente na rota primria) ROUTOPTD =Yes/No (Desabita otimizao de rota)
2) ADD-KNDEF
NNO =
(Nmero do n virtual TYPE = prprio/externo
ISDNCC = Substitui os parmetros do TDCSU; Para modificaes do ISDNAC = nmero do chamado e chamador; ISDNLC = ISDNSK = (Skip Digits; Standard: Length of the ISDNLC) ISDNUL = (Unique Level; Defines to which level a number should be reduced) PNPL2C = Replace the TDCSU Parameter; For modification of the PNPL1C = called and calling number; PNPLC = PNPSK = (pula digitos; Padro: Tamanho do PNPLC) PNPUL = (nvel nico; Define o nmero de qual nvel pode ser descartado) NODECD = (De acordo com o PNODECD no AMO:ZAND) NODECDSK = (Pula digitos; Padro; tamanho do NODECD)
3) CHA-KNDEF
NNO= DFLT = y (nmero de n padro; se existirem vrios ns virtuais criados no AMO KNDEF, um novo ramal automaticamante assume o n marcado como default veja o AMO: SDAT
4) LCR-COS upgrades
CHA-ZAND:
TYPE = LCR LCRCOSUP = LAUTH-Situao a) quando a discagem externa feita atravs da agenda abreviada b) para tomar uma linha no discada por VPL c) para desvio para a rede pblica LCRNSTN= LAUTH-Situao de ramal noturno ativo
5) PRODE (Descritor de protocolo)

COPY-PRODE:PVCD,1;
Obs: Verificar se ja esta habilitado na central, caso no esteja habilitar! Como padro, vem desabilitado na central!
6) MFCTA (Tabela MFC para troncos R2Digital)

COPY-MFCTA:19,1;
Obs: A tabela utilizada para o Brasil a 19, veja um bloco que esteja livre e copie a tabela de depois faa as alteraoes necessarias! Como padro, vem desabilitado na central!
6) PTIME (Tabela de temporizadores para troncos analgicos)

COPY-PTIME:49,1; (R2 Digital Brasil) COPY-PTIME:87,2; (Troncos analogicos, ex: interface celular!)
Obs: Caso no esteja configurada, veja um bloco que esteja livre e copie! Como padro, vem desabilitado na central!
Configurao de troncos digitais
3.1
S0 - tronco tie-line digital com protocolo ECMAV2
3) CHA-COT
COTNO= COTTYPE= PAR= INFO=
7) ADD-TDCSU
OPT=NEW PEN=1-xx-xxx-xx COTNO= COPNO= DPLN= ITR= COS= LCOSV= LCOSD= CCT= Info-field DESTNO= PROTVAR=ECMAV2 SEGMENT=8 TRACOUNT= SATCOUNT= NNO= ALARMNO= CARRIER= ZONE= COTX= FWDX= CCHDL= SRCGRP= TGRP= SRCHMODE= INS=Yes DEV=S0CONN NO= No of trunks MASTER= SMD= BCNEG=
1) ADD-BCSU
MTYPE=PER LTG= LTU= SLOT= PARTNO=Q2174-x
4) CHA-COP
COPNO= COPTYPE= PAR= INFO=
5) CHA-COSSU
TYPE=LCOSV / D LCOSV/D= ALCR= DLCR= INFO=
6) ADD-REFTA
TYPE=CIRCUIT PEN= PRI= BLOCK= READYASY=
2) ADD-BUEND
TGRP= NAME= NO=e.g. 4
Exemplo de parametrizao mnima Tie Line S0

BCSU
ADD-BCSU:PER,1,5,3,"Q2217-X ",1,0,,,,,,A,,0; /*MODULO STMD3*/
BUEND
ADD-BUEND:105,"TRONCO S0 STMD3 ",20,0,*,2,ON,0,0,NEUTRAL;
COS
ADD-COSSU:,52,,,,,,,,; CHA-COSSU:COS,52,TA&TNOTCR; CHA-COSSU:COS,52,,NOCO&NOTIE; CHA-COSSU:COS,52,,,NOCO&NOTIE; CHA-COSSU:LCOSV,32,1&&64; CHA-COSSU:LCOSD,32,1&&64;
COP
ADD-COP:194,ANS,,;
COT
ADD-COT:194,XFER&ANS&CEBC&CBBN&CBFN&LWNC&CECO&TSCS&CFOS&LINO&NTON;
LWPAR
CHA-LWPAR:DIUS2,0,COPPER,S2,ON,N,16,0,D5,10,10,N,Y,DF,N,0,255,N,N,INDEP,;
TDCSU
ADD-TDCSU:NEW,1-05-0030,194,194,0,0,10,32,32,"",194,ECMAV2,8,,NONE,,,,GDTR,N,TIE,NONE,N,0,,, ,,,,31,MANY,195,0,1,1,EMPTY,194,1,N,,,,,,16,8,1,10,,EC&G711&G729OPT,,1 05,CIR,Y,S0CONN,,Y,Y,0,N;
3.2
S0 - tronco digital com a central pblica
3) CHA-COT
7) ADD-TDCSU
OPT=NEW PEN=1-xx-xxx-xx COTNO= COPNO= DPLN= ITR= COS= LCOSV= LCOSD= CCT= Info-field DESTNO= PROTVAR= ETSI SEGMENT=1 TRACOUNT= SATCOUNT= NNO= ALARMNO= CARRIER= ZONE= COTX= FWDX= CCHDL= SRCGRP= TGRP= SRCHMODE= INS=Yes DEV=S0COD NO= No of trunks PERMACT1= PERMACT2= BCNEG= SMD e MASTER setado automaticamente para SMD=No MASTER=No
1) ADD-BCSU
MTYPE=PER LTG= LTU= SLOT= PARTNO=Q2174-x
4) CHA-COP
6) ADD-REFTA
5) CHA-COSSU
2) ADD-BUEND
TGRP= NAME= NO= e.g. 2
Exemplo de parametrizao mnima troncos acesso CO S0

BCSU
ADD-BCSU:PER,1,5,3,"Q2217-X ",1,0,,,,,,A,,0; /*MODULO STMD3*/
BUEND
ADD-BUEND:105,"TRONCO S0 STMD3 ",20,0,*,2,ON,0,0,NEUTRAL;
COS
COP
ADD-COP:194,ANS,,;
COT
ADD-COT:194,XFER&ANS&CEBC&CBBN&CBFN&LWNC&CECO&TSCS&CFOS&LINO&NTON;
LWPAR
CHA- LWPAR:DIUS2,0,COPPER,S2,ON,N,16,0,D5,10,10,N,Y,DF,N,0,255,N,N,INDEP,;
TDCSU
ADD-TDCSU:NEW,1-05-0030,194,194,0,0,10,32,32,"",194,ETSI,1,,NONE,,,,GDTR,N,CO,NONE,N,0,,, ,,,,31,MANY,195,0,1,1,EMPTY,194,1,N,,,,,,16,8,1,10,,EC&G711&G729OPT,,1 05,CIR,Y,S0COD,,Y,Y,0,N;
3.3 DIUN2 : S2 (E1)

3.3.1 S2 - tronco digital tie-line com protocolo ECMAV2
3) CHA-COT
8a) ADD-TDCSU
OPT=NEW PEN=1-xx-xxx-xx COTNO= COPNO= DPLN= ITR= COS= LCOSV= LCOSD= CCT= Info-field DESTNO= PROTVAR= ECMAV2 SEGMENT=8 TRACOUNT= SATCOUNT= ATNTYP=TIE NNO= ALARMNO= CARRIER= ZONE= COTX= FWDX= CCHDL= SRCGRP= CLASSMARK=EC TGRP= SRCHMODE= INS= DEV=S2CONN BCHAN=1&&30 BCNEG= BCGR=1 LWPAR=0-25
1) ADD-BCSU
MTYPE=DIU (PER) LTG= LTU= SLOT= PARTNO= Q2196-X FCTID= 1
4) CHA-COP
7) ADD-REFTA
5) CHA-COSSU
6) DISP-LWPAR
TYPE=DIUS2 respectivamente
CHA-LWPAR
TYPE=DIUS2 BLNO=0-25 LNTYP=COPPER/OWG QUAL=Yes/No (CRC4) MASTER=Yes/No SMD=Yes/No
2) ADD-BUEND
TGRP= NAME= NO=30
Exemplo de parametrizao mnima Tie Line S2
BCSU
ADD-BCSU:DIU,1,1,25,"Q2196-X ",0,,,,,1,,,,,A;
BUEND
ADD-BUEND:8,"TIELINE ",100,0,*,1,ON,0,0,NEUTRAL;
COS
ADD-COSSU:,70,,,,,,,,; CHA-COSSU:COS,70,TA&TNOTCR; CHA-COSSU:LCOSV,32,1&&64; CHA-COSSU:LCOSD,32,1&&64;
COP
ADD-COP:115,,TA,TA;
COT
ADD-COT:115,PRI&RCL&XFER&ANS&CEBC&CBBN&CBFN&BLOC&DPRE&ROPT&CECO&TSCS&ICZL& ICZO&PINR&LINO&TRBA&NTON;
LWPAR
CHA-LWPAR:DIUS2,0,COPPER,S2,ON,N,16,0,D5,10,10,N,Y,DF,N,0,255,N,N,INDEP,;
TDCSU
ADD-TDCSU:NEW,1-02-0250,115,115,0,0,70,32,32,"",182,ECMAV2,8,,NONE,,,,GDTR,N,cTIE,NONE,N,0,,5 5,19,3736,,,31,MANY,82,0,1,1,EMPTY,115,10,N,,,,,,16,8,1,10,,EC&G729A,, 1,CIR,Y,TRADITIO,S2CONN,1&&16,N,1,0,0,0,0,0,0,N,;
ADD-REFTA:CIRCUIT,1-2-25-0,90,0,N,N;
3.3.2
S2 - troncos digitais com a central pblica (EURO ISDN)
3) CHA-COT
8) ADD-TDCSU
OPT=NEW PEN=1-xx-xxx-xx COTNO= COPNO= DPLN= ITR= COS= LCOSV= LCOSD= CCT= Info-field DESTNO= PROTVAR= ETSI SEGMENT=1 TRACOUNT= SATCOUNT= ATNTYP=CO NNO= ALARMNO= CARRIER= ZONE= COTX= FWDX= CCHDL= SRCGRP= CLASSMARK=EC TGRP= SRCHMODE= INS= DEV=S2COD BCHAN=1&&30 BCNEG= BCGR=1 LWPAR=0-25
1) ADD-BCSU
MTYPE=DIU (PER) LTG= LTU= SLOT= PARTNO= Q2196-X FCTID= 1
4) CHA-COP
7) ADD-REFTA
5) CHA-COSSU
6) DISP-LWPAR
CHA-LWPAR
TYPE=DIUS2 BLNO=0-25 LNTYP=COPPER/OWG MASTER=Yes/No QUAL=Yes/No (CRC4) SMD=Yes/No
2) ADD-BUEND
TGRP= NAME= NO=30
9) CHA-KNDEF
Identificao TRK
Exemplo de parametrizao mnima troncos ISDN acesso rede pblica
BCSU
ADD-BCSU:DIU,1,1,25,"Q2196-X ",0,,,,,1,,,,,A;
BUEND
ADD-BUEND:8,"TIELINE ",100,0,*,1,ON,0,0,NEUTRAL;
COS
COP
ADD-COP:115,,TA,TA;
COT
ADD- COT:115,PRI&RCL&XFER&ANS&CEBC&CBBN&CBFN&BLOC&DPRE&CECO&ICZL& ICZO&PINR&LINO&TRBA&NTON;
LWPAR
CHA- LWPAR:DIUS2,0,COPPER,S2,ON,N,16,0,D5,10,10,N,Y,DF,N,0,255,N,N,INDEP,;
TDCSU
ADD-TDCSU:NEW,1-02-0250,115,115,0,0,70,32,32,"",182,ETSI,8,,NONE,,,,GDTR,N,cCO,NONE,N,0,,5 5,19,3736,,,31,MANY,82,0,1,1,EMPTY,115,10,N,,,,,,16,8,1,10,,EC&G729A,, 1,CIR,Y,TRADITIO,SOCOD,1&&16,N,1,0,0,0,0,0,0,N,;
ADD-REFTA:CIRCUIT,1-2-25-0,90,0,N,N;
3.4 STMI4 : IP TRUNKING

3.4.1 IP Trunking - TIE
3) CHA-COT
8a) ADD-TDCSU
OPT=NEW PEN=1-xx-xxx-xx COTNO= COPNO= DPLN= ITR= COS= LCOSV= LCOSD= CCT= Info-field DESTNO= PROTVAR=ECMAV2 SEGMENT=8 TRACOUNT= SATCOUNT= ATNTYP=TIE NNO= ALARMNO= CARRIER= ZONE= COTX= FWDX= CCHDL= SRCGRP= CLASSMARK=EC&G729 TGRP= SRCHMODE= INS= DEV=HG3550IP BCHAN=1&&30 BCNEG= BCGR=1 LWPAR=0-25
1) ADD-BCSU
MTYPE= STMI4 (IPGW) LTG= LTU= SLOT= PARTNO= Q2324-X500 FCTID= 1 FCTBLK= (BFDAT)
4) CHA-COP
7) ADD-REFTA
5) CHA-COSSU
6) DISP-LWPAR
2) ADD-BUEND
TGRP= NAME= NO=30
CHA-LWPAR
TYPE=DIUS2 BLNO=0-25 LNTYP=COPPER MASTER=Yes SMD=Yes
10) CGWB
Endereo IP do mdulo
11) GKREG
Internal e External GW
Para adicionar canais B em um grupo existente
8b)ADD-TDCSU
OPT = NEW PEN = 1-xx-xxx-xx : DEV = S2CONN TGRP = : BCHAN = BCGR = 2-8
ADD-TDCSU
OPT=EXT PEN=1-xx-xxx-xx BCGR=1-8 BCHAN=
8b) Canais B de um tronco so relacionados para diferentes BCGRs. Esses BCGRs so adicionados em diferentes TGRPs. (Para realizar chamadas de entrada, sada e bidirecionais
Configurao de Troncos Exemplo de parametrizao mnima para IP Trunking

BFDAT
ADD-BFDAT:23,HG3550,BCHL60&BCHL120; CHA-BFDAT:CONT,23,HG3550,2,3,; CHA-BFDAT:OK,23,YES;
BCSU
ADD-BCSU:IPGW,1,2,25,"Q2324-X500",1,0,23,,,,60,,,0; /*Mdulo STMI4*/
CGWB
ADD-CGWB:2,25,NORMAL,10.20.2.5,255.255.255.0; CHANGECGWB:CGW,2,25,GLOBIF,,,213,NO,0,10.20.2.254,,100MBFD,0,0,0,0,4060,0.0. 0.0;
BUEND
ADD-BUEND:1,"IP TRUNK ",60,0,*,2,ON,0,0,NEUTRAL;
COS
COP
ADD-COP:115,,TA,TA;
COT
ADDCOT:115,PRI&RCL&XFER&ANS&CEBC&CBBN&CBFN&BLOC&DPRE&ROPT&CECO&TSCS&ICZL& ICZO&PINR&LINO&TRBA&NTON;
LWPAR
CHALWPAR:DIUS2,0,COPPER,S2,ON,N,16,0,D5,10,10,N,Y,DF,N,0,255,N,N,INDEP,;
TDCSU
ADD-TDCSU:NEW,1-02-0250,115,115,0,0,70,32,32,"",182,ECMAV2,8,,NONE,,,,GDTR,N,TIE,NONE,N,0,,5 5,19,3736,,,31,MANY,82,0,1,1,EMPTY,115,10,N,,,,,,16,8,1,10,,EC&G729A,, 1,CIR,Y,TRADITIO,HG3550IP,1&&16,N,1,0,0,0,0,0,0,N,;
4 Troncos analgicos
4.1 E1 - R2 Digital - CAS
3) CHA-COT
9) ADD-TACSU
PEN=1-xx-xxx-xx NO= COTNO= COPNO= DPLN= ITR= COS= LCOSV= LCOSD= INIGHT= TGRP= COFIDX= CCT= DESTNO= NNO= ALARMNO= CARRIER= ZONE= LINE= CIDDGTS= CBMATTR= SRCGRP= CLASSMARK=EC&G729
1) ADD-BCSU
MTYPE= DIU (PER) LTG= LTU= SLOT= PARTNO= Q2196-X FCTID= 2
4) CHA-COP
7) ADD-REFTA
TYPE=CIRCUIT PEN= (Circuito 0 ou 32) PRI= BLOCK= READYASY=
5) CHA-COSSU
6) MFCTA
Tabela 19
2) ADD-BUEND
TGRP= NAME= NO=30
8) PTIME
Initblock 49
TRTBL=GDTR ATNTYP=CO DEVTYPE=TC DEV=DIUCQ421 MFCVAR= DGTCNT=4 CIRCIDX= DIALTYPE=MFC-MFC DIALVAR=6-0
Obs: Tem que ter pelo menos 01 mdulo SIX2 (FCTID=3) configurado na central! Caso contrario os circuitos no entram em servio!
Exemplo de parametrizao mnima para R2 Digital MFCTA

COPY-MFCTA:19,1; CHANGE-MFCTA:1,MFCVAR,MISC,,,,IDBEFBS&NOMFCMO&CATTOID,N,,N,,N,,N,; CHANGE-MFCTA:1,MFCVAR,SUPERV,,,,,,,,,,,,,,,,,13,; CHANGE-MFCTA:1,TBLB,BSIGB,NASS,7,; CHANGE-MFCTA:1,TBLF,BSIGA,5,IDENT; CHANGE-MFCTA:1,TBLF,BSIGB,2,NOPO; CHANGE-MFCTA:1,TBLF,BSIGB1,2,NOPO;
CHANGE-MFCTA:1,TBLF,FIDENT,,,3455,4,,,,4,,,,34551000,8,0;
PTIME
COPY-PTIME:49,1; CHANGE-PTIME:TYPE=REST,TBLK=1,BTYPE=SHORT,S4=0,S5=1,S7=10; CHANGE-PTIME:TYPE=REST,TBLK=1,BTYPE=PARA,P11=2;
COP
ADD-COP:COPNO=32,PAR=ANS&LSUP&RLSA,TRK=TA,TOLL=TA,INFO="R2 DIGITAL";
COT
ADD-COT:COTNO=32,PAR=RCL&XFER&ANS&MFC&ATDI&NTON,INFO="R2 DIGITAL";
COS
ADD-COSSU:NEWCOS=10,AFAX=TA&TNOTCR,INFO="R2 DIGITAL";
LCOSV
CHANGE-COSSU:TYPE=LCOSV,LCOSV=32,ALAUTH=1&&64,INFO="R2 DIGITAL";
LCOSD
CHANGE-COSSU:TYPE=LCOSD,LCOSD=32,ALAUTH=1&&64,INFO="R2 DIGITAL";
REFTA
ADD-REFTA:CIRCUIT,1-1-13-0,90,N,N;
BCSU (MDULO SIU)

ADD-BCSU:SIUP,1,1,14,"Q2187-X ",R2B&R2F&R2B&R2F&R2B&R2F&R2B&R2F,0,3;
FEASU
CHANGE-FEASU:TYPE=A,CM=TRACCO; Obs: Para identificao do nmero de A no aparelho digital tem que ter parmetro TSUID na COS
Tabela de temporizao para os troncos DIU (DIUCQ421) DIS-PTIME:REST,DIUCQ421; REST TIMERS:
INIBLK TBLK LONGTIME: L1 = L2 = L3 =
: :
49 1
DEVICE : DIUCQ421
96 MS Envio de confirmacao de ocupacao depois do reconhecimento de ocupacao 1000 MS Impulso de atend. p/ DDC (so valido se P11 = 1 ou 2) 2000 MS Tempo de abertura do LOOP p/ DDC (somente valido, se P11 = 1 ou 2)
L4 = 10000 MS Reconhecimento de falha na combinacao dos Bit's da linha L5 = L6 = 200 MS Tempo de reconhecimento de deslig. forcado da Publica no sentido sainte 400 MS Nao utilizado no Brasil
L7 = 5000 MS Supervisao da confirmacao de ocupacao depois do envio de ocupacao
SHORTTIME: S1 S2 = = 60 MS Nao utilizado no Brasil MS Tempo minino de reconhecimento p/ o sinal de fim de discagem (so valido se P14 dif. 0) S3 S4 S5 S6 S7 S8 S9 = = = = = = = MS Envio do sinal do fim de discagem (so valido se P14 dif. 0) MS Vago MS MS MS MS MS MS MS MS MS MS " " " " " " " " " "
S10 = S11 = S12 = S13 = S14 =
SHORT-PARA: P1 = 2 Tipo de discagem : 0 = ,1 = MFV, 2 = MFC
P2 = 0 Deslig. forcado do Hicom : 0 = s/ deslig. forcado em trafego entrante, 1 = c/ deslig. forcado em trafego entrante P3 P4 P5 P6 P7 P8 P9 = = = = 0 Sentido de ocupacao : 0 = bid., 1 = saida, 2 = entrada 7 Nao utilizado no Brasil 1 Tempo de bloqueio de reocupacao sentido sainte ( 1 = 250 Ms ) 0 Supervisao de tom de discagem sentido sainte
= 90 Supervisao de atendimento em sentido sainte = = 0 Nao utilizado no Brasil 0 Intercalacao (Camp-on) 1 Desligamento forcado da Publica 0 Procedimentos de atendimento : 0 = sem procedimentos DDC, 1 = c/ procedimentos DDC s/ consulta de categoria, 2 = c/ procedimentos DDC c/ consulta de categoria
P10 = P11 =
P12 =
0 Nao utilizado
P14 =
0 Fim de discagem : s/ fim=0, c/ fim=1
4.2
Tronco analgico - BWA
3) CHA-COT
9) ADD-TACSU
PEN=1-xx-xxx-xx NO= COTNO= COPNO= DPLN= ITR= COS= LCOSV= LCOSD= INIGHT= TGRP= COFIDX= CCT= DESTNO= NNO= ALARMNO= CARRIER= ZONE= LINE= CIDDGTS= CBMATTR= SRCGRP= CLASSMARK=EC&G729
1) ADD-BCSU
MTYPE= PER LTG= LTU= SLOT= PARTNO=
Q2327-X182 (TMANI) Q2129-X170 (TM2LP)
4) CHA-COP
5) CHA-COSSU
2) ADD-BUEND
TGRP= NAME= NO=30
TRTBL=GDTR ATNTYP=CO DEVTYPE=TC DEV=ANMOSIG

DGTPR= CIRCIDX= DIALTYPE=MOSIG-DTMF DIALVAR=6-0
8) PTIME
Initblock 87 (TM2LP) Initblock 119 (TMANI)
Exemplo de parametrizao mnima para troncos analgicos (TMANI & TM2LP)
BCSU
ADD-BCSU:PER,1,1,3,"Q2159-X170",0,0,,,,,,A,,0; /*modulo TM2LP*/
ADD-BCSU:PER,1,1,3,"Q2327-X182",0,0,,,,,,A,,0; /*modulo TMANI*/ COS

COP
ADD-COP:5,DTMF&RLSB&RLSA&TDED&NO1A&TIM1&NSDL&DITW &DTM1,,;
COT
ADD-COT:5,RCL&XFER&NTON;
PTIME ( modulo TM2LP)

COPY-PTIME:87,6; CHANGE-PTIME:REST,6,LONG,,,200,,,,; CHANGE-PTIME:REST,6,SHORT,,,,,,,,,,6,6,,,; /*S12 temporiza a chamada*/ CHANGE-PTIME:REST,6,PARA,,,,,,0,,,,5,,,,1;
PTIME ( modulo TMANI)

COPY-PTIME:119,7; CHANGE-PTIME:REST,7,LONG,,,200,,,,; CHANGE-PTIME:REST,7,SHORT,,,,,,,,,,6,6,,,; /*S12 temporiza a chamada*/ CHANGE-PTIME:REST,7,PARA,,,,,,0,,,,5,,,,1;
TACSU ( modulo TM2LP)

ADD-TACSU:PEN=1-1-3-0,NO=1,COTNO=10,COPNO=10,COS=32,LCOSV=32,LCOSD=32,TGRP=3, CCT="TRK ANALOG",DESTNO=223,NNO=224,CARRIER=1,ZONE=EMPTY, CLASSMRK=EC&G711,ATNTYP=CO,INS=Y,DEVTYPE=TC,DEV=ANMOSIG, CIRCIDX=6,DIALTYPE=MOSIG-DTMF,DIALVAR=6-0;
TACSU ( modulo TMANI)
ADD-TACSU:PEN=1-1-3-0,NO=1,COTNO=10,COPNO=10,COS=32,LCOSV=32,LCOSD=32,TGRP=3, CCT="TRK ANALOG",DESTNO=223,NNO=224,CARRIER=1,ZONE=EMPTY, CLASSMRK=EC&G711,ATNTYP=CO,INS=Y,DEVTYPE=TC,DEV=TMANIMSG, CIRCIDX=7,DIALTYPE=MOSIG-DTMF,DIALVAR=6-0;
Tabela de temporizao para os troncos ANALGICOS
DIS-PTIME:REST,ANMOSIG; H500: REST AMO PTIME STARTED TIMERS:
INIBLK TBLK LONGTIME: L1
87
DEVICE : ANMOSIG
: 2
= 200 MS, - Tempo de tx. de sinal de flash ou terra.
L2 = 10000 MS, - Tempo de superviso de chamada para desconexo da pblica antes do atendimento (trfego entrante). L3 = 200 MS, - Tempo min. de desligamento da rede pblica.
L4 = 400 MS, - Tempo de atraso para conexo de caminho de voz, tempo min. para atendimento e atraso para ativao de superviso de linha aps atendimento. L5 L6 L7 = 400 MS, - tempo mximo para tarifao de pulsos. = 120 MS, - tempo min. para reconhecimento de ring. = 5000 MS, - tempo de superviso de tronco livre.
SHORTTIME: S1 S2 S3 S4 S5 S6 = 40 MS, - Tempo min. para pulso de tarifao (no utilizado) = 90 MS, - tempo min. para pausa de tarifao (no utilizado) = 0, - canal de escuta (0) ou de controle (1) = 0, - sinalizao de linha : HKZ (0), sem loop (1), com loop (2) = 0, - discando com V_ON (no utilizado) = 0 x 500 MS, - Atraso na ativao de deteo de ring (0 = sem atraso)
S7 = 10 x 10 MS, - tempo min. para reconhecimento de inverso de polaridade e tempo mx. para reconhecimeno da inverso no pulso de tarifao S8 = xy (xy em Decimal ou XY em Hex), - Proteo contra chamada a cobrar (DDC)
X=0 - Sem proteo contra DDC X=1 - Proteo contra DDC
X=2 - Proteo contra DDC para ramais autorizados (COS - REVCHA) Y=0 - Tempo para interrupo DDC de 250 ms y=1-10 - Tempo para interrupo DDC mltiplo de 500 ms Ateno:s8 deve ser representado em decimal. Ex. XY=11, ento S8=17 S9 S10 S11 S12 S13 S14 = 0, - superviso de reconexo. Para superviso, P2 = 2 ou 18. = 6 S, - tempo de aguardo aps chamada sainte. = 6 S, - tempo de aguardo aps chamada entrante = 0 x 30 S, - tempo limite de conversao (0 - sem limite). = 0 - inicio de ocupao de sada para resistncia baixa. 0- 10 ms e 1- 350 ms = 36, - Caracterstica da tarifao de pas para 12kHz/16kHz (no utilizado)
SHORT-PARA: P1 = 16 - Reconhecimento da interrupo de alimentao / reverso de polaridade pela PSTN em chamada entrante. P2 = 18 - Reconhecimento de desconexo para trs em caso de interrupo de alimentao e/ou reverso de polaridade da PSTN em chamada sainte P3 = 0 - Fechamento de loop / reconhecimento de liberao por interrupo da pblica antes do atendimento. P4 P5 = 0 - Estado de inicio de loop / tipo de pulso de comutao de tarifa. = 0 - Verso de SICOFI.
P6 = 1 - envio de terra (1 fio, 2 fios) / superviso de tom de discar. (0 - sem superviso de tom de disco. 1 - com superviso de tom de disco) P7 = 0 S - Superviso de sianl de atendimento em chamadas saintes (0 - sem superviso). Para superviso P2 = 2 ou 18. P8 = 0 utilizado) P9 P10 Superviso de liberao da pblica aps desconexo no HiPath/Hicom. (no
= 0 - Simulao de comutao de tarifa (no utilizado) = 5 - Atraso na ativao da superviso de linha
P11 = 32 - Nvel de ring P12 = 36 - no utilizado P13 = 17 Valores limiares para corrente alta (5 a 50 mA) e baixa (0,5 a 5 mA)
P14 = X - Parmetro dependente da impedncia de entrada e de balanceamento utilizada no pas. X=1 - Imped. de entrada = 900 , imped. de balanceamento 800//50nF X=2 - Imped. de entrada = 900 , imped. de balanceamento 400+590//50nF X=3 - Imped. de entrada = 900 , imped. de balanceamento 190+1400//105nF
5
AANT
Descrio dos parmetros COP

Texto Artificial de Anncio no comeo do reconhecimento Parmetro controla dispositivos para TMOM, de modo a ativar anncios gravados imediatamente. Anncios 'Sncronos' iro trabalhar como assncronos, e tambm anncios com msica iro iniciar imediatamente. Veja tambm AMO COT parmetro ANOD!! (Portanto, atribuir anncio gravado para a/b, ponte em c/d na TMOM). Linha com atendimento antes do anncio (MFC-R2). Linha com atendimento antes de ps-discagem (MFC-R2). Linha com reconhecimento de desconexo para trs, esperada pelo lado B, quando este desliga primeiro. Linha com reconhecimento de desconexo para trs, espereda pelo lado A, quando este desliga primeiro. Linha com codograma ANI (Para transmisso na opupao entrante, ver tambm AMO COT, parmetro ANIC) (GUS) ANI sem tom (GUS) ANI com tom (GUS) Este parmetro deve ser inserido se um anncio local (tom da SIU) deve ser escutado pelos chamadores ao invs de tom de discagem em trfego entrante analgico tipo TIE. DTN ou ANNC podem ser configurados! A linha transamite o sinal de atendimento para indicar que o lado chamado (lado B) atendeu. Ajuste relevante para aprovao e teste APDUs que so muito longas e no correspondem com Elementos de Informao de Facilidades padro ECMA/ISO, sero segmentadas. O parmetro deve ser setado para todas variantes de protocolo de CorNet-NQ, a partir da EV3.0. Mostra mensagens de erro ASN.1. Para diagnose apenas !! Temporizador 1 para superviso ANI se ANI sem tom. O tempo ajustado por meio do AMO STIM2, TYPEDH=LNGEN, REQTIM1. Temporizador 2 para superviso ANI se ANI sem tom. O tempo ajustado por meio do AMO STIM2, TYPEDH=LNGEN, REQTIM2. Este parmetro marca uma linha com discagem por pulso (decdica), e define o raio de pulsos comum (make/break) de 60/40 ms para discagem na taxa de 10 pps. Se este parmetro no for setado, a discagem por pulso transmitida em taxas de disgem a alta velocidade, com raio de pulso/pausa de 30/30 ms. tTempo de vencimento 1 de tom de ocupado para chamadas entrantes. O tempo ajustado por meio do AMO DTIM2, TYPEDH=GEN, BSGNL2. Tempo de vencimento 2 de tom de ocupado para chamadas entrantes. O tempo ajustado por meio do AMO DTIM2, TYPEDH=GEN, BSGNL2. Tempo de vencimento 3 de tom de ocupado para chamadas entrantes. O tempo ajustado por meio do AMO DTIM2, TYPEDH=GEN, BSGNL3. Tom de ocupado em resposta a solicitao CO, sem transferncia para AC. Violao da sinalizao de protocolo Modo Meet-me (busca-pessoa) Desconectao de busca-pessoa aps cada tarefa
ABAN ABPD ACKB ACKF ANIC ANIO ANIW ANNC
ANS APPR ASEG
ASNM AST1 AST2 BR64
BTN1 BTN2 BTN3 BTOF CAUS CCM CCR
CCTN COCN COTT COEI CTGF
DITW
DT1A DT2A DTBR
DTM1 DTM2 DTM3 DTM4 DTMF DTN DTT
DTV EMOV EO10 EOD
EODA
FDGT
Para CCR e CCM, espera por tom de progresso aps bloco de despacho a. Consulta para shamadas CO possvel. Tom da pblica para trfego de trnsito para troncos CO O parmetro usado para diferenciao da avaliao de ndice de calsse de mensagens IAM/ SAM (CCS#7-China) Tom contnuo em eventos de falha de grupo TSC para freqncia de portadora em troncos analgicos do tipo tie. Em bloqueio remoto de entrada ou estado de alarme de linha, o tm contnuo processado de acordo no evento de um grupo de falha do equipamento de freqencia de portadora. Se DITW declarado, a informao de dgito para ocupaes de entrada ser transferida da memria DGTPR (parmetro DGTPR no AMO TACSU) para o plano de numerao (nmero de ramal ou cdigo). Isto habilita conexes de entrada automaticamente configuradas para ramais pr-definidos (funo DIT). Tempo de atraso 1 para envio de codograma ANI. O tempo ajustado por meio de AMO DTIM2, TYPEDH=LNGEN, DELTIM1. Tempo de atraso 2 para envio de codograma ANI. O tempo ajustado por meio de AMO DTIM2, TYPEDH=LNGEN, DELTIM2. Linha com tom de discagem ao invs de desconexo para trs, aps a desconexo do ramal para ocupao de entrada (somente para discagem por pulso!). Este parmetro pode ser ajustado para permitir linha chamante a opo de estabelecer uma nova conexo para outro usurio no PABX chamado, aps desligamento da primeira chamada (conexo no desfeita e ao invs disso, um tom de discagem aplicado linha). Taxa de pulso (Make/break ratio) para DTMF 1 (Pulso=80ms/Pausa=80ms). Parmetro DTMF deve ser setado! Taxa de pulso (Make/break ratio) para DTMF 2 (Pulso=150ms/Pausa=150ms). Parmetro DTMF deve ser setado! MTaxa de pulso (Make/break ratio) para DTMF 3 (Pulso=200ms/Pausa=200ms). Parmetro DTMF deve ser setado! Taxa de pulso (Make/break ratio) para DTMF 4 (Pulso=300ms/Pausa=300ms). Parmetro DTMF deve ser setado! Dualtone multiplefrequency (um dos parmeter DTM1 - 4 deve ser setado). Tom de discagem para ocupaes de entrada. DTN ou ANNC podem ser setados! Tom de discagem ao invs de sinal de incio de discagem. O receptor de tom de discagem da linha chamante deteta e avalia o tom de discagem, e a linha chamante pode iniciar transmitindo os pulsos de discagem. So possveis mltiplos tons de discagem Habilita intercalao de emergncia e disconexo para troncos analgicos tie de entrada. Intercalao de emergncia em troncos analgicos tie com E&M ou sinalizao CF (carrier frequency) com 10 pulsos ao invs de 11 (por exemplo, interligao com EMS601) Linha transmite o sinal de fim-de-discagem para indicar que todos caracteres de discagem po pulso foram recebidos. Em trfego analgico tie, no tem outros significados (ex. para indicar que o nmero chamado esteja livre ou ocupado). Fim de discagm analisada (interligao com sistema GTD) para troncos analgicos tie com sinalizao com freqncia de portadora (CF) e n parceiro do tipo GTD ( = Sistema GTD120), se um sinal EOD especfico (livre / ocupado) deve ser avaliado. Parametro EOD deve ser setado! Linha com flash, nenhum dgito enviado
ICAC
IDP1 IDP2 IDP3 IDP4 IMEX
IVSN LAI8 LAO0 LA03 LKNQ LSI0 LSI3 LSO0 LSO3 LSUP
LWCC L3AR NBAR NO1A NOAN
NOCH
NONA NOTO NOTR NSDL NTON PDP1
Cdigo de reconhecimento interno. Se este parmetro marcado, o primeiro dgito marcado para discagem MFP2 reconecido com um sianl de linha. Este parmetro obrigatrio para controle de sinal de linha do tipo INITIAL_CODE_ACKNOWLEDGE em sistemas de sinalizao chinesas para DIUC 32 / 64 com MFP2. (China) Pausa Interdigital 1. O tempo ajustado por meio do AMO DTIM2, TYPEDH=LNGEN, IDGT1. Pausa Interdigital 2. O tempo ajustado por meio do AMO DTIM2, TYPEDH=LNGEN, IDGT2. Pausa Interdigital 3. O tempo ajustado por meio do AMO DTIM2, TYPEDH=LNGEN, IDGT3. Pausa Interdigital 4. O tempo ajustado por meio do AMO DTIM2, TYPEDH=LNGEN, IDGT4. Converso de nmero implicito para explcito com DSS1 Se o sistema usado como um DSS1 CO e "Type of number" UNKNOWN para uma ocupao entrante, o nmero encurtado pelos prefixos fornecidos, ou seja, convertido de um nmero implcito para explcito. So usados os prefixos configrados com AMO TDCSU are used. Se o parmetro no foi configurado, Type of number = SUBSCRIBER usado. Conexo E&M em interface IVSN (GUS). Este parmetro deve ser ajusado se for requerida uma adaptao de E&M para rede IVSN. Nvel de entrada ANI -0,8 dB (Padro -4,3 dB0) Nvel de sada ANI 0 dB (alternativa LAO3, Valor padro -7 dB0) Nvel de sada ANI -3,5 dB (alternativa para LAO0, Valor padro -7 dB0) Link de 2 PABX CorNet-NQ via inter-link Nvel MFR-Shuttle entrante 0 dB0 (alternativa para LSI3, padro -7 dB0) Nvel MFR-Shuttle entrante -3,5 dB0 (alternativa para LSI0, padro -7 dB0) Nvel MFR-Shuttle entrante 0 dB0 (alternativa para LSI3, padro -7 dB0) Nvel MFR-Shuttle entrante -3,5 dB0 (alternativa para LSI0, padro -7 dB0, Default -7 dB0) a) Para linhas com superviso de interrupo da linha em estado livre. b) Para linhas com superviso de interrupo da linha enquanto espera por reconhecimento de ocupao ou critrio de sinal de incio de discagem (somente para E&M). Linha com verificao contnua em caso de ocupao (CSN7, China) Registro de advertncia de camada 3. Sem tom de ocupado na desconexo da linha (Polnia). Para tom de ocupado, ver BTN1/2/3. No far reteno de sada de dgitos (sincronizao 1a para ramais analgicos) Sem atendimento na recepo do primeiro pulso de tarifao. Parametro no marcado significa que em caso de recebimento de pulso de tarifao na linha, entra como critrio de atendimento. Vlido para todos modos de sinalizao analgica sem atendimento. Linha sem tarifao. Se este parmetro marcado, a facilidade de usurio NOCHRG (valor de COSSU) transferida por DH para o LW do circuito de linha apropriado. O circuito E&M deve ser configurado com critrio de sinalizao de atendimento. Para trfego de sada para uma interface IVSN, um critrio artificial de atendimento deve ser gerado, desde que IVSN no transmite este critrio. Se este parmetro ou a facilidade da COSSU NODHRG no marcado, nenhuma mensagem transferida. Nenhum nome enviado Sem tom entre fim de discagem e atendimento. Desativa modo de transparncia entre ECMA e ISO QSIG. Linha sem sinal de incio de discagem. Invalida entrada de SDL para valor TIMx. Parmetro deve ser marcado, se o primeiro tom de discagem de troncos CO ou tie um tom de discagem pulsado, ao invs de um tom contnuo. (Padro: tom contnuo) Atraso de pr-discagem 1. O tempo ajustado por AMO DTIM2, TYPEDH=LNGEN, PDLY1
PDP2 PDP3 PDP4 PMPO PNIO RBLK
RCLA RF0C RDIG RF1C RF2C RF3C RGSZ
RLSA RLSB RMSG RRST R174 ... R191 SACK
SDL
SEDL
Atraso de pr-discagem 2. O tempo ajustado por AMO DTIM2, TYPEDH=LNGEN, PDLY2 Atraso de pr-discagem 3. O tempo ajustado por AMO DTIM2, TYPEDH=LNGEN, PDLY3 Atraso de pr-discagem 4. O tempo ajustado por AMO DTIM2, TYPEDH=LNGEN, PDLY4 POperao ponto-multiponto para chamada de troncos S0/S2 Discagem entrante/sainte em rede com precedencia Linha com bloqueio remoto. Se o circuito manualmente bloqueado, ou bloqueado devido a soft restart, o critrio de bloqueio remoto enviado para sistema parceiro. Chamada de retorno temporizada AC se outro lado no disconecta Fator de repetio 0 para codograma ANI. Codograma ANI enviado no ser repitido. Reteno do 1o. e 2o. dgito como um dgito para rota mlpp. (EUA) Fator de repetio 1 para codograma ANI. Codograma ANI ser enviado uma vez. Fator de repetio 2 para codograma ANI. Codograma ANI ser enviado duas vezes. Fator de repetio 3 para codograma ANI. Codograma ANI ser enviado trs vezes. Discagem aps registro de ocupao a) Se um destino fixo deve ser buscado via esta segunda opo de ocupao, pela transmisso dos pulsos discados do nmero de destino pela linha, este parmetro deve ser marcado. b) Se um destino fixo deve ser buscado via esta segunda opo de ocupao (registro de ocupao), que pr-inicializado no sistema B, este parmetro no deve ser marcado no sistema A. Este parmetro s relevante para registro de ocupao. Transmisso para linha do critrio desconexo para trs aps disconexo Transmisso para linha do critrio deesconexo para trs quando ocupado Envia uma mensagem de reinicializao se camada 1 ativada Reflete indicador de reinicializao & canal B quando reinicializa Elemento reserva 154 ... Elemento reserva 175 Transmisso para linha do critrio de reconhecimento de ocupao para trs, de modo a indicar que a ocupao entrante foi detectada e aceita. A linha chamante pode iniciar a transmisso dos pulsos discados aps um tempo de espera no recebimento do sinal de reconhecimento de ocupao, ou pode aguardar pela aplicao de outros critrios como um sinal de incio de discagem ou tom de discagem. Transmisso para linha do sinal para trs de incio de discagem para a linha chamante, de modo a indicar que a ocupao entrante foi detectada e a linha est pronta para receber os pulsos de discagem. A linha chamante pode iniciar a transmisso dos pulsos discados aps um tempo de espera no recebimento do sinal de incio de discagem. Este parmetro usado para cortar atravs da sequncia de discagem em interligaes com anncios locais por n discado, por exemplo, como usado em companias de utilizao de energia. Este parmetro deve ser ajstado somente junto com DP (discagem por pulso). O critrio de dim-de-discagem imediatamente marcado para ocupaes de sada, ou seja, os pulsos de discagem so transmitidos assim como discagem de sufixo para uma linha aberta.
SFRM
Linha com modo especial. Este parmetro deve ser setado para critrios individuais para linhas E+M (variantes US e UK), Alm disso, o parmetro deve ser marcado para conexes TSC com sinalizao intermediria (AC/CF). Dependendo do dispositivo manipulado, o parmetro SFRM tem diferentes funes. a) Funes para troncos de comutao S0/S2. Este valor de parmetro deve ser marcado para linhas comutadas S0/S2 que no podem processar mensagens RESTART. b) Funes para dispositivos tipo TMLS Isto afeta os seguintes tipos DEV no AMO TACSU: BWLD, BWEDG, BWELS, BWELSC, BWLG, BWLRS, DIDLSR, BWSR, DIDBELG, DIDIT, DIDN2, DODBELG, DODFR, DODIT, DODN2, BWALS70, BWMSCH, BWMFR, BW, DIDALS70, BWRSA, BWFIN, BWCHINA, ICF, ICLCH, ICLLP, ICLFB, ICLIB, NDIDIT, NDIDN2, ICN2, SOCFR. Reconhecimeto de discagem abreviada Este parmetro permite um transporte transparente de discagem de elementos de informao HLC, LLC e BC dentro de um sistema e, com restries, dentro de uma rede CorNet-N. Transmisso transparente correntemente possvel entre terminais EDSS1 e/ou entre um terminal EDSS1 e uma central EDSS1. Aviso: Parametros devem ser setados para todos os troncos digitais at EV1.0. A partir da EV2.0 a funo revertida, o que significa que o parmetro no deve ser marcado por padro! Ramal de identificao externa. Linha com tempo dependente de tom de discagem CO Usado para atribuir troncos CO BWFIN (R2-Finlandia) e SOCFR (R2-Frana) como troncos tie Temporizador de sinal de incio de discagem 1. O tempo deve ser ajustado por meio do AMO DTIM2,TYPEDH=LNGEN, STADIAL1. Temporizador de sinal de incio de discagem 2. O tempo deve ser ajustado por meio do AMO DTIM2,TYPEDH=LNGEN, STADIAL2. Temporizador de sinal de incio de discagem 3. O tempo deve ser ajustado por meio do AMO DTIM2,TYPEDH=LNGEN, STADIAL3. Temporizador de sinal de incio de discagem 4. O tempo deve ser ajustado por meio do AMO DTIM2,TYPEDH=LNGEN, STADIAL4. Habilita sinalizao de 'intercalao de emergncia'. Somente em conjuno de troncos analgicos tie com sinalizao E&M ou CF signaling e a facilidade intercalao de emergncia (n parceiro tambm deve ser um Hicom/HiPath). Assegura a imediata disconexo de um tronco in grupo de troncos requerido no n trnsito se estado de todos os troncos ocupados (ATB) ocorre. Parametro deve ser marcado, se outros tons de discagem de troncos CO um tom de discagem pulsado, ao invs de contnuo. (Padro: tom contnuo)
SPD SPTR
STNI TDED TIE TIM1 TIM2 TIM3 TIM4 TRAC
WOT2
Relao de grupos: Ou nenhum ou exatamente um dos valores IDP1, IDP2, IDP3 or IDP4 deve ser especificado. Ou nenhum ou exatamente um dos valores TIM1 ou TIM2 deve ser especificado. Ou nenhum ou exatamente um dos valores TIM3 ou TIM4 deve ser especificado. Ou nenhum ou exatamente um dos valores PDP1, PDP2, PDP3, PDP4 deve ser especificado. Se DTMF especificado, exatamente um dos valores DTM1, DTM2, DTM3 ou DTM4 deve ser especificado.
Notas no parmetro PAR a) Se SDL especificado em TIM1-2, TIM1 entrado no COP, mas TIM1 ou TIM2 podem ser alocados de maneira especfica. b) Se TIM1 ou TIM2 especificado, SDL automaticamente marcado, porm tambm pode ser entrado. c) Em casos excepcionais, por ex. TSILP, TSAUST e TSIFD, o valor de parmetro TIM... requerido, mas no SDL. SDL pode ser suprimido pela especificao de NSDL. d) Tronco TSILP tem tom de discagem em ocupao de sada ao invs de sinal de incio de discagem. Os parmetros DTT + TIM.. + NSDL devem ser marcados. e) Troncos TSAUST e TSIFD podem ser atribudos ou sinal de incio de discagem ou tom de discagem na ocupao de sada, assim como desejado. Em parmetros COP [SDL] + TIM.. + SACK ou DTT + TIM.. + NSDL so marcados. f) Tronco TSAUST tambm requer parmetro COP ACKF (release acknowledgement forwards). g) Para discagem direta a sada de um PABX satlite via MAINLPNW, se PAR=STNI marcado (no PABX principal), a identificao do nmero do ramal iniciada via dados de linha MFC. O parmetro somente relevante para DEV=MAINLPNW (AMO TACSU, modulo TMBS). h) Dependendo do dispositivo manipulado, os valores de parmetro SFRM e DITW deem ter diferentes funes. Valor de parmetro SFRM 1. Funes para troncos de comutao S0/S2 Este valor de parmetro deve ser marcado para linhas comutadas S0/S2 que no podem processar mensagens RESTART. 2. Funes para dispositivos tipo TMLS (DB_DH_DEV_TYPE_TMLS) Isto afeta os seguintes tipos DEV no AMO TACSU: BWLD, BWEDG, BWELS, BWELSC, BWLG, BWLRS, DIDLSR, BWSR, DIDBELG, DIDIT, DIDN2, DODBELG, DODFR, DODIT, DODN2, BWALS70, BWMSCH, BWMFR, BW, DIDALS70, BWRSA, BWFIN, BWCHINA, ICF, ICLCH, ICLLP, ICLFB, ICLIB, NDIDIT, NDIDN2, ICN2, SOCFR. Funo de SFRM Se o valor de parmetro no especificado, a faixa completa de dgitos e caracteres (0-9,*,#,A,B,C,D) transmitida para a central, para conexes saintes. Se este parmetro especificado, # no ser transmitido para a pblica, mas usado como um fim-de-discagem. 3. funes de SFRM para troncos tie analgicos O valor de parmetro SFRM deve ser marcado (para sinalizao de freqncia de portadora) se o sistema parceiro um sistema trnsito com sinalizao AC/CF.
O valor de parmetro SFRM deve ser marcado para sinalizao E&M, mtodo de sinalizao "Padro Americano", GBR/UIL, DC5/AC15, DELAY-DIAL e IMMEDIATE (para discagem por pulso e discagem DTMF), para loop e conversor. Valor de parmetro DITW Se DITW declarado, a informao de dgito par aocupao de entrada transferido da memria de DGTPR (parmetro DGTPR no AMO TACSU) para o plano de numerao (nmero de ramal ou cdigo). Isto habilita conexes de entrada para ramais pr-definidos serem marcados automaticamente.
5.1
Novos parmetros COP a partir do HiPath 4000 V 2.0
COP
Novos parmetros: LCOS -> Limitao de LAUTH para 32 para transferncia Parmetros RES 162-171 so omitidos
Siemens
Descrio dos parmetros de COT

Descrio Anncio Sncrono no ramal se ocupado ou no atende Anncio Sncrono antes da interceptao pela operadora, se parte chamada est ocupada ou no atende Atendimento antes da ps-discagem ou anncio Este parmetro deve ser marcado se a CO requer um critrio de atendimento antes da permisso de discagem por sufixo ou anncio AC com reverso de tarifa Este parmetro deve ser ajustado de modo a permitir operadora configurar chamadas com reverso de tarifa Console de atendimento com trace de chamada Este parmetro deve ser setado, de modo a permitir operadora iniciar um trace de chamada na linha Atenuao em troncos DIUC CO Este parmetro marcado para troncos comutados DIUC, que requerem um repeidor de linha (na direco para o qual o parmetro setado) para estimular o nvel de transmisso Os repetidores de linha so tambm requeridos para conexes de um grupo de troncos digital para uma central local analgica. Desde que os conversores na central local no possam resetar para um nvel de transmisso mais alto, os sinais devero ser amplificados no Hicom /HiPath. O estmulo de sinal somente necessrio para caminhos de conexes entrantes, mas ainda deve ser marcado para todas as conexes Se este COT no for marcado, a matriz T-REF verificada para todas as linhas com o valor TMA_AMT Linha com avano em transmisso de fim-de-discagem (ex. para sinalizao disagem por pulso e Mosig) Interceptao da operadora para chamadas desviadas. Chamadas que tem que ser marcadas como desviadas no so redirecionadas de volta central pblica. Se este valor marcado, a chamada interceptada pela operadora, pois de outro modo um tom de ocupado enviado central pblica. Este parmetro previne desvio de chamada sendo encaminhado de volta central de comutao.
Parmetro ABNA
ABPD
ACRC
ACTR
ADIU
AEOD
AICF
ANHT
Anncio gravado em grupo de busca se chamada entrada em uma fila de chamada. Se este parmetro marcado, um anncio ativado para cada chamada entrada em uma fila de chamada de um grupo de busca. O parmetro usado em pases que preferem transmitir um tom de reteno para chamantes em um a fila de um grupo de busca, ao invs de um tom de chamada Anncio assncrono na interceptao para ATND Se este parmetro marcado, um anncio curto tocado para o chamante na interceptao operadora O anncio pode ser configurado com AMO-SSC, CPCALL=ANNICPT Anncio Local Este parmetro deve ser marcado se um anncio local deve ser alimentado Anncio sem atraso Se este parmetro marcado, um anncio comutado para chamadas via esta linha sem atraso (se configurada). Ver tambm AMO SYNCA e parmetro COP AANT (anncio de texto artificial no comeo do reconhecimento) Sinal de atendimento da linha Linha com atendimento. Este parmetro deve ser marcado na direo do sistema parceiro, se linhas devero ser comutadas atravs deste sistema Aviso de tarifao por chamadal (automatico ou na requisio) Configurao relevantes para aprovao Este parmetro permite configuraes especiais para aprovao
ANNA
ANNC
ANOD
ANS
AOCC APPR
APSM
Anncio sncrono se PSM Anncio sncrono comutado para chamantes a um sistema CCM (PSM) Anncio sncrono se rmal no est ocupado Este parmetro marcado se um anncio sncrono deve ser comutado para chamadas entrantes para ramais livres. Este anncio somente comutado para chamadas via troncos com este parmetro Identificao de atendente Um nmero para CO demandado pela pblica em chamadas entrantes para ATND. Para identificao CO (central) no console da operadora Ativa administrao de contagem de trnsito para linhas S0/S2. O nmero mximo de conexes em uma rede pode ser administrada com parmetro TDCSU TRSCOUNT marcado um bloqueio de fim-de-discagem Se este parmetro marcado, o campo SENDING_COMPLETE setado para true to logo os contadores de limite de pulso em srie atingido (fornecida pela restrio de tarifadora externa e dependente dos dgitos discados) Desligamento para trs aps chamada de retorno Segue com uma chamada de retorno para o originador (atendente ou terminal noturno), este parmetro usado para liberar o tronco se no houver atendimento. o tempo de liberao aps a chamada de retorno ajustada usando o AMO CTIME, parmetro RELREC. Este parmetro permite um desligamento para trs (de uma chamada CO entrante) se um sistema inicia uma chamada de retorno para operadora ou ramal em noturno no atende Permite chamada para grupo de busca ocupado. Se uma chamada em fila atribuda ao grupo de busca, chamadas entrantes sero postas na fila Rechamada em rede automtica em caso ocupado Rechamada se ocupado permitida no mbito da rede (na direo em que o parmetro marcado). Este parmetro somente liberado para WTK e linhas So/S2. Rechamada em rede automtica em caso livre Rechamada em no atendimento permitido no mbito da rede (na direo em que o parmetro marcado). Este parmetro somente liberado para WTK e troncos S0/S2 CDR para chamadas entrantes Este parmetro permite detalhamento de bilhete para conexes de sada aps quebra de uma portadora da rede Mostra tarifa da chamada no display do usurio do telefone CDR para chamada entrante Este parmetro permite bilhetagem para conexes entrantes CDR para chamada sainte Este parmetro permite bilhetagem para conexes saintes CDR para chamadas de trnsito Transferncia de chamada sobre a linha (em estado de conversao ou ocupado) Se este parmetro marcado, pode ser feita uma transferncia de chamada antes ou aps o atendimento (ou seja, para transferncia para destinos independentemente se estiverm ocupados, livres ou em conversao). Este parmetro vlido para circuitos analgicos em rede, circuitos ISDN e troncos ISDN Transferncia de chamada para ramal ocupado com aviso camp-on Se este parmetro marcado, uma chamada transferida so possvel de um estado de chamada. O parmetro deve ser setado para o lado B (lado entrante) de um circuito. Este parmetro vlido para circuitos em rede analgica, rede ISDN e troncos ISDN. Transferncia da operadora para ramal ocupado com aviso camp-on Este parmetro permite operadora extender uma chamada para um usurio ocupado com envio de um aviso camp-on ( ou seja, indicao de chamada entrante)
ASNB
ATDI
ATRS
BLOC
BRAR
BSHT
CBBN
CBFN
CDBO
CDRD CDRI
CDRO
CDRT CEBC
CEOC
CECO
CFBU
O parmetro deve ser setado para permitir desvio de chamada para assinantes em estado ocupado O parmetro FWDN tem a funo de desvio em caso incondicional (CFU - Call Forwarding Unconditional) e continua vlido para todos os tipos de troncos Este parmetro COT pode ser atribudo para todas linhas comutadas entrantes e saintes do tipo S0/S2 e linhas tie com protocolos CORNET-N ou ECMA-Qsig Desvio em caso de no atendimento com desligamento precoce Desligamento precoce requer por CFNR/FNAN (Call forwarding No Reply / Forward on No Answer) Este parmetro deve ser marcado para permitir programao de um desvio por outros usurios na rede. Este parmetro COT pode ser atribudo para todas linhas comutadas entrantes e saintes do tipo S0/S2 e linhas tie com protocolos CORNET-N ou ECMA-Qsig Este parmetro permite desvio remoto para assinantes (desvio para destinos remotos) Ativar, desativar, interrogar troncos com desvio na provedora possvel programao de desvio para todos os troncos Este parmetro deve ser marcado para procedimento de validao de desvio a um destino Este parmetro COT vlido para troncos com protocolo CORNET-N ou Qsig Comutao de reteno para tom de chamada Este parmetro deve ser setado se chamadores devem escutar tom de chamada ao invs de tom de reteno, aps transferncia da chamada pela operadora (ou seja, estado de final de reteno) Tom CO regenerado em ocupao de sada Um tom simulado internamente na central transmitido pela linha para conexes saintes. Somente para linha S2/S0 inter-PABX CPS 6 setado com conexo tipo "CO" Se este parmetro marcado, todas chamadas entrantes na central via trnsito ou linhas tie so tratados como CPS6. Isto tambm se aplica se parmetros TIE ou ITT so setados Conexo DIUS2 para CSN7- Rede Chinesa Transferncia de chamada somente em estado de alerta Se este parmetro marcado, transferncia de chamada somente permitida se parte consultada Es livre ou j atendeu. Este parmetro vlido para troncos com protocolo CORNET-N ou ECMA-Qsig Nmero de n padro deve ser usado Este parmetro deve ser marcado se o nmero de n padro da linha para ser usada para propsitos de verificao em display. O nmero de n padro atribudo em TACSU/TDCSU/TSCSU, parmetr0 NNO Este parmetro somente trabalha na direo entrante. No necessrio assinalar este parmetro para linhas comutadas. Deve ser atribudo para linhas tie. O parmetro LWNC executa a mesma funo na direo sainte (para uso de verificao em display) DIU-CAS with digital data transmission Feature for China Digital data transmission via DIU-C This value is only specified for trunk t circuits. (Add the digit analysis results n DTED, DTE and/or the combi-codes DTEDNO, DTENO using the AMO WABE. Use AMO RUFUM to initiate digit conversion to specific DTE devices. Tom de discagem na ocupao entrante tipo 1 Tom de discagem na ocupao entrante tipo 1 - nmero de n prprio Tom de discagem na ocupao entrante tipo 2 Tom de discagem na ocupao entrante tipo 2 - nmero de n prprio Tom de discagem na ocupao entrante tipo 3 Tom de discagem na ocupao entrante tipo 3 - nmero de n prprio Mostra o nmero discado do assinante B no assinante A
CFER
CFOS
CFRM CFTR
CFVA
CHRT
COTN
CPS6
CSN7 CTAL
DFFN
DIUD
DI1 DI1N DI2 DI2N DI3 DI3N DISN
DIT DPRE
Tronco de entrada dedicado Nmeros de destino com dgitos de prefixo para distribuio de dados de chamada. Se usurio A chama usurio B em um n diferente e todas as linhas tie so ocupadas, a chamada ser reroteada via CO. Neste caso, os dgitos de prefixo atribudos com AMO RICHT sero transferidos para CDR. Este valor de parmetro deveria ser usado para circuitos de troncos CO. Se um nmero chamado no pode atingir um usurio requerido em um sistema parceiro, pela maioria das rotas diretas, uma rota alternativa pode ser solicitada (por ex. via rede pblica). Neste caso, o no. chamado deve discar um prefixo (por ex. cdigo da central) Se o parmetro DPRE marcado, ento o nmero de destino completamente transferido para CDR, com os dgitos de prefixo discados No envia operao div_leg, baseado em dss1 e qsig Desligamento de superviso para tronco de entrada Tom de discagem entrante. Para sada marca a chamada como conexo CO Tom de discagem interno. Somente para trfego entrante analgico Desconexo de emergncia antes do atendimento. Intercalao de emergncia e desligamento somente possvel localmente (em circuitos analgicos). Os troncos somente permitem intercalao de emergncia / desconexo nesta linha / canal B. A desconexo possvel em todos os troncos analgicos e digitais, exceto TCOM e troncos CCM/CC Transbordo de FAX para phone mail - no atendimento Este parmetro marcado para transferncia de chamada de fax entrante para phonemail se a linha chamada no atender dentro de um tempo definido Transbordo de FAX para phone mail ocupado ESte parmetro marcado para transferncia de chamada de fax entrante para phonemail se a linha chamada est ocupada Desvio para rede em caso de no atendimento permitido com este parmetro (na direo em que o parmetro marcado). Este parmetro vlido para todos os tipos de chamadas O desvio incondicional permitido para o mbito da rede (na direo em que o parmetro marcado). Este parmetro vlido para todos os tipos de chamadas O servio de grupo de busca transportvel para o n parceiro Interceptao em caso de ocupado A operadora intercepta de o destino discado est ocupado. O flag FEASU ICPTDID deve ser ativado para o funcionamento desta facilidade Bilhetagem entrante pela zona ou da linha Tarifao entrante calculada pela zona ou fornecida pela linha. Para trfego entrante, as tarifas de chamada so calculadas de acordo com as tabelas da zona (tableas de tarifa) a no ser que as tarifaes sejam fornecidas pela linha (mensagens de aviso de tarifao) Bilhetagem entrante somente pela zona Tarifas de entrada computadas pela zona. Para trfego entrante, taricas de chamada somente so calculadas de acordo com as tabelas de zona. A informao de tarifa na linha no avaliada Interceptao quando o nmero no permitidor Se este parmetro marcado, todas as chamadas com cdigos de discagem no autorizados sero comutados para a operadora Interceptao quando no-perturbe ativado A operadora intercepta se o usurio chamado tiver ativado a facilidade No perturbe. O flag FEASU ICPTDID deve ser ativado para o funcionamento desta facilidade.
DSDL DSIT DTNE DTNI EDBA EODL
FAX1
FAX2
FNAN
FWDN
HGTR IBSY
ICZL
ICZO
IDIS
IDND
IEVT
Registro de eventos implausveis Se este parmetro marcado, todos os eventos implausveis sero registrados e impressos (somente funes estatsticas) Interceptao em caso livre (aps timeout) Operadora intercepta se chamada DID para um ramal no atendida aps o vencimento de um temo (timeout). O flag FEASU ICPTDID deve ser ativado para o funcionamento desta facilidade Este parmetro marcado se deve ser ignorada a ID de chamada entrante Ignora bilhetagem entrante As unidades de custo recebidas e o bit TRANSORG recebido (AMO LDAT) no so transferidos dos elementos de bilhete. Este parmetro ativado se a tarifao de chamada entrante deve ser ignorada Interceptao quando a discagem incompleta Operadora intercepta se a discagem incompleta. O flag FEASU ICPTDID deve ser ativado para o funcionamento desta facilidade Interceptao em caso de no autorizado Operadora intercepta se o destino discado no tem as autorizaes necessrias na classe de servio (flag de COSSU NOCO marcado). O flag FEASU ICPTDID deve ser ativado para o funcionamento desta facilidade. Interceptao de chamada se nenhum dgito discado Este parmetro setado para uma interceptao da operadora se nenhum dgito for discado. Esta interceptao da operadora no deveria ser setada para discagem por pulso analgica Operadora intercepta se intercalao no foi executada com sucesso Se este parmetro marcado, chamadas so comutadas para o console de atendimento seguido por uma tentativa de intercalao remota com falha Interceptao quando todos os troncos esto ocupados. Operadora intercepta se no h um caminho disponvel (por ex. todos os troncos esto ocupados ou transbordo de chamadas em fila) Incio de temporizao interna para chamada de retorno via mdulo CDG Este parmetro setado se um temporizador de chamada de retorno interna deve ser inicializado para chamadas de retorno via mdulo CDG (CORNET-DPNSS Gateway) Transferncia de usurio de grupos ITR groups via S0/S2 (NWU) Este parmetro permite a transferncia de informaoo de um grupo ITR via circuitos S0/S2 (ou seja, no mbito da rede) Troncos inter-PABX Este parmetro indica que os troncos entrantes so operados como linhas trnsito inter-PABX. O parmetro ativado para trfego entrante em conjunto com CPS 12 Nota: Se este parmetro no for ativado, chamadas entrantes so operadas como linhas de ramal com CPS 10 setado para trfego entrante Interceptao quando vago Operadora intercepta se nmero no est disponvel (no programado no WABE). O flag FEASU ICPTDID deve ser ativado para o funcionamento desta facilidade Aviso de segunda chamada em discagem direta a ramal Permite indicao de chamada em espera automtica (sinal knocking) para chamadas entrantes diretas central Aviso de segunda chamada para chamadas de troncos de entrada aps transferncia Permite indicao automtica de chamada em espera 9sinal knocking) para chamada entrante no sistema aps uma transferncia pela operadora ou ramal Aviso de segunda chamada e intercalao possvel Se este parmetro setado, intercalao ou indicao de chamada em espera em rede ser possvel na linha do usurio chamado que est ocupado.
IFR
IGID IICB
IIDL
INAU
INDG
IONS
ITB
ITRC
ITRN
ITT
IVAC
KNDI
KNEX
KNOR
LINO
Linha com nmeros implcitos O parmetro COT LINO deve ser setado para sistemas antigos (<V3.5) ou sistemas externos conectados a esta linha, para entender somente nmeros implcitos (discveis) e enviar uma combinao NPI/TON indefinida ou incorreta. Permite ativar a linha com possibilitade de enviar prestadora nmeros implcitos Ativa restrio permanente de nmeros para EDSS1 CO O ltimo de redirecionamento pode ser enviado ao phonemail Linha sem cdigo de n Este parmetro indica uma linha sem transporte de cdigo de n. O parmetro ativado para facilidades em rede mostrar nmero de ramal em rede de numerao aberta e livre de loop na rede O parmetro deve ser atribudo para todas linhas entrantes analgicas e digitais que no fornecem seus cdigos de n como parte da infomrao do nmero, por ex. linhas de ns parceiros que no so sistemas Hicom/HiPath, ou anteriores a V3.3 O cdigo de n (nmero de n) administrado nos AMOs ZAND, TDCSU, TACSU, RICHT e KNMAT. Intercalao manual Este parmetro deve ser ajustado de modo a permitri intercalao manual Rechamada para caixa de correio em interligaes com HiPath 3000 Este parmetro usado para linhas com protocolo Qsig para permitir rechamada do sistema remoto HiPath 3000. Este parmetro deve ser setado para a correo na sinalizao de requeridas rechamadas para usurios de um sistema HiPath 3000 remoto, gravadas como mensagens de correio de voz Sinalizao MFC na linha Se este parmetro marcado, o parmetro MFCVAR no dever ser posto como zero Sinalizao MFC-R2 sem sinal B Este parmetro deve ser ativado para permitir chamadas em trnsito (chamadas DDI) via um PABX principal par um PABX satlite, independentemente do protocolo de rede usado (ou seja, CORNET-NQ ou MFC-R2/CIS). Isso necessrio para sistemas MRF-R2 sem sinal para trs mas com controle de desligamento (Amo COT:COEX) Suprime a sinalizao de mensagens especficas CDR-e Chamada do Console de Atendimento sem tarifao Uma parte CO chamante no tarifada para uma chamada para console ATND (MFC). Este parmetro marcado se tarifa de chamadas para estabelecidas pela operadora paraa central de comutao no deve ser atribuda operadora Requer FEASU parmetro NOCHRG No envia aviso de tarifao durante a chamada No intercepta se trnsito sainte (somente para troncos analgicos) Se este parmetro ajustado, no h permisso de interceptao da operadora para conexes em sada de trnsito. Este parmetro foi intencionado originalmente para aplicaes especiais com PNE, mas atualmente usada para previnir a interceptao mesa operadora Circuito de entrada de um sistema sem LCR (voz) Este parmetro deve ser ativado se os parmetros de tronco para LCR no podem ser transmitidos na linha (por ex. devido a incompatibilidade de protocolos) Nesses casos, os parmetros de LCR do usurio chamado sero usados (parmetros LCOS em TDCSU/TACSU) Sem tom de reteno local, tom de reteno do sistema remoto. Este parmetro deve ser ativado se nenhum tom de reteno de ser alimentado.
LINC LPRN LRPM LWNC
MAOV
MCIW
MFC
MFOB
NCDR NCHG
NCHD NITO
NLCR
NLHT
NLRD
Este parmetro deve ser ajustado de modo a permitir o uso de autorizao LCR do tronco para conexes de dados. Conexes de dados entrantes no iro mais fornecer dados LCR No informa conferncia de sada No informa sobre causa de uma transferncia de sada No ativa Flag Trace no tronco Tronco no pose ser posto em reteno para conferncias em rede Tronco no faz re-roteamento Sem disponibilidade de dilogo simples Sem intercalao para chamadas da CO NPI ISDN, chamadas saintes NPI PRIVATE, chamadas saintes NPI Unknown, chamadas saintes Se setado, no permite ao tronco participar de uma captura no mbito da rede CorNet-NQ Se setado, no suporta informao da captura CorNet-NQ Sem tom. Somente para trfego entrante analgica Fila de chamdas tipo fora do gancho em caso de trnsito Intercalao / intruso da operadora Opo para ps-discdagem em caso ocupado possvel uma discagem por sufixo, se a parte chamada estiver ocupada Opo de ps-discagem em caso de timeout para ramal livre possvel uma discagem por sufixo se a parte chamada no atender
NOCI NOCT NOFT NOHO NORR NOSD NOVC NPIS NPPR NPUN NQNP NQPI NTON OHKQ OVRA PDOB
PDOT
PINR
Possibilidade de PIN remoto (trfego entrante e sainte) Este parmetro permite ativao / desativao remota de PIN em trfego entrante e sainte Supresso de informao no display VMS para PNE Para sinalizao entrante, este parmetro bloqueia o canal de voz para sinalizao da informao no display VMS para o terminal chamante, ou seja, a sinalizao no ir mais interferir com o prompt do operador que estiver falante. Mensagem ir determinar a prioridade da fila para AC Prioridade de intercalao / desconexo via linha S0/S2 Intercalao de emergncia na rede / desconexo para linhas tie S0/S2 (via simples canal B) ou para linhas analgicas tie com E&M ou sinalizao CF Requer em FEASU flag EMOVR Controle de desconexo com sinal de ocupado Este parmetro deve ser ajustado para permitir controle de desconexo com simulao de um sinal de ocupado (tom de ocuapado/mensagem de texto no display para linhas chamadas quando a parte chamante desliga). O sinal de ocupado (e texto) resetado quando a parte chamante toma o mono-fone novamente Chamada de retorno (se usurio desliga aps consulta da chamada) Chamada de retorno para operadora se usurio vai para estado no gancho durante consulta de chamada. Este parmetro vlido para linhas analgicas (DEV=BW). Este parmetro deve ser declarado pra todos os troncos analgicos que devem iniciar uma chamada de retorno nestes casos.
PNEV
PRI PROV
RCBS
RCL
RCLS
Supresso de chamadas de retorno para operadora, em ns que no possuem operadora Este parmetro marcado se chamadas de retorno para operadora no so necessrios (na direo em que o parmetro setado). Isto , para trfego interno via linhas tie ou trfego para PABX satlite sem uma operadora. Este flag tambm requerido para troncos DDR (junto com parmetro COP flag DITW), ou seja, para configurar chamadas de troncos diretas a ramais Linha com anncio sncrono de acordo com requisio pela DDI Este parmetro marcado se um dgito requerido para discagem entrante direta (em discagem por sufixo) Conexo para rota com otimizao de n. Este parmetro indica uma linha que leva a um n com otimizao de rota O parmetro marcado apenas para linhas CORNET-N/NQ conduzindo a sistemas Hicom / HiPath. Isso marca aquelas linhas que so configuradas para otimizao de rota. , ou seja, para as quais o parmetro ROUTOPT do AMO RICHT setado Conexo satlite via linha S0/S2 Este parmetro indica que as linhas S0/S2 so usadas para conexes de satlite O nmero mximo de conexes de satlites em uma rede pode ser administrado como auxlio do contador de satlites do AMO TDCSU, parmetro SATCOUNT. Anncio sncrono do tipo transporte Linha com dgito simples DDR No envia elementos de bilhete. Este parmetro suprime a transmisso dos elementos de tarifao (elementos de bilhete) Canal de voz comprimido. Este parmetro deve ser ajustado para operao com compresso de canal B Este parmetro usado para as facilidades de captura sistmica e reteno para ramal analgico. Para chamadas entrantes, quando a chamada posta em espera para uso das facilidades de captura sistmica ou reteno de ramal analgico, ao se expirar o tempo de reteno, a chamada interceptada pela operadora.
RDDI
ROPT
SATC
SATR SDID SNBE
SPCM
SPAH
SUPN TCET
Suprime o nome do display para trfego externo Conexo atravessada se chamada transferida para estado chamante, em caso de trnsito ISDN Se este parmetro marcado, as chamadas so comutadas para um estado de transferncia de ringe nenhum tom de reteno aplicado. O grupo de troncos marcado apenas para re-roteamento. Tie lines Este parmetro indica que os troncos de entrada so tratados como troncos TIE. O parmetro marcado com trfego entrante em conjunto com CPS 11 (Call progress state 11). Nota: Se este parmetro no for marcado, as chamadas entrantes sero operadas como linhas de ramal com CPS 10 para trfego entrantre Identificao de tie Para centrais pblicas, a identificao no console da operadora para conexo roteadas via linha de trnsito (DAR=TIE) Ocupao de circuito trnsito sobre concluso de sinalizao MFC (sinaliza tom de chamada para pblica) Permite trace de chamada maliciosa na linha (por exemplo, em ISDN)
TGRE TIE
TIEI
TMFC TRAI
TRSC
Tronco envia os custos sobre tarifao para o n de origem. Se este parmetro marcado, o tronco retorna o custo total ao invs das unidades de tarifao para o n de origem, para bilhetagem em trfego de trnsito (aplica-se para bilhetagem interna). Se este parmetro no marcado, as unidades de trarifao (pulsos) so retornados para o n de destino. Neste caso, os dados centrais de sistema do n de origem deve ser configurado de modo apropiado (ZAND:TYPE=CCD,CDDISPEXT=UNIT). O parmetroTRSC substitui o antigo parmetro COT CHRG Tirado do Manual de Servios Se TRSC marcado, valores de cursto so enviados nesta linha na direo do n de origem e pode ser mostrado na fonte, mesmo se bilhetagem noesteja rodando. Se TRSC no marcado, unidades so enviadas ao invs de valores de custos. Este parmetro tem efeito somente em ns trnsitos de uma conexo. Sinalizao TSC de mensagens de correio externas. Este parmetro permite a sinalizao de mensagens de caixa de correio externa (controle de Servidor). Com este parmetro ajustado, ativa-se sinalizao TSC. Este parmetro permite discagem irrestrita de sufixo (isto , discagem em linha aberta) para usurios DIGITE para conexes analgicas/CAS entrantes e saintes, em conjunto com discagem DTMF Servio de sinalizao usurio-a-usurio classe 1 (conexo no estabelecimento da chamada bsica) Servio de sinalizao usurio-a-usurio classe 2 (conexo de chamada bsica) Servio de sinalizao usurio-a-usurio classe 3 (conexo no estabelecimento da chamada bsica, conexo no desligamento da chamada bsica) Compresso de voz no permitida Este parmetro deve ser marcado se deve haver preveno contra compresso de canais B Voice Mail Service Acesso ao correio de voz integrado ao sistema HICOM, voice mail server (VMS). Somente para trfego entrante. Anncio sncrono para chamadas em fila de ATND Este parmetro deve ser ajustado para um anncio de espera na linha ( aguarde por favor) Transferncia de chamada de tronco (desvio) Transferncia da chamada entrante CO. Se parmetro ZAND CONFSUB=Y setado, este parmetro (XFER) tambm avaliado para chamadas de conferncia com linha comutada. Conferncias com uma linha de ramal interno, uma linha comutada e outra linha comutada no so executados se CONFSUB=Y e XFER no marcado. Incio de temporizao externa para chamada de retorno via CDG. Os parmetros ITRC e XTRC so mutuamente exclusivos.
TSCS
USD
UUS1 UUS2 UUS3
VCMN
VM
WAAN
XFER
XTRC
6.1
Novos parmetros COT a partir do HiPath 4000 V 2.0
COT
BKNA BFSR CDN CFBN DTMF IBBA PGEP SPCP -> -> -> -> -> -> -> -> Ativao desabilita facilidade entrega do nmero chamante Bloqueia comutao para desvio aps rejeio desvio de chamada no mbito da rede Desvio em caso ocupado no mbito da rede Entrada dtmf quando SETUP no contm classmarks Envia dgitos via grupo de netrada dtmf antes do atendimento N parceiro no conhece sinalizo GEP do HiPath Preferncia para compresso de voz
LCR
2. LCR
LCR
LCR
Contedo
- LCR bsica - LCR para plano de nmerao fechado - LCR para plano de nmerao aberto - LCR baseado no grupo de origem - LCR por horario. - LCR para IP Trunking
LCR
LCR
1
1.1
Roteamento por Menor Custo (LCR)

Definies Gerais do termo LCR
O termos geralmetne referido com Roa de Menor Custo (LCR - Least Cost Routing) aponta para a habilidade da central em otimizar o controle da seleo de um canal para conectividade. Portanto, LCR se refere normalmente ao fato de tomar o caminho mais barato. Os dgitos discados pela parte chamante devem, essencialmente, corresponder a um sistema de cdigo de dgitos definidos (AMO LDPLN). Isto resulta em um direcionamento permitindo vrios caminhos alternativos para atingir a parte chamada (AMO LDAT). Dependendo do caminho escolhido, os dgitos discados podem ser manipulados na seqncia pelo sistema, de forma a definir regras de discagem para o LCR (AMO LODR). Alm disso, com LCR possvel a escolha de direes a serem ocupadas ou as rotas alternativas a serem controladas. Os dados configurados no ramal tambm sero usados como critrio de escolha da rota (LCOS (LAUTHs), grupo ITR, grupo DPLN, grupo de origem (SRCGRP)). A procura por uma porta livre manipulada uma vez durante o processamento da chamada, ou repetidamente, baseado em controle de espera de loop. O processamento somente feito aps uma verificao completa do plano de numerao. A recepo de um sinal de congestionamento da central de destino, no resulta necessariamente no cancelamento do processamento de chamada. No caso de um re-roteamento, outro caminho determinado para o destino desejado, caso disponvel, e a chamada continua por este caminho. Chamadas externas so roteadas para o n privado, que localizado mais prximo do destino, caso o destino possa ser encontrado dentro da rea de interligao da rede privada. Isto resulta em uma otimizao de custo, pois gera uma quebra na conexo com a central pblica (Breakout).
1.1 1.2.1
Definies mais importantes Nmeros de n
O nmero de n uma estrutura de construo hierrquica para facilitao da localizao do n dentro da rede privada (desde Hicom 300E V1.0). Uma rede pode conter at 3 nveis, resultando em at 3 estgios de nmeros de n. A apresentao para os parmetros de AMO ser (exceto para AMO KNMAT) aa-bbb-ccc. Isto : aa = Nvel 2 (domnio) nmero de rea (0-29) bbb = Nvel 1 (sub-domnio) nmero de rea (0-253) ccc = Nvel 0 (n) nmero de n (0-999) Um n multi-nvel estimado como nico, se diferir de pelo menos um nvel de outro nmero de n. O nmero 0 do nvel mais baixo significa qualquer (ex. 2-0-0).Os zerospodem ser omitidos (ex. 0-0-2 = 2).
LCR
Nmero de n Fsico Um nmero de n fsico atribudo a todo n (HiPath 4000). Este nmero de n deve ser nico dentro da rede e define o PABX. O nmero entrado de forma sistmica (AMO ZAND, parmetro PNNO). a base para a determinao automtica da topologia da rede (AMO KNTOP) e para gerao da identificao da chamada e identificao de facilidades (como por ex. bilhetagem). Nmero de n virtual Um nmero de n virtual caracteriza um n com todos os ramais e consoles de operadora. O AMO SDAT define a quais ns um ramal ou operadora sero assignados. Pelo menos um n virtual deve ser definido dentro de um n fsico. Ele pode se extender sobre vrios ns fsicos ou poderia ser um dos vrios ns virtuais dentro do mesmo n fsico. Nmeros de n virtuais so gerenciados em uma tabela separada com AMO KNDEF, Type=OWN e deve diferir do n fsico. Isto tambm se aplica a ns altenativos (LCR) e mostra a modificao do nmero.
LCR
Exemplos:
1) ZAND
PNNO>onmerodenfsicodoPABX,nuncapodeserigualaZEROetemquesernicona rede,serviraparapropsitosdedescobrimentodatopologiadaredee(identificaoda centralnarede)facilidadesemrede. PNODECD>Cdigodeacessoparaodonodonfsico(aprpriacentral),nuncapodeser igualaZEROetrabalhaemconjuntocomocdigoOWNNODEatribudonoWABEquetem queserocriadocomomesmonmeroeseracessadodacentraladjacenteviaumcdigoTIE demesmonmero.utilizadoparaasfacilidadesdeotimizaoderotaereroteamento. Obs:NUNCAPODESERIGUALAZERO
LCR
2) WABE
OWNNODE>CdigodeacessododonodoN,utilizadoparaplanode numeraoabertaetemqueserigualaoPNODECDdoZAND
LCR
3) WABE
TIE>Cdigodeacessoaosramaisefacilidadesdacentraladjacente,temqueser igualaocdigoOWNNODEdacentraladjacente.
LCR
4) KNDEF
ADDKNDEF:NNO=101,TYPE=OWN,ISDNUL=EXT,PNPUL=EXT; CHANGEKNDEF:NNO=101,DFLT=Y; KNDEF>NmerodenvirtualdetodososramaisdoPABX.
LCR
5) RICHT
DNNO>onumerodeNfsicodoPABXadjacente(902). DESTNO>atribudoonumerovirtualatribudonoKNDEFdoPABX. PDNNO>onumerofictcioparaeatribuiseomesmonumerodoDESTNO. Obs:OscamposdenmerosdeNSfictciosnuncapodemserigualaZERO.
LCR
6) LDAT
DNNO>SeronumerodeNvirtualcriadonoKNDEFqueaquiserfictcio Obs:NuncapodeserigualaZEROetemqueserniconarede
LCR
UNKNOWN>PlanodenumeraoabertoparaHipath4000 LEVEL=0IstoporquenoestamosutilizandosegmentaodonmerodeN. ONNO=onumerodeNvirtualatribudonoKNDEF DNNO=atribudoonumerodeNfsicodacentraladjacente(ZAND)eo numerodeNfictcio(KNDEF)daprpriacentral NUMEXT=901>onmeroquesedesejaqueapareanodisplaydoramal chamadoantesdaidentificaodonmerodoramalqueestachamando.
LCR
LCR
Exemplo para definio de nmero de n: 32072 +55 11 3687 - X
1-30-100
32073
HiPath 4000
N Virtual
ISDN
1-11-100
+55-11-3687-32072
1-30-100
42113
OWN
+55 41 322 - X
AMO KNDEF N Virtual
Curitiba IPDA
43113
1-41-160
1-89-160
OWN
+55-41-322-42113
So Paulo
1-41-160
N Fsico: 10-11-100 (AMO ZAND: ALLDATA)
Interrogao do AMO KNDEF
Virtual Node Table +-----------+-------+--------------+--------------+-----------+-----+-----+----+ | VIRTUAL | TYPE | ISDN (E.164) | PRIVATE(PNP) | UNKNOWN |POPU-| CAC |DFLT| | Node| | CC | L2 | | LA- | PRE-| | | NUMBER | | AC | L1 | KNOTEN|TION | FIX | | | | | LC SK | L0 SK | KZ SK | | | | | | | UL | UL | | | | | +===========+=======+==============+==============+===========+=====+=====+====+ |1- 11-100 |OWN | 55 | | | 58| | Y | | | | 11 | | | | | | | | | 3687 4 | | | | | | | | | EXT | EXT | | | | | +-----------+-------+--------------+--------------+-----------+-----+-----+----+ |1- 41-160 |OWN | 55 | | | 10| | | | | | 41 | | | | | | | | | 322 3 | | | | | | | | | EXT | EXT | | | | | +-----------+-------+--------------+--------------+-----------+-----+-----+----+ Station Numbers
LCR
Referindo ao nmero chamado, no HiPath 4000 distingue-se entre: a) dois planos de numerao (fechado ou aberto), que implicam em diferentes seqncias de LCR. b) trs tipos de nmeros (Unknown, ISDN e PNP (Private)) para cada plano de numerao
Nmero de ramal discado

ex. 45000
Numerao Aberta:
O primeiro campo entrado em WABE como DAR=TIE;
Numerao Fechada:
O nmero chamado entrado em WABE como DAR=STN ou. DAR=NETW; ex. 91-45000 Somente o Tipo de Nmero UNKNOWN contm nmeros de ramais em numerao fechada.
ex. 0-567-45000(Local) 0-041-322-45000(Nat.) 0-012-567-45000(Lev1) 0-0055-41-322-45000(Intern.) 0-0054-12-567-45000(Lev2) O Nmero ISDN da parte chamada segue o cdigo de sada (ex. 0) em um de trs nveis possveis (LOCAL, NATIONAL, ou INTERNATIONAL) no plano de numerao ISDN. Estes cdigos de trs nveis so padronizados (fixos). Este tipo de nmero pode ser usado dentro da rede mas tambm para redes pblicas (central pblica). Os prefixos 0 (Nat.) e 00 (Intern.) no so enviados normalmente. O Nmero PNP da parte chamada segue o cdigo de sada (ex. 0) em um de 3 nveis posseis (LOCAL, LEVEL 1, ou LEVEL 2) no Plano de numerao PNP. Estes 3 nveis de cdigos so arbitrrios. Este tipo de nmero deve ser usado comete dentro de uma rede. Os prefixes 0 (L1) e 00 (L2) no are enviados normalmente.
ex. 0-322-45000(Local)
O nmero do ramal (45000) da parte chamante segue o codigo de sada (91) no Plano de numerao UNKNOWN. Este tipo de no. deve ser usado somente dentro da rede HiPath 4000. O cdigo TIE prprio geralmente incrito como DAR=OWNNODE em WABE.
LCR
1.3
Seqncia de Interrogao Clssica de Processamento de Chamadas LCR Coleta Geral, Informao da Discagem e Categorizao
1.3.1
dados do lado chamante (7100): TLN: 7100 AMO SDAT: COS 1/2: a gerao do LCR roteia a chamada em caso da COS reter a autorizao TA (isto , sua LCOS est ativa). LCOS 1/2: mostra a chave de autorizao (LAUTHs) para sada do PABX. ITR: mostra o grupo de relao de trfego. DPLN: mostra o grupo DPLN. SRCGRP: mostra o grupo de origem. NNO: mostra o nmero de n virtual do assinante. determinao da COS ativa (LCOS) 1 ou 2: AMO BERUM
PABX
dados do sistema (PABX): AMO ZAND:ALLDATA PNNO: nmero do n fsico do sistema AMO KNDEF: dados caractersticos do sistema virtual do assinante A atribudo ( SDAT parmeter NNO).
LCR
1.3.2
LCR para Plano de Numerao Aberto
Informao de discagem de sada por ex. ISDN national: 0-041-3341-5252

Dica:
1) DISP-WABE:TYPE=GEN,CD=0;
CD DAR 0 TIE TIE Line
Os parmetros marcados em itlico so para uso posterior!
3) DISP-LPROF:PROFIDX=?
SRCGRP de acordo com SRCGRP do lado chamante LRTE
2) DISP-LDPLN:TYPE=CD,CD=00897227240
PROFIDX ? ou LROUTE ? correspondente ao grupo DPLN-do lado chamante LDP 0-W-0-89-722-x
3) DISP-RICHT:ART=LRTE,LRTE=?
MODE LRTE TRGP SVC DNNO LRTE ?
4) DISP-LDAT:LRTE=?
LROUTE schedule (A-H) LAUTH TRGP ODR ? ? ? ? ? ? 1 2 3
6) DISP-LSCHD:ITR=# do nmero chamante

sada da agenda dedicada para STN destes grupos ITR
valores no campo schedule: * -> grupo de troncos disponvel na agenda - -> grupo de troncos bloqueado na agenda E -> grupo de tronco, marcado como caro na agenda 4 5 6 ISDN NATIONAL
5) DISP-LODR:LWR=?
ODR CMD CMD CMD CMD CMD CMD echo echo echo NPI TON END
7) DISP-BUEND:TRGP=?
portas de sada (PENs)
9) DISP-SDSU:............ 8) DISP-TDCSU:PEN=?
PEN status das portas
LCR
1.3.3
LCR para plano de Nu merao Fechado UNKNOWN
Informao de discagem de sada: 7240

Dica:
1) DISP-WABE:TYPE=GEN
,CD=7240; CD DAR DESTNO DNNO 7240 STN 0 = n prprio > 0 = n externo ?
Os parmetros marcados em itlico so para uso posterior!
2)
CD
Obs: CPS=0 DISP-RICHT:MODE=CD,SVC=ALL,DNNO=? CD ? ?
MODE LRTE TRGP SVC DNNO
3) DISP-WABE:TYPE=GEN,CD=?
CD DAR 200 NETRTE
4) DISP-LDAT:LRTE=?
LROUTE schedule (A-H) LAUTH TGRP ODR ? ? ? ? ? ? 1 2 3
DESTNO
6) DISP-LSCHD:ITR=# do nmero chamante

sada da agenda dedicada para STN destes grupos ITR
valores no campo schedule: * -> grupo de troncos disponvel na agenda - -> grupo de troncos bloqueado na agenda E -> grupo de tronco, marcado como caro na agenda
5) DISP-LODR:LWR=?
ODR CMD CMD CMD CMD echo NPI TON END
1 UNKNOWN UNKNOWN
7) DISP-BUEND:TGRP=?
portas de sada (PENs)
9) DISP-SDSU:............ 8) DISP-TDCSU:PEN=?
PEN status das portas
LCR
1.3.4
Descrio dos AMOs para rota de menor custo (LCR)
Seqncia de gerao:
DIMSU ---> WABE ---> COSSU ---------------+-> LDPLN | BUEND -+-> TACSU -+-> RICHT -+-+-> LDAT -+ +-> TDCSU -+ | | +-> TSCSU -+ | | DIMSU -----------------------+ | LODR -------------------------+
1.3.4.1
AMO RICHT (rota)
Uma rota consiste em todas as vias possveis (grupos de troncos) entre dois pontos (para todos os servios possveis), sendo o primeiro ponto o sistema local e o segundo ponto o destino. O destino pode ser alcanado diretamente ou por meio de transbordo de outro grupo de troncos (grupo de troncos alternativos). O AMO RICHT usado para atribuir os grupos de troncos para as rotas LCR. Programao do servio O parmetro LSVC utilizado para atribuir o servio da chamada a ser roteado. Se no for introduzido nenhum LSVC, os grupos de troncos so instalados em comum para ambos os servios (VCE e DTE), o que resulta em um grupo principal para todos os servios da rota. Se ambos os servios devem conter grupos de troncos diferentes ou valores diferentes em LDAT, o primeiro servio deve ser instalado com o uso de MODE=LRTNEW, e o outro servio por MODE=LRTEXT, usando o mesmo LRTE (nmero de rota). Mudanas subseqentes para as rotas LCR no AMO RICHT devem usar MODE=LRTE. LCR em rede O encaminhamento para uma rede corporativa pode ser feito por uma numerao aberta entre centrais (onde usa-se cdigo de acesso para encaminhamento) onde programa-se a rota por MODE=LRTE, ou fechada (onde encaminaha-se diretamente pelo nmero do ramal) onde a programao feita por MODE=CD. necessria a definio do nmero de n da central, alm do cdigo de n das centrais de origem e destino. Nmero de destino (DESTNO) Com o DESTNO, um cdigo fictcio atribudo a um n externo. Todos os DESTNO devem ser nicos dentro de um n. O DESTNO usado pelo AMO WABE para atribuir uma rota para ramais ligados remotamente na rede.
LCR
Nmero de n de destino (DNNO e PDNNO) Para cada rota deve ser atribudo um DNNO que independente do DESTNO. Ele descreve um endereo nico dentro da rede. O DNNO deve ser diferente do nmero do prprio n. O parmetro consiste em 3 nveis: LEVEL2 - LEVEL1 - LEVEL0. Os zeros esquerda no so considerados em nenhum comando, ou seja, so tratados como se no tivessem sido introduzidos. Um DNNO todo de zeros no permitido. Otimizao de rota (ROUTOPT) Para cada rota pode ser atribuda a capacidade de otimizao de rota na rede, programada com ROUTOPT = Y e ativao de facilidade em FEASU. Reencaminhamento (REROUT) Conforme o padro, a facilidade Reencaminhamento (seleo de uma nova via) atribuda para cada rota. Entretanto, tambm possvel desabilitar esta facilidade para cada rota, usando o parmetro REROUT = Y. 1.3.4.2 LSCHD (agendamentos LCR)
A facilidade de encaminhamento de menor custo possui um conjunto de agendamentos que so usados ao configurar os elementos da rota com AMO LDAT. Podem ser definidos at 8 agendamentos, identificados pelas letras A a H. Tipicamente, eles iro cobrir a semana em faixas correspondentes s taxas de tarifao. Ao configurar uma rota LCR, deve ser feita uma introduo em cada agendamento para indicar se a rota deve ou no ser usada durante os horrio abrangidos por aquele agendamento, e, em caso positivo, um tom especial pode ser aplicado para indicar que a rota uma rota cara. 1.3.4.3 LODR (Administrao das normas de seleo de sada LCR)
O LODR usado para criar regras de seleo LCR completas (ODR), que consistem em diversos comandos para regular a seleo. Os comandos so identificados por um nmero para cada ODR e atribudos aos elementos de rota LCR com AMO LDAT. Valores mais utilizados do ODR:
ECHO - envia todos os dgitos de um campo especfico, definido com AMO LDPLN. O nmero do campo deve ser especificado no parmetro FIELD. ECHOALL - envia todos os dgitos de todos os campos remanescentes definidos com AMO LDPLN. NPI - Identificador do plano de rede Define-se o plano de numerao usados caso os usurios desejem se comunicar entre si, mas estejam localizados em redes diferentes e usando planos de numerao diferentes, necessitam de uma converso de seus nmeros de assinante.
LCR
OUTPULSE - envia dgitos especficos no parmetro DGTS. TON - Tipo de nmero (de acordo com o NPI - identificador do plano de rede) END - Final da seqncia do comando ODR. necessrio ao final da regra. O parmetro CMDPOS, que deve ser especificado ao introduzir e substituir, determina a posio na qual o novo comando da norma de seleo de sada deve ser introduzido (parmetro REPLACE=NO) ou o comando antigo da norma de seleo de sada deve ser substitudo (parmetro REPLACE=YES). AMO LDAT (Administrao de rotas LCR)
1.3.4.4
O AMO LDAT cria os elementos de rota LCR (LRTEL) para cada rota LCR (LROUTE). Estes elementos de rota LCR especificam em qual seqncia os grupos de troncos devem ser ocupados, qual a regra de discagem a ser utilizada e quais as condies de sada. Cada elemento de rota LCR priorizado dentro da rota LCR e lhe atribudo um grupo de troncos a partir desta rota, uma norma de seleo de sada e uma autorizao LCR. Adicionar (ADD) o primeiro elemento de rota LCR a um LROUTE tambm adiciona a prpria rota. A rota pode ento ser atribuda a padres de dgitos LCR individuais, usando-se AMO LDPLN. Apagar o ltimo elemento de rota LCR de um LROUTE tambm apaga a prpria rota. Tambm possvel alterar (CHANGE) os dados de um elemento de rota LCR, adicionar (ADD) novos elementos de rota LCR e apagar (DELETE) elementos de rota LCR. Com o AMO LDAT, podem ser usados para uma rota LCR apenas os grupos de troncos que tenham sido previamente atribudos rota por meio do AMO RICHT. 1.3.4.5 AMO LDPLN (Administrao do padro de dgitos LCR)
O AMO LDPLN administra o plano de seleo LCR. Os padres de dgitos LCR (LDP) so classificados e armazenados na base de dados. Uma rota LCR configurada e uma autorizao LCR so atribudas para cada LDP. Cada padro de dgitos LCR pode ser atribudo a um grupo DPLN especfico (parmetro DPLN). Se o DPLN no for especificado, todos os grupos DPLN sero vlidos na anlise. Os padres de dgitos LDP devem ser dispostos em um plano de numerao LCR, chamado DIPLNUM. O valor padro para anlise de numerao aberta 0. A seqncia de dgitos de qualquer padro de dgitos LCR pode ser dividida em at 10 campos separados por -. Estes campos podem ser acessados diretamente pela norma de seleo de sada atribuda durante o envio (ver AMO LODR).
LCR
Para que padres de dgitos individuais no tenham que ser criados para todas as combinaes possveis dentro de uma determinada faixa de dgitos, existem caracteres especiais para representar as faixas de dgitos: X - para qualquer dgitos entre 0 e 9, A e D ou * (por ex. 0 - 5X ) T - para temporizao vencida ou # (=caractere de fim de seleo. Por ex. 200 - 190 - T) Z - para qualquer seqncia de dgitos seguida por uma temporizao vencida ou # (=caractere de fim de seleo. Por ex. 540 - 543Z) W - para transmitir o tom de seleo (por ex. 0 - W - 0 - 11 - 3XX) Por exemplo, 997-XXXX representa todos os nmeros de 997-0000 a 997-9999. O modelo de dgitos (997-XXXX) identificado pelo parmetro LDP. O ltimo valor do modelo de dgitos indica o ponto de ocupao do circuito fsico. A sinalizao enviada pela linha estar definida de acordo com a regra de discagem tomada (LODR). O primeiro campo deve conter um cdigo de encaminhamento vlido (ver AMO WABE). Caracteres especiais no podem, portanto, ser usados no primeiro campo do padro de dgitos. Os cdigos de encaminhamento podem ter no mximo 6 dgitos. Os outros dgitos podem ser divididos em campos, conforme a necessidade. O padro de dgitos LCR no deve exceder a extenso de 22 dgitos. Um nvel de autorizao LCR (parmetro LAUTH) atribudo para cada grupo DPLN de um padro de dgitos, de forma que padres de dgitos LCR podem ser habilitados ou desabilitados para usurios especficos dentro do mesmo grupo DPLN. Este padro pode ser selecionado com sucesso apenas pelos usurios no grupo DPLN que tiverem esta autorizao LCR na sua classe de servio LCR ativa (AMO COSSU, parmetro LCOS). Tambm pode ser atribudo um contador de pulsos serial ao padro de dgitos LCR (parmetro SPC). O contador de pulsos serial especifica quantos caracteres em um pulso so avaliados se o final do padro de dgitos LCR estiver aberto (caractere especial Z). O valor padro do parmetro SPC o mesmo que a quantidade mxima de dgitos, isto , 22.
LCR
1.3.5
LCOSV LCOSD LAUTH LDPLN 1. 2. LROUT RICHT
Resumo: Quem quem em LCR?

pacote autorizao para LCR (voz & fax), composto por n LAUTHs; pacote autorizao para LCR (dados), composto por n LAUTHs; autorizao individual para acesso LCR. Atribudo aos ramais (LCOS) e rota (LDAT), e faz parte da anlise no padro de discagem LDPLN. LCR- com duas tarefas: LAUTH, autorizao para o padro de seleo independente de rota; determinao da rota LCR (LROUT); rota LCR: composta por todos os TGRPs possveis para esta rota; atribui TGRPs (grupos de troncos) e os dados suplementares (nmero do n de destino, reencaminhamento de rota, etc. para LROUT. No entanto, ele no controla a seqncia. Possui as entradas dos tipos: 1. 2. 3. LRTENEW - entrada para cdigos com plano de numerao aberta CD - entrada para cdigos com plano de numerao fechado LRTEEXT - expanso da rota com plano de numerao aberta seleo de dispositivos de LCR: controla as ocupaes de TGRP e determina: 1. 2. 3. 4. autorizao LAUTH para a rota (TGRP) selecionada; ODR para este TGRP; atributos nas faixas de horrios A at H (disponvel, cara, bloqueada); determinao do provedor de rede e da zona para CDR. Seqncia de ocupao: 1. 2. provedores baratos na seqncia das entradas; provedores caros na seqncia das entradas;
LDAT
LSCHD LODR
atribui faixas de horrios para o LCR controlado por tempo; regras de seleo externa;
LCR
1.3.6
Exemplos bsicos de configurao de LCR
LCR para acesso basico a rede publica

ADD-WABE:CD=0,DAR=CO,CHECK=N; ADD-LODR:ODR=1,INFO="LOCAL",CMD=ECHO,FIELD=2; ADD-LODR:ODR=1,CMD=END; ADD-RICHT:MODE=LRTENEW,LRTE=1,LSVC=ALL,NAME="LOCAL",TGRP=10,DNNO=902,DESTNO=101,PDNNO=101; ADD-LDAT:LROUTE=1,LSVC=ALL,LVAL=1,TGRP=10,ODR=1,LAUTH=1,CARRIER=1,ZONE=EMPTY,LATTR=WCHREG,DNNO=101; ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP="0"-"X",LROUTE=1,LAUTH=1;
LCR para plano de numerao fechado entre centrais

ADD-WABE:CD=001,DAR=NETRTE,CHECK=N; ADD-WABE:CD=5555,DAR=STN,CHECK=N,DESTNO=1; ADD-LODR:ODR=10,INFO="FECHADO",CMD=ECHOALL; ADD-LODR:ODR=10,CMD=END; ADD-RICHT:MODE=CD,LRTE=10,CD=001,CPS=0,SVC=ALL,NAME="FECHADO",TGRP1=11,DESTNO=1,DNNO=902,PDNNO=101; ADD-LDAT:LROUTE=10,LSVC=ALL,LVAL=1,TGRP=11,ODR=10,LAUTH=1,CARRIER=1,LATTR=WCHREG,DNNO=902;
LCR para plano de numerao aberto entre centrais

ADD-WABE:CD=811,DAR=OWNNODE,CHECK=N; ADD-WABE:CD=812,DAR=TIE,CHECK=N; ADD-LODR:ODR=20,INFO="ABERTO",CMD=ECHO,FIELD=2; ADD-LODR:ODR=20,CMD=END; ADD-RICHT:MODE=LRTENEW,LRTE=20,LSVC=ALL,NAME="ABERTO",TGRP=20,DNNO=902,DESTNO=101,PDNNO=101; ADD-LDAT:LROUTE=20,LSVC=ALL,LVAL=1,TGRP=20,ODR=20,LAUTH=1,CARRIER=1,ZONE=EMPTY,LATTR=WCHREG,DNNO=101; ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP="812"-"X",LROUTE=1,LAUTH=1; CHANGE-KNMAT:NPI=UNKNOWN,LEVEL=0,ONNO=901,DNNO=902,NUMEXT=811;
LCR
LCR para IP Trunking entre centrais

No exemplo, o LCR configurado para o n 10-69-100, de tal forma que um ramal usando a numerao aberta (UNKNOWN) neste n possa acessar um ramal no n 10-69-200 via tronco IP. Os planos de numerao fechada ou ISDN so suportados e configurados da mesma forma. Uma ramal no n 10-69-100 acessa o n 10-69-200 atravs do nmero TIE 902. ADD-WABE:CD=902,DAR=TIE; O LRTE 520 deve rotear o n 10-69-200 e usa o grupo de troncos 50 (ver acima): ADD-RICHT:MODE=LRTENEW,LRTE=520,LSVC=ALL,NAME="IP TO KN 69 200",TGRP=50,DNNO=1-69-199; A seguir mostrada uma regra simples de discagem: ADD-LODR:ODR=520,CMD=ECHO,FIELD=2; ADD-LODR:ODR=520,CMD=END; ADD-LODR:ODR=520,INFO="TIE TO GW2"; Como novidade para LDAT, entrar GW1=2-0 no LRTE 520. O 2 se refere ao parmetro GWNO no AMO GKREG. No GKREG para o n 10-69-100, GWNO=2 indica gateway com endereo IP 1.69.21.80. O 0 se refere ao nmero do sector-path (RM). Como o gerenciador de recursos no foi liberado, o caminho do setor sempre 0. ADD-LDAT:LROUTE=520,LSVC=ALL,LVAL=1,TGRP=50,ODR=520,LAUTH=1,GW1=2-0; O nmero TIE inserido no LDPLN. O nmero de chamada inserido no plano de discagem padro com DIPLNUM=0. Um ndice de perfil PROFIDX tambm pode ser usado no lugar da rota LRTE (AMO LPROF): ADD-LDPLN:LCRCONF=LCRPATT,DIPLNUM=0,LDP="902"-"X",LROUTE=520,LAUTH=1; Se o usurio deseja ser capaz de acessar o n 10-69-100 a partir do n 10-69-200, deve-se executar as mesmas configuraes. Naturalmente, o GWNO=1-0 inserido no AMO LDAT.
LCR
LCR por horrio

EXPLICAO
O LSCHD vinculado a cada LRTEL do LDAT (parmetro LSCHED), assim configuramos para cada um, as faixas de horrio no permitidas ou as faixas de horrio que so caras. Esta combinao faz com que o Hicom busque para cada faixa de horrio um LRTEL o qual no exista restrio, e este o que ser utilizado para completar a chamada. Esta caracterstica torna possvel escolher qual Operadora ser utilizada por horrio, atravs da configurao de diferentes LODR para cada LRTEL. O AMO responsvel pelo vnculo da letra da restrio com a faixa de horrio que ela compreende o LSCHD. O AMO responsvel pelo vnculo da restrio rota o LDAT, onde poderemos ter: LSCHED = [A B C D E F G H] restringe o uso desta rota na faixa de horrio definido pela letra (AMO LSCHD). LSCHED= [AE BE CE DE EE FE GE] determina que neste horrio, esta rota cara. Podemos utilizar os dois tipos de restrio para uma mesma rota. Abaixo temos trs diferentes exemplos prticos do uso destas facilidades.
EXEMPLO I
No exemplo abaixo trata-se de um cliente que quer que seu PABX seja programado para que todos possam discar da maneira antiga (sem digitar o nmero da Operadora). O cdigo CO 0 (zero). Supomos que nos dias de semana, a Operadora 21 cobra mais barato chamadas DDD das 00hs s 08hs, a Operadora 23 das 08hs as 18hs e a Operadora 89 das 18hs at 23:59. Nos outros dias (Sbado e Domingo), a Operadora 21 ser a escolhida pela empresa para efetuar as chamadas DDD. /* /* /* /* cria as faixas de horrio (obs: se configurado das 08&&18, toda a faixa de 08:00 at 19:00 ser coberta, ou at comear uma nova faixa, ex: 18&&23, deste modo a primeria faixa (08&&18) teria a abrangncia diminuda para 08:00 s 18:00)
CHA-LSCHD:ITR=0&&15,DAY=MON&TUE&WED&THU&FRI,HOUR=00&&08,SCHED=A; CHA-LSCHD:ITR=0&&15,DAY=MON&TUE&WED&THU&FRI,HOUR=08&&18,SCHED=B; CHA-LSCHD:ITR=0&&15,DAY=MON&TUE&WED&THU&FRI,HOUR=18&&23,SCHED=C; /* Regras de discagem com os respectivos cdigos de Operadora ADD-LODR:ODR=100,CMD=ECHO,FIELD=1; ADD-LODR:ODR=100,CMD=OUTPULSE,DGTS=21; ADD-LODR:ODR=100,CMD=ECHO,FIELD=3; ADD-LODR:ODR=101,CMD=ECHO,FIELD=1; ADD-LODR:ODR=101,CMD=OUTPULSE,DGTS=23; ADD-LODR:ODR=101,CMD=ECHO,FIELD=3; ADD-LODR:ODR=102,CMD=ECHO,FIELD=1; ADD-LODR:ODR=102,CMD=OUTPULSE,DGTS=89; ADD-LODR:ODR=102,CMD=ECHO,FIELD=3;
LCR
/* Exemplo de uma programao convencional de Richt ADD-RICHT:MODE=LRTENEW,LRTE=1,LSVC=VCE,NAME="LIG. DDD",TGRP=1,DNNO=100,DESTNO=200; /* Cadastro da rota 1 e as restries de horrio /* observe que as letras cadastradas no parmetro LSCHED restringem /* a LRTEL na faixa de horrio cadastrada no AMO LSCHD ADDLDAT:LROUTE=1,LSVC=VCE,LVAL=1,TGRP=1,ODR=100,LAUTH=1,LSCHED=B&C,LATTR=WC HREG&EODSTCDR; ADDLDAT:LROUTE=1,LSVC=VCE,LVAL=2,TGRP=1,ODR=101,LAUTH=1,LSCHED=A&C,LATTR=WC HREG&EODSTCDR; ADDLDAT:LROUTE=1,LSVC=VCE,LVAL=3,TGRP=1,ODR=102,LAUTH=1,LSCHED=A&B,LATTR=WCHR EG&EODSTCDR; /* Cadastro do LDPLN baseado no LODR proposto ADD-LDPLN:LDP=0-0-X,LROUTE=1,LAUTH=1 importante verificar o parmetro DPRE no COT do tronco. Este parmetro faz com que o nmero discado que enviado para bilhetagem seja o nmero real, e no o que o usurio discou no aparelho telefnico. Este parmetro normalmente requerido quando temos um tarifador conectado ao PABX. Importante: Os cdigos utilizados neste documento so meramente ilustrativos. Podem ser necessrias modificaes nas linhas de comando dependendo das programaes existentes no Hipath 4000.
AVISO DE CHAMADAS CARAS COM LCR CONVENCIONAL

Uma outra funo que poder ser utilizada a LCR convencional, porm com um aviso sonoro para chamadas feitas em horrio de pico. Depois de completar o ltimo dgito da LCR (LDPLN), se o LDAT (no parmtero LSCHED ) estiver programado com a letra da faixa de horrio do AMO LSCHD e o sufixo E (ex. AE, BE, CE),o aviso emitido, e para os ramais digitais tambm ser apresentado o texto "LIGACAO DISPENDIOSA" no display. Esta programao atenderia aos clientes que desejam que o usurio no necessite discar o cdigo da operadora ( o cdigo seria sempre o mesmo embutido na LCR) para efetuar uma discagem DDD, porm gostaria de avislos que aquele um horrio caro para efetuar a chamada.
LCR
EXEMPLO II
O cliente no quer roteamento por horrio (sempre efetuada a chamada pela operadora 21), mas quer um aviso sonoro quando a chamada for efetuada no horrio entre 12hs e 14:00. O cdigo CO 0 (zero). /* Habilitar tom de aviso de ligaes caras (tom caro): CHA-FEASU:TYPE=A,CM=LCRET; /* Habilitar o tom caro para as LCOS. CHA-COSSU:TYPE=LCOSV,LCOSV=<n.lcos>,LCROPTS=LCRET; /* Criar faixa de horrio de pico CHA-LSCHD:ITR=0&&15,DAY=MON&TUE&WED&THU&FRI,HOUR=12&&13,SCHED=A; /* Exemplo de uma programao convencional de Richt ADD-RICHT:MODE=LRTENEW,LRTE=1,LSVC=VCE,NAME="LIG. DDD",TGRP=1,DNNO=100,DESTNO=200; /* Criar regra de discagem embutindo cdigo da operadora 21 ADD-LODR:ODR=100,CMD=ECHO,FIELD=1; ADD-LODR:ODR=100,CMD=OUTPULSE,DGTS=21; ADD-LODR:ODR=100,CMD=ECHO,FIELD=3; /* /* /* /* Criar LDAT especificando que ser emitido o aviso na faixa de horrio definida como A no AMO LSCHD. Observe que cadastramos o conjunto AE, e no apenas a letra A, pois queremos o tom caro (E = expensive).
ADDLDAT:LROUTE=1,LSVC=VCE,LVAL=1,TGRP=1,ODR=100,LAUTH=1,LSCHED=AE,LATTR=WCH REG&EODSTCDR; /* Cadastro do LDPLN baseado no LODR proposto ADD-LDPLN:LDP=0-0-X,LROUTE=1,LAUTH=1 importante verificar o parmetro DPRE no COT do tronco. Este parmetro faz com que o nmero discado que enviado para bilhetagem seja o nmero real, e no o que o usurio discou no aparelho telefnico. Este parmetro normalmente requerido quando temos um tarifador conectado ao PABX.
Importante: Os cdigos utilizados neste documento so meramente ilustrativos. Podem ser necessrias modificaes nas linhas de comando dependendo das programaes existentes no Hiipath4000.
LCR UTILIZANDO LCR POR HORRIO COM FACILIDADE DO TOM CARO

Poderamos utilizar os dois recursos ao mesmo tempo. Para tanto necessrio saber que o Hicom sempre tentar sair pela rota mais barata, deste modo, se tenho duas rotas possveis para o mesmo horrio, porm uma tem restrio A e a outra AE, sairemos pela AE. Um outro exemplo ter a restrio AE para uma rota e ter uma outra rota sem restrio para uma dada faixa de horrio A. Independente do LVAL da rota no LDAT, a rota escolhida seria a sem restrio. A rota AE, s seria ocupada, neste caso, se todos os troncos do grupo pertencente rota que no restringe o horrio A, estivessem ocupados.
EXEMPLO III
Neste exemplo todas as rotas tm restrio ao horrio B, porm o LRTEL 2 tm uma restrio BE (diz apenas que caro), enquanto as outras rotas restringem a faixa do horrio em questo. Na prtica, na faixa de horrio B o usurio sair pela LRTEL 2 mas ouvir o tom CARO, na faixa de horrio A sair pela LRTEL 1 e na faixa de horrio C pela LRTEL 3, sem o aviso do tom caro. /* Habilitar tom de aviso de ligaes caras (tom caro): CHA-FEASU:TYPE=A,CM=LCRET; /* Habilitar o tom caro para as LCOS. CHA-COSSU:TYPE=LCSV,LCOSV=<n.lcos>,LCROPTS=LCRET; /* /* /* /* cria as faixas de horario (obs: se configurado das 08&&18, toda a faixa de 08:00 at 19:00 ser coberta, ou at comear uma nova faixa, ex: 18&&23, deste modo a primeria faixa (08&&18) teria a abrangncia diminuda para 08:00 s 18:00)
CHA-LSCHD:ITR=0&&15,DAY=MON&TUE&WED&THU&FRI,HOUR=00&&08,SCHED=A; CHA-LSCHD:ITR=0&&15,DAY=MON&TUE&WED&THU&FRI,HOUR=08&&18,SCHED=B; CHA-LSCHD:ITR=0&&15,DAY=MON&TUE&WED&THU&FRI,HOUR=18&&23,SCHED=C; /* Regras de discagem com os respectivos cdigos de Operadora ADD-LODR:ODR=100,CMD=ECHO,FIELD=1; ADD-LODR:ODR=100,CMD=OUTPULSE,DGTS=21; ADD-LODR:ODR=100,CMD=ECHO,FIELD=3; ADD-LODR:ODR=101,CMD=ECHO,FIELD=1; ADD-LODR:ODR=101,CMD=OUTPULSE,DGTS=23; ADD-LODR:ODR=101,CMD=ECHO,FIELD=3; ADD-LODR:ODR=102,CMD=ECHO,FIELD=1; ADD-LODR:ODR=102,CMD=OUTPULSE,DGTS=89; ADD-LODR:ODR=102,CMD=ECHO,FIELD=3; /* Exemplo de uma programao convencional de Richt ADD-RICHT:MODE=LRTENEW,LRTE=1,LSVC=VCE,NAME="LIG. DDD",TGRP=1,DNNO=100,DESTNO=200; /* Cadastro da rota 1 e as restries de horrio /* observe que as letras cadastradas no parmetro LSCHED restringem /* a LRTEL na faixa de horrio cadastrada no AMO LSCHD
LCR
ADDLDAT:LROUTE=1,LSVC=VCE,LVAL=1,TGRP=1,ODR=100,LAUTH=1,LSCHED=B&C,LATTR=WC HREG&EODSTCDR; ADDLDAT:LROUTE=1,LSVC=VCE,LVAL=2,TGRP=1,ODR=101,LAUTH=1,LSCHED=A&BE&C,LATTR =WCHREG&EODSTCDR; ADDLDAT:LROUTE=1,LSVC=VCE,LVAL=3,TGRP=1,ODR=102,LAUTH=1,LSCHED=A&B,LATTR=WCHR EG&EODSTCDR; /* Cadastro do LDPLN baseado no LODR proposto ADD-LDPLN:LDP=0-0-X,LROUTE=1,LAUTH=1 importante verificar o parmetro DPRE no COT do tronco. Este parmetro faz com que o nmero discado que enviado para bilhetagem seja o nmero real, e no o que o usurio discou no aparelho telefnico. Este parmetro normalmente requerido quando temos um tarifador conectado ao PABX. Importante: Os cdigos utilizados neste documento so meramente ilustrativos. Podem ser necessrias modificaes nas linhas de comando dependendo das programaes existentes no Hipath 4000
LCR
LCR
LCR
LCR
2
2.1
Grupos de Origem LCR (AMO LPROF)

Descrio da Facilidade
Dependendo do grupo de origem, diferentes rotas LCR podem ser selecionadas sem, por exemplo, a necessidade de usar um LCOSx especial. Isso permite no s que o roteamento seja designado dependendo do n, mas tambm que seja dividido ainda mais. As rota LCR pertencentes a um grupo de origem so definidos em uma tabela com o AMO LPROF. No AMO LDPLN, ento possvel fazer referncia tabela com o parmetro PROFIDX. Se uma entrada existe no padro de dgito (no AMO LDPLN), a tabela administrada pelo AMO LPROF levada em conta, e a aprovao do grupo de origem especfico com os valores da tabela confirmada. se uma entrada que combine encontrada, o prximo passo para a seleo realizado com base no LTRE especificado, seno, o LROUTE originalmente inserido no AMO LDPLN utilizado para futuras selees.
2.1.1
Informao do Servio
Um grupo de origem pode explicitamente ser designado a um Calling Party (e.g. com AMO SDAT) ou, como padronizado, derivado do slot (in shelf, AMO UCSU). No AMO LPROF, somente vlido, i.e. LRTEs existentes podem ser inseridos.
LCR
Calling Party
Discagem SRCGRP Wegeauswahl
AMO WABE
AMO LDPLN LROUTE PROFIDX
AMO LPROF PROFIDX SRCGRP LRTG
OR
1 to 99
AMO RICHT LRTE
AMO RICHT LRTG
AMO LDAT LROUTE
AMO LDAT LRTG
AMO LODR
AMO LODR
Called Party (No h roteamento do Grupo de Origem)
Called Party (LROUTE para SRCGRP existe)
LCR
IPDA
PSTN Salvador
LRTE=100
LTU 17
SDAT:DATA1 SRCGRP=2
PSTN Sao Paulo
LRTE=1
LTU 2 LTU 1
Grupo de Origem 1 config. padro para todas as estaes
LDP=0-110 Figura 3-1 Exemplo de configurao de um Grupo de Origem Dependente
2.2

Gerao (Exemplo)
Para IPDA Amo UCSU e diversos outros AMOs devem ser usados Configurar LTU 17 com Grupo de Origem 2: ADDUCSU:UNIT=AP,LTU=17,SRCGRP=2,FRMTYPE=INCH19,CONNTYPE=NBCSIPDL,LO CATION="TESTLAB";
ou configurar STN no LTU 17 com o Grupo de Origem 2: CHANGE-SDAT:STNO=7140, TYPE=DATA1,SRCGRP=2;
Definio do LCR rota 100 (rota para PSTN Salvador) para Grupo de Origem 2 com AMO LPROF: e LCR rota 1 para Grupo de Origem 1 ADD-LPROF:PROFNAME="EMERGENCY",SRCGRP=2,LRTE=100; CHANGE-LPROF:PROFIDX=1,SRCGRP=1,LRTE=1;(Profidx encontrado do DISPLAYLPROF:;)
LCR
Referncia a uma entrada na tabela de um Grupo de Origem (aqui: ndice 1) com AMO LDPLN: ADD-LDPLN:LDP="0"-"110",PROFIDX=1,LAUTH=1;
2.3
Gerao (exemplo no mesmo sistema)
SRCGRP LRTE 91 ISDN ISDN LRTE 322 7140 02 7143 99 xxxx CHANGE-SDAT:STNO=7140,TYPE=DATA1,SRCGRP=1; CHANGE-SDAT:STNO=7143,TYPE=DATA1,SRCGRP=2; ADD-LODR:ODR=33,CMD=NPI,NPI=UNKNOWN,TON=UNKNOWN; ADD-LODR:ODR=33,CMD=ECHO,FIELD=3; ADD-LODR:ODR=33,CMD=END; ADD-LDAT:LROUTE=322,LSVC=ALL,TGRP=30,ODR=33,LAUTH=1; ADD-LDAT:LROUTE=91,LSVC=ALL,TGRP=31,ODR=33,LAUTH=1 ADD-LPROF:PROFNAME="GROUP 1",SRCGRP=1,LRTE=91;

01
Para cada entrada de ADD-LPROF um ndice criado Com o comando DISPLAY-LPROF o Profidx pode ser visto Usando-se o comando CHA-LPROF outros grupos de origem podem ser adicionados ao mesmo Profidx
CHA-LPROF:PROFIDX=1",SRCGRP=2,LRTE=322; ADD-LDPLN:LDP="0"-"W"-"X",PROFIDX=1,LAUTH=2,PINDP=N;
LCR
2.4
AMO UCSU UCSU UCSU UCSU LPROF LPROF LPROF LDPLN LDPLN LDPLN LDPLN SDAT Tabela 3-1
AMOs Relevantes
Parmetro SRCGRP INCH19 NBCSIPDL NBCSIPNW PROFIDX SRCGRP LRTE LDP LAUTH LROUTE PROFIDX SRCGRP Idioma e e e e e e e e e e e e e Descrio ndice do grupo de origem Trama de 19 polegadas para ap shelves ap shelf conectado ip - direct link ap shelf conectado via IP net LCR Profil-Index ndice do grupo de origem Nome do LCR Profile (Perfil LCR) Rota LCR Padro de Dgito LCR Nvel de autorizao LCR Nmero da Rota LCR ndice do LCR Profile (Perfil LCR) ndice do Grupo de Origem
LPROF PROFNAME
AMOs Relevantes
LCR
Grupos de Atendimento
3. Grupos de Atendimento
s
Contedo
1 1.1 1.2 Programao da Mesa Telefonista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 AMOs para o console de telefonista (AC), servio noturno . . . . . . . . . . . . . . . . . . . 3 Descrio abreviada dos AMOs utilizados . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.1 CTIME: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.2 ACSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.3 NAVAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.4 VFGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.5 VFGKZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Descrio Geral . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Ns sem um Console de Atendimento . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Exemplo de uso de AMOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.5.1 Atribuir um Atentende (AC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.5.2 Atribuir um Grupo de Atendimento (ATNDGR) . . . . . . . . . . . . . . . . . . . . . 7 1.5.3 Atribui um Nome a um Grupo ATND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.5.4 Remover um ATND do grupo ATNDGR e apag-lo do sistema . . . . . . . . 8 1.5.5 Alterar o Nmero Pessoal da Operadora . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.5.6 Adicionar um ATND ao grupo ATNDGR . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.5.7 Servio de Atendimento Centralizado (Interno) . . . . . . . . . . . . . . . . . . . . . 9 1.5.8 Grupo de Servio de Atendimento Centralizado Externo. . . . . . . . . . . . . . 9 Atribuio de atendimento noturno automtico . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Interceptao para Operadora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 1.4 1.5
1.6 1.7
s
1
1.1
Programao da Mesa Telefonista

AMOs para o console de telefonista (AC), servio noturno
LRNGZ
listas de seleo abreviada central No. da lista
WABE
dados de anlise de dgitos No DPLN
CTIME
temporizadore s para AC
COSSU
classes de servio No COS
SBCSU SCSU
dados de ramal STNO
ZAND
dados de sistema
ACSU
dados AC para servio diurno / noturno - AC No LST ATNDNO ATNDNO
ramal especial (atendimento noturno universal) GENANSNO
SSC
NAVAR
cdigos do No DPLN opo de comutao noturna NOPTNO
VFGR
opo noturna para o horrio do dia AC ATNDGR
VFGKZ
cdigos e nomes para os grupos AC
SYNCA
mensagem gravada sncrona
ZRNGZ
destinos para seleo abreviada central
TSCSU
troncos especiais
s
1.2 Descrio abreviada dos AMOs utilizados
No Hipath 4000, possvel administrar consoles de atendimento dos tipos AC4 ou consoles baseados em Windows ACWin-4/5 (DQ) e ACWinMQ-2/3 (MQ). Os seguintes AMOs so usados para configurao,
1.2.1
CTIME:
Temporizadores para AC: ativao do terminal (AC2, AC3 ou AC4) atualizao do mostrador, atribuindo o tratamento e a consulta de chamadas
1.2.2
ACSU
Configurao do console de telefonista Especificao dos dados e colocao em operao (ACWin ou AC4) do console de telefonista)
1.2.3
NAVAR
Opes de noturno Especificao de destinos para no mximo 128 opes de comutao noturna
1.2.4
VFGR
Grupos de console de telefonista Combinao de consoles de telefonista em grupos, especificando os nmeros da opo de comutao noturna por grupo 1.2.4.1 Relao entre os AMOS NAVAR e VFGR
NAVAR
NOPTN
1 3000
3 3001
128 3009 NOPT 1 = 1 VFGR NOPT 8 = 3 AUNTS = Y ( destino do AUNTS )
s
1.2.5 VFGKZ
Definio de qual cdigo de acesso criado no AMO WABE (cdigos ATND e ATNDDID) deve acessar cada um dos grupo de console de telefonista.
1.3
Descrio Geral
Ao atendente dado um nmero individual conhecido como nmero pessoal com cdigo ATNDIND Ao contrrio de ramais e troncos, um Atendente no est preparado para operao aps criao. Eles devem ser atribudos a um grupo ATND (VFGR). A partir do momento em que as opes noturnas sejam tambm atribudas a todos terminais de atendimento (pelo menos uma opo nula (dummy), caso no haja ramais com opo de servio noturno), eles devem ser criados de antemo com AMO NAVAR. As seguintes opes noturnas podem ser atribudas com o AMO NAVAR: NONE STN GENANS CASEXT CASINT Opo nula ou dummy ramal de atendimento noturno Atendedor Universal noturno Grupo ATND para servio externo centralizado Grupo ATND para servio interno centralizado
A partir da liberao do Hipath 4000 V1.0, atendentes noturnas no sero mais suportadas para opes noturnas. O AMO VFGR usado para alocar todos os ATND relevantes, assim como opes noturnas para grupos ATND. Atravs do parmetro ACTYPE no AMO ACSU, pode-se escolher entre os seguintes atendimentos: AC4, AC-WIN (ACW2Q) e AC-WIN MQ (ACWMQ). Para um grupo AC-WIN MQ, o AMO-VFGR deve ser criado com o parmetro QUEMODE=MQ (fila mltipla) enquanto que um grupo com outros atendentes (AC4, ACWin) criado via QUEMODE=DQ (fila dupla). Atendente AC-WIN MQ no podem estar dentro do mesmo grupo de outros tipos de atendentes. As opes noturnas so atribudas a um nmero de ndice criado no AMO NAVAR e alocado como opo noturna no grupo de Atendimento (1 - 8) Uma vez que o grupo esteja definido, assinalado aos cdigos:

ATNDDID para discagem direta de entrada (DDR de entrada da rede pblica) Cdigo de atendimento ATND, (chamadas internas ao atendente)
GENANS, se for implementado atendimento de tronco desde um ramal qualquer
necessrio atribuir os cdigo ATND e ATNDDID para todos os grupos de atendimento via AMO VFGKZ. O grupo de atendimento no pode ser chamado sem atribuio desses cdigos de acesso (mesmo em caso de chamadas interceptadas ou chamadas pessoais para atendente). Se um grupo ATND for controlar as tarefas de um outro grupo como variante noturna, ele se torna um grupo de Servio de Atendimento Centralizado, que pode ser atribudo internamente (CASINT) ou em um outro n da rede (CASEXT). Um grupo ITR e/ou um grupo DPLN nonecessita ser especificado, a no ser que desej fazer uma restrio do acesso ao grupo de atendimento. isto necessrio se por exemplo, vrios clientes dividem um nico sistema e um grupo ATND configurado por cliente. Se todos clientes dividem um grupo de atendimento comum, at 1000 cdigos de acesso ATNDDID podem ser atribudos para chamadas CO entrantes e um nome de companhia pode ser atirbuda para cada cdigo. Isto feito atrav do AMO-ZAND, TYPE=ATND, COMP1000=YES e com a apropriada atribuio do AMO VFGKZ. Se no AMO-ZAND o valor COMP1000 posto para NO, ento at 10 cdigos de ATNDDID podem ser adicionados por cliente para chamadas entrantes CO (VBZGR AMO). As mesas de atendimento podem ser adicionadas ou apagadas de um grupo a qualquer momento. Porm, uma atendedora no pode pertencer a mais de um grupo ao mesmo tempo. Atendentes em opo noturna no so mais suportadas. Ramais com atendimento noturno podem ser atribudos a vrias opes de noturno. Para opo noturna GENANS, somente uma estao (ANATE) pode ser entrada, usando o AMO SSC. Podem ser configurados at 16 grupos de atendimento em um sistema. consoles de Atendimento no podem ser configurados em gupos de busca. No caso de sistemas sem console de atendimento, um grupo ATND deve ser configurado, Ie a ele deve ser assinalado um raml de atendimento noturno (pode ser dummy), porm, nenhum hardware necessrio
s
1.4 Ns sem um Console de Atendimento
Descrio da facilidade Assegurar que um grupo de atendimentotenha atribudo um ramal ou uma variante de noturno vazia, para ns ramal sem operadoras. Para essa configurao, nenhum HW necessrio. Exemplo
Atribuir um ramal para comutao de opo noturna AD-NAVAR:NOPTNO=128,TYPE=STN,STNO=53200; ou como variante vazia: AD-NAVAR:NOPTNO=128,TYPE=NONE; Atribuir um grupo ATND com o ramal acima AD-VFGR:ATNDGR=0,NOPT1=128,OPT=1;
1.5 1.5.1
Exemplo de uso de AMOs Atribuir um Atentende (AC)
Atribuir um nmero de telefone para a operadorea no AMO WABE
ADD-WABE=CD=<nmero individual de chamada>,DAR=ATNDIND;
Atribuir uma classe de servios com AMO COSSU
ADD-COSSU:AVCE=parameter...; (geralmente possui valores TA e TNOTCR)
Atribui console de atendimento com AMO ACSU
ADD-ACSU:ATNDNO=<nmero individual de chamada>,PEN =<ltg-ltu-slot-cct>,DPLN =<0 - 15>,COS =<classe de servio>,LCOSV =<classe de servio LCR>,LANG =<idioma da operadora: por ex. BRA para Brasil>,ACTYPE =<ACW2Q / AC4 / ACWMQ>;
1.5.2
Atribuir um Grupo de Atendimento (ATNDGR)
Atribuir um resultado de anlise de dgitos (DAR) no AMO WABE
ADD-WABE:CD=<nmero do grupo de atendimento interno>,DAR=ATND; ADD-WABE:CD=<Nmeor entrante externo para grupo de operadora>,DAR=ATNDDID;

Atribuir as Operadoras com AMO ACSU (idem item 1.5.1) Atribuir as opes notrnas no AMO NAVAR
ADD-NAVAR:NOPTNO=<nmero da opo noturna>,TYPE=<tipo de opo noturna>,.....;
Atribuir um grupo de atendimento com AMO VFGR Grupos de atendimento com modo Double Queue (DQ) podem consistir de consoles dos tipos AC4, AC-Win 4.x e ACWIN XP. e ACWIN IP ADD-VFGR:ATNDGR=<No.Grp.Atend.>,QUEMODE=DQ,ATNDNO=<No. mesa>,NOPT1=<Opo noturna em NAVAR>,OPT=<Nmero 1....8 para NOPT ativa>,ITDEST=<grupos ITR para interceptao>,CQMAX=<nmero de chamadas em fila>; Attendant groups with Multiple Queues mode (MQ) can consist of AC-Win MQ 2.x Attendant type only. ADD-VFGR:ATNDGR=<No.Grp.Atend.>,QUEMODE=MQ,ATNDNO=<No. mesa>,NOPT1=<Opo noturna em NAVAR>,OPT=<Nmero 1....8 para NOPT ativa>,ITDEST=<grupos ITR para interceptao>,CQMAX=<nmero de chamadas em fila>;
O AMO VFGR coloca todos os consoles automaticamente em operao. Atribuir cdigo de discagem ao grupo criado (grupo ATND e ATNDDID) to the new defined Attendant Group ADD-VFGKZ:TYPE=ATNDGR,CD=<cdigo>,ATNDGR=<nmero do grupo ATND>;
1.5.3
Atribui um Nome a um Grupo ATND
Em sistemas comparilhados por at 1000 cdigos de acesso, um nome para empresa pode ser atribudo via AMO VFGKZ. Esse nome aparece no display do console de atendimento.
Atribuir um nome ao nmero de console
ADD-VFGKZ:TYPE=NAME,CD=<cdigo>,NAME=<string>; Para interceptao, o grupo ITR da estao do usurio verificada e o nome atribudo a esse grupo ITR mostrado no terminal. O nome do cliente alocado com grupo IT no AMO VBZGR.
Atribuir o mesmo nome para interceptao pela operadora AD-VBZGR:GROUP=<nmero>,TYPE=CUSNAME,NAME=<string>;
Obs.: O nome dever ser precedido do nmero da opo NOPT, por exemplo, 1-PORTARIA
1.5.4
Remover um ATND do grupo ATNDGR e apag-lo do sistema
Remover o atendente do grupo
CHA-VFGR:ATNDGR=<nmero>,ATNDNO=<nmero>,FUNCT=DEL;
apagar o atendente
DEL-ACSU:ATNDNO=<nmero>,DELOPT=ALL;
apagar o nmero de telefone de atendimento do DPLN (caso necessrio)
DEL-WABE:TYPE=CD,CD=<cdigo>,DAR=ATNDIND;
1.5.5
Alterar o Nmero Pessoal da Operadora
Alterar o nmero no DPLN CHA-WABE:CD=cdigo,CDNEW=novo nmero,DAR=ATNDIND; Alterar nmero: CHA-ACSU:ATNDNO=nmero,NEWNO=novo nmero;
1.5.6
Adicionar um ATND ao grupo ATNDGR
Pr-requisito: o ATND deve ser configurado.
Adicionar ATND para ATNDGR
CHA-VFGR:ATNDGR=<nmero>,ATNDNO=<nmero>,FUNCT=ADD;
1.5.7
Servio de Atendimento Centralizado (Interno)
O grupo de servio de atendimento centralizado interno (CASINT) atribudo no n local. Esta funo habilita uma faixa de funes de atendimento de um grupo ATNDGR a serem transferidos para um outro grupo no mesmo sistema. A atribuio de um grupo enrada como opo noturna com AMO NAVAR.
Atribuir uma opo noturna para CASINT
ADD-NAVAR:NOPTNO=<nmero>,TYPE=CASINT,ATNDGR=<nmero>;
Mais de uma opo noturna pode ser atribuda a um CASINT como destino. Atribuir um grupo de atendimento para opo noturna CASINT
ADD-VFGR:ATNDGR=nmero,{NOPT1...NTVA8},OPT=nmero,CQMAXF=nmero;
1.5.8
Grupo de Servio de Atendimento Centralizado Externo
Um grupo de Servio de Atendimento Centralizado Externo (CASEXT) localizado em um n externo. Vrios CASEXT podem ser atribudos e ativados dentro de uma rede ou mesmo dentro do mesmo sistema.
Atribuir opo noturna para CASEXT
ADD-NAVAR:NOPTNO=nmero,TYPE=CASEXT,CD=nmero,DESTNO=nmero;
s
O parmetro CD deve ser um cdigo de acesso interno para o sistema de destino. Em planos de numerao aberta, este nmero consiste de um cdigo de linha seguido pelo nmero de acesso ATND do sistema externo. Em numerao fechada, deve ser entrado o cdigo de acesso ATND do grupo de atendimento do sistema de destino. Este odigo progrmado com DAR=NETWno AMO WABE, mais DESTNO igual ao nmero de destino da rota de sada.
Atribui uma opo nourna para um ATNDGR
ADD-VFGR:ATNDGR=nmero,{NOPT1...NTVA8},OPT=nmero;
1.6
Atribuio de atendimento noturno automtico
O atendimento noturnpo automtico na verdade a variante 8 (oito) programada no AMO VFGR. O funcionamento desta facilidade depende de programao nos AMOs VFGR, NAVAR e ZAND: ZAND -> CHA-ZAND:TYPE=ATND,AUTNS=YES; (ou AUTNS=NO) NAVAR -> ADD-NAVAR:NOPTNO=30,TYPE=STN,STNO=3000; VFGR -> CHA-VFGR:ATNDGR=1, NOPT8=30; VFGR -> CHA-VFGR:ATNDGR=1,TYPE=GENERAL,AUTNS=ON; CTIME - > CHA-CTIME:TYPESWU=ATND,ATNDCALL=40;
AUTNS ZAND -> ATND AUTNS VFGR como funciona
yes on comuta mesa p/ noturno: chamada vai p/ NOPT8
yes off no comuta mesa p/ noturno: chamada permanece na mesa
no on chamada vai p/ NOPT8 e mesa permanece em diurno
no off no comuta mesa p/ noturno: chamada permanece na mesa
s
1.7 Interceptao para Operadora
A interceptao para operadora controlada de acordo com grupos ITR: A alocao do grupo ITR para interceptao de um entrado com AMO VFGR (parmetro ITDEST). Auomaticamente todos os grupos ITR so atribudos ao primeiro grupo ATNDGR criado. Outros grupos ATNDGR podero ser configurados com grupos ITR especficos para interceptao. Desta forma, as entradas originais sero sobrescritas. Observaes
Se o nmero do ramal discado enviado a um ramal no mesmo sistema, ou ento a chamada externa tipo DDR, o grupo ITR do ramal discado ser usado para seleo do grupo de atendimento para o qual a chamada ser desviada. Se o nmero de ramal discado conduz a um ramal de um sistema remoto, com rede privada CorNet-NQ, o grupo ITR para interceptao depender do parmetro de classe de tonco (COT) para linha chamante: Se ITRN setado, o grupo do ramal chamado ser usado para seleo do grupo de atendimento ao qual a chamada dever ser desviada. Se ITRN no setado, o grupo ITR da linha (tronco) chamante ser usada para seleo do grupo de atendimento ao qual a chamada dever ser desviada.
Se o nmero discado encaminhado para ramais de sistemas remotos que no estejam em rede, sempre ser tomado o grupo ITR da linha chamante. Antes de apagar um grupo ATNDGR, e considerando que ele no seja nico no sistema, deve-se carregar um outro grupo do sistema com os valores dos grupos ITR de interceptao, usando CHANGE-VFGR.
AD-VFGR:ATNDGR=nmero,{NOPT1...NOPT8},OPT=nmero,ITDEST=5; Exemplo /* Permitir facilidade interceptao*/ CHANGE-FEASU:TYPE=A,CM=ICPTDID; /* Alterar o tronco para interceptao em caso de nmero livre (IVAC), todos os troncos ocupados (ITB), sem autorizao (INAU), erro na intercalao (IONS), em caso de ramal com -no-perturbe (IDND) e destino ocupado (IBSY)*/ CHA-COT:COTNO=xxx,PAR=IVAC&ITB&INAU&IONS&IDND&IBSY,INFO="TRK WITH INTERCEPT"; /* Instalar ATNDGR com opo para interceptao ITR (5) */ CHANGE-VFGR:ATNDGR=0,TYPE=GENERAL,ITDEST=5;
Siemens
6.4

Console de operadora central (CAC) em uma rede do sistema

O ATND normal tambm pode ser utilizado como ATND central (CAC). Um ATND sempre atribudo exclusivamente a um grupo de ATND (ATNDGR). Cada ATNDGR pode ser alcanado exclusivamente em trfego de terminal de entrada. A seleo ocorre atravs do terminal ou cdigo de atendimento ou indiretamente atravs da restrio de trfego interna ou alocao do grupo de anlise de dgitos. Se um ATNDGR tambm controlar temporariamente ou permanentemente, por meio de transferncia, o trfego de terminal de outros ATNDGRs (de outros sistemas de uma rede ou do prprio sistema) em complemento ao prprio trfego de terminal (local), ele por definio, opera como ATNDGR central (CACGR) para este ATNDGR. Cada ATND de um CACGR um ATND central (CAC). Ele no difere de um ATND normal no que se refere ao equipamento e facilidades. Vrios CACGRs podem ser instalados e ativados simultaneamente em uma rede de sistemas e em um sistema. Um CACGR tambm pode ser operado no modo de comutao noturna sem que um ATND seja instalado (terminal noturno central). Os sistemas na rede que no possuem um ATND nem uma facilidade de comutao noturna so atendidos por um ATNDGR de outro sistema, no que se referir a trfego de terminal (= CACGR para o sistema atendido). Os ATNDGRs com ATND podem comutar temporariamente o trfego de terminal para uma variante de comutao noturna prpria ou alternativamente para um CACGR de um outro sistema na rede ou no prprio sistema. A seleo deve ser realizada por meio de um procedimento no ATND. A comutao tambm pode ser realizada automaticamente, se o ltimo ATND de um ATNDGR no atender uma chamada (analogamente para comutao noturna automtica). Filas de espera comuns em um CACGR para as chamadas locais e para as chamadas de todos os ATNDGRs atendidos por ele (tempos de espera parelhos). Um CACGR pode comutar, por sua vez, para uma variante de comutao noturna interna do sistema. O ATND ou os ramais noturnos de um CACGR devem ser capazes de alcanar todos os assinantes e ATNDs da rede do sistema e estender as chamadas at eles.
Siemens
Informativo Tccnico
s
HiPath 4000
Quick-Check Instructions Attendant Console AC4
Keypad
Keypad
MCID JOIN TAPE TRACE SERIAL PARK RLS ALARM ACCT NIGHT RSV COS SMDR R1 R2
Output call data Connect a call to another on-hold connection Activate/deactivate Trunk no. identification (test) Serial call Park call Release connection Alarm inquiry Charge inquiry Night service Trunk reservation Class-of-service changeover Mark connection for charge registration at attendant console Seize external route 1 Seize external route 2
DIAL PER LINE 1 LINE 2 PAGE
Call setup Answer or set up a personal call Answer call on line 1 Answer call on line 2 Page a person - no function -
PROG ENTER OVER REDIAL
Open Program menu Memory input Override Number redial/notebook (memory/repeat) - no function -
EXTEND CLEAR DEST
Call transfer Clear Call extension with announcement
Examples of operation
Dialing
Dial destination Wait for answer Speak or Disconnect
Extend call (seebelow)
Answering
Disconnect or Speak or or
Extend call (see below)
Extending a call
Speak or Speak or Dial destination Wait for answer or Dialed party/ caller is Normal extending Dial destination Dialed party/caller Speed servicing is automatically extended only for answering with
and
Toggle (see next page)
Toggling (alternating)
or Switch back to dialed party/ caller Speak or Switch back to destination Speak Dialed party/ caller is extended or Dialed party/caller is extended
Wait for answer or (destination)
or
Charge registration at the attendant console

If a station user requests you to record the charges of a trunk call, mark the extended call with (ACCT) when the called subscriber answers.
Press once Lamp flashes Charge display appears Read/note Press again Lamp flashes
Setting up a blocked connection for 2 parties

Dial 1st party Wait for answer Dial 2nd party Wait for answer Both parties are connected
Descrio das facilidades bsicas disponveis para a plataforma Hipath 4000
Mesa AC-4
Atendimento de chamadas _ Chamadas externas: Para o atendimento de uma chamada externa pressione a tecla _ Chamadas internas: Para o atendimento de uma chamada interna pressione a tecla - Chamada pessoal: Para o atendimento de uma chamada pessoal pressione a tecla . . .
Transferncia rpida _ Aps o atendimento da chamada, digite o nmero do ramal desejado, se o ramal estiver livre a ligao transferida automaticamente. Transferncia anunciada _ Esta transferncia usada quando se deseja anunciar a chamada. , digite o nmero do ramal e pressione a tecla Aps atender a chamada, pressione a tecla de reteno
. Caso ocorra um erro na digitao do ramal ou se o ramal estiver ocupado e voc desejar tentar outro
ramal, pressione a tecla Estacionar _ Para estacionar uma ligao pressione a tecla _ Para recuperar uma chamada estacionada, voc dever pressionar a tecla em uma das posies disponveis de 0 a 9. e selecionar a chamada e digite um novo nmero de ramal.
Realizando uma ligao _ Para realizar uma ligao externa, digite Cdigo de acesso linha + Nmero externo. Sempre que voc estiver realizando uma ligao a tecla de feixe Noturno . _ Para ativar o noturno basta pressionar a tecla _ Para desativar o servio noturno pressione a tecla estar acessa.
Siemens
Informativo Tccnico
Operation
HiPath 4000
AC-Win 2Q IP V1.0
www.siemens.de/enterprise
ndice
Bem-vindo ao AC-Win 2Q IP . . . . . . . . . . . . . . . . . . . . 7
A sua nova consola de operadora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requisitos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acerca deste Manual de instrues . . . . . . . . . . . . . . . . . . . . . . . . . . . . Funes de operadora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Funes de administrao. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 8 8 9 9
Inicializar e sair do programa . . . . . . . . . . . . . . . . . . 10

Logon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Alterar a senha. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Desligar o PC da consola de operadora . . . . . . . . . . . . . . . . . . . . . . . . . 11
rea de trabalho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
O controlo de chamadas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Botes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 As teclas de nome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Navegao nas janelas da rea de trabalho . . . . . 19

Utilizao com o teclado ou o rato. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Utilizao com os botes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Suporte acstico e ptico ao utilizador . . . . . . . . . 20

Sinais de marcar para guia do utilizador. . . . . . . . . . . . . . . . . . . . . . . . . 20 Sinais para a sinalizao de chamada . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Aparncia dos botes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Transferncia de chamadas . . . . . . . . . . . . . . . . . . . 21
Transferir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Desligar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Desactivar intruso . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Apagar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intercalao . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intruso . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chamada em cadeia (Serial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consulta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Continuar uma chamada retida . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Comunicao alternada (alternar entre dois interlocutores) . . . . . . . . . Comunicao alternada entre as linhas . . . . . . . . . . . . . . . . . . . . . . . . Parque . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Retomar uma chamada parqueada . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 24 24 24 25 25 26 27 27 28 29 29 29 3
ndice Acoplar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Marcar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Marcar com a Repetio de marcao (ltimo nmero guardado) . . . . Marcar com a Repetio de marcao (nmero guardado) . . . . . . . . . . Marcar com as teclas de nome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Marcar com o bloco de notas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Marcar com o Histrico de Chamadas . . . . . . . . . . . . . . . . . . . . . . . . . Marcar com a rea de transferncia . . . . . . . . . . . . . . . . . . . . . . . . . . . Marcar com "Arrastar e soltar" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduo de nmeros de telefone com o rato . . . . . . . . . . . . . . . . . . Marcao posterior MF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 31 32 32 33 33 34 34 35
Funes do sistema . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Procura de pessoas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procura de pessoas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gravador . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activar gravador. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Desactivar gravador . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activao automtica do gravador. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identificao de chamadas (MCID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consultar a informao de linha . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 36 37 37 37 37 38 38
Teclas de nome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Abrir o objecto Teclas de Nome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Programao das Teclas de Nome . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Salvar a janela Teclas de Nome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Repetio de marcao . . . . . . . . . . . . . . . . . . . . . . .42

Configuraes bsicas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abrir um novo objecto Repetio de marcao . . . . . . . . . . . . . . . . . . Salvar nmeros para repetio de marcao. . . . . . . . . . . . . . . . . . . . . Salvar o objecto Repetio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 43 44 44
Bloco de notas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Abrir um novo bloco de notas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incluir uma chamada no bloco de notas . . . . . . . . . . . . . . . . . . . . . . . . Adicionar outros dados no bloco notas . . . . . . . . . . . . . . . . . . . . . . . . . Excluir registos do bloco de notas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Salvar bloco de notas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 46 46 46 47
ndice
Histrico de Chamadas . . . . . . . . . . . . . . . . . . . . . . . 48
Solicitar o Histrico de Chamadas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abrir o Histrico de chamadas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Indicao dos dados actuais da ligao . . . . . . . . . . . . . . . . . . . . . . . . . Mostrar os dados da ligao guardados . . . . . . . . . . . . . . . . . . . . . . . . Imprimir dados da ligao . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Salvar o Histrico de Chamadas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 49 49 49 50 50
Taxao no Posto de operadora. . . . . . . . . . . . . . . . 51

Configuraes bsicas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activar o registo de taxao . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Desactivar o registo de taxao. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consultar taxao . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verificar taxao de chamadas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Imprimir a taxao . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reiniciar o contador de taxao. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Salvar o objecto Taxao . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 52 52 52 53 53 53 53
Servio nocturno . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Activar servio nocturno . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Servio nocturno automtico. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Desactivar servio nocturno . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verificar e alterar servio nocturno . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 55 55 56
Restrio de trfego interno para grupos de utilizadores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Consultar a restrio de trfego interno para grupos de utilizadores . . 57 Activar e desactivar a restrio de trfego interno para grupos de utilizadores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Alterao de classe de servio para grupos de utilizadores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Consultar as classes de servio para grupos de utilizadores. . . . . . . . . 59 Activar e desactivar classes de servio para grupos de utilizadores . . . 60
No incomodar para grupos de utilizadores . . . . . 61

No incomodar para os grupos de utilizadores . . . . . . . . . . . . . . . . . . . 61 Activar e desactivar No incomodar para grupos de utilizadores . . . 62
ndice
Alarme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Consultar as mensagens de erros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Imprimir alarmes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Apagar alarme(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Regulao do sinal de chamar . . . . . . . . . . . . . . . . .64 Diagnstico de erros . . . . . . . . . . . . . . . . . . . . . . . . . .66

CAPI Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Diagnstico AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Determinar nmero da verso . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Salvar a rea de trabalho . . . . . . . . . . . . . . . . . . . . . .69 ndice remissivo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Bem-vindo ao AC-Win 2Q IP
O AC-Win uma consola de operadora moderna, desenvolvido para funcionar com base em Windows XP e oferecer o maior conforto nas funes de telefonia. Se optou tambm pelo pacote adicional DS-Win, dispe adicionalmente de uma agenda telefnica electrnica. O seu trabalho facilitado pela integrao das funes de telefonia com uma agenda telefnica electrnica. Vantagens do AC-Win: Utilizao confortvel, com: Interface de rpida aprendizagem Aces rpidas com o teclado e o rato
Personalizao da interface do utilizador Diversas funes de operadora Capacidade de integrao com a agenda telefnica electrnica em moderno ambiente Microsoft Windows.
A sua nova consola de operadora

Com a sua nova consola de operadora, agora poder atender chamadas e procurar nmeros de telefone na agenda telefnica electrnica. Vantagens da consola de operadora Procedimentos fceis com o guia de utilizador Funes de conforto para o atendimento e a transferncia de chamadas Funes de administrao de fcil utilizao Teclas de nome de programao livre Intercalao de chamadas fcil Indicao de todas as chamadas parqueadas. Marcao automtica de um nmero da agenda telefnica DS-Win Procura fcil e rpida localizao de um utilizador Indicao de informaes adicionais detalhadas de um utilizador Diversos critrios de busca como, por exemplo, nome, nmero de telefone, sector ou palavras-chave.
O pacote adicional DS-Win oferece alm disso:
Requisitos
A instalao do computador da consola de operadora com o Microsoft Windows efectuada por um tcnico da Siemens. A aplicao AC-Win deve ser instalada antes de iniciar o trabalho com o PC da consola de operadora. Siga os procedimentos descritos no Manual de Administrao. So necessrios conhecimentos bsicos de PCs e Windows para utilizar o programa.
Acerca deste Manual de instrues

Objectivo
Com deste manual, pode utilizar todas as funes para o controlo de chamadas com a interface grfica do Windows XP.
Grupo alvo
Estas instrues destinam-se aos utilizadores que j esto familiarizados com a interface grfica do Windows XP com uma consola de operadora ligada.
Nota importante
Para facilitar a leitura, sero utilizados neste manual os seguintes meios de apresentao: caracteriza observaes importantes caracteres em negrito caracteres em itlico
.
caracteriza comandos ou opes de menu caracteriza indicaes de caminhos e nomes de programa
O Manual de instrues contm ilustraes das janelas e teclas no layout padro. As janelas e teclas podero ser diferentes, a depender de cada configurao.
Funes de operadora
Indicao de trfego e chamadas actuais Atendimento de chamadas Estabelecimento / Corte / Intercalao de chamadas Chamadas em cadeia (Serial) Comunicao alternada Parque de chamadas Reteno de chamadas Marcao / Correco de erros de marcao / Repetio de marcao / Programao das teclas de nome Bloco de notas Registo de taxao de chamadas Activao do servio nocturno Consulta das causas de alarme Histrico de chamadas Iniciar a procura de pessoas
Funes de administrao
Activao/desactivao da restrio de trfego interno para grupo de utilizadores Activao/desactivao da comutao de classe de acesso para grupos de utilizadores Activao/desactivao da funo "No incomodar" para grupos de utilizadores (No incomodar para grupos) Gravao de chamadas Identificao do nmero da linha
Inicializar e sair do programa
Passo a Passo

Para inicializar o AC-Win: Clicar duas vezes no smbolo do programa AC-Win, ou seleccionar AC-Win com Iniciar -> Programas -> AC-Win. O dilogo de incio da sesso aparece automaticamente aps ter ligado o PC, se a sua consola de operadora estiver configurada correctamente.
Logon
Ao abrir o programa AC-Win, aparece um dilogo de incio de sesso, no qual deve ser introduzida uma senha. O primeiro acesso s possvel com a identificao de utilizador "admin .
Seleccionar a sua ID do utilizador. Introduzir a sua senha. "Admin" a identificao de utilizador para o primeiro acesso. O programa AC-Win inicializado e apresentada a rea de trabalho standard. Por motivos de segurana, a introduo da senha protegida, ou seja, so mostrados apenas asteriscos (*).
10
Passo a Passo
Alterar a senha
1. Seleccionar no menu Opes, o registo Parmetros da Aplicao. 2. Clicar no boto Senha.
3. Introduzir a senha actual no campo Senha antiga . 4. Introduzir a nova senha no campo Nova Senha". 5. Introduzir novamente a senha no campo Repita a senha . Por motivos de segurana, a introduo da senha protegida, ou seja, so mostrados apenas asteriscos (*).
Desligar o PC da consola de operadora

Seleccionar a opo Sair no menu Arquivo, ou Alt
+
F4
premir Alt + F4. O programa AC-Win fechado. Encerrar o Windows antes de desligar o PC da consola de operadora. Se desligar o PC antes de encerrar o Windows, pode provocar perda de dados!
11
rea de trabalho
rea de trabalho
A figura seguinte mostra a rea de trabalho standard que apresentada aps a inicializao do AC-Win. possvel seleccionar entre vrias reas de trabalho predefinidas.
Controlo de chamadas
Teclas de nome Botes Barra de estado Data/Hora Indicao do estado
12
rea de trabalho
O controlo de chamadas
A figura seguinte mostra as funes das teclas e explica as indicaes na janela Controle de chamadas
Quantidade das chamadas ainda no atribudas para Linha 1 ou Linha 2
"Chamadas parqueadas"
Atender uma chamada na Linha 1 Ocupar linha Chamada pessoal Atender uma chamada na Linha 2 Atender chamadas pessoais Atendimento automtico de chamadas; Consulta Se esta funo estiver activada, as cha- Transferir chamadas madas de entrada sero atendidas automaticamente. Cortar a ligao Data/Hora; O formato corresponde quele na sua configurao do Windows. Apagar introduo Parquear chamada Retomar chamadas parqueadas
13
rea de trabalho
Primeiro participante
Esses campos contm o nmeros do telefone, o nome
do utilizador actual ligado, ou seleccionado, se estas informaes forem reconhecidas pelo sistema.
Segundo participante
Esses campos contm informaes acerca do segundo utilizador consultado numa ligao.
Desvio
Esses campos contm o nmero do telefone e o nome (se existente), que correspondem s chamadas desviadas para o respectivo utilizador.
Estado
Esses campos contm o estado actual da chamada: Ocupado Em reteno Transferido Livre
14
rea de trabalho
Botes
A janela Todos Botes contm as teclas para a utilizao das funes de atendimento e do sistema AC-Win. A figura abaixo mostra 29 teclas do layout standard. Todavia, a sua configurao actual pode ser diferente.
Funes das teclas

As funes de cada tecla esto listadas na configurao standard. Elas esto agrupadas por temas e descritas brevemente.
Atender chamadas na Linha 1
Atender chamadas na Linha 2
Atender chamada pessoal
Iniciar a consulta para uma extenso
Transferir a chamada
Cortar a ligao
15
rea de trabalho
Parquear a chamada
Retomar chamadas do parque
Apagar introduo
Ocupar linha
Chamada em cadeia
Iniciar chamada pessoal
Chamada com taxao
Verificar taxao de chamadas
Identificao de linha
Marcar o nmero para a repetio de marcao
Guardar o nmero para a repetio de marcao
Procura de pessoas (com o sistema de procura de pessoas opcional = "Pager")
Bloco de notas
Mudar classe de acesso
Consulta de alarme 16
rea de trabalho
Gravador
Intercalao
Servio nocturno
Identificao de chamadas maliciosas (MCID)
Activao / desactivao do AC-Win (corresponde a desligar o microtelefone de cabea).
Teclas de nome
Introduo alfanumrica
Marcar nmero, introduzir dgitos
Tecla de funo
Comutao para marcao MF (multifrequncia)
Acoplar
Intercalao de emergncia
Desligamento de emergncia
17
rea de trabalho
Passo a Passo
As teclas de nome
Pode guardar nmeros de destino chamados com frequncia nas teclas de nome e marcar a extenso com apenas um clique na respectiva tecla de nome.
As teclas de nomes podem ser configuradas segundo suas necessidades. Os procedimentos necessrios para a configurao encontra na Pgina 39.
18
Navegao nas janelas da rea de trabalho
Passo a Passo
Navegao nas janelas da rea de trabalho

Utilizao com o teclado ou o rato
Pode utilizar o teclado ou o rato para navegar nas janelas da rea de trabalho e activar botes. recomendada a utilizao do teclado para o processamento de chamadas por ser mais rpido e fcil do que o rato. Os botes seleccionados so apresentados premidos (em baixo relevo). De acordo com a chamada de entrada, no dilogo Controle de chamadas activado o respectivo boto e a funo pode ser iniciada imediatamente com <Enter> ou <Espao>.
Utilizao com os botes

Tambm pode utilizar os botes de controlo atravs de teclas de funo. Estas teclas podem ser livremente atribudas aos botes. Como fazer a atribuio das teclas aos botes est descrito no Manual de Administrao. A atribuio actual dos botes encontra-se na janela Todos Botes . Apenas podem ser utilizadas as teclas de funo quando a janela Todos Botes estiver aberta.
Os botes seleccionados so activados com Enter
Pode seleccionar botes e campos activos sequencialmente com a tecla Tab.
Ctrl
Pode utilizar Ctrl + Tab ou
Ctrl
F6
Ctrl + F6 para alternar entre as aplicaes activas.
As teclas de cursor permitem o rolamento das listas.
19
Suporte acstico e ptico ao utilizador
Suporte acstico e ptico ao utilizador

Sinais de marcar para guia do utilizador
Sinal Sinal de marcar (opcional) Sinal de chamar Sinal de ocupado Sinal de intercalao Chamada em espera (confirmao) Sinal NU (mensagem) Msica ou mensagem Favor aguardar. Sinal triplo sequencial (- - -) com pausas de 1s. A sequncia de sinais depende das configuraes no sistema. Som Significado Favor marcar (interno / externo). N ou servio livre. N ou servio ocupado. Est a intercalar-se noutra chamada. Aguarde! Outro utilizador est em consulta. Telefone desligado ou nmero inexistente.
Sinais para a sinalizao de chamada

Sinal Chamada normal Chamada especial Som ficheiro Wav ficheiro Wav Significado Chamada normal a ser atendida Chamada urgente
O significado dos sinais de chamada depende da configurao do seu sistema e do pas definido. possvel efectuar configuraes individuais.
Aparncia dos botes

Aparncia Normal Cinzento Em cor (vermelho) Estado disponvel indisponvel activado Significado Funo a ser activada. Funo no pode ser activada no momento. Funo est activada e deve ser utilizada.
20
Transferncia de chamadas
Passo a Passo
Para transferir uma chamada, deve primeiro atend-la. Se existir apenas uma chamada em espera, esta poder ser atendida directamente com <Enter> ou tambm poder atender as chamadas com o respectivo boto:
Atender chamada na Linha 1
No caso de vrias chamadas em espera, poder atend-las com o respectivo boto, segundo o tipo de chamada. Pode tambm atender chamadas ao premir <Enter> ou <Espao>. O tipo de chamada que ser atendida primeiro depende da configurao de sua consola de operadora. A configurao standard atender primeiro "Chamada na Linha 1". Se for indicada a mensagem Nenhuma ligao possvel na linha de estado aps ter atendido e transferido uma chamada, intil tentar transferir novamente. Pode cancelar esta chamada e marcar outra extenso.
21
Passo a Passo
Transferir
Uma chamada atendida pode ser transferida para uma extenso ou para uma operadora com a tecla Ligar (transferncia normal) ou com o servio rpido.
Transferncia normal
Deve utilizar a transferncia normal se desejar notificar a chamada ao utilizador de destino antes da transferncia, ou se desejar conversar com o chamador e o chamado alternadamente antes de transferir a chamada. Atender a chamada com <Enter> ou o boto correspondente:
Premir <Enter> para reter a chamada
ou ou o boto Consulta para reter a chamada.
Marcar a extenso de destino com o teclado, ou se possuir agenda telefnica electrnica, introduzir o nome do utilizador desejado.
22
Passo a Passo
Premir <Enter> ou Transferir, se ouvir um sinal de chamar, sinal de ocupado ou se a extenso chamada atender.
A chamada transferida directamente ao destino correspondente. Se o utilizador de destino no atender, a chamada volta novamente consola de operadora aps aproximadamente 30 segundos (Rechamada).
Servio rpido
Utilizar o servio rpido se no desejar falar com o utilizador antes de transferir a chamada. Atender a chamada com <Enter> ou o boto correspondente:
Marcar a extenso de destino com o teclado, ou se possuir agenda telefnica electrnica, introduzir o nome do utilizador desejado.
Quando o utilizador for encontrado, premir <Enter> para estabelecer a chamada. Permanecer em ligao com o chamador at que a chamada seja transferida. Se o utilizador de destino no atender, a chamada volta novamente consola de operadora aps aproximadamente 30 segundos (Rechamada).
23
Passo a Passo
Desligar
Pode utilizar o boto Desligar para interromper a chamada e terminla.
Desactivar intruso
O boto Desactivar intruso possibilita cortar uma chamada na rede, caso durante o estabelecimento da ligao para o destino todas as junes para o nmero de destino estiverem ocupadas ou o prprio nmero de destino estiver ocupado
As junes solicitadas so desligadas e disponibilizadas sem aviso prvio. Esta facilidade s possvel com a respectiva configurao. Se deseja utilizar esta facilidade, deve primeiro configurar o cdigo para a activao do desligamento de emergncia de acordo com a programao do sistema (p. ex., *24). Introduzir o respectivo cdigo no menu Opes/Parmetros AC-Win/separador Controle de chamadas/campo Cdigos de facilidades.
Apagar
Se premir o boto Apagar, desliga a chamada. Em seguida pode seleccionar outro destino. Se a extenso de destino no estiver acessvel, pode premir o boto Apagar para cortar a ligao e marcar outro nmero.
24
Passo a Passo
Intercalao
Se a extenso desejada estiver ocupada, pode intercalar-se nesta linha e conversar com o utilizador (s em chamadas internas, utilizar apenas em caso de emergncia).
Para intercalar-se numa chamada existente, seleccionar o nmero do utilizador interno. A linha indicada como ocupada . Premir o boto Intercalao para falar com os dois interlocutores. O utilizador desejado ouve um sinal que avisa sobre a intercalao na chamada. 1 Caso: o utilizador de destino termina a chamada actual Premir Transferir. A chamada transferida ao utilizador de destino. 2 Caso: o chamador deseja terminar a tentativa de chamada Premir <Enter> ou o boto Intercalao para terminar a funo.
Intruso
O boto Intruso possibilita intercalar para uma juno ocupada, ou para uma extenso numa rede (p. ex., em casos de emergncia), caso todas as junes estiverem ocupadas ou quando o prprio nmero de destino estiver ocupado.
Esta facilidade s possvel com a respectiva configurao. Se deseja utilizar esta facilidade, deve primeiro configurar o cdigo para activao da intercalao de emergncia de acordo com a programao do sistema (p. ex., *24). Introduzir o respectivo cdigo no menu Opes/Parmetros AC-Win/separador Controle de chamadas/campo Cdigos de facilidades.
25
Passo a Passo
Chamada em cadeia (Serial)

Se um chamador externo deseja falar com vrias extenses sequencialmente, a ligao dever ser tratada como uma chamada em cadeia: Atender a chamada com <Enter> ou o boto Linha 1 ou Linha 2.
Premir o boto Cham. em cadeia para iniciar a funo. Pode agora transferir a chamada com o procedimento normal ou rpido. Assim que o utilizador interno desligar o telefone, a chamada transferida retomada para ser novamente atendida e o modo de chamada em cadeia automaticamente apagado. Antes de cada nova transferncia, deve ser activada previamente a funo de chamada em cadeia. A depender da configurao da sua consola de operadora, o smbolo no boto Chamada em cadeia aparece em cor quando esta funo estiver activada. A cor predefinida o vermelho. Pode terminar a chamada em cadeia ao premir novamente o boto correspondente (Serial). Esta facilidade s funciona para chamadas externas. Se sero sinalizadas as chamadas na Linha 1 ou na Linha 2, depende da configurao do sistema.
26
Passo a Passo
Consulta
Clicar no boto Consulta para estabelecer uma chamada de consulta a uma extenso. Assim, a chamada actual ser retida. (=reteno indirecta). O chamador no pode ouvir a sua chamada de consulta a um utilizador interno.
Continuar uma chamada retida

Clicar novamente no boto Consulta para voltar ao chamador em reteno (alternar).
Clicar no boto Transferir.
27
Passo a Passo
Comunicao alternada (alternar entre dois interlocutores)

A funo Comunicao alternada permite falar alternadamente com dois interlocutores. O interlocutor que fica em espera no pode ouvir a sua conversa. Atender a chamada com <Enter> ou o boto correspondente:
Atender a chamada na Linha 1
Atender a chamada na Linha 2
Premir <Enter> ou o boto Consulta.
Marcar a extenso desejada com o teclado.
Alternar entre o chamador e o chamado ao premir <Enter> ou o boto Consulta.
apresentada a mensagem Em ligao na linha de estado para o chamador com o qual est a falar. O interlocutor em espera indicado com Reteno .
Premir o boto Transferir para interligar os dois interlocutores.
28
Passo a Passo
Comunicao alternada entre as linhas

Pode alternar entre Linha1, Linha2 e Chamada pessoal, ao premir os botes correspondentes. A chamada activa retida e indicada novamente na janela de chamadas.
Parque
Pode parquear uma chamada atendida, que no foi transferida, numa das 10 posies de parque disponveis. Premir o boto Parquear para parquear uma chamada atendida ou estabelecida. As chamadas parqueadas aparecem no campo de janelas de parque no dilogo Controlo de chamadas .
Retomar uma chamada parqueada

Premir o boto Religar para retomar uma chamada parqueada. A chamada seleccionada retomada. S poder retomar uma chamada parqueada, se o Primeiro participante e oSegundo participante no estiverem ocupados.
Acoplar
Clicar no boto Join, seleccionar um chamador parqueado e lig-lo com o chamador actual.
29
Marcar
Passo a Passo
Marcar
Para efectuar uma chamada para uma extenso, deve marcar o nmero correspondente. Pode introduzir o nmero do telefone de diversos modos. A seguir sero mostradas as diferentes possibilidades de introduo do nmero. Em estado inactivo, isto , quando no estiver numa chamada, pode introduzir o nmero: ao clicar no boto Ocupar Linha ou Linha Privada.
Se introduzir um nmero sem antes seleccionar uma linha, ser automaticamente ocupada uma linha assim que for marcado o primeiro dgito.
Ao transferir, pode, com ou sem clique no boto Consulta,
simplesmente introduzir o nmero da extenso desejada
Apaga as introdues incorrectas com a tecla <Del> ou o boto Apagar.
30
Marcar
Passo a Passo
Marcar com a Repetio de marcao (ltimo nmero guardado)

Ao clicar no boto Repetio, marca o ltimo nmero guardado. Se deseja repetir um nmero diferente do ltimo nmero marcado, deve primeiro abrir a janela Repetio .
Marcar com a Repetio de marcao (nmero guardado)

1. Clicar na janela Repetiopara activ-la.
2. Seleccionar o nmero desejado com as teclas de cursor e premir <Enter> ou o boto Repetio. O nmero marcado.
Consultar o pargrafo Repetio para mais informaes sobre como abrir a respectiva janela e como guardar nmeros para repetio Pgina 42.
31
Marcar
Passo a Passo
Marcar com as teclas de nome

Clicar no boto do nmero que deseja marcar na janela Teclas de Nome . O nmero programado marcado. Para informaes sobre a programao das teclas, consultar o pargrafo Teclas de nome Pgina 39
Marcar com o bloco de notas

1. Clicar na janela Bloco de notas para activ-la.
2. Seleccionar uma opo na janela Bloco de notas. 3. Premir o boto Marcar 1, para marcar o primeiro nmero.
Se existir um segundo nmero no registo, premir o boto Marcar 2 para marc-lo. A chamada estabelecida. Consultar o pargrafo Bloco de notas para as respectivas informaes. Pgina 45
32
Marcar
Passo a Passo
Marcar com o Histrico de Chamadas

1. No menu Arquivo ->Novo Objecto, seleccionar Histrico de Chamadas.
2. Seleccionar da lista a ligao necessria. 3. Clicar em Marcar. O nmero para a ligao registada marcado. Para mais informaes sobre a funo, consultar o pargrafo "Histrico de Chamadas" Pgina 48.
Marcar com a rea de transferncia

Pode copiar nmeros externos (sequncia de dgitos) de uma outra aplicao (p. ex., lista telefnica pessoal) para o AC-Win, atravs da rea de transferncia do Windows. O prefixo da rede adicionado automaticamente antes do nmero. Se o nmero copiado contiver outros caracteres alm de dgitos, estes sero automaticamente apagados pelo programa. Ctrl
+
Copiar o nmero da aplicao externa para a rea de transferncia. Para tal, premir, ao mesmo tempo, as teclas <Ctrl> e <C>. Maximizar ou activar o dilogo Controle de chamadas do AC-Win e clicar no campo Primeiro participante ou Segundo participante.
Ctrl
Para inserir o nmero, premir, ao mesmo tempo, as teclas <Ctrl> e <V>.
33
Marcar
Passo a Passo
Marcar com "Arrastar e soltar"

Com ajuda do rato, pode arrastar nmeros externos de outras aplicaes como, por exemplo, de uma lista telefnica pessoal, para o ACWin. Clicar no nmero de telefone na aplicao e arrast-lo para o dilogo desejado (p. ex., para o campo Primeiro ou Segundo participante). Esta aco s tem efeito, se existir uma ligao com o sistema. Caso contrrio, o nmero no poder ser "arrastado" com o rato.
Introduo de nmeros de telefone com o rato

Pode marcar nmeros no teclado, com o rato ou um display touch screen. 1. Seleccionar o menu Arquivo -> Novo Objecto->Teclado de Marcao.
2. Clicar os nmeros desejados com o rato. 3. A introduo directa de nmeros com o rato, ou o teclado representada aqui pelo smbolo do teclado.
34
Marcar
Passo a Passo
Marcao posterior MF
Deseja ouvir mensagens, por exemplo, do seu correio de voz, ou consultar informaes sobre um servio que possui estrutura hierrquica. Para isso, deve comutar para marcao MF , para poder navegar pelo sistema. Requisito: A gerao automtica de MF no est activada. Estabelecer primeiro uma chamada para o seu correio de voz. 1. Premir MF para comutar. activado o modo de multifrequncia.
2. Introduzir a sua senha pessoal para a teleconsulta (ps-marcao).
3. Terminar a chamada com o boto Desligar.
Se deseja utilizar esta facilidade, deve primeiro configurar o cdigo para activao de marcao MF de acordo com a programao do sistema (por exemplo, *24). Introduzir o respectivo cdigo no menu Opes->Parmetros AC-Win->separador Controle de chamadas->campo Cdigos de facilidades .
35
Funes do sistema
Passo a Passo
Funes do sistema
AC-Win fornece funes do sistema adicionais.
Procura de pessoas
Requisito: deve possuir uma senha para o servio de procura de pessoas. Introduzir o respectivo cdigo no menu Opes->Parmetros AC-Win->separador Controle de chamadas->campo Cdigos de facilidades. Se um utilizador interno chamado no atender ou se um substituto atender no seu lugar, o utilizador desejado pode ser localizado atravs do sistema de procura de pessoas.
Procura de pessoas
Clicar no boto Paging de pessoas.
Marcar o nmero da extenso do utilizador ou o nmero do servio de procura de pessoas. A procura iniciada. Aguardar at que o utilizador procurado responda. Se o utilizador no responder ou se o sistema de procura de pessoas for desactivado aps um determinado perodo de tempo, a procura pode ser cancelada com o boto Desligar. A procura de pessoas terminada.
36
Funes do sistema
Passo a Passo
Gravador
Pode gravar uma chamada, se a sua consola suportar esta funo e se um gravador estiver ligado ao PC da consola de operadora.
Activar gravador
Clicar no boto Gravador para gravar as chamadas. O smbolo no boto aparece na cor vermelha.
Desactivar gravador
Clicar novamente no boto Gravador para interromper a gravao. O smbolo no boto aparece na cor preta.
Activao automtica do gravador

Para que o gravador seja activado automaticamente com cada chamada externa: 1. Seleccionar Parmetros AC-Win no menu Opes. 2. Seleccionar a opo Gravao automtica na janela Controle de chamadas.
37
Funes do sistema
Passo a Passo
Identificao de chamadas (MCID)

Esta funo possibilita a sada de dados da ligao no terminal do sistema. Requisito: A facilidade deve estar activada no sistema. Clicar no boto MCID enquanto estiver a falar com o chamador. Os dados da ligao (nmero do telefone, data, hora, nmero da consola de operadora) so indicados no terminal do sistema.
Consultar a informao de linha

Determinar o nmero da linha antes de informar eventuais avarias aos servios tcnicos. Clicar no boto Identificar linha.
1234567AG001
O(s) nmero(s) de linha(s)* externa(s) aparece(m) na linha de estado da rea de trabalho. *) O nmero da linha apresentado no seguinte formato: 1234567AS001 LINHA S: de sada; E: de entrada; B:bidireccional
Direco
Clicar novamente no boto Identificar linha para desactivar esta funo.
38
Teclas de nome
Passo a Passo
Teclas de nome
Para informaes sobre como efectuar chamadas com as teclas de nome, consultar o pargrafo Marcao com as teclas de nome . O dilogo "Teclas de Nome" encontra-se sempre na rea de trabalho standard. Se programou as teclas de nome e guardou a rea de trabalho, esta ser aberta com as teclas de nome ao inicializar o AC-Win. Pode tambm criar um novo objecto "Tecla de Nome" e guard-lo.
Abrir o objecto Teclas de Nome

1. Seleccionar a opo Abrir Objecto no menu Arquivo. 2. Seleccionar Teclas de Nome 3. Clicar no boto Abrir. 4. aberta a janela Teclas de Nome .
Pode fechar a janela Teclas de Nome ao premir <CTRL>+<F4> ou pelo campo de menu do sistema.
39
Teclas de nome
Passo a Passo
Programao das Teclas de Nome

Pode programar teclas de nomes vazias ou j ocupadas. 1. Mover o cursor para uma tecla de nome na janela Teclas de Nome e premir a tecla direita do rato.
2. Seleccionar Propriedades das teclas de nome.
3. Introduzir o nome a ser atribudo tecla no campo Legenda . 4. No campo Nmero introduzir o nmero que deve ser marcado quando a tecla for premida. 5. Fechar a janela Propriedades da Tecla de Nome com o boto OK ou <Enter>. A tecla de nome apresentada com a legenda atribuda na janela "Propriedades da Tecla de Nome". Pode utilizar estas teclas para marcar. Para apagar uma tecla de nome, remover os registos dos campos e confirmar com OK.
40
Teclas de nome
Passo a Passo
Salvar a janela Teclas de Nome

Pode salvar a janela Teclas de Nome junto com a rea de trabalho. No pargrafo "Salvar rea de Trabalho" Pgina 69 encontra uma descrio detalhada dos procedimentos necessrios. Pode tambm salvar o objecto "Tecla de nome" independente da rea de trabalho. 1. Seleccionar a opo Salvar Objecto no menu Arquivo. 2. Seleccionar um nome e um directrio. 3. Confirmar a introduo com OK.
41
Repetio de marcao
Passo a Passo
Repetio de marcao
A funo de repetio de marcao permite salvar o ltimo nmero marcado para a posterior repetio. Isto importante, por exemplo, se o utilizador no pde ser contactado na primeira tentativa de chamada. Podem ser guardados at dez nmeros para a repetio de marcao.
Configuraes bsicas
Pode definir se o nmero deve ser registado manual ou automaticamente na lista do dilogo Repetio de marcao: Adio automtica na lista: Cada nmero marcado registado na lista de repetio de marcao. Adicionar quando solicitado pelo utilizador: Define, se o nmero marcado deve ser registado na lista.
Para configurar a funo: 1. Para isto, seleccionar a opo Parmetros AC-Win no menu Opes. 2. Seleccionar a opo Objectos.
3. Seleccionar uma opo. 4. Seleccionar Salvar em Arquivo, para salvar a lista de repetio de marcao num arquivo. 5. Clicar no boto Salvar. 6. Confirmar a introduo com OK.
42
Repetio de marcao
Passo a Passo
Abrir um novo objecto Repetio de marcao

1. Seleccionar a opo Novo Objecto no menu Arquivo. 2. Seleccionar Repetio. 3. Clicar no boto Abrir.
Para abrir uma janela de repetio anteriormente guardada, seleccionar a opo Abrir dilogo no menu Arquivo.
43
Repetio de marcao
Passo a Passo
Salvar nmeros para repetio de marcao

Requisitos: Se seleccionou a opo "Adio a partir de requisio do utilizador" (consultar Configuraes bsicas Pgina 51).
A tecla de funo "Adic. p/repetio" foi configurada no dilogo "Todos Botes". Os procedimentos necessrios so descritos no Manual de Administrao AC-Win. 1. Marcou um nmero ou atendeu uma chamada.
2. Salvar o nmero marcado/indicado com o boto Adic. p/repetio. Com isso, guardado o nmero marcado, mas no o desvio configurado. O nmero e o nome (se configurado) da extenso chamada so adicionados lista de repetio de marcao. Esta lista pode conter at 10 registos. 3. Agora pode Desligar.
Salvar o objecto Repetio

Pode salvar o dilogo actual junto com a rea de trabalho. A opo "Salvar em arquivo" tem de estar activada (ver Configuraes bsicas Pgina 42). O dilogo "Repetio" que tiver os respectivos registos ser indicado ao inicializar o AC-Win. No pargrafo "Salvar rea de Trabalho" Pgina 69 encontra uma descrio detalhada dos procedimentos necessrios.
44
Bloco de notas
Passo a Passo
Bloco de notas
possvel salvar dados da ligao com o bloco de notas, ou seja, pode memorizar no bloco de notas os nmeros de telefone dos dois interlocutores. Isto til, p. ex., quando deve estabelecer uma ligao e a extenso no est disponvel. Pode salvar at 10 nmeros no Bloco de notas . Consultar o pargrafo Marcao com o bloco de notas para as respectivas informaes Pgina 32.
Abrir um novo bloco de notas

1. Seleccionar a opo Novo Objecto no menu Arquivo. 2. Seleccionar Bloco de notas. 3. Clicar o boto OK.
Dessa maneira, pode abrir tambm um bloco de notas j existente. Para isto, clicar, no menu Arquivo, na opo Abrir dilogo e seleccionar um bloco de notas.
45
Bloco de notas
Passo a Passo
Incluir uma chamada no bloco de notas

1. Premir o boto Adic.bloco notas para adicionar a chamada ao bloco de notas. Tambm possvel salvar nmeros que no podem ser marcados. A integridade dos dados no verificada.
Adicionar outros dados no bloco notas

Pode adicionar nmeros de telefone, nome e anotaes no bloco de notas. Utilizar o rato, ou o teclado para mover o cursor para a posio desejada. 1. Clicar no boto Nova linha.
2. Introduzir os dados.
Excluir registos do bloco de notas

1. Seleccionar primeiro um registo no bloco de notas 2. Clicar no boto Apagar. O registo excludo do bloco de notas. Os registos do bloco de notas so excludos automaticamente ao fechar o AC-Win. Os registos do bloco de notas podem ser guardados junto com a rea de trabalho.
46
Bloco de notas
Passo a Passo
Salvar bloco de notas

Pode salvar o bloco de notas com a rea de trabalho. Deve efectuar as seguintes configuraes: 1. Seleccionar a opo Parmetros AC-Win no menu Opes. 2. Seleccionar o separador Objectos.
3. Clicar em Salvar em arquivo para salvar os registos no arquivo definido. 4. Clicar em Salvar. 5. Confirmar a introduo com OK No pargrafo "Salvar rea de Trabalho" Pgina 69 encontra uma descrio detalhada dos procedimentos necessrios. O bloco de notas com os registos guardados indicado automaticamente ao inicializar o AC-Win.
47
Histrico de Chamadas
Passo a Passo
Um Histrico de chamadas uma lista que contm os seguintes dados: Nome (se existente), Nmero Estado (de entrada ou de sada), depende da configurao Data Hora Durao da chamada.
No pargrafo "Marcar com o Histrico de Chamadas" ( Pgina 33) descrito como estabelecer uma ligao com o histrico de chamadas.
Solicitar o Histrico de Chamadas

Tem de activar a funo de registo do Histrico de chamadas: 1. Seleccionar a opo Parmetros AC-Win no menu Opes. 2. Seleccionar o separador Objectos 3. Seleccionar os tipos de chamadas que devem ser registados.
4. Clicar em Salvar em arquivo para salvar os dados. 5. Clicar no boto Salvar. 6. Confirmar a introduo com OK.
48
Passo a Passo
Abrir o Histrico de chamadas

1. Seleccionar a opo Novo Objecto no menu Arquivo. 2. Seleccionar Histrico de Chamadas. 3. Clicar em OK.
Indicao dos dados actuais da ligao

1. Clicar no boto Apres. actual. So indicados os dados da ligao guardados desde a inicializao do AC-Win.
Mostrar os dados da ligao guardados

1. Clicar no boto Abrir arquivo. Os dados da ligao so carregados e indicados.
49
Passo a Passo
Imprimir dados da ligao

1. Clicar no boto Imprimir. A sada dos dados executada na impressora standard.
Salvar o Histrico de Chamadas

O Histrico de Chamadas guardado automaticamente se configurou esta opo no menu Opes/Parmetros AC-Win/separador Objectos/campo Histrico de Chamadas. Por predefinio, a funo Salvar o Histrico de Chamadas est desactivada. Pode salvar o Histrico de Chamadas junto com a rea de trabalho. No pargrafo "Salvar rea de Trabalho" Pgina 69 encontra uma descrio detalhada dos procedimentos necessrios.
50
Taxao no Posto de operadora
Passo a Passo

O AC-Win permite o registo dos dados de taxao de chamadas na consola de operadora. A facilidade deve estar activada no sistema.
Configuraes bsicas
Pode definir, se deseja actualizar os dados de taxao manual ou automaticamente, salvar os dados num arquivo geral.
Proceder da seguinte maneira: 1. Seleccionar a opo Parmetros AC-Win no menu Opes. 2. Seleccionar o separador Controle de Chamadas. 3. Seleccionar Reteno automtica para taxao, para actualizar automaticamente a lista de dados de taxao no dilogo Taxao de Chamadas. 4. Seleccionar a opo Objectos. 5. Clicar em Salvar em arquivo para salvar os dados. 6. Clicar no boto Salvar. 7 . Confirmar a introduo com OK.
51
Passo a Passo
Activar o registo de taxao

1. Premir o boto Req. taxao. O smbolo na tecla aparece na cor vermelha . Agora podem ser visualizados os custos para novas chamadas.
Desactivar o registo de taxao

1. Clicar no boto Req. taxao. O smbolo na tecla aparece na cor preta. O registo de taxao desactivado.
Consultar taxao
Para poder consultar os custos, deve estar activada a taxao de chamadas e a janela Taxao deve estar aberta. 1. Clicar no boto Taxao. aberta a janela Taxao. Podem ser visualizados os custos das chamadas efectuadas.
Pode fechar a janela Taxao ao premir <CTRL>+<F4> ou pelo campo de menu de sistema.
52
Passo a Passo
Verificar taxao de chamadas

1. Clicar no boto Taxao na janela "Taxao" ou no dilogo "Todos Botes". Podem ser visualizados os custos das chamadas efectuadas.
Imprimir a taxao
1. Clicar no boto Imprimir na janela "Taxao". A sada da taxao executada na impressora standard, configurada no PC da consola de operadora.
Reiniciar o contador de taxao

1. Clicar no boto Apagar na janela "Taxao". O registo seleccionado ser apagado. Se no seleccionar um registo, ser apagada a lista completa.
Salvar o objecto Taxao

Se configurou esta opo nas configuraes bsicas, os dados da taxao sero guardados automaticamente Pgina 42. Esta configurao est desactivada por predefinio. Pode salvar a Taxao de chamadas junto com a rea de trabalho. No pargrafo "Salvar rea de Trabalho" Pgina 69 encontra uma descrio detalhada dos procedimentos necessrios.
53
Servio nocturno
Passo a Passo
Servio nocturno
Quando a consola de operadora est desactivada (p. ex., aps o expediente dirio), o "Servio nocturno" encaminha todas as chamadas de entrada para um telefone de servio nocturno (p. ex., para o porteiro).
Activar servio nocturno

1. Clicar no boto Nocturno. A cor do boto Nocturno alterada. As chamadas em espera que ainda constam da janela Controle de Chamadas devem ser atendidas. As novas chamadas de entrada so encaminhadas para as consolas de operadora ainda operacional, ou para o telefone de servio nocturno. 2. Clicar no boto Plug. As chamadas em espera e as novas chamadas de entrada (excepto as chamadas pessoais) so encaminhadas para uma consola de operadora ainda operacional ou para o telefone de servio nocturno.
54
Servio nocturno
Passo a Passo
Servio nocturno automtico

O servio nocturno activado automaticamente aps alguns segundos (standard: 60 s.), se existirem uma ou mais chamadas na fila de espera e no forem executadas funes de controlo de chamadas durante este tempo. Atendimento de chamadas Transferncia de chamadas Estabelecer ligaes Consultar informaes da linha Marcar Activar a procura de pessoas O intervalo de tempo, aps o qual o servio nocturno activado automaticamente, administrado no sistema e no pode ser alterado no AC-Win.
Neste caso, as funes de controlo de chamadas so, p. ex.,
Desactivar servio nocturno

1. Se a ficha do microtelefone de cabea no foi puxada, pode desactivar o servio nocturno com o boto Nocturno. 2. Clicar no boto Plug.
55
Servio nocturno
Passo a Passo
Verificar e alterar servio nocturno

Entre as variantes de servio nocturno existentes no sistema, activada a variante que foi seleccionada pela ltima vez de qualquer consola de operadora. Na janela Modo de servio nocturno, o modo activado indicado seleccionado. So possveis 8 servios nocturnos diferentes. 1. Abrir a janela Servio nocturno. Para isto, seleccionar no menu Opes a opo Alterar Configurao. 2. Seleccionar o separador Nocturno. indicada a variante de servio nocturno actualmente seleccionada.
3. Seleccionar a variante de servio nocturno desejada e clicar no boto Aplicar. activada a nova variante de servio nocturno.
As variantes de servio nocturno disponveis so especficas do sistema e no podem ser administradas com o AC-Win.
56
Restrio de trfego interno para grupos de utilizadores
Passo a Passo

As chamadas internas entre determinados grupos de extenses podem ser bloqueadas temporariamente por um SuperUser ou administrador, para evitar a marcao do prprio nmero. Estas chamadas s podem ser estabelecidas pela operadora (p. ex., em hotis).
Consultar a restrio de trfego interno para grupos de utilizadores

1. Seleccionar no menu Opes a opo Alterar Configurao. 2. Seleccionar o separador Restrio de Trfego.
As restries de trfego interno existentes so especficas do sistema e no podem ser administradas com o AC-Win.
57
Passo a Passo
Activar e desactivar a restrio de trfego interno para grupos de utilizadores

1. Seleccionar o grupo de utilizadores na janela Restrio de Trfego. Pode efectuar as seguintes configuraes: Clicar em Reter para verificar a configurao actual. Clicar em Aplicar para salvar as configuraes. Clicar em Cancelar para fechar a janela. Clicar em Alternar para activar ou desactivar a classe de servio. Clicar em Ligar Tudo para activar a classe de servio para todos os grupos de utilizadores. Clicar em Desligar Tudo para desactivar a classe de servio para todos os grupos de utilizadores.
58
Alterao de classe de servio para grupos de utilizadores
Passo a Passo

possvel alterar temporariamente a classe de servio para um determinado grupo de utilizadores. A alterao de classe de servio permite, p. ex., evitar o estabelecimento de chamadas com custos fora do horrio de expediente.
Consultar as classes de servio para grupos de utilizadores

Clicar no boto COS ou 1. Seleccionar no menu Opes a opo Alterar Configurao. 2. Seleccionar o separador Classe de servio.
mostrada a lista de grupos de utilizadores com suas respectivas classes de servio. As classes de servio possveis so especficas do sistema e no podem ser administradas com o AC-Win.
59
Passo a Passo
Activar e desactivar classes de servio para grupos de utilizadores

1. Marcar a opo desejada na janela Classe de servio. Pode efectuar as seguintes configuraes: Clicar em Reter para verificar a configurao actual. Clicar em Aplicar para salvar as configuraes. Clicar em Cancelar para fechar a janela. Clicar em Alternar para activar ou desactivar a classe de servio. Clicar em Ligar Tudo para restringir a classe de servio para todos os grupos de utilizadores. Clicar em Desligar Tudo para cancelar a restrio da classe de servio para todos os grupos de utilizadores.
60
No incomodar para grupos de utilizadores
Passo a Passo

A funo No incomodar pode ser activada temporariamente para determinados grupos de utilizadores (extenses), se estes no desejarem receber chamadas.
No incomodar para os grupos de utilizadores

1. Seleccionar no menu Opes a opo Alterar Configurao. 2. Seleccionar o separador No incomodar.
mostrada a lista dos grupos de utilizadores com a funo No incomodar activada. As opes do servio No incomodar disponveis so especficas do sistema e no podem ser administradas com o ACWin.
61
Passo a Passo
Activar e desactivar No incomodar para grupos de utilizadores

1. Seleccionar a opo desejada na janela No incomodar. Pode efectuar as seguintes configuraes: Clicar em Reter para verificar a configurao actual. Clicar em Aplicar para salvar as configuraes. Clicar em Cancelar para fechar a janela. Clicar em Alternar para activar ou desactivar a classe de servio. Clicar em Ligar Tudo para restringir a classe de servio para todos os grupos de utilizadores. Clicar em Desligar Tudo para cancelar a restrio da classe de servio para todos os grupos de utilizadores.
62
Alarme
Passo a Passo
Alarme
A cor do boto de alarme muda quando ocorrem erros ou falhas na consola de operadora. Pode ser determinado o tipo de erro pela cor do boto de alarme. A cor amarela indica erros de menor importncia. A cor vermelha indica erros que devem ser informados imediatamente Assistncia Tcnica. Cor vermelha amarela Alarmes alarmes urgentes alarmes gerais
Consultar as mensagens de erros

1. Premir o boto Alarmes.
As causas dos alarmes so apresentadas na janela Alarmes.
Imprimir alarmes
As causas dos alarmes so apresentadas na janela Alarmes. 1. Clicar no boto Imprimir.
Apagar alarme(s)
As causas dos alarmes so apresentadas na janela Alarmes . 1. Clicar no boto Apagar, para apagar os registos.
63
Regulao do sinal de chamar
Passo a Passo

No dilogo Definies do sinal de chamar define os recursos de entrada e sada para voz. Se possuir um carto de udio, pode atribuir diferentes ficheiros WAV a chamadas normais ou chamadas de emergncia. 1. Seleccionar a opo Config. sinal de chamar no menu Opes.
2. Nos campos de seleco, definir o driver para Toque (sada) Misturador para o microtelefone (de cabea) (sada) Altifalante (sada) Microfone (entrada)
64
Passo a Passo
Se utilizar uma placa de som 3. No campo Sinal de chamar placa de som pode seleccionar ficheiros WAV para chamadas normais e chamadas especiais/de emergncia ao clicar em Browse. 4. Clicar em OK. 5. Testar os ficheiros WAV seleccionados. Se desejar um outro sinal, repetir o passo 3. 6. Clicar em Aplicar, para guardar as alteraes. 7 . Clicar no boto Cancelar para fechar a janela sem guardar as alteraes. 8. Confirmar a introduo com OK.
65
Diagnstico de erros
Passo a Passo
Diagnstico de erros
Nos casos de falhas na aplicao AC-Win, pode activar programas de diagnstico, que possibilitam ao tcnico de assistncia encontrar possveis erros com facilidade. Esto disponveis trs tipos de informao: Rastreio CAPI (Common ISDN Application Interface) Diagnstico AC Informaes acerca do software, nmero da verso do AC-Win utilizado
CAPI Trace
Com a funo Rastreio CAPI so gravadas informaes sobre o comportamento da interface CAPI da ficha de AC-Win utilizada. 1. Seleccionar a opo CAPI-Trace no menu Opes.
2. Para sair do rastreio CAPI, tem de fechar o AC-Win e reinici-lo.
66
Diagnstico de erros
Passo a Passo
Diagnstico AC
A funo Diagnstico AC possibilita a gravao de informaes sobre o comportamento interno do AC-Win. 1. Para isto, seleccionar a opo Iniciar AC-Diag no menu Opes.
2. Clicar em Trace-Information sichern (Salvar informao de rastreio).
As informaes de rastreio so guardadas no ficheiro indicado.
67
Diagnstico de erros
Passo a Passo
Determinar nmero da verso

Para determinar a verso do AC-Win utilizado e outras informaes, deve proceder da seguinte maneira: 1. Seleccionar a opo Acerca AC-Win no menu Ajuda.
Esta janela fornece informaes sobre a Verso AC-Win Verso AC-Win 2Q IP Verso SoftOLA
68
Salvar a rea de trabalho
Passo a Passo
Salvar a rea de trabalho

Deve salvar a rea de trabalho se tiver efectuado alteraes nesta, p. ex., nas teclas de nome 1. Seleccionar a opo Salvar rea de Trabalho no menu Arquivo.
2. Ao salvar a rea de trabalho pela primeira vez, aberta uma caixa de dilogo na qual deve ser introduzido o nome do arquivo e o directrio correspondentes. 3. Clicar no boto OK para salvar a rea de trabalho. A sua rea de trabalho guardada.
69
ndice remissivo
ndice remissivo
A
Abrir bloco de notas ........................................ 45 Abrir a janela Teclas de nome .................. 39 Abrir janela de repetio de marcao ... 43 Abrir o Histrico de chamadas ................ 49 Acoplar ................................................... 17, 29 Activao / desactivao do AC-Win ...... 17 Activao automtica do gravador .......... 37 Activar gravador ......................................... 37 Activar o registo de taxao ..................... 52 Activar servio nocturno ........................... 54 Alarme .......................................................... 63 Alterao de classe de servio ................ 59 Alterar a senha ........................................... 11 Alterar modo de servio nocturno .......... 56 Apagar .......................................................... 24 Apagar alarme(s) ........................................ 63 Apagar introduo ...................................... 16 rea de trabalho ......................................... 12 Atender chamada pessoal ........................ 15 Atender chamadas externas .................... 15 Atender chamadas internas ..................... 15 Atendimento automtico de chamadas . 13 Atendimento de chamadas .................. 7, 21
Comunicao alternada ............................. 28 Comunicao alternada entre as linhas .. 29 Comunicao alternada entre os tipos de chamada ...................................................... 29 Comutao para marcao MF ................ 17 Configuraes do sistema ........................ 56 Consulta ....................................................... 27 Consulta de alarme .................................... 16 Consultar as mensagens de erros (alarmes)
....................................................................... 63
Consultar taxao de chamadas .............. 52 Continuar uma chamada retida ................ 27 Cortar a ligao ........................................... 15 Cortar ligao .............................................. 24
D
Desactivar gravador ................................... 37 Desactivar intruso .................................... 24 Desactivar o registo de taxao .............. 52 Desactivar servio nocturno ..................... 55 Desligamento de emergncia .................. 17 Desligar ........................................................ 24 Desligar o PC da consola de operadora . 11 Diagnstico AC ........................................... 67 Dilogo controlo de chamadas ........................... 13 teclas de nome ....................................... 18 todos botes ........................................... 15 Dilogo de incio da sesso ...................... 10 DS-Win ........................................................... 7
B
Bloco de notas ...................................... 16, 45 Bloco notas adicionar outros dados .......................... 46
E
Excluir registos do bloco de notas ................... 46 Excluir registos do bloco de notas .......... 46
C
CAPI Trace .................................................. 66 Chamada alternada .................................... 28 Chamada com taxao .............................. 16 Chamada em cadeia ............................ 16, 26 Chamada serial ........................................... 26 Classe de servio activar ....................................................... 60 consultar .................................................. 59 desactivar ................................................ 60
F
Ficheiro WAV .............................................. 65 Funes das teclas .................................... 15 Funes de operadora ................................ 7 Funes de telefonia ................................... 7 Funes do sistema .................................. 36
70
ndice remissivo
G
Gravador ................................................ 17, 37 Grupo alvo ..................................................... 8 Guardar o nmero para a repetio de marcao ............................................................ 16
N
No incomodar activar ....................................................... 62 desactivar ................................................ 62 No incomodar para grupos de utilizadores
....................................................................... 61
H
Histrico de Chamadas ............................. 48 dados da ligao guardados ................. 49
Navegao rea de trabalho ..................................... 19 Novo objecto ............................................... 43 Nmero da verso ..................................... 68
I
Identificao de chamadas maliciosas (MCID) .......................................................... 17 Identificao de linha ................................. 16 Identificao do nmero de linha ............ 38 Identificao do utilizador ......................... 10 Imprimir a taxao ..................................... 53 Imprimir alarmes ........................................ 63 Imprimir dados da ligao ......................... 50 Incluir uma chamada no bloco de notas 46 Inicializar o programa ................................. 10 Iniciar a consulta para uma extenso ..... 15 Iniciar chamada pessoal ............................ 16 Intercalao ........................................... 17, 25 Intercalao de chamadas .......................... 7 Intercalao de emergncia ..................... 17 Introduo alfanumrica ........................... 17 Intruso ........................................................ 25
O
Objectivo ....................................................... 8 Objecto Tecla de Nome abrir ........................................................... 39 Ocupar linha ................................................ 16
P
Parque .......................................................... 29 Parquear a chamada .................................. 16 Personalizao da interface do utilizador . 7 Placa de som .............................................. 65 Procura de pessoas ............................. 16, 36 Procura de pessoas (Paging) .................... 36 Programao das teclas de nome ........... 40
R
Registo de taxao .................................... 51 Regulao do sinal de chamar ................. 64 Repetio guardar nmero automaticamente ...... 42 Repetio de marcao ....................... 42, 43 Requisitos ...................................................... 8 Restrio de trfego interno .................... 57 activar ....................................................... 58 consultar .................................................. 57 desactivar ................................................ 58 Retomar chamadas do parque ................. 16 Retomar uma chamada parqueada ......... 29
M
Marcao posterior MF ............................. 35 Marcar .......................................................... 30 com "Arrastar e soltar" ........................... 34 com a rea de transferncia ................. 33 com a repetio de marcao .............. 31 com as teclas de nome ......................... 32 com o bloco de notas ............................ 32 com o histrico de chamadas .............. 33 com o rato ............................................... 34 Marcar nmero ........................................... 17 Marcar o nmero para a repetio de marcao ............................................................ 16 Mostrar dados da ligao ......................... 49 Mudar classe de acesso ........................... 16
71
ndice remissivo
S
Sair do programa ........................................ 10 Salvar a rea de trabalho ........................... 69 Salvar a janela Teclas de nome ............... 41 Salvar bloco de notas ................................ 47 Salvar informao de rota ......................... 67 Salvar nmeros para repetio de marcao ................................................................ 44 Salvar o Histrico de Chamadas .............. 50 Salvar o objecto Repetio ....................... 44 Servio nocturno .................................. 17, 54 Servio nocturno automtico ................... 55 Servio rpido ............................................. 23 Sinais de chamada ..................................... 20 Sinais de marcar ......................................... 20 Solicitar Histrico de Chamadas .............. 48 Suporte acstico ........................................ 20 Suporte ptico ............................................ 20
T
Taxao apagar ....................................................... 53 salvar o objecto ...................................... 53 Tecla de funo .......................................... 17 Teclas de nome .................................... 17, 39 de programao livre ............................... 7 Todos Botes ............................................. 15 Transferncia de chamada ....................... 21 Transferncia de chamadas ....................... 7 Transferncia normal ................................. 22 Transferir ..................................................... 22 Transferir a chamada ................................. 15
U
Utilizao com o rato ................................. 19 Utilizao com os botes ......................... 19
V
Verificao do modo de servio nocturno .
56
Verificar taxao de chamadas .......... 16, 53 Verso AC-Win ........................................... 68
72
Copyright Siemens Enterprise Communications GmbH & Co. KG 06/2007 Hofmannstr. 51, D-81359 Mnchen N de encomenda: A31003-G4010-U100-2-7919 As informaes neste documento contm apenas descries gerais ou facilidades, que nem sempre correspondem, na forma como esto descritas, e que podem sofrer alteraes devido ao desenvolvimento dos produtos. As facilidades desejadas apenas sero vinculativas, se tiverem sido estabelecidas por expresso nos termos do contrato. Reserva-se a possibilidade de entrega e o direito de alteraes tcnicas. As marcas comerciais utilizadas so propriedade da Siemens Enterprise Communications GmbH & Co. KG ou do respectivo titular.
www.siemens.com/enterprise
Ramais IP
4. Ramais IP
Ramais IP
Devices IP
Siemens
Devices IP
Contents
1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 2 2.1 3 3.1 3.2 3.3 3.4 4 4.1 4.2 5 5.1 6 6.1 optiPoint 410 / 420 Family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 General informations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Overview of the terminals and the optional modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 optiPoint 410/420 Adapter support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Service information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 HiPath 4000 V2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 AMO changes for the feature Self Labling Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Installation optiPoint 410 / 420 with Terminal software < 5.x.x . . . . . . . . . . . . . . . 23 Settings for all optiPoint 410 and 420 except optiPoint 410 entry . . . . . . . . . . . . . . . . 23 optiClient 130 V5.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Installation and Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Generating of the optiClient 130 V5.0 in the HiPath 4000 V2.0. . . . . . . . . . . . . . . . . . 45 Short description of the user interface of the optiClients 130 V5.0 . . . . . . . . . . . . . . . 46 optiPocket V1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 W-LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 optiPoint WL2 professional / S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 OpenStage IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
BR0038
17/09/2009
Page 1 of 102
Siemens
Devices IP
6.2 6.3 6.4 6.5 6.6 6.7 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 8 8.1 8.2
OpenStage 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OpenStage 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OpenStage 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OpenStage 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OpenStage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Phone Book Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Search functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Screensaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AC-WIN IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Systemconcept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Variants from ACWIN IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.1 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.2 Initial operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.3 Entering general data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.4 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.5 DLS/DLC Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.6 General settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.7 Voice Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.8 Settings in the AC for automatic voice recording . . . . . . . . . . . . . . . . . . . . . 8.2.9 Deinstallation of the AC-Win IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customer License Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.1 Installation of the CLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.1.1 Standalone Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License Management (CLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.1 Installation of the CLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.1.1 Standalone Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.1 License Management Contents Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.2 License Management Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.3 Activating Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.4 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.5 License Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.6 Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55 56 57 58 59 60 61 61 61 62 63 63 66 66 67 69 69 70 72 72 73 74 75 76 77 78 79 81 81 81 84 85 88 90 91 92 94 94 95 96 97 98 99
9 9.1 9.2
9.3
9.4
BR0038
17/09/2009
Page 2 of 102
Devices IP
Siemens
9.4.7
Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
BR0038
17/09/2009
Page 3 of 102
Siemens
Devices IP
BR0038
17/09/2009
Page 4 of 102
Devices IP
Siemens
1
1.1
optiPoint 410 / 420 Family

General informations
The terminals of the optiPoint 410 / 420 family can be connected as IP-phones to the HiPath 3000 and HiPath 4000 systems.
1.2
Overview of the terminals and the optional modules
optiPoint 410 entry IP standards: - HFA - H323, CorNet IP, SIP - G.711, G.723, G.729 AB, G.722 for DMC, QoS, Security H.235 - SNMP, HTTP, DHCP, FTP 10/100Base-T, VLAN support Power over LAN resp. power supply unit CTI (TAPI) applications No display Eight function keys with LED Loudspeaker Two keys (+/-) for settings ringer tone volume, ringer pitch and alerting tone No adapter ports for add-on modules No key module- and display module - interface Wall mountable Colors: arctic, mangan
BR0038
17/09/2009
Page 5 of 102
Siemens
Devices IP
optiPoint 410 economy IP standards: - HFA - H323, CorNet IP, SIP - G.711, G.723, G.729 AB, G.722 for DMC, QoS, Security H.235 - SNMP, HTTP, DHCP, FTP 10/100Base-T, VLAN support Power over LAN resp. power supply unit CTI (TAPI) applications Alphanumeric LCD swivel display 2 lines (24 characters per line) 12 function keys LED Two keys (+/-) for settings ringer volume, ringer pitch and alerting tone Three dialog keys for easy menu navigation and selection Loudspeaker No adapter ports for add-on modules No key module- and display module - interface Wall mountable Colors: arctic, mangan
BR0038
17/09/2009
Page 6 of 102
Devices IP
Siemens
optiPoint 410 economy plus IP standards: - HFA - H323, CorNet IP, SIP - G.711, G.723, G.729 AB, G.722 for DMC, QoS, Security H.235 - SNMP, HTTP, DHCP, FTP 10/100Base-T, mini-switch (VLAN) support Power over LAN resp. power supply unit CTI (TAPI) applications Headset port (121 TR9-5) Alphanumeric LCD swivel display 2 lines (24 characters per line) 12 function keys LED Two keys (+/-) for settings ringer volume, ringer pitch and alerting tone Three dialog keys for easy menu navigation and selection Loudspeaker No adapter ports for add-on modules No key module- and display module - interface Wall mountable Colors: arctic, mangan
BR0038
17/09/2009
Page 7 of 102
Siemens
Devices IP
optiPoint 410 standard IP standards: - HFA - H323, CorNet IP, SIP - G.711, G.723, G.729 A / AB, G.722 for DMC, QoS, Security H.235 - SNMP, HTTP, DHCP, FTP 10/100Base-T, mini-switch (VLAN) support Power over LAN resp. power supply unit CTI (TAPI) applications Headset port (121 TR9-5) Alphanumeric LCD swivel display 2 lines (24 characters per line) additional background lighting 12 function keys with LED Two keys (+/-) for settings ringer volume, ringer pitch and alerting tone Three dialog keys for easy menu navigation and selection Full duplex handsfree talking Two adapter ports for add-on modules Key module (self labling and standard) - and display module - interface Wall mountable Colors: arctic, mangan
BR0038
17/09/2009
Page 8 of 102
Devices IP
Siemens
optiPoint 410 advance IP standards: - HFA - H323, CorNet IP, SIP - G.711, G.723, G.729 AB, G.722 for DMC, QoS, Security H.235 - SNMP, HTTP, DHCP, FTP 10/100Base-T, mini-switch (VLAN) support Power over LAN resp. power supply unit CTI (TAPI/JTAPI) applications USB master port One headset port (121 TR9-5) Excellent audio quality with Speech Extender LCD swivel display with 4 lines (24 characters per line) additional background lighting 19 function keys with LED Support of the self labeling keys Two keys (+/-) for settings ringer volume, ringer pitch and alerting tone Three dialog keys for easy menu navigation and selection Loudspeaker Full duplex handsfree talking 1 port for add-on modules Key module (self labling and standard) - and display module - interface Wall mountable Colors: arctic, mangan
BR0038
17/09/2009
Page 9 of 102
Siemens
Devices IP
optiPoint 420 economy IP standards: - HFA - H323, CorNet IP, SIP - G.711, G.723, G.729 AB, G.722 for DMC, QoS, Security H.235 - SNMP, HTTP, DHCP, FTP 10/100Base-T, VLAN support Power over LAN resp. power supply unit CTI (TAPI) applications Alphanumeric LCD swivel display 2 lines (24 characters per line) 12 self labeling function keys (5+7) with LED Two keys (+/-) for settings ringer volume, ringer pitch and alerting tone Three dialog keys for easy menu navigation and selection Loudspeaker No adapter ports for add-on modules No key module- and display module - interface Wall mountable Colors: arctic, mangan
BR0038
17/09/2009
Page 10 of 102
Devices IP
Siemens
optiPoint 420 economy plus IP standards: - HFA - H323, CorNet IP, SIP - G.711, G.723, G.729 AB, G.722 for DMC, QoS, Security H.235 - SNMP, HTTP, DHCP, FTP 10/100Base-T, mini-switch (VLAN) support Power over LAN resp. power supply unit CTI (TAPI) applications Headset port (121 TR9-5) Alphanumeric LCD swivel display 2 lines (24 characters per line) 12 self labeling function keys (5+7) with LED Two keys (+/-) for settings ringer volume, ringer pitch and alerting tone Three dialog keys for easy menu navigation and selection Loudspeaker No adapter ports for add-on modules No key module- and display module - interface Wall mountable Colors: arctic, mangan
BR0038
17/09/2009
Page 11 of 102
Siemens
Devices IP
optiPoint 420 standard IP standards: - HFA - H323, CorNet IP, SIP - G.711, G.723, G.729 AB, G.722 for DMC, QoS, Security H.235 - SNMP, HTTP, DHCP, FTP 10/100Base-T, mini-switch (VLAN) support Power over LAN resp. power supply unit CTI (TAPI) applications Headset port (121 TR9-5) Alphanumeric LCD swivel display 2 lines (24 characters per line) additional background lighting 12 self labeling function keys (5+7) with LED Two keys (+/-) for settings ringer volume, ringer pitch and alerting tone Three dialog keys for easy menu navigation and selection Full duplex handsfree talking Two adapter ports for add-on modules Key module (self labling and standard) - and display module - interface Wall mountable Colors: arctic, mangan
BR0038
17/09/2009
Page 12 of 102
Devices IP
Siemens
optiPoint 420 advance IP standards: - HFA - H323, CorNet IP, SIP - G.711, G.723, G.729 AB, G.722 for DMC, QoS, Security H.235 - SNMP, HTTP, DHCP, FTP 10/100Base-T, mini-switch (VLAN) support Power over LAN resp. power supply unit CTI (TAPI/JTAPI) applications USB master port One headset port (121 TR9-5) Excellent audio quality with Speech Extender LCD swivel display with 4 lines (24 characters per line) additional background lighting 18 self labeling function keys (5+13) with LED Support of the self labeling keys; Two keys (+/-) for settings ringer volume, ringer pitch and alerting tone Three dialog keys for easy menu navigation and selection Loudspeaker Full duplex handsfree talking 1 port for add-on modules Self labeling key module - and display module - interface Wall mountable Colors: arctic, mangan
BR0038
17/09/2009
Page 13 of 102
Siemens
Devices IP
AP1120 Connection to STMI 2 for HFA 2x RJ11 for analog devices 1x 10/100 BaseT Ethernet access 10/100 BaseT Ethernet, inline powered Connection for analog devices
BR0038
17/09/2009
Page 14 of 102
Devices IP
Siemens
optiPoint 410 key module and self labeling key module 16 function keys with LED Maximum two key modules per terminal, if no Display Module is installed Button is twice verifiable for named buttons Can not be connected to an optiPoint 410/420 entry, economy and economy plus Colors: arctic, mangan 13 function keys with LED Indication of the key function, name or phone number over integrated LCD displays. Button is fourfold verifiable with named buttons and get select over the Shift button (button 13). Maximum two key modules per terminal, if no Display Module is installed Can only be connected to an optiPoint 410/420 standard and advance Colors: arctic, mangan
optiPoint 420 Self Labling Key Module
BR0038
17/09/2009
Page 15 of 102
Siemens
Devices IP
optiPoint Display Module Big LCD display with touchscreen function (320x240) and additional background lighting Swivel display Applications: - Graphical user interface for telephony - Online help - JAVA platform, JDK (only for advance) - Local, personal telephon book - Access to Corporate directories via LDAP - WML/HTML Browser - Voice dialing Can only be used for optiPoint 410/ 420 standard and advance Colors: arctic, mangan
optiPoint Application Module Full color LCD display with touchscreen function Integrated alphanumeric Keyboard (English or German) Applications: - Graphical user interface for telephony - Online help - JAVA platform, JDK (only for advance) - Local, personal telephon book - Access to Corporate directories via LDAP - WML/HTML Browser - Voice dialing Colors: arctic, mangan
BR0038
17/09/2009
Page 16 of 102
Devices IP
Siemens
optiPoint acoustic adapter Permits to connect telephony accessories: active speaker, external microphone via Y cable Headset (wired or wireless official 121 TR9-5) dry contact "contact adapter" e.g. door opener, Busy display, second bell. can not be used, if the terminal is connected via power over LAN
optiPoint recorder adapter external recorder connection or secondary speaker Second handset
optiPoint signature module Telephone adapter for Chipcard reader (Smart Card Application) The cards are programmed with the help of a card reader and a PC program max. 1 module per telephone can be connected Colors: arctic, mangan
BR0038
17/09/2009
Page 17 of 102
Siemens
Devices IP
1.3
Feature description
The new optiPoint 410 terminal is available in five different configurations. One terminal has no display, 4 include a display. The new optiPoint 420 terminal is available in five different configurations and supports self labling keys. All terminals include a display. 2 key modules can be connected, if no display or application module is installed. If a display/application module is installed, only one key module can be used. All optiPoint 410 / 420 have the same UI (user interface) as the optiPoint 500 terminals. Display of country-specific characters is supported. The integrated USB 1.1 interface is used to connect an external keyboard. When adapters or add-on-modules are used, the wall mounting option is not possible.
BR0038
17/09/2009
Page 18 of 102
Devices IP
Siemens
1.4
optiPoint 410/420 Adapter support
The optiPoint family of telephones support adapters and add-on modules as detailed in the table below. Basically the Entry, Economy and Economy plus do not support any adapters or add-on modules. The standard and Advance however support them as shown in the table below. Optipoint Key Add-On Modules BLF Signature Self labeling key N N N Y Y N N Y Y Recorder Adapters Acoustic DSM
410 Entry 410 Economy 410 Economy plus 410 Standard 410 Advance 420 Economy 420 Economy plus 420 Standard 420 Advance Notes: 1. 2.
N N N Y Y N N Y Y
N N N Y Y N N Y Y
N N N Y Y N N Y Y
N N N Y Y N N Y Y
N N N Y Y N N Y Y
N N N Y Y N N Y Y
The BLF (Busy-Lamp Field) is not supported by the Hipath 4000 The Signature (Card-Reader) module is not supported by the Hipath 3000
BR0038
17/09/2009
Page 19 of 102
Siemens
Devices IP
1.5
Service information
Care has to be taken, that the correct Key standard for optiPoint 410/420 is always used. T8 for optiPoint 410 entry, T12 for optiPoint 410/420 economy, 410/420 economy plus and 410/420 standard, and T19 for optiPoint 410/420 advance. The self labling key module can be connected to an optiPoint 410 advance and standard, but only in HiPath 4000 V2.0, not in HiPath 4000 V1.0. To reach the "Configuration Menu" of the terminal, the buttons 1 0 3 have to be pressed at the same time. The standard password is 123456. To reset a terminal, a Factory Reset can be executed via the Configuration Menu respectively via the WBM (depending on the loaded phone software). An additional possibility is to use key combination 2 8 9 (simultaneously). The Reset password is 124816.
1.6
HiPath 4000 V2.0

The optiPoint 410 /420 are generated in the same way as the optiPoint 400. New parameters in AMO SBCSU:...CONN=IP2, if the terminal is connected to a STMI2 board. In the AMO ZAND the type=optiset is also valid to the optiPoint 410 / 420. Max. one "optiPoint signature module" is possible per terminal. An "optiPoint self labeling key module" may only be connected/disconnected to an optiPoint 410 / 420 in the power off condition. An optiClient 130 is configured like a corresponding optiPoint telephone. An exchange of an optiPoint IP telephone for an optiClient 130 soft client is possible. The optiPoint display module for the optipoint 410 / 420 family can not be added to an optiPoint500 or 600. There can be only one optiPoint display module connected to an optiPoint 410 / 420. An "optiPoint display module" must always be attached directly to the optiPoint 410 / 420.
BR0038
17/09/2009
Page 20 of 102
Devices IP
Siemens
1.7
AMO changes for the feature Self Labling Key
ADD-ZIEL: TYPE=NAME/DSS,SLKTYPE=yyyyyyyyy ADD-ZIELN: TYPE=RNGXFER/DSS/DSSWOOVR, SLKTYPE=yyyyyyyyy ADD-KCSU: TYPE=PRIM,PRIMKEY=zz,SLKTYPE=yyyyyyyyy ADD-KCSU: TYPE=SEC,KYNO=zz,SLKTYPE=yyyyyyyyy CHANGE-KCSU: TYPE=PRIM,PRIMKEY=zz,SLKTYPE=yyyyyyyyy CHANGE-KCSU: TYPE=SEC,KYNO=zz,SLKTYPE=yyyyyyyyy CHANGE-CHESE:...,TYPE=EXECSLK,EXEC=xxxxxx,KEY=RNGXFER1,SLKTYPE=yyyyyyyyy CHANGE-CHESE:...,TYPE=SECRSLK,SECR=xxxxxx,KEY=RNGXFER1-RNGXFER4 resp. PUS1-PUS4, SLKTYPE=yyyyyyyyy
Explanation:
yyyyyyyyy = SLKSTNO SLKNAME SLKTEXT
-> Station number of the destination subscriber -> Name coming from AMO PERSI, if available -> Individual text with capital or lower case letters (max. 12 characters)
Number of self labling keys with individual text in the system:

DISPLAY-DIMSU:TYPE=USER; ADD-DIMSU:TYPE=USER,SLKTEXT=......;
Set display contrast for Self Labling Key:

ADD-ACTDA: TYPE=STN,STNO=xxxxxx,FEATCD=OPTISET,SLKCONT=[0,3]
BR0038
17/09/2009
Page 21 of 102
Siemens
BR0038
17/09/2009
Page 22 of 102
Devices IP
Siemens
2
2.1
Installation optiPoint 410 / 420 with Terminal software < 5.x.x

Settings for all optiPoint 410 and 420 except optiPoint 410 entry
In this document only the basic steps are described. For detailed information please use the Administration resp. User manual.
a) DHCP is used (standard-setting):

Change into Configuration-Menu (push keys 1 0 3 simultaniously); -> By first installation use Enter key:
Administration: 01 = Configuration?
Enter
Enter admin password
123456 Enter
Change to 02 = System:
Configuration: 02 = System?
Enter
System: HiPath-4K-V1 01 = System type? Select System type with arrow keys:
Enter
System type: HiPath-4K-V2
Enter
BR0038
17/09/2009
Page 23 of 102
Siemens
Devices IP
Change to 02 = PBX Address:
System: 02 = PBX Address? Change to Edit IP:
0.0.0.0
Enter
PBX Address: Edit IP?
Enter
PBX Address: 001.040.031.070 Change to 03 = Subscriber number:
Enter
Dot in IP address is equivalent to*-key!
System: 03 = Subscriber number?
Enter
Subscriber number: 7376
Enter
If a password is needed-> change to 04 = Subscriber password: This password has to be configured with AMO SBCSU with parameter IPPASSW.
System: 04 = Subscriber password?
Enter
BR0038
17/09/2009
Page 24 of 102
Devices IP
Siemens
Change to 00 = End:
System: 00 = End? Change to 00 = End:
Enter
Configuration: 00 = End?
Enter
Save Changes? Yes Change to 03 = Start Phone:
Enter
Administration: 03 = Start Phone?
Enter
16:08 7376
Th 01.07.04 TI Munich
BR0038
17/09/2009
Page 25 of 102
Siemens
Devices IP
b) Without DHCP:
Change into Configuration-Menu (push keys 1 0 3 simultaniously); -> By first installation use Enter key:
Administration: 01 = Configuration?
Enter
Enter admin password
123456 Enter
Configuration: 01 = Network?
Enter
Netwerk: 01 = DHCP IP assign?
On
Enter
Change DHCP setting with arrow key to OFF , confirm with Enter. Change to 02 = Terminal IP addr.:
Network: 0.0.0.0 02 = Terminal IP addr.?
Enter
Terminal IP addr.: 001.040.031.006
Enter
BR0038
17/09/2009
Page 26 of 102
Devices IP
Siemens
Change to 03 = Terminal mask:
Network: 03 = Terminal mask?
0.0.0.0
Enter
Terminal mask: 255.255.255.0 Change to 04 = Default route:
Enter
Network: 03 = Default route?
0.0.0.0
Enter
Default route: 001.040.031.254 Change to 00 = End:
Enter
Network: 00 = End?
Enter
Change to 02 = System:
Configuration: 02 = System?
Enter
BR0038
17/09/2009
Page 27 of 102
Siemens
Devices IP
System: HiPath-4K-V1 01 = System type? Choose system type with the arrow key:
Enter
System type: HiPath-4K-V2 Change to 02 = PBX Address:
Enter
System: 02 = PBX Address? Change to Edit IP:
0.0.0.0
Enter
PBX Address: Edit IP?
Enter
PBX Address: 001.040.031.070 Change to 03 = Subscriber number:
Enter
Enter dot with *-key!
System: 03 = Subscriber number?
Enter
Subscriber number: 7376
Enter
BR0038
17/09/2009
Page 28 of 102
Devices IP
Siemens
If a password is needed-> change to 04 = Subscriber password: This password has to be configured with AMO SBCSU with parameter IPPASSW.
System: 04 = Subscriber password? Change to 00 = End:
Enter
System: 00 = End? Change to 00 = End:
Enter
Configuration: 00 = End?
Enter
Save Changes? Yes Change to 03 = Start Phone:
Enter
Administration: 03 = Start Phone?
Enter
16:08 7376
Th 01.07.04 TI Munich
BR0038
17/09/2009
Page 29 of 102
Siemens
BR0038
17/09/2009
Page 30 of 102
Devices IP
Siemens
3
3.1
optiClient 130 V5.0

Description
The optiClient 130 V5.0 is the succession product of the Version V2.5 for the HiPath 4000 V2.0 and the HiPath 3000. It supports the feature Direct Media Connection (DMC) and is connected to a STMI2 board. The used protocol is HFA.
3.2
Installation and Settings
In this document only the basic steps are described. For detailed information please use the Administration resp. User manual. The installation will be started with the Setup.exe file. Then follow the menu of the installation routine.
The optiClient 130 V5.0 can be installed with a 30-day-license for testing. to activate this 30-day-license, you have to start the Setup.exe in the directory ..../Licensing/ CLA, on the PC and follow the menu of the installation routine.
BR0038
17/09/2009
Page 31 of 102
Siemens
Devices IP
After starting the optiClient 130 V5.0 on the PC, the following settings and entries are required.
1.
3.
2.
If an user ID is added without a password, the login window will not be displayed for future starts of the client. To get the login window, e.g. to change settings, it is necessary to press the Shift-key during the client boot.
BR0038
17/09/2009
Page 32 of 102
Devices IP
Siemens
3.
Select color scheme for the Client-surface
BR0038
17/09/2009
Page 33 of 102
Siemens
Devices IP
Example for Audio settings in the PC:

Signal channel via Sound card USB Handset is used
BR0038
17/09/2009
Page 34 of 102
Devices IP
Siemens
Select the desired Audio-Scheme and move it to the upper position.
BR0038
17/09/2009
Page 35 of 102
Siemens
Devices IP
In this menu it is possible to define the options for click in the display of the Client.
Free phone can be closed by clicking on the display a second time.
BR0038
17/09/2009
Page 36 of 102
Devices IP
Siemens
There the symbols in the communication circuit and the image of the easyCom - design can be defined.
If you want to select image to be represented in colors that match the current color scheme, enable the option.
BR0038
17/09/2009
Page 37 of 102
Siemens
Devices IP
Selection of phone type, Key module type and of maximum number of key modules (0-4).
BR0038
17/09/2009
Page 38 of 102
Devices IP
Siemens
Extension number of the optiClient from AMO WABE and SBCSU. User password from AMO SBCSU, Parameter=IPPASSW IP address of the STMI2 board from AMO HFAB. Type options are HiPath 3000 resp. HiPath 4000.
BR0038
17/09/2009
Page 39 of 102
Siemens
Devices IP
Settings of the Central Office (CO) access:
BR0038
17/09/2009
Page 40 of 102
Devices IP
Siemens
Bandwidth - and DMC control:
Teleworking deactivated -> G711 resp. setting in field Codec sequence Teleworking activated with setting in the field Codec sequence -> G723 / G729
depending on the codec sequence in AMO HFAB: TYPE=ASC -> CODECLIST
BR0038
17/09/2009
Page 41 of 102
Siemens
Devices IP
Quality of Service settings (QoS for L2 and L3 are deactivated in standard):
BR0038
17/09/2009
Page 42 of 102
Devices IP
Siemens
Under Server, enter the IP address of the PC on which the license server for optiClient 130 is installed. For a local installation of the license server (as in the illustrated example), enter the local IP address or the address of the local host. If the license server is installed on the network, enter its IP address on the network.
BR0038
17/09/2009
Page 43 of 102
Siemens
Devices IP
Only the function keys F2 up to F11 of the PC can be used!
BR0038
17/09/2009
Page 44 of 102
Devices IP
Siemens
3.3
Generating of the optiClient 130 V5.0 in the HiPath 4000 V2.0
1.
Define the number of STMIHFA2 boards: ADD-DIMSU:TYPE=SYSTEM,STMIHFA2=xx;
2.
Define the number of optiClients: CHANGE-ZAND:TYPE=CIT,APIMAX=xxx; ADD-DIMSU:TYPE=APPLICAT,WSPROT=xxx; (the same value xxx is to set in both AMOs!)
3.
Add the STMI2 board: ADD-BCSU:MTYPE=PER,LTG=1,LTU=2,SLOT=25,PARTNO=Q2316-x/Q2316-x10, FCTID=3; ADD-HFAB:MTYPE=STMIHFA2,LTU=2,SLOT=25,SMODE=NORMAL, IPADDR=1.40.31.70,NETMASK=255.255.255.0,DEFRT=1.40.31.254;
4.
Add the optiClient 7375 with TAPI: ADD-SBCSU:STNO=7375,OPT=OPTI,CONN=IP2,PEN=1-2-25-0, DVCFIG=OPTIIP&API,COS1=33,COS2=30,LCOSV1=9,LCOSV2=1,LCOSD1=9, LCOSD2=1,DPLN=0,ITR=0,COSX=0,SPDI=30,REP=1,STD=101,SECR=NO, INS=YES,HEADSET=NO,HSKEY=NORMAL,TEXTSEL=ENGLISH, CALLOG=TRIES,APICLASS=TSX,IPPASSW=xxxxxxxx,IPCODEC=G711PREF;
For using the HiPath 4000 Headset, the parameter HEADSET= WITHIND is to be set. If a user password is set in the HiPath-Provider settings, this password must be set in the parameter IPPASSW.
5.
Activate the authorization for Direct Media Connection (DMC) for the subscriber: CHANGE-SDAT:STNO=7375,TYPE=ATTRIBUT,AATTR=DMCALLWD;
BR0038
17/09/2009
Page 45 of 102
3.4
Siemens
BR0038
Using the right mouse key in the main bar, the following functions can be selected:
Short description of the user interface of the optiClients 130 V5.0
17/09/2009
It is not possible to make basic changes in the Setting-Menu, like extension number, Gatekeeper, Audio settings etc. Do you want to make such changes, the Setting-Menu has to be activated during the program start.
Devices IP
Page 46 of 102
BR0038
Devices IP
Using the function button, the extended key pads (additional 8 resp. 13 function key pad, and the add on modules, if configured in the HiPath 4000), the callog and the internal phone book are shown. Furthermore the design of the Client (with easyCom communication circuit) can be controlled.
17/09/2009
Page 47 of 102
Siemens
Siemens
BR0038
Extended key pads. The add on modules can be fade in or fade out with the arrows.
17/09/2009
Devices IP
Page 48 of 102
BR0038
Devices IP
Key descriptions can be changed individually (use the right mouse key on the desired key). If the phone type optiPoint 420 is selected, this function can not be used.
17/09/2009
Page 49 of 102
Siemens
Siemens
BR0038
Complete design with easyCom and an incoming call.
17/09/2009
Devices IP
Page 50 of 102
Devices IP
Siemens
optiPocket V1.0
In this document only the installation in the HiPath 4000 V2.0, installation of the Pocket PDAs and its settings are described. The configuration of the WLAN-Router is not part in this documentation.
4.1
Feature description
The optiPocket software offers a mobile business telephony interface for high-end handhelds (PDA). This provides secure access to voice and data in a LAN/WLAN environment (hotspots and company campus, for example). As soon as you activate optiPocket, all incoming calls are automatically diverted to your PDA, and you have simple telephone facilities. You enjoy online access to your data and Microsoft Outlook, or you can dial a number from the Corporate Directory - just as conveniently as if you were in the office. The optiPocket software can be used on almost all PDAs running under Microsoft Pocket PC 2003. The Voice-over-IP application uses a secure VPN solution for call set-up, and supports the CorNet IP features in a WLAN environment. On large company campuses, WLAN-Access-Points extend the range of the PDAs. Here, a HiPath WLAN server enables realtime "Roaming", so that handover to the next WLAN Access Point takes place without interrupting the flow of the conversation, even if the user is moving quickly around the site.
BR0038
17/09/2009
Page 51 of 102
Siemens
Devices IP
4.2
Usage
HiPath 4000
HG3530V2
IP Network
WLAN Access Point 64530

xxxxxxxxxxx WEP-Key: SSID: e.g.: WLAN Authentification: shared
IP-Address: Netmask: Default-GW:
1.50.50.203 255.255.255.0 1.50.50.254
BR0038
17/09/2009
Page 52 of 102
Devices IP
Siemens
5
5.1
W-LAN
optiPoint WL2 professional / S
The optiPoint WL2 professional/ professional Sis capability characteristics equipped with a colored background-lit display and simple access to various. The Devices possess additional applications like an extensive directory, language choice and an access to local enterprise directories.

Interfaces: WLAN, USB Environment: WLAN- and IP-Infrastructure and over HiPath and/or SIP-based HiPath independent communication systems orders. Standards: WLAN, 802.11b (11 Mbit/s), 802.11g (54Mbit/s), CorNet IP, SIP G.711 (a-law und -law) G.729ab (G.729a with VAD Voice Activity Detection) G.723 , G.722 Advanced Echo Cancellation (AEC) ToS, DiffServ, 802.1q , 802.11e (WMM-Subset) 802.11g (Fall-Back to 802.11b) Frequency: 2,4 - 2,497 GHz Number of channel: 13 (ETSI) or 11 (Nordamerika) SSID WEP (64, 128 Bit) , WPA Telephone can be protected with PIN VPN-Client Authentifizierung (Login/Password)
BR0038
17/09/2009
Page 53 of 102
Siemens
BR0038
17/09/2009
Page 54 of 102
Devices IP
Siemens
6
6.1
OpenStage IP
General Information
The OpenStage IP telephones are members of a completely new generation of end devices that round out the existing end device portfolio. The OpenStage IP product family contains four variants. The OpenStage can only be used with a HiPath 4000 V4.0.
6.2
OpenStage 20
OpenStage 20 is a universal solution for efficient and professional telephony. Each subsequent model contains expanded functionalities. Properties: Tiltable graphical display with 2 lines, 205 x 41 pixel No backlit Monochrome display with 2 lines 24 characters No visual call alert Fixed function keys (push buttons) 7 keys with 5 red LEDs (no LED for release and redial) Volume adjustment via +/- keys No headset jack External power supply unit Integrated 10/100 MBit/s Ethernet switch Gigabit Ethernet variant optional Possible color in iceblue and lava
BR0038
17/09/2009
Page 55 of 102
Siemens
Devices IP
6.3
OpenStage 40
With its ability to be customized for various workplace environments OpenStage 40 T is recommended to be used as office phone, e.g. for desk sharers, people working in teams or call center staff. Properties: Tiltable graphical display with 6 lines, 240 x 126 pixel Backlit Monochrome display 5,1 inch (diagonal) Visual call alert with red LEDs Fixed function keys (push buttons) 8 keys with 6 red LEDs (no LED for release and redial) Programmable touch/sensor keys 6 (the shift key enables programming on 2nd level for name keys) Volume adjustment via +/- keys Headset jack for corded (121 TR9-5) and cordless (121 TR9-5*) headset External power supply unit Integrated 10/100 MBit/s Ethernet switch Gigabit Ethernet variant optional Possible color in iceblue and lava
BR0038
17/09/2009
Page 56 of 102
Devices IP
Siemens
6.4
OpenStage 60
Offers top notch functionality and innovations with a maximum of usability combined with a clear intuitive and sleek design. Its functionality and personalization options make this phone the first choice for boss-/secretary environments and people interacting with other devices, like mobile phones or PDAs. Properties: Tiltable graphical display with 320 x 240 pixel (QVGA), TFT backlit Color display 5,7 inch (diagonal) with 16-bit color depth, 65.000 colors Visual call alert with blue LEDs Fixed function keys (push buttons) 6 keys with 6 blue LEDs (no LED for release) Programmable touch/sensor keys 8 (the shift key enables programming on 2nd level for name keys), 8 blue LEDs (functionality of the programmable keys similar to the optiPoint) Volume adjustment via touchslider with blue/white LEDs Headset jack for corded (121 TR9-5) and cordless (121 TR9-5*) headset External power supply unit Integrated 10/100 MBit/s Ethernet switch Gigabit Ethernet variant optional HTML browser / XML interface Bluetooth 2.0, USB Possible color in iceblue and lava
BR0038
17/09/2009
Page 57 of 102
Siemens
Devices IP
6.5
OpenStage 80
Premium features, materials and components turn this device into an extraordinary user experience. The best in class LCD display and open interfaces for easy synchronization with other devices, like PDA and mobile phone are specially designed with the needs of the top level manager and executive in mind. Properties: Tiltable graphical display with 640 x 480 pixel (VGA), TFT backlit Color display 6,4 inch (diagonal) with 16-bit color depth, 65.000 colors Visual call alert with blue LEDs Fixed function keys (push buttons) 6 keys with 6 blue LEDs (no LED for release) Programmable touch/sensor keys 9 (the shift key enables programming on 2nd level for name keys), 9 blue LEDs (functionality of the programmable keys similar to the optiPoint) Volume adjustment via touchslider with blue/white LEDs Headset jack for corded (121 TR9-5) and cordless (121 TR9-5*) headset External power supply unit Integrated 10/100 MBit/s Ethernet switch Gigabit Ethernet variant optional HTML browser / XML interface Bluetooth 2.0, USB Possible color aluminium
BR0038
17/09/2009
Page 58 of 102
Devices IP
Siemens
6.6
Key Modules
The maximum number of key modules is 2. A busy lamp field and key modules can not be combined. Even if only one key module is connected, it requires an external power supply because the two large displays (in the end device and key module) have a higher power consumption than the optiPoint and cannot be supplied by the UP0/E interface.
BR0038
17/09/2009
Page 59 of 102
Siemens
Devices IP
6.7
Key assignment
OpenStage telephones have fixed keys. For this reason, the correct standard key layouts must be assigned. The variable keys start from key 9 onwards.
Shift key
A Shift key can also be configured on OpenStage terminals (previously this was only possible on key modules). This is achieved with the AMO TAPRO or via the Service menu on the terminal. When the SHIFT key is pressed on an optiPoint key module, the same action is performed on all other key modules. In other words, the SHIFT level is also activated on the second and fourth key modules. This is not the case on OpenStage telephones and key modules. In this case, the SHIFT level is only activated on the telephone/key module on which the SHIFT key was pressed.
Tapro CHANGE-TAPRO:STNO=<station number>,KYxx=SHIFT;
xx must be greater than 08 since the first 8 keys are fixed. Only key 9 onwards can be freely assigned!
Separate key standard for an OpenStage 40: CHANGE-TAPRO:SNU=122,DIGTYP=OPENST40,TD09=xx,,,,,,INFO="OPENSTAGE 40";
BR0038
17/09/2009
Page 60 of 102
Devices IP
Siemens
7
7.1
OpenStage Manager
General
OpenStage Manager is a comprehensive tool for your telephone. The main function of OpenStage Manager is to act as an interface betweenyour telephone and your PC for convenient PC-based phonebookadministration. OpenStage Manager also allows you to synchronize contacts from Microsoft Outlook and Lotus Notes with your telephone contacts. In addition, you can use OpenStage Manager to configure various telephone settings conveniently via your PC. These settings include programming keys and adjusting graphic display or audio settings.
7.2

Installation
Installation of Microsoft.NET2.0 Installalation of OpenStage Manager Software Telephone registration via the service program of OpenStage Manager (ServiceLayer) see next figure
BR0038
17/09/2009
Page 61 of 102
Siemens
Devices IP
7.3
Log on
Your phone must be logged on to the OpenStage Manager ServiceLayer utility before it can establish a connection with the OpenStage Manager installed on your PC.
These settings are necessary
The Password must also be set by the phone (in the User settings).
If the connection is established between the phone and the OpenStage device an icon in the windows system tray is visible.
BR0038
17/09/2009
Page 62 of 102
Devices IP
Siemens
7.4
Start Program
You can access OpenStage Manager via the following path:
Start --> Programs --> Siemens --> OpenStage Manager

When starting the OpenStage Manager for the first time all data saved on the telephone will be copied to the computer. Depending on the pack of data, this can take several minutes.
7.5
Phone Book Maintenance
With the help of the Phone Book Maintenance you can create, edit and delete contacts.
BR0038
17/09/2009
Page 63 of 102
Siemens
Devices IP
You can manage images and assign them to individual contacts in the Phonebook Editor using the Images tab. You may save a maximum of 20 images, the following data format are supported:

.png (Portable Network Graphics) .jpg (JPEG)
First you have to download the pictures to the OpenStage Phone Manager, then you can allocate a image to a contact.
BR0038
17/09/2009
Page 64 of 102
Devices IP
Siemens
BR0038
17/09/2009
Page 65 of 102
Siemens
Devices IP
7.6
Search functionality
By using the search function of the Phonebook-Editor you can search the contact table for certain terms and definitions. You can restrict the search process on only one column (e. g. First Name) or expand it on several columns.
7.7
Synchronization
Automatic synchronization allows you to synchronize data in your phonebook with Outlook contact data (or Lotus Notes contact data). There are three options for doing this:

OpenStage Phone --> Outlook contacts OpenStage Phone <-- Outlook contacts Both ways
BR0038
17/09/2009
Page 66 of 102
Devices IP
Siemens
7.8
Screensaver
You can upload pictures in the screensaver area.
BR0038
17/09/2009
Page 67 of 102
Siemens
BR0038
17/09/2009
Page 68 of 102
Devices IP
Siemens
AC-WIN IP
The comfort operators position AC-Win IP V1.0 of the Realtime-IP-Systems HiPath 4000 V2.0 / V3.0 is a Windows-application being based on a PC. According to size of the system and the company structure one or several operator positions can be fit out. The up to 60 different service features AC-Win are by means of a Windows surface easy help. They facilitate for example of external or internal calls. The arriving calls know in two (AC-Win 2Q IP V1.0) or twelve queues (AC-Win MQ IP 1.0) to be represented.
8.1
Systemconcept
The activation of the comfort operators position AC-Win IP V1.0 occurs about IP at a HG3530 V2.0 in a system HiPath 4000 V2.0 / HiPath 4000 V3.0. At the PC the USB-Device (Handset and Headset) are connected that. At the PC it concerns a commercial execution, hoever the tested Fujitsu-Siemens-PCs are recommended. The offered functionalty is provided exclusvely by means of software.
BR0038
17/09/2009
Page 69 of 102
Siemens
Devices IP
8.2
a)
Variants from ACWIN IP

ACWIN 2Q IP
BR0038
17/09/2009
Page 70 of 102
Devices IP
Siemens
b)
ACWIN MQ IP
BR0038
17/09/2009
Page 71 of 102
Siemens
Devices IP
8.2.1
Hardware
For AC-Win IP V1.0 (AC-Win 2Q IP V1.0 and AC-Win MQ IP V1.0) Windows XP Professional with Service Pack 2 Pentium 4 with at least 1,7 GHz RAM: at least 512 Mbyte Harddisk: at least 256 Mbyte free non removable disk capacity At least 19"- Screen (1240 x 1024 ) CD-ROM- or DVD-Device Sound-Card Multimedia-Keyboard For AC-Win IP approved USB-Hand-/Headset
Supported Communication systems HiPath 4000 V2.0 HiPath 4000 V3.0 HiPath 4000 V4.0
Applications which can be used with AC-Win IP V1.0 DS-Win V3.0 BLF-Win V3.0 ASC V5.0
8.2.2
Initial operation
After the installation, or with Start->Programs->AC-Win [2Q|MQ] IP->AC-Win IP Configuration the configuration interface is displayed. The first window displayed is the "Main connections" window. There the IP address of the Common Gateway (Registration Address), the extension number (Admin number), the used headset (Mixer and Wave settings) and the license server must be filled out. Optional the address of the DLS can be set. The default language is english. This can be changed.
BR0038
17/09/2009
Page 72 of 102
Devices IP
Siemens
8.2.3
Entering general data
After starting the AC-Win IP configuration, the following dialog window is displayed:
Registration address: the IP address of the HiPath 4000 IP gateway (STMI2 module/Common Gateway). Admin number: AC-Win number which is used with the Admin user ID. Admin password/Retype admin password: If a password is assigned when setting up the AC-Win number in the HiPath 4000, enter it here. Otherwise, an arbitrary password can be assigned for use when logging on to AC-Win. Note: The password is case-sensitive. Mixer, Microphone, Speaker: Specify the audio I/O device (headset) to be used with AC-Win here. Note: Before these values are specified, the headset must be connected. Only then can the corresponding I/O devices be selected. If these values are not set, AC-Win will not operate. After filling out these parameters Save settings must be done.
BR0038
17/09/2009
Page 73 of 102
Siemens
Devices IP
8.2.4
Licensing
Server IP Address: Enter the IP address of the computer on which the CLA (Common License Agent) application is installed. After doing the settings concerning the license a restart of the PC is necessary!
BR0038
17/09/2009
Page 74 of 102
Devices IP
Siemens
8.2.5
DLS/DLC Configuration
DLS deployment enabled: specifies whether or not the central configuration is to be used. Connection: Specify here whether all DLS services are to be used, or only the encryption of voice packets. Server (DLS): Address: IP address or DNS name of the DLS. Port: port number of the DLS
Client (DLC): Address: AC-Win IP address to be used for communication with the DLS. Port: port number of the DLS connection on the AC-Win PC. Network card: MAC address at which the data will be stored on the DLS.
BR0038
17/09/2009
Page 75 of 102
Siemens
Devices IP
8.2.6
General settings
Program type: shows which attendant console (2Q/MQ) is installed. Software version: software version of the installed AC-Win application. Selected language: from this list, you can select one of the AC-Win languages.
BR0038
17/09/2009
Page 76 of 102
Devices IP
Siemens
8.2.7
Voice Recording
Use this dialog to make settings for digital voice recording at the attendant console.
Voice recording active: This setting activates voice recording in AC-Win. Note: In the HiPath 4000, use AMO ZAND to set the parameter TAPALOW =YES in the ATND branch. Automatic tape recording: If this setting is activated, voice recording starts automatically (without pressing the record button) after a call is taken. Voice recording directory: This is the directory where the digital speech files (.wav files) are stored. Note: We recommend that you use a local directory. With network drives, delays can result. Voice recording beeps: When this setting is active, a beep is played at intervals while a conversation is being recorded. Beep wave file location: here you can select the *.wav file with the voice recording beeps.
BR0038
17/09/2009
Page 77 of 102
Siemens
Devices IP
8.2.8
Settings in the AC for automatic voice recording
Select the menu Extra in the AC-WIN settings.
The "Automatic tape recording" function can be started on the left side.
BR0038
17/09/2009
Page 78 of 102
Devices IP
Siemens
8.2.9
Deinstallation of the AC-Win IP
An installed AC-Win IP V1.0 variant can be deinstalled at anytime. Therefor open the folder "system" (Start -> settings) and start the application "software". Select the setting AC-Win 2Q IP resp. AC-Win MQ IP and select "change/remove"- button.
BR0038
17/09/2009
Page 79 of 102
Siemens
BR0038
17/09/2009
Page 80 of 102
Devices IP
Siemens
9
9.1 9.1.1
License Management
Basic Information Introduction
Whether you are a customer or a sales partner, License Management provides you with a userfriendly and efficient license management tool for all your licensing needs. With License Management, you can license a range of different products, for example communication systems, workpoint clients, applications, etc. You can apply for a license via the Internet. The relevant products are activated immediately. If you are a sales partner, you can also purchase multiple license packages and manage these using License Management.
License Management consists of the following components: Central License Server/License Server (CLS) Customer License Client/License Client (CLC) Customer License Agent/License agent (CLA) Customer License Management/License Management (CLM)
CLC, CLA and CLM can be operated together on the product PC
Additional PC Admin - PC
CLS
Internet
Product (for HW) or PC (for SW)
(CLM) CLA
CLM
CLC
LAN
BR0038
17/09/2009
Page 81 of 102
Siemens
Devices IP
Central License Server/License Server (CLS) License files are requested via the License Server (CLS) and are created there by a license generator. License applications are made over the Internet. Customers are allowed a grace period, for example, 30 days (depending on the product) after product purchase or installation to apply for a license. The product functions properly during the grace period but ceases to work when this period runs out. The license server also manages the license agents and the product licenses allocated to the license agents. Each customer or sales partner has an individual license account (=user) on the CLS. These accounts can be administered at the CLS over a separate Web-based interface. Available and previously purchased licenses can be displayed. Licenses can also be transferred from one license agent to another. A hierarchical structure of accounts is employed here so that every user who sells software licenses to sub-contractors can create users, assign licenses, and manage user authorizations on behalf of these sub-contractors. This is supported by the use of different user levels.
Customer License Client/License Client (CLC) The CLC represents the interface between the product and the CLA. The product can use the CLC to query CLA and find out if a valid license is available. The CLC is a key component of the product to be licensed and is contained in the products installation.
Customer License Agent/License agent (CLA) The License Agent (CLA) is a software application that is installed either on the PC with the product(s) or on an administration PC that is connected to the product PC in a common network. This application automatically starts running in the background as soon as it is installed on the PC. The License Agent (CLA) saves the acquired product licenses and makes them available to the products. The product queries the CLC to find out if the license entered is valid or not. The CLA checks the request and releases the software if the license is valid. While there is only one CLA per PC, there can be several CLAs in a network, distributed over several PCs A CLA can manage licenses for an individual product or several products.
Customer License Management/License Management (CLM) The CLM can be installed on the product, on the administration PC together with the CLA or on any PC in the network. The CLM accesses the license agent(s) over the network. The CLM features an interface to the CLS and the CLA that can be used to manage various License Management processes, such as activating a license or displaying the current license distribution for the individual products. The CLM is a Web application. The CLM is connected to the CLS over the Internet.
BR0038
17/09/2009
Page 82 of 102
Devices IP
Siemens
You can use License Management to activate licenses for a product, retrieve licenses for a product or license agent, manage license agents, etrieve products and product features for a license agent, create group members for a feature and bring together in groups, retrieve networked computers that use License Management, display configuration and error logs.
BR0038
17/09/2009
Page 83 of 102
Siemens
Devices IP
9.2
Customer License Agent
The License Agent manages all license files required by the Central License Server (CLS) and should therefore be installed in every network containing licensed products. In the case of standalone configurations, the License Agent is installed on all PCs containing products that require licensing. The license files can be requested either via the License Management tool (CLM, Customer License Management) or directly via the License Server. The License Agent checks the validity of the license files and enables the licensed products.
Software requirements Windows NT 4.0 Workstation or Server (Service Pack 6 or later) Windows 2000 Professional or Server (valid for all Service Packs) Windows XP Home or Professional (valid for all Service Packs) Windows 2003 Server Administrator DNS must be correctly configured so that the response times for name resolution (computer name for IP address) are as short as possible. The SMNP service must be activated. The TLS protocol must be available. The IP address 224.0.23.23 must not be assigned in the existing network because it is needed by the software (for multicast). The IP address must be changed if it was already assigned in the current network. A firewall should be configured so that the multicast address and all ports are accepted. Rejections, enquiries or separate authentication block the License Agent.
Operating systems
Installation rights DNS (Dynamic Name Solution) SNMP TLS protocol Free IP address 224.0.23.23
Additional software
BR0038
17/09/2009
Page 84 of 102
Devices IP
Siemens
Hardware requirements At least Pentium II 400 MHz, if possible Pentium 4. At least 128 MB, if possible 256 MB or more. Approximately 5 MB of free disk space on the installation drive for the software. The size of the CLA database depends on the products installed and licensed. Disk space is also required for the trace and log files: - Default size for trace files: 100 MB, max. 200 MB. - Log files are limited for the most part by the variable length of the time period - their absolute size is potentially unlimited. LAN card.
Processor power Memory Disk space
Additional hardware
9.2.1
Installation of the CLA
The License Management software consists of two components: License Management and License Agent. The two components share the same setup routine. This routine allows you to install License Management, License Agent, or both components together. The CLA service starts up automatically as soon as the License Agent is installed.
>
You can also install the two components, License Management (CLM) and License Agent (CLA), separately (the common setup routine is not used). The setup program for this (setup.exe) is located in the corresponding subdirectory "...\Clm" or"...\Cla". This program allows you to change the installation path and the default values of the configuration data during the installation.
>
If License Management and License Agent are to be installed on the same PC, you need to make certain that License Management is either installed together with the license agents or, in the case of a standalone installation, before the license agents. In this case, the login to the license agent is not reuqired in License Management. In all other cases, you need to log on to the license agent in License Management.
BR0038
17/09/2009
Page 85 of 102
Siemens
Devices IP
Important hint for installing License Management and License Agent on different PCs
If you install a License Agent on a PC that does not have License Management installed, you can only administer this License Agent with License Management via the network. License Management must be installed on another PC in the network for this. To avoid unauthorized use, access to a License Agent via the network is protected. When you install the License Agent, you are therefore prompted to specify a user as the administrator of the License Agent. At a later stage, this user must log on to the License Agent via License Management using his/ her user name and password. The following dialog then appears during the installation:
Default User
This option configures the user who is logged on to the PC and who is performing the installation as the administrator for the license agent. When logging on to the license agent, the user must enter their user name and password.
BR0038
17/09/2009
Page 86 of 102
Devices IP
Siemens
New User
This option allows you to set up another, already existing user as the administrator for the License Agent. The user name must, however, be known on the PC or in the domain of the PC. In order to prevent mistakes and misunderstandings (such as when the same user identification is used on the local computer and in a domain), it is important that you also enter the domain name with the user name ("user name@domain name"). This is imperative if users want to identify themselves over a domain. When logging on via License Management, this user name, including the domain name and password, must also be entered. The domain name must be entered during logon if a local ID is used on the PC with License Agent installed. You do not need the user password while you are installing the License Agent. To log on to the the license agent from License Management at a later stage, the user name and password must be entered in full.
BR0038
17/09/2009
Page 87 of 102
Siemens
Devices IP
9.2.1.1 1.
Standalone Setup
Insert the setup CD in your CD/DVD drive. If the setup routine does not start automatically (AutoRun function disabled), use Windows Explorer to open the setup.exe file from your CD/DVD drive. The InstallShield Wizard starts and guides you through the setup routine. Confirm with the Continue button. Select whether you want to install only the License Agent, only License Management, or both components.
2. 3.
Click Continue. 4. Start the License Agent installation by clicking Start. The necessary files are copied to the installation directory specified. During the installation, the following configuration data are automatically set to the values given in the table:
BR0038
17/09/2009
Page 88 of 102
Devices IP
Siemens
Configuration data Service Port Number License error log size (days) License audit trail size (days)
default value 61740 180 180
If you clicked the Dialog to change the default settings option, the setup program displays an additional configuration dialog where you can change the configuration data during setup. You can also modify the configuration data after installation by selecting Start | Settings | Control Panel | Software | Change or Remove Programs | License Agent. The setup program for the License Agent displays the progress of the installation and ends automatically following installation.
BR0038
17/09/2009
Page 89 of 102
Siemens
Devices IP
9.3
License Management (CLM)
The License Management is a browser-supported application that can be used to request licenses from the central license server (CLS) and activate them on a customer license agent (CLA). A further function of the License Management is the management of the licenses on the license agents. In a network, the License Management only needs to be installed once. For the other users in the network, access to the License Management can be set up in the License Management later on.
Software requirements XP/2000/2003 Administrator Java Runtime Environment, JRE 1.4 for Windows Tomcat Servlet Engine (contained on the installation CD)

Operating systems Rights Additional software
Browser
Internet Explorer as of version 5.5 Service Pack 2 Netscape Navigator as of version 7.1 Cookies and JavaScript must be enabled. If you are using a proxy server, you should deactivate the "Bypass proxy server for local addresses" option under the LAN settings in the browser.
Hardware requirements Min. Pentium II 400 MHz, preferably Pentium 4 256 MB or more Approx. 50 MB free hard disk memory on the installation drive (incl. JRE and Tomcat Servlet Engine) LAN card
PC performance RAM Hard disk memory Additional hardware
BR0038
17/09/2009
Page 90 of 102
Devices IP
Siemens
9.3.1
Installation of the CLM
The License Management software consists of two components: License Management and License Agent. The two components share the same setup routine. This routine allows you to install License Management, License Agent, or both components together.
>
You can also install the two components, License Management (CLM) and License Agent (CLA), separately (the common setup routine is not used). The setup program for this (setup.exe) is located in the corresponding subdirectory "...\Clm" or"...\Cla". This program allows you to change the installation path and the default values of the configuration data during the installation.
>
If License Management and License Agent are to be installed on the same PC, you need to make certain that License Management is either installed together with the license agents or, in the case of a standalone installation, before the license agents. In this case, the login to the license agent is not reuqired in License Management. In all other cases, you need to log on to the license agent in License Management.
>
If your system supports a firewall (automatically the case for Windows XP SP 2 or later), then you must take into consideration the required ports/applications for your network. If browsers in your network are to access an installed CLM, then you need to activate the appropriate HTTP or HTTPS ports (default settings 8818 and 8819). If License Management is to access license agents in the network, then the license agent service port (default setting 61740) on the license agent PCs must be activated. In order for License Management to be able to search for license agents in the network, multicast must be activated on port 23232 for IP address 224.0.23.23.
BR0038
17/09/2009
Page 91 of 102
Siemens
Devices IP
9.3.1.1 1.
Standalone Setup
Insert the setup CD in your CD/DVD drive. If the setup routine does not start automatically (AutoRun function disabled), use Windows Explorer to open the setup.exe file from your CD/DVD drive. The InstallShield Wizard starts and guides you through the setup routine. Confirm with the Continue button. Select whether you want to install only License Management, only the License Agent, or both components. If you click the Dialog to change the default settings option, the setup program will offer you an additional dialog during setup where you can change the default values of the configuration data. You can also change these default values after the successful installation.
2. 3.
4.
Start the License Management installation by clicking Start. The necessary files are copied to the installation directory specified. During the installation, the following configuration data are automatically set to the values shown below: HTTP port: 8819
BR0038
17/09/2009
Page 92 of 102
Devices IP
Siemens
HTTPS port: 8818 Shutdown port: 8820
The HTTP port and the HTTPS port are needed for setting up the connection from the Web browser to License Management. In the case of a connection over the HTTPS protocol, all data is transmitted in encrypted format. The shutdown port is needed to exit the license management service (Tomcat Servlet Engine) on the local license management system. 5. The shared installation routine shows you the currently installed versions of the License Management and the license agents (if installed). Click on the Finish button.
BR0038
17/09/2009
Page 93 of 102
Siemens
Devices IP
9.4 9.4.1
Working with License Management License Management Contents Page
The License Management contents page appears as soon as License Management is started up. You do not have to log on to License Management to see this page. However, access to some license agents can be restricted by the allocation of user names and password. If this is the case, you must log on to the license agent with License Management. This contents page provides you with an overview of the License Management functions on the left in the navigation area. Important initial actions and information are provided in the work area. Content of the License Manager
BR0038
17/09/2009
Page 94 of 102
Devices IP
Siemens
9.4.2
License Management Setup
You have clicked the License Management setup button under Actions for License Management on the contents page. The general License Management settings are shown here. The settings provided vary depending on whether "expert mode" has been set.
BR0038
17/09/2009
Page 95 of 102
Siemens
Devices IP
9.4.3
Activating Licenses
You have clicked the Activate license button under Actions for License Management on the contents page. Various ways of activating a license are displayed. However, you must have done the following before you can activate a license: 1. 2. The software has been ordered or purchased from the dealer. You have received an appropriate license authorization code. The license authorization code identifies you as the legal user of the software. You can now activate the software via the License Management. You cannot use License Management to order licenses. You can only activate the purchased software for your PC.
>
The options available to you depend on whether or not "expert mode" has been enabled . The additional options that are only available in expert mode are indicated as such in the following. You can select from a choice of three (in expert mode, four) preset licensing types: Create license key and install on license agent (online activation). The license is generated immediately by the license server and installed on a license agent. Create license key and save locally (online connection required) The license is generated immediately by the license server and can be installed on a license agent later on.
BR0038
17/09/2009
Page 96 of 102
Devices IP
Siemens
Install local license key on license agent (offline activation) The license is already activated and you have a license file or a license string. You can now install this license file or license string on a license agent. Retrieve/restore a previously generated license (online) (only in expert mode)
Select this item if you have just installed new systems, for instance, and would now like to restore existing license files.
Selecting the licensing type 1. 2. Select one of the licensing types listed above. Click Continue.
9.4.4
Products
You have selected Products in the navigation area. A list of products for all available license agents is now displayed in the work area. If a product is installed on several license agents, it will also be displayed several times in the product list. If you click the + symbol in front of the menu item Products in the navigation area, a list of all products in the product list is displayed.
Further information/actions for a product If you click the icon in the Details column for a product in the product list, detailed information and additional actions are displayed for this product. Product licenses for this product If you click a product in the product list or in the navigation area, an overview is displayedof all licenses for that product. All products for a license agent If you click a license agent in the list of products, an overview is displayed of all products installed on that license agent.
BR0038
17/09/2009
Page 97 of 102
Siemens
Devices IP
9.4.5
License Agents
You have selected the License agents menu item in the navigation area. A list of all license agents found is now displayed in the work area. The menu item License agents also opens in the navigation area. All license agents with the connection status connected are displayed here. If you use a firewall in your system (e.g. Windows XP SP 2 or later), the service port must be activated in the firewall of the license agents system so that License Management can request data from a license agent. The default setting for a license agent is port 61740. If License Management is to find license agents in a network, access to the multicast port 23232 for IP address 224.0.24.24 must also be taken into account.
Further information/actions for a license agent Detailed information and additional actions are displayed for a license agent if you click the icon in the Details column for a license agent in the list of license agents. All products for a license agent If you click a license agent in the list of license agents or in the navigation area, an overviewof all products installed on this license agent appears.
BR0038
17/09/2009
Page 98 of 102
Devices IP
Siemens
9.4.6
Computer
You have selected the Computer menu item in the navigation area. A list of all network computers whose installed products use CLA via the CLC is displayed in the work area. The products installed on the computer must be activated for a computer to be displayed in the list. If there are several products installed and activated on the same PC, this PC appears several times in the list, with a separate line for each activated product.
Computer features If you directly click a computer in the list of computers or in the navigation area, a feature overview of all products installed on the selected computer is displayed. If several products are activated on the same PC, there is a separate entry in the list of PCs for each product. The top entry for the corresponding PC contains the link to the features that all products on this computer are using. Computer feature details Detailed information on the computer features is displayed.
BR0038
17/09/2009
Page 99 of 102
Siemens
Devices IP
9.4.7
Logs
You have selected the Logs menu item in the navigation area (only possible in expert mode). You can display the different logs for the selected license agents here.
License audit trail Changes in the license configurations are documented here. License error log Incomplete license requests and abandoned connections are listed here.
BR0038
17/09/2009
Page 100 of 102
Abbreviations
Siemens
Abbreviations
This table shows some important abbreviations. Abbreviation A AMO C CLA CLC CLM CLS D DLC DLS DNS H HTTP HTTPS I IP J JRE L LAN LCD LED P PDA Q QVGA Definition
Administration and Maintenance Operation
Customer License Agent Customer License Client Customer License Management Central License Server
Deployment Client Deployment and Licence Service Dynamic Name Solution
HyperText Transfer Protocol HyperText Transfer Protocol Secure
Internet Port
Java Runtime Environment
Local Area Network Liquid Crystal Display Light Emitting Diode
Personal Digital Assistant
Quarter Video Graphics Array
BR0038
17/09/2009
Page 101 of 102
Siemens
Abbreviations
S SNMP T TFT TLS U USB
Simple Network Management Protocol
Thin-Film Transistor Transport Layer Security
Universal Serial Bus
BR0038
17/09/2009
Page 102 of 102
Siemens
Informativo Tccnico
BR0049
2009 Siemens Enterprise Communications - APT-LAM
90
Informativo Tcnico
Siemens Enterprise Communications Technology Support Center So Paulo
Como configurar ramal IP HFA.

Documento Categoria Principal Verso Autor: : IT 2008 Hipath 4000 V4.0 DOC 0016 Configurar Ramal IP HFA.Doc : HiPath 4000 : Hipath 4000 V4.0 : 1.0 : Thiago Roldo Pinheiro Costa
vlido o documento visualizado via ISI em https://sistemas.siemens.com.br/isi/

As informaes contidas neste documento so de propriedade de Siemens Enterprise Communication. No podero ser usadas, reproduzidas ou divulgadas a terceiros salvo quando especificamente permitido por escrito pelo proprietrio. O recebedor destas informaes, ao det-las e us-las, concorda em proteger as mesmas contra perda, roubo ou uso indevido. Esse documento cpia no controlada quando impresso no todo ou em partes.
Histrico de Verses
Verso 1.0 Data 3/05/08 Descrio Criao do documento Autor Thiago Roldo P. Costa
Autores
Autor Thiago Roldo P. Costa Departamento SEN CS RS TSC Fone/Fax 11 38172655 e-mail thiago.roldao@siemens.com Captulos Integral
Referncias
Ttulo do Documento e-Doku Verso Autor Siemens AG Link http://apps.gdms.com:8081/techdoc/search _en.htm Emitido em 2008-05-3
Produtos envolvidos
Modelo HiPath 4000 Verso V4 R1.6.0 Comentrio
SEM CS RS TSC Technology Support Center So Paulo
Pgina 2/9
Contedo
1 2 3 4 Introduo............................................................................................................................... 4 Como utilizar esse documento ................................................................................................... 4 Objetivo .................................................................................................................................. 4 Itens bsicos............................................................................................................................ 5 4.1. 4.2. 4.3. 4.4. 5 6 Software para os terminais IP............................................................................................ 5 Mdulo HG3500 STMI4. ................................................................................................. 5 Terminais IP suportados. .................................................................................................. 5 Polticas de QoS ............................................................................................................... 5
Topologia. ............................................................................................................................... 6 Configura o Hipath 4000. .......................................................................................................... 7 6.1. 6.2. 6.3. 6.4. Configurar o AMO BFDAT. ................................................................................................. 7 Configurar o AMO BCSU. ................................................................................................... 7 Configurar o AMO CGWB................................................................................................... 8 Criar o ramal no Hipath 4000 ............................................................................................ 9
Lista de Figuras
Figura 9: Topologia. ....................................................................................................................... 6
Lista de Tabelas
Tabela 1: Endereos IP. .................................................................................................................. 6
Pgina 3/9
1 Introduo
Esse informativo tcnico visa orientar nossos colaboradores e parceiro, quanto ao procedimento para configurar um ramal IP com o protocolo HFA no HiPath 4000 V4.0.
2 Como utilizar esse documento

Sugerimos ao profissional fazer uma primeira leitura deste documente para assimilar cada etapa e posteriormente iniciar as configuraes sugeridas em cada mdulo. Leia cada captulo e respeite a seqncia aqui exposta, pois, um mdulo que esteja no captulo de nmero 1000 depender da configurao do mdulo que est no captulo de nmero 999. Caso tenha dificuldades em proceder com as configuraes aqui expostas, solicite ajuda atravs de um chamado (0800149002), pois, dependendo do erro a melhor soluo ser refazer todas as configuraes desde o inicio.
3 Objetivo
Configurar o mdulo STMI no HiPath 4000. Definir o endereo IP do mdulo STMI. Configurar dois ramais com o amo SBCSU.
Boa sorte e bom trabalho!!!!!!!!!!!!!
Pgina 4/9
4 Itens bsicos.
4.1. Software para os terminais IP.
O primeiro passo atualizar os terminais IP com a ltima verso de software que esteja disponvel no site do SWS ou no site do ISI. Caso tenha dificuldades, solicite o software diretamente ao suporte, atravs de um chamado.
4.2. Mdulo HG3500 STMI4.

Na verso Hipath 4000 V4.0, somente o mdulo STMI4 est liberado para uso em clientes. O antigo mdulo STMI2 poder ser utilizado nos casos em que o mdulo STMI4 no poder ser fornecido de imediato e para que o cliente no fique esperanto, o mdulo STMI2 poder ser fornecido.
4.3. Terminais IP suportados.

Toda a linha OptiPoint 410. Toda a linha OptiPoint 420. Toda a linha OpenStage. OpitClient 130.
4.4. Polticas de QoS

O cliente dever aplicar polticas de QoS nos equipamentos da rede (Roteadores, Switches) para garantir que o trafego de voz e sinalizao, proveniente dos aparelhos IP e do mdulo HG3500 tenham prioridade em relao ao trafego de dados. Caso as polticas de QoS no sejam aplicadas, no ser possvel garantir que a soluo VoIP ir funcionar corretamente, pois, poder ocorrer falhas na comunicao, como: Rudo, Chiados, Echo, Picotes (Chamada chega faltando partes), Atrasos, etc...
Importante: Qualquer duvida quanto aos itens acima, contate o suporte ou o gerente responsvel pelo projeto.
Pgina 5/9
5 Topologia.
Para os testes, ser utilizado uma central telefnica modelo Hipath 4000 V4.0 com uma bandeja de periferia (LTU 1), dois telefones IP modelo OptiPoint 420 e um Switch do fabricante Enterasys. Foi definido um seguimento de rede classe C para ser utilizado nos testes, sendo um (01) endereo IP para a interface Customer LAN do Hipath 4000, um (01) endereo IP para o mdulo HG 3500 e dois (02) endereos IP para os terminais OptiPoint 420. Veja na figura abaixo, como ficar a nossa topologia e a seguir, a lista com os endereos IP utilizados.
Figura 1: Topologia.
Rede Mascara Gateway Hipath 4000 (Customer LAN) HG3500 Ramal 9000 Ramal 9001 Tabela 1: Endereos IP.
172.24.1.0 255.255.255.0 (/24) 172.24.1.254 172.24.1.90 172.24.1.92 172.24.1.105 172.24.1.106
Pgina 6/9
6 Configurar o Hipath 4000.
6.1. Configurar o AMO BFDAT.

O BFDAT no HiPath 4000 V4.0 ser utilizado para dizer ao mdulo STMI4, quanto canais sero utilizados para a funo HFA. Lembrando que no Hipath 4000 V4.0, um mesmo mdulo STMI4 pode ser utilizado para prover ramais HFA, SIP, IP Trunking H323 ou SIP, etc Criar o bloco de funes ADD-BFDAT:FCTBLK=8,FUNCTION=HG3530,BRDBCHL=BCHAN120; HG3530 = HFA / BCHAN60 = STMI Q2324-X500 / BCHAN120 = STMI Q2324-X510 Configurar a quantidade de canais CHANGE-BFDAT:CONFIG=CONT,FCTBLK=8,FUNCTION=HG3530,LINECNT=240,BCHLCNT=120; Posso criar at 240 ramais em uma placa. Somente 120 ramais falam ao mesmo tempo. Ativar o BFDAT CHANGE-BFDAT:CONFIG=OK,FCTBLK=8,ANSW=YES; Visualizar como ficou configurado. DISPLAY-BFDAT:FCTBLK=8;
6.2. Configurar o AMO BCSU.

Utilize o AMO BCSU para configurar o mdulo STMI4 no sistema operacional do Hipath 4000, defina o parmetro FCTID com o valor 1 (um), o parmetro FCTBLK com o mesmo nmero do BFDAT que foi criado anteriormente e o parmetro IPADDR com o endereo IP do mdulo. Criar o mdulo STMI no HiPath 4000. ADD-BCSU:TYPE=IPGW,LTG=1,LTU=1,SLOT=85,PARTNO=Q2324X510,FCTID=1,FCTBLK=8,IPADDR=172.24.1.92; Importante: O mdulo STMI 4 demora aproximadamente 20 minutos para entrar em servio. Aps o mdulo entrar em servio. CHANGE-FUNSU:PIT=FLASH,PARTNO="Q2324-X510",FCTID=1,ACTION=RESET; Observao: Este comando faz com que o modulo STMI carregue mais rpido da prxima vez, pois, j possui o loadware. SEM CS RS TSC Technology Support Center So Paulo Pgina 7/9
6.3. Configurar o AMO CGWB.

Este AMO substitui o antigo AMO STMI e utilizado para definir dados complementares relacionado configurao de rede e trafego de voz. Configurar os dados de rede. ADD-CGWB:LTU=1,SLOT=85,SMODE=NORMAL,IPADR=172.24.1.92,NETMASK=255.255.255.0; CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=GLOBIF,DEFRT=172.24.1.254; Configurar o range de portas UDP. CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,UDPPRTLO=29100,UDPPRTHI=29339; Configurara o QoS LAYER 3 - VOZ (EF) Sinalizao (EF31). CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,TOSPL="184",TOSSIGNL="104"; Ativar DTMF via RFC2833 CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,RFCFMOIP=YES,RFCDTMF=YES,REDRFCTN=YES; Configurar lista de prioridade dos CODEC's CODEC VAD G.723 G.729 NO G.729A NO G.729B YES G.729AB YES Tabela 2: CODEC RTP SIZE 60 e 90 30, 40, 50, 60, 70 e 80 30, 40, 50, 60, 70 AND 80 30, 40, 50, 60, 70 AND 80 30, 40, 50, 60, 70 AND 80
30, 20, 20, 20, 20,
CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO1,CODEC=G729AB,VAD=YES,RTP="20"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO2,CODEC=G729A,VAD=NO,RTP="20"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO3,CODEC=G711A,VAD=NO,RTP="30"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO4,CODEC=G711U,VAD=NO,RTP="30"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO5,CODEC=G723,VAD=NO,RTP="30"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO6,CODEC=NONE,VAD=NO,RTP="20"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO7,CODEC=NONE,VAD=NO,RTP="20"; Ativar as configuraes RESTART-BSSU:ADDRTYPE=PEN,LTG=1,LTU=1,SLOT=85;
Pgina 8/9
6.4. Criar o ramal no Hipath 4000

Parmetros centrais ADD-DIMSU:TYPE=APPLICAT,WSPROT=600; CHA-ZAND:TYPE=CIT,APIMAX=600; CHANGE-ZAND:TYPE=OPTLOAD; Ramal 9000 ADD-SBCSU:STNO=9000,OPT=OPTI,CONN=IP2,PEN=1-1-850,DVCFIG=OPTIIP&API,COS1=1,COS2=1,LCOSV1=10,LCOSV2=10,LCOSD1=10,LCOSD2=10,APICLASS= TSX; Ramal 9001 ADD-SBCSU:STNO=9001,OPT=OPTI,CONN=IP2,PEN=1-1-851,DVCFIG=OPTIIP&API,COS1=1,COS2=1,LCOSV1=10,LCOSV2=10,LCOSD1=10,LCOSD2=10,APICLASS= TSX;
FIM
Pgina 9/9
Informativo Tcnico
Como configurar ramal SIP.

Documento Categoria Principal Verso Autor: : IT 2008 Hipath 4000 V4.0 DOC 0017 Configurar Ramal SIP.Doc : HiPath 4000 : Hipath 4000 V4.0 : 1.0 : Thiago Roldo Pinheiro Costa

Histrico de Verses
Autores
Referncias
Produtos envolvidos
Pgina 2/9
Contedo
1 2 3 4 Introduo............................................................................................................................... 4 Como utilizar esse documento ................................................................................................... 4 Objetivo .................................................................................................................................. 4 Itens bsicos............................................................................................................................ 5 4.1. 4.2. 4.3. 4.4. 5 6 Software para os terminais IP............................................................................................ 5 Mdulo HG3500 STMI4. ................................................................................................. 5 Terminais IP suportados. .................................................................................................. 5 Polticas de QoS ............................................................................................................... 5
Topologia. ............................................................................................................................... 6 Configurar o Hipath 4000. ......................................................................................................... 7 6.1. 6.2. 6.3. 6.4. Configurar o AMO BFDAT. ................................................................................................. 7 Configurar o AMO BCSU. ................................................................................................... 7 Configurar o AMO CGWB................................................................................................... 8 Criar o ramal no Hipath 4000 ............................................................................................ 9
Lista de Figuras
Figura 1: Topologia. ....................................................................................................................... 6
Lista de Tabelas
Tabela 1: Endereos IP. .................................................................................................................. 6 Tabela 2: CODEC............................................................................................................................ 8
Pgina 3/9
1 Introduo
Esse informativo tcnico visa orientar nossos colaboradores e parceiro, quanto ao procedimento para configurar um ramal IP com o protocolo SIP no HiPath 4000 V4.0.

3 Objetivo
Configurar o mdulo STMI no HiPath 4000. Definir o endereo IP do mdulo STMI. Configurar dois ramais com o amo SBCSU.
Pgina 4/9
4 Itens bsicos.
O primeiro passo atualizar os terminais IP com a ltima verso de software que esteja disponvel no site do SWS ou no site do ISI. Caso tenha dificuldades, solicite o software diretamente ao suporte, atravs de um chamado.
4.2. Mdulo HG3500 STMI4.

Na verso Hipath 4000 V4.0, somente o mdulo STMI4 est liberado para uso em clientes. O antigo mdulo STMI2 poder ser utilizado nos casos em que o mdulo STMI4 no poder ser fornecido de imediato e para que o cliente no fique esperanto, o mdulo STMI2 poder ser fornecido.
4.3. Terminais IP suportados.

Toda a linha OptiPoint 410. Toda a linha OptiPoint 420. Toda a linha OpenStage. OpitClient 130.
4.4. Polticas de QoS

O cliente dever aplicar polticas de QoS nos equipamentos da rede (Roteadores, Switches) para garantir que o trafego de voz e sinalizao, proveniente dos aparelhos IP e do mdulo HG3500 tenham prioridade em relao ao trafego de dados. Caso as polticas de QoS no sejam aplicadas, no ser possvel garantir que a soluo VoIP ir funcionar corretamente, pois, poder ocorrer falhas na comunicao, como: Rudo, Chiados, Echo, Picotes (Chamada chega faltando partes), Atrasos, etc...
Importante: Qualquer duvida quanto aos itens acima, contate o suporte ou o gerente responsvel pelo projeto.
Pgina 5/9
5 Topologia.
Para os testes, ser utilizado uma central telefnica modelo Hipath 4000 V4.0 com uma bandeja de periferia (LTU 1), dois telefones IP modelo OptiPoint 420 e um Switch do fabricante Enterasys. Foi definido um seguimento de rede classe C para ser utilizado nos testes, sendo um (01) endereo IP para a interface Customer LAN do Hipath 4000, um (01) endereo IP para o mdulo HG 3500 e dois (02) endereos IP para os terminais OptiPoint 420. Veja na figura abaixo, como ficar a nossa topologia e a seguir, a lista com os endereos IP utilizados.
Figura 1: Topologia.
Rede Mascara Gateway Hipath 4000 (Customer LAN) HG3500 Ramal 9000 Ramal 9001 Tabela 1: Endereos IP.
172.24.1.0 255.255.255.0 (/24) 172.24.1.254 172.24.1.90 172.24.1.92 172.24.1.105 172.24.1.106
Pgina 6/9
6 Configurar o Hipath 4000.
6.1. Configurar o AMO BFDAT.

O BFDAT no HiPath 4000 V4.0 ser utilizado para dizer ao mdulo STMI4, quanto canais sero utilizados para a funo SIP. Lembrando que no Hipath 4000 V4.0, um mesmo mdulo STMI4 pode ser utilizado para prover ramais HFA, SIP, IP Trunking H323 ou SIP, etc Criar o bloco de funes ADD-BFDAT:FCTBLK=10,FUNCTION=SIP,BRDBCHL=BCHAN120; BCHAN60 = STMI Q2324-X500 / BCHAN120 = STMI Q2324-X510 Configurar a quantidade de canais CHANGE-BFDAT:CONFIG=CONT,FCTBLK=10,FUNCTION=SIP,LINECNT=240,BCHLCNT=120; Posso criar at 240 ramais em uma placa. Somente 120 ramais falam ao mesmo tempo. Ativar o BFDAT CHANGE-BFDAT:CONFIG=OK,FCTBLK=10,ANSW=YES; Visualizar como ficou configurado. DISPLAY-BFDAT:FCTBLK=10;
6.2. Configurar o AMO BCSU.

Utilize o AMO BCSU para configurar o mdulo STMI4 no sistema operacional do Hipath 4000, defina o parmetro FCTID com o valor 1 (um), o parmetro FCTBLK com o mesmo nmero do BFDAT que foi criado anteriormente e o parmetro IPADDR com o endereo IP do mdulo. Criar o mdulo STMI no HiPath 4000. ADD-BCSU:TYPE=IPGW,LTG=1,LTU=1,SLOT=85,PARTNO=Q2324X510,FCTID=1,FCTBLK=10,IPADDR=172.24.1.92; Importante: O mdulo STMI 4 demora aproximadamente 20 minutos para entrar em servio. Aps o mdulo entrar em servio. CHANGE-FUNSU:PIT=FLASH,PARTNO="Q2324-X510",FCTID=1,ACTION=RESET; Observao: Este comando faz com que o modulo STMI carregue mais rpido da prxima vez, pois, j possui o loadware.
Pgina 7/9
6.3. Configurar o AMO CGWB.

Este AMO substitui o antigo AMO STMI e utilizado para definir dados complementares relacionado configurao de rede e trafego de voz. Configurar os dados de rede. ADD-CGWB:LTU=1,SLOT=85,SMODE=NORMAL,IPADR=172.24.1.92,NETMASK=255.255.255.0; CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=GLOBIF,DEFRT=172.24.1.254; Configurar o range de portas UDP. CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,UDPPRTLO=29100,UDPPRTHI=29339; Configurara o QoS LAYER 3 - VOZ (EF) Sinalizao (EF31). CHANGE-CGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,TOSPL="184",TOSSIGNL="104"; Ativar DTMF via RFC2833 CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,RFCFMOIP=YES,RFCDTMF=YES,REDRFCTN=YES; Configurar lista de prioridade dos CODEC's CODEC VAD G.723 G.729 NO G.729A NO G.729B YES G.729AB YES Tabela 2: CODEC RTP SIZE 30, 20, 20, 20, 20, 60 e 90 30, 40, 50, 30, 40, 50, 30, 40, 50, 30, 40, 50, 60, 60, 60, 60, 70 70 70 70 e 80 AND 80 AND 80 AND 80
CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO1,CODEC=G729AB,VAD=YES,RTP="20"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO2,CODEC=G729A,VAD=NO,RTP="20"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO3,CODEC=G711A,VAD=NO,RTP="30"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO4,CODEC=G711U,VAD=NO,RTP="30"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO5,CODEC=G723,VAD=NO,RTP="30"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO6,CODEC=NONE,VAD=NO,RTP="20"; CHANGECGWB:MTYPE=CGW,LTU=1,SLOT=85,TYPE=ASC,PRIO=PRIO7,CODEC=NONE,VAD=NO,RTP="20"; Ativar as configuraes RESTART-BSSU:ADDRTYPE=PEN,LTG=1,LTU=1,SLOT=85;
Pgina 8/9
6.4. Criar o ramal no Hipath 4000

Parmetros centrais ADD-DIMSU:TYPE=APPLICAT,WSPROT=600; CHA-ZAND:TYPE=CIT,APIMAX=600; CHANGE-ZAND:TYPE=OPTLOAD; Ramal 9000 ADD-SBCSU:STNO=9000,OPT=FPP,CONN=SIP,PEN=1-1-850,DVCFIG=S0PP,COS1=90,COS2=90,LCOSV1=1,LCOSV2=1,LCOSD1=1,LCOSD2=1,PROT=SBDSS1,INS= Y,OPTIDX=10; Ramal 9001 ADD-SBCSU:STNO=9001,OPT=FPP,CONN=SIP,PEN=1-1-851,DVCFIG=S0PP,COS1=90,COS2=90,LCOSV1=1,LCOSV2=1,LCOSD1=1,LCOSD2=1,PROT=SBDSS1,INS= Y,OPTIDX=10;
FIM
Pgina 9/9
Informativo Tcnico
Como atualizar aparelhos IP OptiPoint 4X0 via WEB

Documento Categoria Principal Verso Autor: : IT 2008 Hipath 4000 V4.0 DOC 0004 Atualizar Aparelhos IP Optipoint 4X0 Via WEB.Doc : HiPath 4000 : Hipath 4000 V4.0 : 1.0 : Thiago Roldo Pinheiro Costa

Histrico de Verses
Autores
Referncias
Produtos envolvidos
Pgina 2/16
Contedo
1 2 3 4 Introduo............................................................................................................................... 4 Como utilizar esse documento ................................................................................................... 4 Objetivo .................................................................................................................................. 4 Itens bsicos............................................................................................................................ 5 4.1. 4.2. 4.3. Software para os terminais IP............................................................................................ 5 Instalar o servidor de FTP 3CDaemon.............................................................................. 8 Fazer o upgrade via interface WEB................................................................................... 13
Lista de Figuras
Figura 1: Tela inicial do SWS. .......................................................................................................... 5 Figura 2: Como localizar a verso .................................................................................................... 6 Figura 3: Iniciar o download da verso............................................................................................. 6 Figura 4: Descompactar o arquivo com a verso. .............................................................................. 7 Figura 5: Instalar o servidor de FTP ................................................................................................. 8 Figura 6: Tela inicial do servidor de FTP ......................................................................................... 11 Figura 7: Configurando o servidor de FTP ....................................................................................... 12 Figura 8: Topologia da rede .......................................................................................................... 13 Figura 9: Confirmar o certificado.................................................................................................... 13 Figura 10: Tela Inicial / Senha....................................................................................................... 14 Figura 11: Tela Inicial File Transfer ............................................................................................. 15 Figura 6: Tela Inicial File Transfer ............................................................................................... 16
Pgina 3/16
1 Introduo
Esse informativo tcnico visa orientar nossos colaboradores e parceiro, quanto ao procedimento para atualizar a verso dos telefones IP modelo optipoint 4X0 que esteja utilizando o software HFA atravs da interface WEB.

3 Objetivo
Instalar e configurar o servidor de FTP. Baixar a verso de software via SWS. Atualizar os terminais via WEB.
Pgina 4/16
4 Itens bsicos.
O primeiro passo atualizar os terminais IP com a ltima verso de software que esteja disponvel no site do SWS ou no site do ISI. Caso tenha dificuldades, solicite o software diretamente ao suporte, atravs de um chamado. Acesse o site do SWS http://sws.siemens.com.br:8080/swsdownload e informe os dados de usurio, senha e pais de origem. Este acesso restrito aos colaboradores Siemens, porm, o software tambm pode ser baixado atravs do site do ISI ou solicitado ao suporte.
Figura 1: Tela inicial do SWS.
Pgina 5/16
Aps acessar o site do SWS, utilize o filtro de busca para indicar exatamente a verso de software correspondente ao modelo de aparelho que deseja utilizar, em nosso exemplo, ser utilizado a verso de software V5 R5.2.0 para terminais IP modelo OptiPoint 420 Advance.
Figura 2: Como localizar a verso Na prxima janela, selecione a verso do arquivo e inicie o download, no se esquea de salvar esse arquivo em um diretrio conhecido.
Figura 3: Iniciar o download da verso.
Pgina 6/16
Localize o diretrio onde o arquivo foi salvo e descompacte-o. O mais importante neste processo saber a onde o arquivo 420adv_HFA_V5_R5_2_0.app est armazenado. Em nosso exemplo o arquivo ficou armazenado no diretrio: C:\Documents and Settings\op7908\Desktop\OptiPoint 420\420adv_HFA_V5_R5_2_0
Figura 4: Descompactar o arquivo com a verso.
Pgina 7/16
4.2. Instalar o servidor de FTP 3CDaemon.

Em nosso exemplo ser utilizado o servidor de FTP 3CDaemon que pode ser baixado facilmente da internet. Descompacte o arquivo e execute o arquivo SETUP.EXE, siga o procedimento de instalao como mostra as figuras a seguir.
Figura 5: Instalar o servidor de FTP
Pgina 8/16
Pgina 9/16
Pgina 10/16
O servidor de FTP foi instalado com sucesso, agora vamos configurar um usurio com as permisses de acesso e definir o diretrio onde o arquivo poder ser encontrado. Execute o servidor de FTP atravs do menu: iniciar \ Programas \ 3CDaemon \ 3CDaemon. Na tela inicial, selecione a aba FTP Server e click na opo Configure FTP Server.
Figura 6: Tela inicial do servidor de FTP
Pgina 11/16
Vamos agora configurar o servidor de FTP e informar os dados do usurio. Defina o Profile Name dls e configure o password hipath*4000 atravs do boto Set/Change users password. Na opo User Directory, selecione diretrio a onde o arquivo com a verso est armazenado, em nosso exemplo o arquivo est no diretrio: C:\Documents and Settings\op7908\Desktop\OptiPoint 420\420adv_HFA_V5_R5_2_0 Marque todas as opes na caixa This user can: e por ultimo, click no boto Save Profile para salvar a nossa configurao.
Figura 7: Configurando o servidor de FTP Click no boto Apply para salvar o novo usurio dls e no boto OK para sair. A partir deste momento o FTP est ativo de ser utilizado quando formos fazer o upgrade de verso do software do aparelho.
Pgina 12/16
4.3. Fazer o upgrade via interface WEB

At o momento, foi configurado o servidor de FTP no notebook e baixamos o novo software para o telefone IP via SWS. A partir de agora, ser necessrio colocar o telefone IP e o notebook na rede para nos permitir configurar o telefone IP via WEB e tambm, permitir ao telefone IP acessar o servidor de FTP para baixar a nova verso de software. Veja na figura abaixo a topologia utilizada nos testes.
Figura 8: Topologia da rede A partir do momento em que a topologia da rede estiver montada, prossiga com os passos para configurar o upgrade atravs da interface WEB do aparelho. Acesse o aparelho atravs do seu Brower, em nosso exemplo, foi utilizado o Internet Explorer Version: 6.0.2900.2180.xpsp_sp2_qfe.070227-2300. Utilize os links https://172.24.1.117/ ou http://172.24.1.117:8085
Figura 9: Confirmar o certificado
Pgina 13/16
Na tela inicia, acesse o menu administrator e informe a senha do telefone IP, normalmente a senha 123456.
Figura 10: Tela Inicial / Senha
Pgina 14/16
Aps se autenticar no aparelho IP, acesse o menu File Transfer para configurar o acesso ao servidor FTP e informar o nome do arquivo com a verso.
Figura 11: Tela Inicial File Transfer
Pgina 15/16
Na tela do File Transfer, informe o endereo IP do servidor de FTP, o nome de usurio e senha, o nome do arquivo com a nova verso e por ultimo, selecione a opo Download application, para que o terminal inicie a download da verso no servidor FTP.
Figura 12: Tela Inicial File Transfer Click no boto Submit para que o terminal IP inicie o processo de upgrade. O terminal IP ir reiniciar e durante o processo de boot, se conectar ao servidor FTP para baixa a nova verso. Esse processo demora uns 2 minutos e no final, o terminal IP voltara em servio j com a nova verso e sem perder as configuraes antigas.
FIM
Pgina 16/16
Key System
5. Key System
Key System
s
1 Viso Geral de Acesso Multilinhas
A facilidade de funcionalidade de teclas integrada est disponvel a partir do Hicom 300E V3.0. As funes da facilidade so similares a sistemas de equipes empresariais ou sistemas telefnicos com teclas para multilinhas.
Primria
Mx. 28 linhas por terminal Mx. 40 terminais por linha 12 layouts de teclas pr-configurados, dos quais 4 so reservados para terminais ACD Funciona em todos os telefones optiset E Exibio do estado da linha por LED No permitido com a facilidade de chefe/secretria. Keyset
Linha 1 Linha 2 Linha 3 Linha 4 Linha 5 Linha 6 Linha 7
Keyset
Primria
Keyset Disponvel a partir do Hicom 300 E V3.0 A facilidade pode ser usada apenas localmente Liberada por cdigo Quantidade das centrais KS limitada por DIMSU Keyset
Linha 1 Linha 2 Linha 3 Linha 4 Linha 5 Linha 6 Linha 7
Central KS
3 configuraes para equipes Sistema de telefone com teclado Sistemas de telefone com teclas de multilinhas
s
1.1 Descrio da facilidade
O acesso de multilinhas est disponvel a partir do Hicom 300E V3.0. Ele compreende novas facilidades e afeta muitas facilidades existentes. O acesso de multilinhas somente pode ser ativado por Optisets ou OptiPoints que tenham sido especialmente configurados com o uso de AMO KCSU. Os telefones configurados para este fim sero mencionados neste documento como Keysets. O acesso de multilinhas permite a ocupao de uma linha primria (linha inicial) e at 28 linhas secundrias a partir de um Keyset para chamadas de entrada e sada. Cada linha corresponde a um nmero de ramal. Um linha pode ser atribuda a 40 telefones diferentes. Para cada linha existe uma tecla de linha com LED no terminal. O LED sinaliza o estado da linha. Livre: o LED est apagado, ocupado: o LED est aceso, em chamada: o LED pisca rapidamente, chamada retida: o LED pisca devagar.
1.1.1
Descrio resumida das facilidades do Keyset
Cada Keyset possui uma linha inicial ou primria, que acessada atravs do nmero da ramal principal. Esta linha pode ser atribuda a outros Keysets como linha secundria. Uma linha fantasma atribuda a outros terminais como uma linha secundria e no atribuda a nenhum terminal como uma linha primria. Uma linha fantasma configurada como um Keyset desabilitado (log off), ou seja, uma vez que a linha fantasma tenha sido configurada (SBCSU:ins=signoff), ela deve ser adicionada como uma linha primria no KCSU para habilitar a sua adio como uma linha secundria em outros Keysets. Chamada: cada linha pode ser configurada como uma linha com, ou sem, toque de chamada (KCSU, parmetro RIOP). O toque de chamada ativado assim que uma chamada sinalizada em uma das linhas para qual o toque de chamada foi configurado para este ramal em particular. O LED da tecla da linha pisca. Vrias chamadas simultneas so sinalizadas por ordem de chegada. Toques de chamada diferentes podem ser configurados para todas as teclas de linha para as quais o tom de chamada foi programado. Se o tom de chamada no pode ser injetado porque o Keyset est ocupado, ativado um tom de alerta (se configurado, KCSU, parmetro BUSYRING). Seleo de linha: est disponvel a seleo automtica e manual de linhas. Com a seleo automtica de linhas, uma das linhas configuradas automaticamente ocupada assim que o usurio retira o monofone do gancho para iniciar ou atender uma chamada. Diversas opes podem ser configuradas para definir as preferncias de conexes de entrada e sada. Dependendo da opo configurada, ocupada para conexes de sada a linha primria (KCSU, ORLNPF=PRIME), a ltima linha usada (KCSU, ORLNPF=LAST), qualquer linha livre (KCSU; ORLNPF=IDLE) ou nenhuma linha (KCSU; ORLNPF=NONE -- > necessria a seleo manual).
s
Dependendo da opo configurada, selecionada, para conexes de entrada, uma linha chamadora (KCSU; TMLNPF=RING), qualquer linha de entrada (primeiro, as linhas chamadoras so consultadas, seguidas por linhas no configuradas para o tom de chamada, com base em FIFO. KCSU; TMLNPF=ALER) ou nenhuma linha (KCSU; TMLNPF=NONE). Chamadas para a linha primria podem ser configuradas para atendimento com prioridade, independente do momento de sua chegada (KCSU; TMLNPF=RINGP ou ALERP).
Com o uso da seleo de linha manual, um usurio pode desviar uma seleo automtica de linha ao pressionar uma tecla de linha antes de colocar o monofone no gancho. Podem ser configuradas as opes: modo de tecla nica, modo de pr-seleo ou seleo da linha subseqente. No modo de tecla nica (KCSU; SGLBMOD= YES), a linha selecionada ao se pressionar uma tecla de linha. O Keyset passa para o modo de viva-voz com o monofone no gancho. No modo de pr-seleo (KCSU; SGLBMOD=NO), a tecla de linha pressionada quando no estado livre e a linha necessria pr-selecionada assim que o usurio retirar o monofone do gancho, pressionar as teclas do alto-falante, nome, DSS ou rediscagem, ou introduzir dgitos de discagem. A pr-seleo vlida por 10 segundos (configurvel por AMO). Se foi configurada uma linha com tom de chamada, o chamador exibido quando a tecla de linha pressionada at que o tempo de pr-seleo expire. Depois da pr-seleo, a chamada de entrada pode ser recebida na linha pr-selecionada ao se retirar o monofone do gancho. Seleo de linha subseqente. O usurio levanta o monofone e pressiona uma tecla de linha para subseqentemente escolher ou mudar a linha a ser usada.
Classes de servio: as chamadas podem ser iniciadas com o uso de qualquer linha em qualquer terminal. Dependendo da configurao do sistema, usada a linha COS ou a COS do Keyset (AMO ZAND, parmetro COSLNBAS). Existem, entretanto, facilidades que sempre usam a COS atribuda ao terminal usado ou linha usada. Mostrador: durante a chamada, e depois do atendimento de uma chamada, o mostrador da parte chamada normalmente exibe <nmero do ramal e nome > da linha primria do ramal chamador ou a linha usada, dependendo da configurao do sistema (AMO ZAND, parmetro DISLNBAS). A tecla tambm afeta a apresentao da parte chamadora depois que o lado B atende. Reteno geral e exclusiva. A reteno permite que um usurio retenha uma conexo e coloque o monofone no gancho ou para iniciar ou para atender uma chamada em uma linha diferente sem perder a conexo retida. Apenas chamadas a dois podem ser retidas. A reteno em chamadas de consulta no possvel. Se for configurada a reteno geral, a conexo retida pode ser capturada por todos os Keysets onde a linha respectiva foi atribuda (o LED pisca lentamente nestes ramais) ao se pressionar a tecla da linha.
s
Se for configurada a reteno exclusiva, a conexo retida apenas pode ser terminada pelo Keyset que colocou a linha em reteno (o LED pisca lentamente apenas neste ramal) ao se pressionar a tecla da linha. Existem 3 maneiras de colocar uma linha em reteno: pressionando-se as teclas Hold ou Exclusive hold ou atravs de seleo a partir do menu de dilogo. Mudar para outra linha ou pressionar a tecla da linha atual tambm coloca uma linha em reteno (ou a libera, dependendo da configurao do sistema, AMO ZAND, parmetro HDNOACKY). Se for selecionada a reteno exclusiva, o Keyset que colocou a linha em reteno recebe uma rechamada com prioridade se a chamada retida no for finalizada depois do vencimento da temporizao. Se for configurada a reteno geral, sinalizada uma rechamada em todos os Keysets onde a linha est atribuda.
Consulta mltipla. Um usurio com diversas linhas atribudas pode iniciar uma conferncia a trs pressionando a tecla da linha que ele deseja intercalar. Uma conferncia a trs estabelecida se uma chamada a dois (A-B) estiver ativa na linha selecionada e uma chamada particular no foi iniciada. O tom de conferncia injetado para as trs partes (A, B, C) se a consulta mltipla for ativada. Apenas um ramal pode entrar em uma conexo existente. Chamada particular. Esta facilidade protege o usurio Keyset contra consulta mltipla por outro usurio Keyset. So possveis chamadas particulares automticas e manuais. A chamada particular automtica (configurada com o uso de AMO KCSU, APRIVAT=YES) ativada assim que uma chamada iniciada. Keysets sem a facilidade de chamada particular automtica so protegidos em uma conexo ao ativar a facilidade manualmente. Exibio da linha ocupada. exibida a linha atualmente ocupada ou selecionada pelo Keyset, assim que o monofone levantado. A exibio automtica da linha atualmente ocupada ativada assim que a linha selecionada. A linha atualmente usada pode ser consultada manualmente em diversos estados atravs da tecla de funo I-USE ou da seleo do menu Show seized line? no menu de servio. Livre O usurio pode desativar o tom de chamada no Keyset ao pressionar a tecla Idle ou selecionar Switch off ringing? no menu de servio. O LED de tecla de funo correspondente est aceso se esta facilidade est ativada. As chamadas de entrada so sinalizadas apenas visualmente atravs do LED piscando na(s) tecla(s) de linha. Todas as chamadas de entrada so sinalizadas no seu destino, porm apenas visualmente (LED, mostrador). Elas podem ser atendidas normalmente. Alguns tipos de chamadas cancelam a opo Idle, p.ex. chamadas exclusivas, ACD. Broadcast possvel programar para que um grupo de keysets recebam mensagens de voz simultaneamente. Para isto, necessrio uma liberao da facilidade para o terminal originador no AMO SDAT (BROADCAST). Os ramais que recebero as chamadas devero ter a linha broadcast com sinalizao sonora, alm de necessitar liberao para chamadas de voz (VC). Verificao da tecla do usurio. exibida a identificao do usurio conectado, de acordo com a linha pr-selecionada.
s
1.1.2 Efeitos em outras facilidades
A funcionalidade da central KS tambm afeta outras facilidades. So elas:
Auxlios discagem, tais como discagem abreviada, nome, teclas DSS ou de rediscagem de nmero so especficos por ramal. Eles podem ser usados com qualquer linha atribuda a um Keyset. O LED da tecla DSS mostra o estado na linha de destino introduzida. Transferncia Temporria de Chamada: cada terminal pode transferir todas as linhas atribudas (isto feito com base na linha individual). O LED da tecla de transferncia sempre sinaliza o estado da linha primria do terminal respectivo. Linhas transferidas ou secundrias no so sinalizadas. No Perturbe: se a opo no perturbe estiver ativada para a linha, nenhum Keyset onde esta linha est atribuda recebe qualquer chamada. Ao invs de no perturbe, selecionar Idle para proteo contra chamadas de entrada nos Keysets. Rechamada: se um Keyset usa uma linha e introduz uma solicitao de rechamada, a linha primria apresentada como a fonte da rechamada. Assim que a rechamada seja possvel, a linha primria chamada exclusivamente. Depois da fonte da rechamada atender, o destino da rechamada chamada no-exclusivamente, ou seja, todos os Keysets onde esta linha est atribuda podem atender chamada. Caixa Postal. Podem ser deixadas introdues na caixa postal do Keyset onde a linha usada est atribuda como linha primria. A exibio da caixa postal e o incio de rechamadas so possveis apenas neste Keyset. A Chamada em Espera executada em linhas ocupadas. O mostrador do Keyset que est usando esta linha em particular mostra a mensagem apropriada e o LED de captura de chamada pisca. A chamada em espera automtica tambm executada no Keyset usando esta linha em particular, se a facilidade de chamada em espera estiver autorizada. A intercalao executada em linhas ocupadas. O Keyset que est usando esta linha em particular intercalado, a mensagem correspondente exibida e o LED de captura de chamada pisca. Telemensagem. Todas as linhas podem ser encaminhadas com fins de telemensagem e o usurio pode atender uma chamada de telemensagem em qualquer linha. A tecla de telemensagem sempre atribuda linha ocupada (paging). Grupo de Captura de Chamadas. As chamadas dentro de um grupo de captura de chamadas so apenas sinalizadas (mostrador, LED e tom de alerta) no Keyset onde a linha em particular est atribuda como linha primria. As chamadas sinalizadas neste Keyset podem ser capturadas usando qualquer linha atribuda. Chamada em grupo. A sinalizao paralela executada em ramais especialmente marcados dentro do grupo de captura de chamadas. Nos Keysets a chamada em grupo exclusiva, o que significa que a chamada no sinalizada em linhas secundrias e tambm no pode ser atendida por outros Keysets. Esta chamada exclusiva pode ser desativada usando-se Idle (livre).
A Captura Direta de Chamadas pode ser ativada atravs da ocupao de qualquer linha. Estacionamento de Chamadas. Um usurio pode transferir a outra parte para a fila de estacionamento do grupo de captura de chamadas onde a linha primria est atribuda, independente da linha que foi ocupada. As chamadas estacionadas podem ser capturadas por Keysets dentro do grupo de captura de chamadas pela ocupao de qualquer linha atribuda. Grupo de busca. De modo similar a terminais, linhas podem ser combinadas para formar grupos de busca. As chamadas no grupo de busca so sinalizadas em todos os Keysets onde a linha est atribuda. A tecla do grupo de busca sempre permanece atribuda linha primria do respectivo terminal. Chamada por voz. O terminal chamada comutado diretamente para o modo viva-voz, se a parte chamada no tiver ativado a opo Stop voice calling. No caso de Keysets, a chamada por voz executada no terminal onde a linha selecionada est atribuda como linha primria. Se este Keyset em particular estiver ocupado, sinalizada uma chamada normal. Timed reminder. Esta facilidade especfica por terminal. Ela sinalizada apenas no terminal do respectivo usurio, contanto que a facilidade de Transferncia Temporria de Chamada no tenha sido ativada. Uma chamada de servio de aviso agendado exclusiva. A comutao COS pode ser executada por qualquer linha atribuda e comuta entre COS1 e COS2 no terminal usado. Identificao (PIN manual / placa de ID). A ativao/desativao de PIN pode ser realizada atravs de qualquer linha atribuda no terminal usado. O PIN vlido apenas para ligaes de sada estabelecidas a partir deste terminal, independente de qual linha usada. So usados o COS (COS1) e os dados (p.ex. nome e nmero do ramal) do ramal para o qual o PIN est atribudo. O PIN no afeta outros Keysets que usam a linha de um terminal com PIN ativado. O registro de chamada atribudo linha primria. So introduzidas apenas chamadas de entrada para a linha primria. As chamadas de sada so introduzidas no registro da linha primria, independente da linha que foi realmente ocupada. O call log pode ser executado por terminal ou por linha. O grupo COM pode ser executado pelo keyset. A origem de chamada sempre baseada no dispositivo originador e no na linha. As chamadas destinadas via COMGRP so sinalizadas em linhas adjacentes.
s
1.1.3

Informaes de servio
A facilidade somente pode ser usada com optiset E. O optiset E deve ser configurado em uma placa SLMO / SLOP2 (ou deve ser configurado como desabilitado) Todos os Keysets onde uma linha atribuda devem estar localizados no mesmo PABX. No possvel o acesso de multilinha num mbito de rede. Relaes com outras facilidades: sistema de secretria A central KS e o sistema de secretria so mutuamente exclusivos. No possvel nem mesmo atualizar um ramal de secretria como um Keyset usando SBCSU AMO (SECR=YES). Autoset Relocate: O optiset E com a funcionalidade da central KS pode ser mudado usando-se Autoset Relocate. Os terminais optiset E (com ou sem as funes da central KS) podem efetuar seu registro na porta anterior. Para registrar um optiset E com as funes da central KS, suficiente uma ligao simples do optiset E que foi apropriadamente preparado.
No necessrio novo hardware. A facilidade no precisa ser liberada atravs de AMO FEASU. A quantidade mxima de Keysets configurados limitada pela capacidade de memria Flexama existente (AMO DIMSU). A funcionalidade da central KS pode ser usada em todos os pases.
s
1.1.4 Fluxograma da central KS
DIMSU USER KEYSYS
CTIME CP CTHLDREC
ZAND ALLDATA KEYSYSTEM DISPMODE; COSLNBAS DISLNBAS RCUTOFF HOLDACKY HDNOACKY
DTIM1 DIGITE CTPRESEL
ACTDA STN
TAPRO para Optiset STD 3 8 12 19 KEY KEY KEY KEY
WABE DAR HOLDKY EXHOLDKY PRIVKY IUSEKEY RCTOFFKY TRNSKY RLSKY TOGGLEKEY CONSKY CBKKY APRIV DPRIV
Ramal fantasma
SBCSU STD SECR INS 19&&31
SBCSU STD SECR INS 19&&31
NO YES
NO SIGNOFF
s
1
KCSU PRIM PRIMKEY RIOP ORLNPF TMLNPF SGLBMOD BUSYRING APRIVAT AICS OFFTYPE KCSU SEC KYNO STNOSEC RIOP AICS OFFTYPE
Linha prpria
Linha associada ou
Linha fantasma
s
1.1.5 Comandos AMO
Configurao de um Keyset: Configurar ou definir layout de teclas padro apropriado para Keysets (layouts de teclas padres com teclas de linhas): DIS-TAPRO:TYPE=STD,DIGTYP=OPTISET,STD= Alterar o layout de teclas padro existente, se no existirem teclas de LINHA: CHA-TAPRO:TYPE=STD,DIGTYP=OPTIT12,STD=26, KY01=LINE,KY02=LINE,KY03=LINE, KY04=IUSE,KY05=HOLD,KY06=EXCLHOLD, KY07=PRIVAT,...,KY12=RCUTOFF; Os novos layouts de teclas padres especficos para Keyset tm os possveis efeitos: (apenas em optisets E que foram reconfigurados para Keysets!!):
Funo da tecla LINE IUSE HOLD EXCLHOLD
Descrio Tecla de linha
Qtde. mx. por Keyset 29
Tecla para identificar a prpria linha usada entre diversas teclas de 1 linha ativas. Tecla para reter uma chamada. Qualquer outro Keyset pode capturar a chamada retida. 1
Tecla para reter uma chamada exclusivamente. Nenhum outro 1 Keyset, exceto o Keyset que colocou a chamada em reteno, pode capturar a chamada. Tecla para evitar que outros Keysets intercalem uma ligao (conferncia) ou removam Keysets intercalados da ligao. Tecla para ativar ou desativar o toque de chamada para todas as teclas de linhas. Tecla para verificar a identificao do chamador em certas linhas. 1 1 1
PRIVAT RCUTOFF PREVIEW
s
Configurar o optiset E com layout de teclas padro do Keyset: Se o optiset E est configurado, atribuir layout de teclas padro do Keyset: CHA-TAPRO:STNO=4711,STD=26; Se o optiset E ainda no foi configurado: ADD-SBCSU:STNO=4711,OPT=<OPTI/OPTIEXP>,DVCFIG=OPTISET,..., STD=26; Verificar a memria Flexama para o Keyset: DIS-DIMSU:TYPE=USER; Ampliar memria insuficiente: ADD-DIMSU:TYPE=USER,KEYSYS=<sufficient_size>; Configurar optisets como Keysets e atribuir linhas primrias: A primeira etapa atualizar todos os optisets para Keysets usando AMO KCSU (TYPE=PRIM). O prprio nmero do ramal (linha primria) deve ser atribudo a uma tecla de linha. Os parmetros usados tm o efeito a seguir:
Parmetro (TYPE=PRIM) STNO
Descrio Nmero de ramal do optiset a ser atualizado para um Keyset.
Valor padro STNO deve ser especificado Nmero de tecla da primeira tecla de LINHA livre
PRIMKEY
Nmero de tecla da linha primria: 1 - 12 (terminal 12 teclas) 13 - 28 (ADD_ON 1 - se configurada) 29 - 44 (ADD_ON 2 - se configurada) 45 - 60 (ADD_ON 3 - se configurada) 61 - 76 (ADD_ON 4 - se configurada)
RIOP
Opo de toque de chamada, ou seja, tipo de sinalizao de chamadas YES de entrada na linha primria: YES- por toque de chamada + LED + mostrador NO - apenas por LED (+ mostrador, dependendo da configurao TMLNPF) Preferncias para ligaes de sada: NONE - sem preferncias IDLE - qualquer linha livre (a linha primria preferencial) LAST - a ltima linha usada PRIME - linha primria PRIME
ORLNPF
s
Parmetro (TYPE=PRIM) TMLNPF Descrio Preferncias para ligaes de entrada: NONE - sem preferncias ALER - qualquer linha de entrada (sinalizao por toque de chamada ou LED) ALERP - como ALER, porm a linha primria preferencial RING - linha chamadora RINGP - como RING, porm a linha primria preferencial Valor padro RING
SGLBMOD
YES Modo de tecla nica: YES - pressionar uma tecla de linha no apenas seleciona, mas tambm ocupa a linha NO - pressionar uma tecla de linha apenas pr-seleciona a linha. A linha somente ocupada quando o monofone levantado. Sinalizao de uma segunda chamada de entrada (em uma linha configurada com RIOP=YES) se o terminal estiver em estado de chamada: ALERT - por LED + tom de alerta NORING - apenas por LED STAND - ring diferenciado Chamada particular automtica: YES - outros Keysets no podem intercalar a ligao (uma tecla PARTICULAR automaticamente ativada quando uma ligao estabelecida) NO - outros Keysets podem intercalar uma ligao (conferncia) (uma tecla PARTICULAR automaticamente desativada quando uma ligao estabelecida) Atendimento automtico na linha primria com o monofone: YES - chamadas de entrada so automaticamente atendidas NO - chamadas de entrada devem ser atendidas manualmente Tipo de bloqueio de ramal durante modificaes usando TYPE=PRIM: NO - sem bloqueio DC - com pr-bloqueio DI - sem pr-bloqueio NORING
BUSYRING
APRIVAT
NO
AICS
YES
OFFTYPE
DC
LINETONE
NO Ativao de diferenciao de tons para linhas YES - Pode-se particularizar-se o tipo de ring e volume para linha primria, de acordo com parmetros RINGTYPE e RINGVOL de KCSU. NO - O tipo de ring e volume definido pelo AMO ACTDA.
Exemplo: configurao de um Keyset. A linha primria atribuda primeira tecla de LINHA. Chamadas de entrada so sinalizadas nesta linha atravs do toque de chamada. Outros Keysets no podem intercalar ligaes estabelecidas: ADD-KCSU:STNO=4711,TYPE=PRIM,RIOP=YES,APRIVAT=YES;
s
Se a linha primria no deve ser atribuda primeira tecla de LINHA disponvel, o parmetro PRIMKEY deve ser especificado (p.ex. PRIMKEY=13, se a linha primria deve ser atribuda primeira tecla de LINHA do discador automtico. Isto somente possvel se o discador automtico foi configurado e a 13 tecla uma tecla de LINHA). Configure secondary lines of the Keyset: The second step is to assign the remaining line keys with the station numbers of other Keysets (secondary lines) using AMO KCSU (TYPE=SEC). Os parmetros usados tm os efeitos a seguir:
Parmetro (TYPE=SEC) STNO KYNO Descrio Nmero de ramal dos Keysets para os quais a linha secundria deve ser configurada Nmero da tecla da linha secundria: 1 - 12 (terminal) 13 - 28 (ADD_ON 1 - se configurada) 29 - 44 (ADD_ON 2 - se configurada) 45 - 60 (ADD_ON 3 - se configurada) 61 - 76 (ADD_ON 4 - se configurada) Valor padro STNO deve ser especificado KYNO deve ser especificado
RIOP
Opo de toque de chamada, ou seja, o tipo de sinalizao de NO chamadas de entrada na linha secundria: YES - por toque de chamada + LED + mostrador NO - apenas por LED (+ mostrador, dependendo da configurao TMLNPF) Nmero de ramal da linha secundria Atendimento automtico na linha secundria com monofone: YES- chamadas de entrada so automaticamente atendidas NO - chamadas de entrada devem ser atendidas manualmente Tipo de bloqueio de ramal durante modificaes usando TYPE=SEC: NO - sem bloqueio DC - com pr-bloqueio DI - sem pr-bloqueio STNOSEC deve ser especificado NO
STNOSEC AICS
OFFTYPE
DC
Exemplo: ocupao da 2 e 3 tecla de LINHA. Chamadas de entrada so sinalizadas na 2 tecla de LINHA apenas visualmente (pelo LED correspondente): ADD-KCSU:STNO=4711,TYPE=SEC,KYNO=2,STNOSEC=4712; ADD-KCSU:STNO=4711,TYPE=SEC,KYNO=3,STNOSEC=4713,RIOP=YES; 1. Modificar as configuraes de Keysets no mbito do sistema: Configuraes de consultas especficas por Keyset: DIS-ZAND:TYPE=KEYSYS;
s
Os parmetros apresentados tm o efeito a seguir:
Parmetro (TYPE=KEYSYS) COSLNBAS Descrio Verificar o COS atribudo linha usada: YES - o COS atribudo para uma linha vlido para o lado A NO - o COS atribudo para uma linha primria valido para o lado A Nmero do ramal/ nome apresentado atribudo a uma linha ocupada: YES - so mostrados os dados do usurio do outro lado atribudo linha ocupada NO - so mostrados os dados do usurio do outro lado atribudo linha primria Inicializao de DB NO
DISLNBAS
NO
HOLDACKY
YES Uma chamada retida ao se pressionar a tecla de linha correspondente: YES - a ligao atual retida ao se pressionar a tecla de linha ativa atribuda NO - a ligao atual terminada ao se pressionar a tecla de linha ativa atribuda YES Uma chamada retida ao se pressionar outra tecla de linha: YES - a ligao atual retida ao se pressionar outra tecla de linha NO - a ligao atual terminada ao se pressionar outra tecla de linha
HDNOACKY
Exemplo: mudar a configurao do sistema para que as ligaes ativas sejam retidas e no liberadas: CHA-ZAND:TYPE=KEYSYS,HOLDACKY=YES,HDNOACKY=YES; Comentrio: os valores dos parmetros para COSLNBAS e DISLNBAS devem ser os mesmos! Se um Keyset deve ser realterado para um optiset, executar as etapas a seguir: Remover todas as linhas secundrias dos Keysets: Primeiro, remover todas as teclas de linha para outros Keysets: DEL-KCSU:STNO=4711,TYPE=SEC [,KYNO=2&3&...]; Se o parmetro KYNO no for especificado, todas as linhas secundrias sero removidas.
s
Remover a linha primria do Keyset e reconfigurar o Keyset para um optiset: A linha primria ento removida (as teclas de linha de outros Keysets que tm uma linha secundria para o Keyset que ser removido so corrigidas). O Keyset torna-se ento um optiset normal: DEL-KCSU:STNO=4711,TYPE=PRIM; O comando DEL-KCSU:STNO=4711; tem o mesmo efeito que os dois comandos individuais anteriores! Atribuir o layout de teclas no-Keyset para o optiset E: As teclas especficas para o Keyset no podem mais ser usadas. Atribuir um layout de teclas padro projetado para optisets sem funes de Keyset (neste exemplo, 4) ao terminal: CHA-TAPRO:STNO=4711,STD=4;
s
1.2
AMO ACTDA CTIME DIMSU
Viso geral dos AMO utilizados

Parmetro RCUTOFF CTHLDREC KEYSYS CTPRESEL Idioma e e e e e e Descrio Corte da corrente de toque temporizador para controlar a durao da reteno manual de uma chamada Quantidade mxima de centrais KS Temporizador de controle para pr-seleo manual de uma linha ver item 1.1.5 Funo de tecla a ser atribuda tecla nmero xx: Tecla de linha Reteno Reteno exclusiva Privacidade Mostrar linha usada real Corte da corrente de toque Verificao do chamador em linha conectada e Resultado de anlise de dgito para: Tecla Reteno Tecla Reteno exclusiva Tecla Privacidade Tecla I-use Tecla Corte da corrente de toque Tecla Transferncia de chamada Tecla Cancelar Tecla Pndulo Tecla Consulta Tecla Rechamada Tecla Rediscagem do ltimo nmero Tecla Rediscagem de nmero salvo Privacidade ativada Privacidade desativada e e e selecionar a derivao para as configuraes para centrais KS Usar o COS que pertence linha apresentada ao invs do COS que pertence ao primrio da linha apresentada Exibir o nmero de ramal e o nome do usurio que pertencem linha apresentada ao invs dos que pertencem ao primrio da linha apresentada. Colocar a chamada ativa em reteno ao pressionar a tecla de linha correspondente chamada ativa. Colocar a chamada ativa em reteno ao pressionar outra tecla de linha no-correspondente chamada ativa.
KCSU TAPRO
----------KYxx = LINE HOLD EXCLHOLD PRIVACY IUSE RCUTOFF PREVIEW
WABE
DAR = HOLDKY EXHOLDKY PRIVKY IUSEKY RCTOFFKY TRNSKY RLSKY TOGGLEKY CONSKY CBKKY LNRKY SNRKY APRIV DPRIV
ZAND
TYPE = KEYSYS COSLNBAS DISLNBAS
HOLDACKY HDNOACKY
e e
s
AMO ZANDE Parmetro BRDGETON Idioma e Descrio Usar para desativar a gerao de tom de sinalizao para facilidade bridge call
s
5
5.1
Ramais Hotline e Warmline

Hotline/Warmline
A facilidade hotline automaticamente configura conexes de VOZ e DTE imediatamente atravs da captura inicial de um destino pr-configurado, atribudo no AMO HOTLN.
Atribuir um destino hotline ADD-HOTLN:TYPE=HOTDEST,HOTLNIDX=<nmero>,DEST=<nmero>; Ativar a facilidade: CHA-FEASU:A,HOTRCL; Atribuir o destino hotline a um ramal CHA-SDAT:STNO=<nmero>,TYPE=DATA1,HOTIDX=<nmero>; Atribuir o atributo HOT para servio de voz de um ramal pela atribuio comutvel a uma COS de ramal (alternando entre uma COS com atributo HOT e um sem HOT possvel - COS1/COS2): CHA-COSSU:TYPE=COS,COS=<nmero>,AVCE=HOT; (para VOZ) ou pela atribuio fixa (COS com AVCE=HOT no necessrio nesse caso): CHA-SDAT:STNO=<nmero>,TYPE=ATTRIBUT,AATTR=HOT;
Atribuir o atributo HOT para servio DTE a um COS do ramal (alternando entre um COS com atributo OFHKRC e um sem OFHKRC): CHA-COSSU:TYPE=COS,COS=<nmero>,ADTE=HOT;
A facilidade rechamada off-hook (warmline) automaticamente configura uma conexo a um destino pr-configurado atribudo no AMO HOTLN se dgitos no so discados, ou se apenas uma seqncia de dgitos incompleta discada dentro de um tempo predeterminado. Para ramais AnaTe, a conexo tambm configurada aps trmino do tempo do tom de ocupado da desconexo A-B de uma parte ou aps trmino do tempo do tom de ocupado aps discagem para um destino Fora de Servio. Esta facilidade fornecida para servio de VOZ apenas.
Atribuir um destino de rechamada off-hook ADD-HOTLN:TYPE=OFRCDEST,HOTLNIDX=<nmero>,DEST=<nmero>; Ativar a facilidade: CHA-FEASU:A,HOTRCL; Mudar o tempo para conexo automtica configurado em AMO DTIM2: CHA-DTIM2:TYPEDH=GEN,DTNT1=10; /*10 segundos o valor padro*/. Atribuir o destino de rechamada off-hook a um ramal CHA-SDAT:STNO=<nmero>,TYPE=DATA1,HOTIDX=<nmero>;
Atribuir OFHKRC a um ramal pela atribuio comutvel via COS do ramal (alternando entre uma COS com atributo OFHKRC e um sem OFHKRC - COS1/COS2): CHA-COSSU:TYPE=COS,COS=<nmero>,AVCE=OFHKRC; ou pela atribuio fixa (COS com AVCE=OFHKRC no necessria nesse caso): CHA-SDAT:STNO=<nmero>,TYPE=ATTRIBUT,AATTR=OFHKRC;
5.1.1
AMO HOTLN TAPRO TAPRO SDAT SDAT COSSU COSSU Tabela 5-1
AMOs Relevantes
Parmetro TYPE HTLNIDX DEST TYPE HOTIDX HOT OFHKRC Idioma e e e e e e e Descrio OFRCDEST, HOTDEST, HOTDEST, ndice hotline desejado para destinos hotline/ offhook destino interceptado offhook DATA1 ndice hotline hotline (AVCE/ADTE) cdigo azul (AVCE)
FlexRouting
6. FlexRouting
FlexRouting
Introduction to FlexRouting
FlexRouting
Configuring the XMU recorded announcement device
2 3
Setting up ACD in HiPath 4000
Configuring FlexRouting
4
Configuring ACD environment
5
Basic batches for FlexRouting
6 7 8 9
Referencias: A31003-G7310-S100-2-7620, November 1998 FlexRouting V1.0, Service manual
A31003-S2270-S120-8-V420, Novembro 2007 HiPath ProCenter Enterprise, V7.0 R2, Guia de Integrao de Hardware
10
Contents
Contents
1 Introduction to FlexRouting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 General overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Agent and supervisor telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Flexible routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.1 Available agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 Queues for incoming calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.3 End-of-shift routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.4 Calendar routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.5 Controlling agent features (CAF). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.6 ACD call forwarding (e.g. for night service). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
0
1-1 1-1 1-3 1-6 1-7 1-7 1-8 1-8 1-8 1-9
2 Configuring the XMU recorded announcement device . . . . . . . . . . . . . . . . . . . . . . . 2-1 3 Setting up ACD in Hicom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 3.1 Enabling FlexRouting in Hicom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 3.2 Types of FlexRouting-compatible telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 3.3 Configuring ACD members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 3.4 Configuring ACD groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 3.5 Configuring agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 3.6 Configuring FlexRouting telephone functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 3.6.1 Telephone key standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14 3.6.1.1 optiset basic (T8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14 3.6.1.2 optiset E Standard, Advance and Advance plus . . . . . . . . . . . . . . . . . . . . . 3-16 3.6.1.3 SET 400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 3.6.1.4 SET 500/SET 700. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20 3.6.3 Configuring customer-specific key standards . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24 3.6.4 Configuring codes for ACD functions (AMO WABE) . . . . . . . . . . . . . . . . . . . . . . 3-26 3.6.5 Configuring CAF codes (AMO WABE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29 3.6.6 Tone monitoring/silent monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34 3.6.7 Automatic Incoming Call Signaling (AICS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37 3.8 IVR (Interactive Voice Response) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38 3.9 Configuring short messages and emergency messages. . . . . . . . . . . . . . . . . . . . . . 3-39 4 Configuring FlexRouting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 4.1 Configuring Route Control Groups and ACD numbers . . . . . . . . . . . . . . . . . . . . . . . . 4-4 4.1.1 Configuring ACD numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 4.1.2 Configuring Route Control Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 4.2 Configuring DNIT tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 4.2.1 Configuring DNIT tables for destination-based routing . . . . . . . . . . . . . . . . . . . . 4-11 4.2.2 Configuring DNIT tables for destination/source-based routing . . . . . . . . . . . . . . 4-13 4.2.2.1 Configuring secondary DNI tables (parameter ROUTING=SA) . . . . . . . . . . 4-20 4.2.2.2 Configuring GDTR rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21 0-1
Contents
4.2.2.3 Configuring primary DNI tables (parameter ROUTING=DRTSA) . . . . . . . . . 4.3 Configuring the ACD call threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4 Configuring ART (ACD Routing Tables) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1 Action steps of ACD routing table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5 Configuring daily/calendar routing and shift numbers . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.1 Configuring shift numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.2 Configuring daily and calendar routing (AMO ACDRS) . . . . . . . . . . . . . . . . . . . .
4-24 4-25 4-26 4-28 4-35 4-37 4-39
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1
0-2
Introduction to FlexRouting General overview
FlexRouting can be used with Hicom 300E from version 2.0 onwards. FlexRouting is a standardized ACD solution which is supported on all Hicom 300 systems worldwide (Hicom 300 from V3.6 and Hicom 300E from V2.0 onwards). FlexRouting enhances Hicom 300 switching technology to include specific routing functions for call distribution systems, and also provides agent locations. Routing Routing distributes calls via ACD Routing Tables which are valid according to date and time. It also searches for available resources and provides the supervisor and report system with both current and history data. Within the Routing Table (ART), calls can be forwarded to other systems. Where destination resources are busy, the next stpe in the Routing Table is processed. Voice terminals and displays As well as being configured for Hicom functions, selected digital voice terminals from the Set 451, Set 551 and Set 751 series, Optiset E and analog Hicom 300 members can also be configured to operate as agent locations. To ensure optimum customer service, the digital terminal displays the call status and call-related information for incoming calls. Supervisor functions at digital voice terminals Supervisor functions include:
q q q q q q
Messages to agents Activation/deactivation of agent and group statistics Control of day and night service Group displays Silent monitoring (requires authorization) Tone monitoring
1-2
Introduction to FlexRouting Agent and supervisor telephones
1.2
Agent and supervisor telephones
Supervisor telephones are configured on a number-specific basis. ACD agents An ACD agent is a telephone connection which has been defined as an agent by the administrator. ACD agents are designed to answer ACD calls distributed via ACD routing. The agent can simultaneously perform both ACD-related and other tasks. The agent features meet Hicom 300 NLS (National Language Support) requirements, i.e., ACD agent texts are available in all the same languages as the text information provided for terminals. Agent IDs All agents are assigned an ID during configuration. The system supports a total of 4,000 agent IDs. The length of an agent ID can be configured individually for each Hicom (max. 6 characters). Agents must first enter their IDs before they can answer ACD calls. Automatic logon Members with the autologon feature are logged on automatically with their IDs following
q q q q q
a group change, system reboot, a hard restart, restart following a status change and configuration as part of normal system operation.
This feature is used for

q
IVR systems (Interactive Voice Response).
ACD telephone modes A logged-on ACD agent can be in one of 3 modes:

q q q
Available Unavailable Work
1-3
Agent telephone states

q
Non-ACD, outgoing Agent in any mode with an outgoing call Non-ACD, incoming Agent in any mode with an incoming call Non-ACD, internal Agent in any mode with an internal non-ACD call ACD incoming Agent in any mode with an incoming ACD call Other Agent in any mode and in transition status (e.g. dialling) Unknown Status temporarily unknown (e.g. restart).
Work ACD calls are not forwarded to the agents during work time.
q
Autowork It can be defined individually for each agent whether work time is automatically allocated when an ACD call is completed. Agents can terminate autowork time at their own discretion. The duration of autowork can be defined as follows: 1-10 seconds in 1-second intervals 15-300 seconds in 5-second intervals
Work The Work key must also be configured for each agent. The agent uses this key to activate work mode during a call and after a call has been completed.
Work time can be terminated either at the

q q
agent telephone or at the supervisor telephone.
1-4
Agent mode LEDs at the agent telephone Certain LEDs at the digital agent telephone indicate whether the agent is in available, unavailable or work mode. These LEDs are assigned to the Available, Unavailable and Work keys. LEDs indicating waiting ACD calls The number of ACD calls waiting for a group can be signalled, via the group status LED, at either the agents or the supervisors digital telephone. Example: LEDs indicating waiting ACD calls LED Waiting calls Out None On 1 to 6 Flashing slowly 7 to 15 Flashing quickly >16
Marking calls and entering billing codes (Account code and transactions code) An agent can enter a billing code during an ACD call. In this way, a call can be assigned to a particular event in the statistics. Example Calls to be marked Call received due an advertisement in a daily paper Call received due an advertisement in a weekly magazine The marking numbers can also be used as billing codes: Maintenance Acceptance of order 701 801 Marking number 101 102
The length of the billing code can be set as required (1-12 characters). It is forwarded to the ACD server via the ACL C protocol for reporting and statistics. Displaying queuing time If a connection has been established with an agent, the length of time for which the caller has had to queue appears on the agent telephone display. This corresponds to the delay between initial assignment of the call to an ACD Routing Table by the system and call pickup by the agent. The time is displayed for 5 seconds, once the call source and call destination have been deleted from the display.
1-5
Introduction to FlexRouting Flexible routing
1.3
Flexible routing
Each ACD is allocated to a particular ACD Routing Table. The selection of this table depends on both the time and the day of the week (and on calendar routing). It also depends on the translation result of the source/destination-related routing which has been determined based on the
q q
called number and calling number.
The ACD routing table is created using one or both numbers. This table defines the command steps, e.g. "route call to agent", "route call to music-on-hold", etc., which are provided to handle ACD calls. Various control and call-control commands can be entered in each ACD Routing Table. 1. 2. 3. 4. 5. 6. 7. 8. 9. Conditional routing (COND) GO STEP Call acceptance and ringing tone delay (DELAYRB) Disconnect (DISCON) Route to ACD group (RTGRP) Route to agent ID (RTAGT) Route to internal member (RTEXT) Route to music (RTMUS) Wait (WTSEC)
10. Route to recorded announcement (RTREC) 11. Route to external member (RTOFF)
1-6
1.3.1
Available agents
Calls are allocated to free ACD agents via:

q
Regular searches The available agent which has been free the longest is selected (FIFO).
Cyclical searches (circular) The search begins at the agent location following the agent which took the last call.
Linear searches The search for a free agent always starts with the first agent location in the list and is linear in nature.
1.3.2
Queues for incoming calls
If agents are not available, calls are ordered in the selected ACD group queue. Group overflow
Maximum number of RTGRP entries in the routing table

A call can be entered in up to 16 group queues (primary group plus max. 15 overflow groups).
More than 15 overflow groups in the routing table

Free agents can also be searched for via more than 15 overflow groups. If the number of RTGRP entered in a routing table is greater than 16, the remaining groups are each searched once only for a free agent. If a free agent is not found, the call is not requeud for the group, i.e., the system continues to search for a free agent only in the first 16 groups. Priority upgrade It is possible to specify the queuing time after which caller priority is to be upgraded by one level (5300 seconds in 5-second intervals, 0=no priority upgrade). You can define the period after which the priority of all the calls in queue is increased by one level (5300 seconds in 5-second intervals, 0=no priority upgrade).
q q
Highest priority = 1 Lowest priority = 64
1-7
1.3.3
End-of-shift routing
It is possible to define whether waiting calls are still to be processed despite the end of a shift, or whether they should be rerouted.
IMPORTANT If waiting calls are rerouted at the end of a shift, the priority upgrades assigned during the last shift are lost.
New incoming calls are routed for processsing by the new shift.
1.3.4
Calendar routing
Using this feature, the customer can configure special rerouting of ACD calls for certain days of the year, e.g. public or local holidays, religious feast days or company holidays. This allows the same date every year, a particular date in the current year or a particular date in any given year to be defined. This feature is an extension of daily routing. Time periods can also be entered using calendar routing (max. 1 year).
1.3.5
Controlling agent features (CAF)
CAF codes are equipped with a remote control function. This allows call distribution to
q q q
a particular agent, a particular group or a particular RCG (route control group)
to be controlled from an authorized telephone (e.g. supervisor).
1-8
1.3.6
ACD call forwarding (e.g. for night service)
There are two night service options: 1. The supervisor can activate and deactivate the night service using the CAF feature (CAF, see page 3-29). The call forwarding function can forward incoming CO calls to a predefined alternative destination number (e.g. an alternative ACD number, a recorded night announcement or an attendant). 2. The system can also activate day and night service automatically by selecting particular ACD Routing Tables using the end-of-shift routing feature.
1-9
1-10
The XMU recorded announcement device is provided for FlexRouting. 64 Western connector lines via distribution frame to SLMA
HiPath 4000
SLMA
Configuring recorded announcement ports for FlexRouting Each XMU announcement channel is connected with a Hicom SLMA port. Recorded announcement numbers All recorded announcements connected to a SLMA port are assigned a recorded announcement number via the AMO RCSU. These numbers can be entered subsequently in the following ACD tables:
q
XMU (eXtended Message Unit)
ART (ACD Routing Table) Step 1 2 3 4 5 ... DNIT Table INTRTDN 93511 ROUTING=DRTD GDTRRULE=0 DISPLAY ACD VIA 93511 RCG index - 100 PRI - 10 OVRPRI - 5 AUDSCRID - 7 THRSHLD - * 2-1 ART 16 RTREC RTGRP RTGRP RTMUS WTSEC RECNUM ACDGRP ACDGRP MUSNUM SEC 30 2 1 2 1
ART (see page 4-26) Recorded announcements can be located either at the start of the ART or further on (e.g. "Please hold..."). Recorded announcement (on request) Music (continuous).
DNIT for audible source ID (see page 4-7). Repeated announcement (continuous)
Using the audible source ID, a short text can be broadcast to agents when answering calls (e.g. "Call from USA") .
Front panel (chassis with 64 recorded announcement ports)
LCD display Function keys Handset: record texts and play back Tape input
Setting XMU playback modes 1. Ensure that the recorded announcements required are loaded into the recorded announcement device. These are normally provided either by a recording studio or are recorded by the customer. 2. Once the announcements are loaded, assign the corresponding description via the front panel: a) b) Recorded announcement: set the mode to "R" (one-off announcement) Repeated announcement and music: set the mode to "CP NO" (continuous).
2-2
Press the Enter key and, using the arrow keys,

q q
select the announcement and the required mode (card and line number) and set the corresponding mode. Main Menu < Card > Select Line # < 1 >
Select Card # < 1 >
Card 1 Line 1 < Mode
Card # 1 Select Line > <
Mode R and < Mode CP NO
Select Line # < ALL >
Recorded Announcement
Recorded Announcement/ Music
The XMU recorded announcement device is configured using the AMO RCSU.
The XMU can have a maximum of 64 ports. Via the front panel, assign the corresponding mode to each of the 64 ports.
>
Although more than 64 announcements can be recorded, only 64 ports are available.
2-3
Configure the recorded announcement port for a greeting (XMU mode "R")
Start of recorded greeting
Start of recorded greeting
New incoming calls are collected together during the repeated greeting. New callers hear the ringing tone during this time.
At this point
q
the collected callers all hear the recorded greeting and callers who have already heard the greeting have their calls processed in accordance with the type of routing configured.
The recorded greeting should be as short as possible, as it also corresponds to the maximum period during which the ringing tone can be applied. The recorded greeting is assigned the mode "R" (fixed announcement length).
q q
The recorded announcement begins when a call is assigned Hicom is notified when the announcement (which is played once only) is completed.
Example: "Welcome to the Siemens AG Munich technical support service. All our technicians are currently busy, your call will be connected as soon as possible. Please hold". ADD-RCSU:PEN=1-2-25-0,NO=1,ACT=YES,OPMODE=DEMAND, OPTYPE=FIXED,RECAPL=ACDR,RECNUM=1,LENGTH=8; PEN OPMODE OPTYPE RECAPL ANSNR Enter the PEN for each XMU recorded announcement port. Demand Fixed Recorded announcement port Recorded announcement number. This is entered subsequently into the ACD Routing Table (ART) using the AMO ACDRT, parameter RTREC (see page 426). Note: Only one-off announcements are used in the ART.
2-4
LENGTH
Duration of a one-off announcement. You can query the length of each announcement via the XMU menu. Either the given duration or a longer period can be entered here.
Interim recorded announcements (e.g. "Please hold...") This announcement is corresponds to item 1, except that if music on hold has already been configured, waiting callers hear music instead of a ringing tone. Configuring a recorded announcement port for audible source ID (XMU mode => "CP NO") These are announcements which can be broadcast to the agent when a call is being taken. The RECNUM is entered subsequently to the corresponding DNIT table with the AMO DNIT, parameter AUDSCRID (see page 4-7). Example: "Call from USA" ADD-RCSU:PEN=1-2-25-2,NO=1,ACT=YES,OPMODE=CONT, OPTYPE=RANDOM,RECAPL=ACDR,RECNUM=2,LENGTH=5; OPMODE OPTYPE RECAPL RECNUM LENGTH Cont Random Recorded announcement Recorded announcement number Duration how long the agent can hear the announcement.This can be queried for each announcement via the front panel of the recorded announcement device.
2-5
Configuring a recorded announcement port for music (XMU mode => "CP NO" ) ADD-RCSU:PEN=1-2-25-3,NO=1,ACT=YES,OPMODE=CONT, OPTYPE=RANDOM,RECAPL=ACDMUS,MUSNUM=1; OPMODE OPTYPE RECAPL MUSNUM CONT RANDOM ACDMUS In this way, the music which is stored on the XMU is broadcast to the member. The MUSNUM is entered subsequently to the required ACD Routing Table with the AMO ACDRT, parameter "RTMUS" (see page 4-26). In order to restrict the duration of the music, enter a time limit for the search for free agents in the ACD Routing Table. It should be entered after the Music destination field (ART command WTSEC). The board port only starts operating when 1. 2. it is connected to the recorded announcement device and the announcement device is configured accordingly.
>
Testing recorded announcements Recorded announcements cannot be selected and tested via a number. Announcements are only available in ACD. If you are not sure whether the announcements are working, they should first be configured using AMO SCSU. In this way they can be selected for test purposes via a number.
2-6
Setting up ACD in Hicom
Setting up ACD in HiPath 4000
Agent
Supervisor
HiPath 4000 XMU (eXtended Message Unit)
The following steps are described in this chapter: Enabling FlexRouting Configuring agents and groups Overview of agent/supervisor telephone features Configure agent and supervisor telephones and their groups: 1. 2. 3. Configure agents and supervisors as members Configure groups Configure special features a) b) c) Silent monitoring (<< requires authorization >> ). Tone monitoring. Automatic call pickup (e.g. where a headset is used).
Routing is described in Chapter 4.
3-1
Setting up ACD in Hicom
4.
Overview of agent and supervisor telephone functions Keys (from page 3-14 onwards) for agent/supervisor telephones Agent logon/logoff Agent unavailable Marking (account code) Automatic call pickup Short message to supervisor Primary group status Primary queue status Typical supervisor telephone keys Short message to agent Supervisor-only keys Tone monitoring Codes (from page 3-26 onwards) for agent/supervisor telephones Agent logon/logoff Agent unavailable Marking (account code) Short message to supervisor Primary queue status Typical supervisor telephone codes Short message to agent Supervisor-only codes Tone monitoring Tone monitoring (third-party monitoring) Secondary queue status Work Agent available Headset Primary group status Secondary queue status Tone monitoring (third-party monitoring) Secondary group status Work Agent available Headset Send emergency message Acknowledgment Scroll key with LED for messages Secondary queue status
CAF codes (from page 3-29 onwards) (CAF=Control of Agent Features) CAF group available CAF group logoff CAF agent available CAF call forwarding on CAF group unavailable CAF agent logoff CAF agent unavailable CAF call forwarding off Tone monitoring (third-party monitoring)
3-2
Setting up ACD in HiPath Enabling FlexRouting in Hicom
3.1
Enabling FlexRouting in HiPath
Requirements
q
A dongle must first be plugged at the operating terminal interface in order to enable FlexRouting in Hicom 300 E. No special LCR, COP or COT details are required.
Dimensioning a FlexRouting datafield in Hicom (AMO DIMSU) These details are used to define the maximum FlexRouting value. ADD-DIMSU:TYPE=CC2,ACDAGT=300,ACDCQ=600,ACDGRP=30,ACDLOGON=50, ACDPRIM=75,ACDRCG=1000,ACDSHIFT=100,ACDRT=100,ACDCALEN=100,ACDRTX=200, ACDMONID=100,GDTR=10,DNI=100,DPDNI=10; ACDAGT ACDCQ ACDGRP ACDLOGON ACDPRIM ACDRCG ACDSHIFT ACDRT ACDCALEN ACDRTX ACDMONID GDTR DNI DPDNI Number of agents which can be configured in ACD G Number of entries in the ACD call queue Number of configurable ACD groups Number of agents which can log on simultaneously Number of primary agents This must be the same as the number in ACDAGT. Number of route control groups (RCG) Number of shifts Number of ACD Routing Tables Number of entries for calendar routing (for weekdays, Sundays and public holidays) Number of additional ACD Routing Tables Number of ACL monitor points (e.g. number=number of ACDRCG) Number of entries for translating source numbers Number of entries for translating ACD numbers Number of datapool elements for the DIMSU parameter DNI
DIS-DIMSU:TYPE=CC; If you discover during further configuration that a particular field has been under-dimensioned, a corresponding message is displayed. You can then extend the required data field using the AMO DIMSU.
3-3
Setting up ACD in Hipath 4000 Enabling FlexRouting in Hicom
>
Old CO trunks which cannot be cleared down at next step These trunks are associated with the following problem. Although the caller has hung up, FlexRouting may not have registered this fact and forwards the call to an agent. When the agent accepts this call, a busy tone is heard. This is why old CO trunks should not be used.
Configuring FlexRouting in Hicom (AMO ZAND) CHANGE-ZAND:TYPE=ACD,ACDALLOW=YES; Number corresponds to the DPLN group for ACD FlexRouting: Default value is 0# The DPLN group ACDWABE should correspond to the DPLN group of the routing destinations. Assign DPLN group (AMO ZAND) CHANGE-ZAND:TYPE=ACD,ACDDPLN=0;
CAUTION
When the parameter ACDALLOW=NO is set,
q q
FlexRouting is deactivated and all agents are logged off.
3-4
Setting up ACD in HiPath Types of FlexRouting-compatible telephones
3.2
Types of FlexRouting-compatible telephones
FlexRouting-compatible telephones are marked with "+" Agent Superv. CAF ANATE + DIGI211 + DIGI260 + SET400 + + + Ext. TTX, DTE KEY300 SET500-based trading phone + + + SET500 + + + SET700 + + + OPTISET + + + SET600 CMI BASE OPTISET-based CMI EXTLINE SET600-based extension line CMI ADM OPTISET-based CMI RADIO OPTISET-based cordless phone + + + SKY MANAGER OPTISET-based SKY EXTLINE SET600-based extension line SKY PHONE OPTISET-based trading phone SKY LINE OPTISET-based trading line + + + NT LOGOPTI Network team OPTISET only logically defined but physically to be plugged in a different Network node NT REMOPTI Network team OPTISET only physically plugged but logically defined in a different Network node NT EXTLINE SET600-based extension line TC LOGOPTI OPTISET-based telecommuting station only logically defined TC REMOPTI OPTISET-based telecommuting station Station signed off Member logged off + + + Floating station Floating member Station with + + + associated DCI CHESE executive Executive + + CHESE secretary Secretary CHESE Secretary representative + + +
3-5
Setting up ACD in Hicom Configuring ACD members
3.3
Configuring ACD members
Configuring members in WABE (AMO WABE) ADD-WABE:CD=3401,DAR=STN,CHECK=N; ADD-WABE:CD=3402,DAR=STN,CHECK=N; ADD-WABE:CD=3403,DAR=STN,CHECK=N; Configuring telephones in Hicom Members may not be configured as secretaries (SECR=N).
q q q q q
AMO SBCSU for optiset AMO SCSU for ANATE and DIGITE SET 400 AMO SSCSU for SKY Line AMO SBCSU for DIGITE SET 500 and Set700 SBCSU, SCSU and SSCSU are transparent for FlexRouting.
Activating members for management using FlexRouting (AMO SDAT) Possible configurations: CHA-SDAT:STNO=3242,TYPE=ATTRIBUT,DATTR=,AATTR=SUPER CHA-SDAT:STNO=3243,TYPE=ATTRIBUT,DATTR=,AATTR=AGENT CHA-SDAT:STNO=3244,TYPE=ATTRIBUT,DATTR=,AATTR=AGENT&SUPER CHA-SDAT:STNO=3245,TYPE=ATTRIBUT,DATTR=,AATTR=AGENT&AUTOLOG CHA-SDAT: STNO=3246 ,TYPE=ATTRIBUT, DATTR=,AATTR=AGENT&SUPER&AUTOLOG AATTR DATTR activates attributes deactivates attributes
Before a member attribute can be deactivated using SDAT, this must have been deactivated using the AMO DSSU.
>
Once a member has been enabled for FlexRouting, it cannot immediately be deleted. In order to delete an agent port, FlexRouting must first be disabled.
3-6
Setting up ACD in Hicom Configuring ACD groups
3.4
Configuring ACD groups
Every ACD group must be assigned a supervisor. The first assigned group is agreed as standard as the primary group for the supervisor. If a supervisor is subsequently assigned to an additional group, the supervisor can also be assigned another group as a primary group using the parameter PRIMARY. Maximum values Up to 255 groups can be configured. Up to 1000 agents can be entered in a group. Changing the search method If the search method is changed from CIRC => FIFO or LIN => FIFO or vice versa, all agents are logged on. Using AUTOLOG, agents which have been overlooked are automatically logged on again in the port when the change occurs.
q q
Logoff is automatic when a change occurs Automatic logon only occurs with AUTOLOG
Configuring ACD groups ADD-ACDGP:ACDGRP=1,SEARCH=FIFO,SUPEXT=3242,PRIMARY=YES, LED=YES,ON=5,FLASH=7,WINK=10; ACDGRP Group number <1-255> or no entry. If a group number is not specified, the next free group number is used. A preexisting ACDGRP group is not used. Call distribution for this group: Standard=FIFO (long. idle), LIN=linear or CIRC=cyclical. This is used to assign a supervisor to a group. (Yes/no) is entered to define whether this is assigned to the supervisor as a primary or secondary group. Each supervisor may only be assigned one primary group. Yes/standard=no: This defines whether the number of waiting calls is indicated by a flashing LED (LED at the ACDPGS or ACDPQS key). The LED remains on once this number of waiting calls is exceeded (1-253 calls). The LED flashes once this number of waiting calls is exceeded (2-254). The LED winks once this number of waiting calls is exceeded (3-255). Example: ON < FLASH < WINK
SEARCH SUPEXT PRIMARY
LED ON FLASH WINK
3-7
Setting up ACD in Hicom Configuring ACD groups
To activate the LED function, either the ACDPGS or the ACDPQS key must be configured. ACDPGS=primary group status, ACDPQS=primary queue status (see page 3-26). Displaying ACD groups Example: Displaying ACD groups assigned to the supervisor 91101 DIS-ACDGP:SUPEXT=91101;
+-------+--------+---------+------+--------+----+-----+-----+ | |NUMBEROF| | | |LED |LED |LED | |ACDGRP |AGENTS |SUPEXT |SEARCH|PRIMARY |ON |FLASH |WINK | +-------+--------+---------+------+--------+----+-----+-----+ | 3 | 15 | 91101 | CIRC | NO | 7 | 15 | 30 | +-------+--------+---------+------+--------+----+-----+-----+ | 4 | 8 | 91101 | LIN | NO | 7 | 15 | 30 | +-------+--------+---------+------+--------+----+-----+-----+ | 11 | 17 | 91101 | FIFO | YES | 7 | 15 | 30 | +-------+--------+---------+------+--------+----+-----+-----+ | 12 | 22 | 91101 | FIFO | NO | 7 | 15 | 30 | +-------+--------+---------+------+--------+----+-----+-----+
Deleting ACD groups An ACD group can be deleted if:

q
It is not a primary group for a supervisor (parameter PRIMARY). If several groups have been assigned to the supervisor, another group must be entered as a primary groups where necessary. Exception: If only one group is assigned to the supervisor, this can be deleted if both of the following conditions are met:
The agents assigned to this group have been reassigned or deleted using the AMO AGENT (see page 3-9). This group is not entered into an ACD Routing Table (see page 4-26).
If these conditions are not met, the deletion action is rejected and an error message is output. Example: DEL-ACDGP:ACDGRP=2; F13: THE ACD GROUP (ACDGRP) IS CONFIGURED AS THE PRIMARY GROUP. IT CAN ONLY BE DELETED ONCE ANOTHER ACD GROUP IS CONFIGURED AS A PRIMARY GROUP FOR THE SUPERVISOR.
3-8
Setting up ACD in HiPath Configuring agents
3.5
Configuring agents
Condition: The ACD groups have already been configured. Define standard system parameters for agents Using the AMO ACDSD, TYPE=SYS, set universally valid agent features: CHA-ACDSD:TYPE=SYS,AGTIDLEN=3,QFACTOR=10,AGTTARGT=EXT,DELAYRBT=1; AGTIDLEN QFACTOR AGTTARGT <1..6> Number of agent ID characters. <0-300> Time after which waiting calls are assigned. Higher priority (0=priority unchanged, 5-sec. intervals). Entry which identifies agents: =EXT : agent extension number. =ID : agent identification number. Ringing tone delay <1...25>, standard = 5 seconds. Maximum time value for DELAYRBT interval in the ART.
DELAYRBT
Example: DELAYRB entry in the ACD Routing Table CHA-ACDRT:ART=22,TYPE=ARTSTEP,STEP=1,ACT=DELAYRB; Configure agents and allocate group AMO AGENT ADD-AGENT:AGTID=101,ACDGRP=1,AGTPOS=1,AUTOWK=10,AUTOEXT=3243; ADD-AGENT:AGTID=102,ACDGRP=1,AGTPOS=2,AUTOWK=10; ADD-AGENT:AGTID=103,ACDGRP=1,AGTPOS=3,AUTOWK=10; AGTID ACDGRP AGTPOS Unique agent identification number. The number of characters is defined in ACDSD. <0-255> group IDs. 0 = flexible agents (agents not assigned group membership). <1...1000> Entering a position assigns a fixed position to the agent within a group. If a position is not entered, the agent is assigned as standard the next free position in the ACD group table. Note: This entry assigns a priority in the case of linear agent searches. Wherever possible, the call is assigned to the agent with the lowest AGTPOS. The agent search is defined in the AMO ACDGP.
3-9
Setting up ACD in HiPath Configuring agents
AUTOWK
<0...300> Work time in 5-second intervals. This defines the number of seconds, after a call is completed, during which calls may not be assigned to the agent. Standard=0, 299="unlimited" work time. 0=no work time, 110 in 1-second intervals 15300 in 5-second intervals. Extension number for automatic logon.
AUTOEXT
Configure flexible agents (agents not assigned group membership) Flexible agents are configured using the parameter ACDGRP=0. In this case, AGTPOS cannot be configured for the agents. Flexible agents are not assigned group membership until the supervisor has entered all corresponding group data for these agents. Only when this is complete can a flexible agent log onto this group. Example: Configuring flexible agents: ADD-AGENT:AGTID=111,ACDGRP=0,AUTOWK=20; H06: THE AGENT (AGTID) 101 HAS BEEN CONFIGURED IN THE FLEXIBLE ACD GROUP. CHA AGENT (change agent) The additional parameter NEWID is available for the action CHA AGENT CHA-AGENT:AGTID=101,NEWID=93101; H02: THE AGENT (AGTID) 101 HAS BEEN CHANGED. Additional notes Whether incoming call should be
q q
ACD-group distributed only or allocated directly to certain agents
can be entered subsequently in the ART.
Allocating calls directly to agents

Example: The agent with agent ID 301 is a member of group 104 Possible ART constellation 1. 2. 3. RTAGT 301 RTGRP 104 ... Unauthorized ART constellations 1. 2. 3. RTGRP 104 RTAGT 301 => ERROR ...
3-10
Setting up ACD in HiPath Configuring FlexRouting telephone functions
3.6
Configuring FlexRouting telephone functions
This section introduces the default key standards of the FlexRouting telephone:
q q q q
optiset E T8 (page 3-14) optiset E T12 (page 3-16) SET 400 (page 3-14) SET 551/SET 751 (page 3-21) Note for SET 500: When installing Set500, use the latest firmware. Although the system will operate with older versions, it cannot receive calls. The terminal must be adjusted before calls can be forwarded to it (e.g. the handset must be lifted or placed on-hook).
With FlexRouting you can also

q
display the features using codes (see page 3-26) This feature is used for workstations where the feature has not been configured on any function key (e.g. ANATE) and
display CAF features using codes (see page 3-29). This allows the user, for example, to log an agent or group off from a supervisor telephone.
Do-not-disturb, voice calling protection, call forwarding and call forwarding, no answer are not activated for ACD calls. These features continue are still available for non-ACD calls.
Features tone monitoring and silent monitoring In certain countries these features may only be activated in consultation with the customer and, where necessary, with employee representatives. Written customer authorization must be provided (see page 3-34).
3-11
Possible agent supervisor telephone functions Default ACD key standards are configured for the ACD functions. These key standards can be modified as described from page 3-24 onwards. Idx A A A A A H H S S A/S A/S S AS AS A S A A AMO TAPRO ACDLOG ACDWORK ACDNAV ACDAV ACC HS AUTOM ADDON MONTONE ACDEMMSG ACDSPVM ACDAGTM ACK SCROL ACDPGS ACDSGS ACDPQS ACDSQS Key description Agent logon/logoff Work Agent unavailable Agent available Marking (account code) Headset Automatic call pickup Silent monitoring Tone monitoring Send emergency message Short message to supervisor Short message to agent Acknowledgement Arrow key with LED Primary group status Secondary group status Primary queue status Secondary queue status Max ID length 6 characters Activate only Activate only Deactivate work/unavailable Enter number of markings Available/unavailable Activate/deactivate Third-party monitoring Tone monitoring Agent to supervisor Agent to Supervisor Supervisor to agent Confirm short message Scrolling in short messages Status of own group Status of selected group Status of own queue factor Queue factor of selected group
Column Idx A H S AS A/S Agent telephone Agent telephone with headset Supervisor telephone Agent and supervisor telephone This key must also be configured on the supervisor telephone so that supervisors can dispatch a message to their superiors. For this purpose the supervisor must be configured as an agent in another group.
3-12
Notes about special keys

q
"Available" key The Available key terminates the unavailable, work and autowork modes.
"Unavailable" key Before leaving their workstations for a short time, agents must press this key.
"ACK" key When recording messages, the ACK and SCROL keys must be configured. The ACK key cannot be configured as a keyboard code.
Expansion to include 20 standard key assignments (STD) The AMO TAPRO already provides standard FlexRouting key assignments for the SET 400, SET 500 and optiset telephones.
3-13
3.6.1
Telephone key standards
The telephones are described on the following pages:

q q q q
optiset E basic (T8) from page 3-14 onwards optiset E standard, advance and advance plus (T12) from page 3-16 onwards SET 400 from page 3-18 onwards SET 500/SET 700 from page 3-21 onwards optiset basic (T8)
3.6.1.1
Key standards for agents optiset basic (T8) optiset E T8 * * * * + * * * * 1 2 3 4 5 6 7 8 6 7 8 Key 1 2 3 4 5 Agent assignment Agent IDs Available Unavailable Work Transactions code Classifies callers for statistical evaluation Parking Release Direct Station Selection TAPRO ACDLOG ACDAV ACDNAV ACDWORK ACC
PARK CL DSS
3-14
Key standards for supervisors optiset basic (T8) optiset E T8 * * * * + * * * * 1 2 3 4 5 6 7 8
Key 1 2 3 4 5 6 7 8
Supervisor assignment Available Unavailable Third-party monitoring Tone monitoring Date Parking Release
TAPRO ACDAV ACDNAV ADDON MONTONE REMIND PARK CL
Direct Station Selection DSS
optiset basic (T8): Display key standards

DIS-TAPRO:STD,14,OPTISET; or DIS-TAPRO:STD,15,OPTISET;
STD DIGTYP KEY ASSIGNMENT
Agents
14 OPTIT8 1 ACDLOG 6 PARK 2 ACDAV 7 CL 3 ACDNAV 8 DSS 4 ACDWORK 5 ACC
Supervisors
15 OPTIT8 1 ACDAV 6 PARK 2 ACDNAV 7 CL 3 ADDON 8 DSS 4 MONTONE 5 REMIND
3-15
3.6.1.2
optiset E Standard, Advance and Advance plus
Key standards for agents optiset E T12
+ -
* * * *
1 2 3 4
* * * * * * * *
5 6 7 8 9 10 11 12
Key 1 2 3 4 5 6 7 8 9
Agent assignment Agent IDs Available Unavailable Work Scroll Message for supervisor Confirm Emergency
TAPRO ACDLOG ACDAV ACDNAV ACDWORK SCROL ACDSPVM ACK ACDEMMSG
Transactions code ACC Classifies callers for statistical evaluation Parking Release Direct Station Selection PARK CL DSS
10 11 12
3-16
Key standards for supervisors optiset E T12
Key + * * * * 1 2 3 4 * * * * * * * * 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12
Supervisor assignment Available Unavailable
Tapro ACDAV ACDNAV
Third-party monitoring ADDON Tone montoring Scroll Message for agent Confirm Primary group status Primary queue status Parking Release Direct Station Selection MONTONE SCROL ACDAGTM ACK ACDPGS ACDPQS PARK CL DSS
optiset E (T12): Display key standards

DIS-TAPRO:STD,17,OPTISET;
STD DIGTYP
or DIS-TAPRO:STD,16,OPTISET;
KEY ASSIGNMENT
Agents
16 OPTIT12 1 ACDLOG 6 ACDSPVM 11 CL 2 ACDAV 7 ACK 12 DSS 3 ACDNAV 8 ACDEMMSG 4 ACDWORK 9 ACC 5 SCROL 10 PARK
Supervisors
17 OPTIT12 1 ACDAV 6 ACDAGTM 11 CL 2 ACDNAV 7 ACK 12 DSS 3 ADDON 8 ACDPGS 4 MONTONE 9 ACDPQS 5 SCROL 10 PARK
3-17
Setting up ACD in Hicom Configuring FlexRouting telephone functions
3.6.1.3
SET 400
Key standards SET 451 T 25 FD * * * * * * * *
9 10 11 12 13 14 15 16 * 5 7 18 17 ACD assignment
* * * * * * * *
1 2 3 4 23 24 19 20 8 6 22 21 TAPRO ACDAV ACDNAV ADDON MONTONE SCROL
29
* * *
Key 9 10 11 12 1
Agent 1/2 Agent IDs Available Unavailable Work Scroll
TAPRO ACDLOG ACDAV ACDNAV ACDWORK SCROL
Supervisor Available Unavailable Third-party monitoring Tone monitoring Scroll
3-18
Key 2 3 4
Agent 1/2 Message for supervisor Confirm Emergency
TAPRO ACDSPVM ACK ACDEMMSG
Supervisor Message for agent Confirm Emergency message
TAPRO ACDAGTM ACK ACDEMMSG
SET 400: Key standards Agent 1: Agent 2: DIS-TAPRO:STD,14,SET400; DIS-TAPRO:STD,15,SET400;
Supervisor: DIS-TAPRO:STD,16,SET400;
STD DIGTYP KEY ASSIGNMENT
Agent 1
14 SET4C2 1 SCROL 6 SNR 11 ACDNAV 16 ST 21 CONS 26 VACANT 2 ACDSPVM 7 PU 12 ACDWORK 17 SPKR 22 RLS 27 VACANT 3 ACK 8 CBK 13 REMIND 18 CH 23 PARK 28 VACANT 4 ACDEMMSG 9 ACDLOG 14 TRNS 19 KNOVR 24 CL 29 MB 5 FWD 10 ACDAV 15 SPLT 20 CONF 25 VACANT | |
Agent 2
15 SET4C2 1 SCROL 6 SNR 11 ACDNAV 16 ST 21 CONS 26 VACANT 2 ACDSPVM 7 PU 12 ACDWORK 17 SPKR 22 RLS 27 VACANT 3 ACK 8 CBK 13 ACC 18 CH 23 PARK 28 VACANT 4 ACDEMMSG 9 ACDLOG 14 TRNS 19 KNOVR 24 CL 29 MB 5 FWD 10 ACDAV 15 SPLT 20 CONF 25 VACANT | |
Supervisors
16 SET4C2 1 SCROL 6 SNR 11 ADDON 16 ST 21 CONS 26 VACANT 2 ACDAGTM 7 PU 12 MONTONE 17 SPKR 22 RLS 27 VACANT 3 ACK 8 CBK 13 REMIND 18 CH 23 PARK 28 VACANT 4 ACDPGS 9 ACDAV 14 TRNS 19 KNOVR 24 CL 29 MB 5 FWD 10 ACDNAV 15 SPLT 20 CONF 25 VACANT
3-19
3.6.1.4
SET 500/SET 700
Key standards SET 500/ SET 700 * * * * * * * * 1 2 3 4 5 6 7 8 * * 25 * * * Key 1 2 3 4 9 10 Agent 1/2 Agent IDs Available Unavailable Work Scroll TAPRO ACDLOG ACDAV ACDNAV ACDWORK SCROL 18 19 20 22 23 24 TAPRO ACDAV ACDNAV ADDON MONTONE SCROL ACDAGTM * * * * * * * * 17 9 10 11 12 13 14 15 16 21
Supervisor Available Unavailable Third-party monitoring Tone monitoring Scroll Message for agent
Message for supervisor ACDSPVM
3-20
Key 11 12
Agent 1/2 Confirm Emergency
TAPRO ACK
Supervisor Confirm
TAPRO ACK ACDEMMSG
ACDEMMSG Emergency message
SET 500/700: Key standards Agent 1: Agent 2: Supervisor:

STD DIGTYP
DIS-TAPRO:STD,9,SET500; DIS-TAPRO:STD,10,SET500; DIS-TAPRO:STD,11,SET500;

KEY ASSIGNMENT
Agent 1
9 SET500 1 ACDLOG 6 TRNS 11 ACK 16 CONF 21 CBK 2 ACDAV 7 SPLT 3 ACDNAV 8 ST 4 ACDWORK 9 SCROL 14 CL 19 CH 24 CONS 5 REMIND 10 ACDSPVM 15 KNOVR 20 SPKR 25 MB | | | |
12 ACDEMMSG 13 NAME 17 FWD 22 SNR 18 PU 23 RLS
Agent 2
10 SET500 1 ACDLOG 6 TRNS 11 ACK 16 CONF 21 CBK 2 ACDAV 7 SPLT 3 ACDNAV 8 ST 4 ACDWORK 9 SCROL 14 CL 19 CH 24 CONS 5 ACC 10 ACDSPVM 15 KNOVR 20 SPKR 25 MB | | | |
12 ACDEMMSG 13 NAME 17 FWD 22 SNR 18 PU 23 RLS
Supervisors
11 SET500 1 ACDAV 6 TRNS 11 ACK 16 CONF 21 CBK 2 ACDNAV 7 SPLT 12 ACDPGS 17 FWD 22 SNR 3 ADDON 8 ST 13 ACDPQS 18 PU 23 RLS 4 MONTONE 9 SCROL 14 CL 19 CH 24 CONS 5 REMIND 10 ACDAGTM 15 KNOVR 20 SPKR 25 MB | | | |
3-21
3.6.2
TAPRO ACC ACDAGTM
TAPRO parameters and key descriptions

Key description Account code (mark call) Send message to agent Agent working Agent LOGON/LOGOFF Send emergency message Agent unavailable (e.g. for a short break) Primary group status Primary queue status Secondary group status Secondary queue status Send message to supervisor Agent available Acknowledge message Do-not-disturb key Key for call override, call waiting ... Direct voice calling protection Call forwarding key Call pickup Call pickup (for executive/secretary telephone) Automatic call pickup Mailbox key Message retrieval key Check (query mailbox contents) Clear Voice calling key Direct Station Selection key Data transfer (store) Key unassigned Conference key Local name key ACD ACD ACD ACD ACD ACD ACD ACD ACD ACD ACD ACD ACD ACD
ACDWORK ACDLOG ACDEMMSG ACDNAV ACDPGS ACDPQS ACDSGS ACDSQS ACDSPVM ACDAV ACK DND KNOVR VCR FWD PU PUS AUTOM MB MSGR CH CL VC DSS STO VACANT CONF LNAME
3-22
TAPRO SPKR SPLT MONTONE MUTE NAME NV PARK CC CONS CBK RNGXFER HT SCROL HS ST REMIND RLS DOOR TRNS TIME REP LNR SNR ADDON
Key description Loudspeaker key Toggle Tone monitoring Loudspeaker mute key Name key Non-voice (data) key Parking key Code calling key Consultation Callback, trunk queuing Ring transfer (for executive/secretary telephone) Hunt group key (on/off) Scroll messages Headset key Start key Reminder function key Release Door key Transfer, pickup Date/time Representative key (for executive/secretary telephone) Redial last number dialled Store number, redial number Third-party monitoring key The LED next to the ACDPGS button (or ACDPQSC if only this button is installed) does not light up when the button is operated as this LED is used as a call waiting level LED. This means that this LED indicates the number of waiting callers, see Section 3.4 on page 3-7. ACD ACD
>
3-23
3.6.3
Configuring customer-specific key standards
Cistomer-specific key standards can be configured in two ways: 1. The standard key assignment can be modified for a particular telephone. Unassigned standard numbers can be configured (depending on availability) or a default standard number (STD) can be overwritten. 2. The key assignment can modified specifically for particular extensions.
Modifying key standards for various types of telephone

DIS-TAPRO:STD,9,SET500; Display the STD 9 key assignment +-----+---------+----------------------------------------------------------------+ | 9 | SET500 | 1 ACDLOG 2 ACDAV 3 ACDNAV 4 ACDWORK 5 REMIND | | | | 6 TRNS 7 SPLT 8 ST 9 SCROL 10 ACDSPVM | | | | 11 ACK 12 ACDEMMSG 13 NAME 14 CL 15 KNOVR | | | | 16 CONF 17 FWD 18 PU 19 CH 20 SPKR | | | | 21 CBK 22 SNR 23 RLS 24 CONS 25 MB | +-----+---------+----------------------------------------------------------------+
q
optiset CHA-TAPRO:,<nn>,OPTISET,ACDLOG,ACDAGTM,...; <nn>standard number 0-19
SET 400 CHA-TAPRO:,<nn>,SET400,ACDLOG,ACDAGTM,...; <nn>standard number 0-19
SET 500/700 CHA-TAPRO:,<nn>,SET500,ACDLOG,ACDAGTM,...; <nn>standard number 0-19
3-24
Modifying agent telephone key standards (e.g. telephone no. 3401)

q
optiset Modify keys 01-04 and 09-12 Function keys: ,01,02,03,04,,,,,,09,10,11,12; CHA-TAPRO:3401,,OPTISET,xx,xx,xx,xx,,,,,,xx,xx,xx,xx; ....additional telephones
SET 451 Modify keys 01-04, 09-14 and 23-24 Function keys: ,01,02,03,04,,,,,09,10,11,12,13,14,..,23,24; CHA-TAPRO:3401,,SET400,xx,xx,xx,xx,,,,,xx,xx,xx,xx,xx,xx,..,xx,xx; ....additional telephones
SET 551 and 751 Modify keys 01-04 and 09-12 Function keys: ,01,02,03,04,05,06,,,09,10,11,12,13,14; CHA-TAPRO:3401,,SET500,xx,xx,xx,xx,xx,xx,,,xx,xx,xx,xx,xx,xx; .....additional telephones xx => ACC / ACDAGTM / ACDWORK / ACDLOG / ACDEMMSG / ACDNAV / ACDPGS / ACDPQS / ACDSGS / ACDSPVM / ACDSQS / ACDAV / ACK / SCROL / MONTONE / ADDON Third-party monitoring (silent monitoring) / DND (do-not-disturb key) / KNOVR (key for call override, call waiting, etc.) .
See page 3-14 for an explanation of parameters. Assigning key standards for an extension CHA-TAPRO:STNO=3401,DIGTYP=SET500,STD=17;
3-25
3.6.4
Configuring codes for ACD functions (AMO WABE)
As well as key functions, features can also be activated using codes. Example: configuring codes Code 927 928 929 930 931 932 933 934 936 937 938 939 980* 981* WABE CP ACC MONSLNT MONTONE ACDLOGOF ACDAV ACDNAV ACDWORK ACDPGS ACDSGS ACDPQS ACDSQS Feature Account code Silent monitoring Tone monitoring Agent logoff Available Unavailable Work Primary group status Secondary group status Primary queue status Secondary queue status Marking calls (# f. terminate) Third-party monitoring Tone monitoring Agent logs on Agent logs off Agent available Agent unavailable Work on Displays own group status Displays status of selected group Displays own queue status Displays queue status of selected group Agent to supervisor
ACDLOGON Agent logon
ACDSHMSG Short message to supervisor ACDEMMSG
Send emergency message Agent to supervisor
*These codes are only available with ANATE.
These codes can also be used to activate features for telephones

q q
which do not have function keys (e.g. ANATE) and where a given feature is not assigned a function key.
>
Configure codes in consultation with the customer and supplement the table on page 3-32 with the customer-specific data. Because agents may also have access to the customer table on page 3-32, it contains no information concerning silent or tone monitoring.
3-26
Digit analysis results are configured in WABE as follows:

q
Mark calls Marking code (account code or transactions code) ADD-WABE:CD=927,DAR=ACC,CHECK=N;
Monitoring Silent monitoring (third-party monitoring) (see also page 3-34) ADD-WABE:CD=928,DAR=MONSLNT,CHECK=N; Tone monitoring (see also page 3-34) ADD-WABE:CD=929,DAR=MONTONE,CHECK=N;
Agents ACD agent logon ADD-WABE:CD=930,DAR=ACDLOGON,CHECK=N; ACD agent logoff ADD-WABE:CD=931,DAR=ACDLOGOF,CHECK=N; ACD agent available ADD-WABE:CD=932,DAR=ACDAV,CHECK=N; ACD agent unavailable ADD-WABE:CD=933,DAR=ACDNAV,CHECK=N; ACD agent work ADD-WABE:CD=934,DAR=ACDWORK,CHECK=N;
Telephone status display Primary ACD group status ADD-WABE:CD=936,DAR=ACDPGS,CHECK=N; Secondary ACD group status ADD-WABE:CD=937,DAR=ACDSGS,CHECK=N; Primary ACD status of the group queue ADD-WABE:CD=938,DAR=ACDPQS,CHECK=N;
3-27
Secondary ACD status of the group queue ADD-WABE:CD=939,DAR=ACDSQS,CHECK=N;

q
Short messages Short message ADD-WABE:CD=980,DAR=ACDSHMSG,CHECK=N; Emergency message ADD-WABE:CD=981,DAR=ACDEMMSG,CHECK=N;
3-28
3.6.5
Configuring CAF codes (AMO WABE)
CAF codes have a remote control function. In this way supervisors can, for example, assign calls to particular agents and particular groups, or select a particular RCG. Example: CAF code assignment Code 982 983 984 985 986 987 988 989 WABE CP CAFGRAV CAFGRNAV CAFGROFF CAFAV CAFNAV CAFLOGOF CAFAFWD CAFDFWD Feature CAF group available CAF group unavailable CAF group logoff CAF agent available CAF agent unavailable CAF agent logoff CAF call forwarding on CAF call forwarding out 982 + group no. 983 + group no. 984 + group no. 985 + agent no. 986 + agent no. 987 + agent no. 988 + RCG address + forwarding destination 989 + RCG address
CAF => Control of Agent Feature (only with telephones with CAF authorization)
Conditions for using CAF functions In order to call up CAF codes at a telephone, it must have CAF authorization. This authorization is assigned using the AMO SDAT. CHA-SDAT:STNO=3520,TYPE=ATTRIBUT,DATTR=,AATTR=AGENT&AUTOLOG&SUPER&CAF&...; Digit analysis results are configured in WABE as follows: CAF group available: CAF group not available: CAF group logoff: CAF agent available: CAF agent not available: CAF agent logoff: CAF RCG call forwarding on: ADD-WABE:CD=982,DAR=CAFGRAV,CHECK=N; ADD-WABE:CD=983,DAR=CAFGRNAV,CHECK=N; ADD-WABE:CD=984,DAR=CAFGROFF,CHECK=N; ADD-WABE:CD=985,DAR=CAFAV,CHECK=N; ADD-WABE:CD=986,DAR=CAFNAV,CHECK=N; ADD-WABE:CD=987,DAR=CAFLOGOF,CHECK=N; ADD-WABE:CD=988,DAR=CAFAFWD,CHECK=N;
CAF RCG call forwarding off: ADD-WABE:CD=989,DAR=CAFDFWD,CHECK=N;
3-29
CAF group available/group unavailable/group logoff

q
Group unavailable Dial code for "CAF group unavailable" (e.g. CAF code 982). Enter the number of the group in question.
Group available Dial code for "CAF group available" (e.g. CAF code 983). Enter the number of the group in question .
Group logoff Dial code for "CAF group logoff" (e.g. CAF code 984). Enter the number of the group in question. This removes the group from call distribution. A confirmation tone is output.
CAF agent available, agent unavailable, agent logoff Use the AMO ACDSD to define whether the number or ID is to be entered.
q
Agent available An agent with status "unavailable" or "work" is now available for call distribution. Dial code for "CAF agent available" (e.g. CAF code 985). Enter the number and agent ID of telephones with status "unavailable" and "work".
Agent unavailable (e.g. pause) Dial code for "CAF agent unavailable" (e.g. CAF code 986) Enter the number of the telephone and agent ID, for which the pause function is to be activated.
Agent logoff This removes the agent from call distribution. Dial code for "CAF agent logoff" (e.g. CAF code 987). Enter the number and ID of the telephone or agent which is to be logged off.
3-30
CAF call forwarding of a Route Control Group (RCG, see page 4-26) This allows an RCG to be forwarded to another destination (e.g. night destination)
q
Activate call forwarding for a RCG Dial the code for call forwarding (e.g. CAF code 988). Wait for the signal tone. Enter the RCG number (CAFDN and not the RCG index). Use the RCG number (CAFDN) which you have used to the configure the RCG in the WABE. Enter the destination number to which the calls to this RCG are to be rerouted. The forwarding destination can also be another ACD number. A confirmation tone is output. In this way the RCG is forwarded to the corresponding destination.
Cancelling call forwarding (activating day destination) Dial the code for "cancel call forwarding (e.g. CAF code 989). Wait for the tone. Enter the RCG address for which call forwarding is to be cancelled.
3-31
Codes for activating FlexRouting features The table below must be supplemented with the codes which each individual customer should dial. This table should be made available to all supervisors and agents. Code Feature Account code Agent logon Agent logoff Agent available Unavailable Work Primary group status Secondary group status Primary queue status Secondary queue status Headset Automatic call pickup Short message to supervisor Send emergency message Short message to agent Acknowledgment Scroll key with LED CAF group available CAF group unavailable CAF group logoff CAF agent available CAF agent unavailable CAF agent logoff Marking calls Agent logon Agent logoff Terminates "unavailable" and "work" modes Agent unavailable Work Displays own group status Displays status of selected group Displays own group queue Displays queue of selected group Switches between available/unavailable Switchover on/off Agent to supervisor Agent to supervisor Supervisor to agent Confirm short message Scroll through short messages CAF code: group available CAF code: group unavailable CAF code: group logoff CAF code: agent available CAF code: agent unavailable CAF code: agent logoff
3-32
Code
Feature CAF forwarding on CAF forwarding off CAF code: call forwarding on CAF code: call forwarding off
3-33
3.6.6
Tone monitoring/silent monitoring

Silent monitoring and tone monitoring In certain countries, these features may only be activated in consultation with the customer, and where necessary, with employee representatives. Written customer authorization must be provided.
The supervisor can use these features to monitor agent calls which are currently in progress. The supervisor microphone is switched off when this feature is in use.
q q
With tone monitoring, agents and callers hear the conference tone. With silent monitoring, agents and callers are not informed that the supervisor is monitoring the call.
Procedure 1. Activate silent and tone monitoring for all calls:

q
Tone monitoring CHA-ZAND:TYPE=ACD,MONTONE=YES;
Silent monitoring This feature is unnauthorized in Germany and can thus only be activated where password level 5 authorization exists. SET-ZAND:MONSLNT=YES; Password: Enter the level 5 password.
2.
Configure digit analysis results This allows silent and tone monitoring to be activated using a speeddial code. ADD-WABE:CD=928,DAR=MONSLNT,CHECK=N; ADD-WABE:CD=929,DAR=MONTONE,CHECK=N; CD DAR=MONSLNT DAR=MONTONE Number used to display the feature on the supervisor telephone Silent monitoring (no tone) Tone monitoring
>
3.
Only extensions with the corresponding authorization can be used for monitoring purposes.
Authorize the supervisor to monitor agent calls.
3-34
Call monitoring must be activated individually for each agent. CHA-SDAT:STNO=AgentNr,TYPE=ATTRIBUT,AATTR=CBSTMON; STNO Number of member for which monitoring is authorized. AATTR=CBSTMON Configures an attribute: The agents calls may be monitored. 4. Authorize the supervisor for silent monitoring CHA-SDAT:STNO=SupervisorNr,TYPE=ATTRIBUT,AATTR=CASTMON; STNO Supervisor member number. This extension can be used for monitoring purposes.
AATTR=CASTMON The station is authorized to monitor agent calls. 5. Now define whether the agents ID or number must be entered in order to activate monitoring CHA-ACDSD:TYPE=SYS,AGTTARGT=EXT and ID AGTTARGT=EXT AGTTARGT=ID To monitor agent calls, the EXTENSION is entered. To monitor agent calls, the AGENT ID is entered.
>
In FlexRouting, the entries EXT or ID refer to the following features:

q q q
Short messages CAF Silent and tone monitoring
3-35
If you wish to monitor a call: 1. Press the following on a telephone authorized for monitoring: a) b) 2. The Silent Monitoring and Tone Monitoring keys or Enter the code for silent monitoring and tone monitoring.
Now enter the processor number of the agent whose calls you wish to monitor: a) If you have used the AMO ACDSD, TYPE=SYS to define that the agent ID is to be used: E N T E R C O D E N U MB E R
b)
If you have used the AMO ACDSD, TYPE=SYS to define that the agent number is to be used: E N T E R E X T E N S I O N
When a correct processor number is entered but

q
monitoring is not authorized for this agent, the function is aborted and a message is output. When configuring agents, monitoring authorization must be defined individually for each agent (AMO SDAT). this agent is already being monitored by another supervisor, the function is also aborted and a message is output.
>
With tone monitoring, an override tone is output at intervals during the conversation being monitored. This notifies the agent and caller that the call is being monitored.
3-36
3.6.7
Automatic Incoming Call Signaling (AICS)
The AICS (Automatic Incoming Call Signaling) facility can be used for automatically connecting telephone calls to the agent. When a call arrives, the agent hears a ZIP tone", and is then immediately connected to the caller. The agent does not have to perform any actions in order to collect the call. AICS is permitted only in conjunction with digital telephones 1. which have a configurable headset key or a headset adapter that notifies the system when a headset has been plugged in. These headsets can be broken down into two types: a) Modular headset (headset instead of earpiece) This is a headset without any hardware detection facility. With this headset, the system is not able to recognize whether a headset has been inserted in the telephone or not. In order to activate these headsets, a button must be provided on the telephone. The headset is activated/deactivated by pressing the headset button. b) Jack headset (headset and ear piece) This headset type requires a special hardware detection facility that notifies the system whether a headset is connected to the telephone or not. With this headset type, the agent does not need to press a button in order to notify the system that a headset has been connected to the telephone. 2. which are equipped with an additional function key and a key table that enables automatic call acceptance to be activated/deactivated. This key is known as the Auto/Manual" key. For telephones that are supplied with a headset, it is possible for the system to automatically switch over to automatic call acceptance with the following activities: When the headset is connected When the headset button is pressed When the Auto/Manual" button is pressed.
3-37
Setting up ACD in Hicom Configuring short messages and emergency messages
3.9
Configuring short messages and emergency messages
Short messages are configured using the AMO ACDSD, TYPE=MSG. CHA-ACDSD:TYPE=MSG,MESSAGE="<Text>",MSGCAT=<TYPE>[,MSGNUM=<n>]; MSGCAT EMER: AGENT: SPV:: MESSAGE [MSGNUM] Examples
q
1 emergency message can be configured up to 8 messages "Supervisor to agent" up to 8 messages "Agent to supervisor"
Text field max. 24 characters (preassigned with blank spaces as default). Number of given message (agent and supervisor only)
Short messages: supervisor to agents CHA-ACDSD: TYPE=MSG,MESSAGE="#1: supervisor to agent",MSGCAT=AGENT,MSGNUM=1; CHA-ACDSD: TYPE=MSG,MESSAGE="#8: supervisor to agent",MSGCAT=AGENT,MSGNUM=8;
Short messages: agent to supervisors CHA-ACDSD: TYPE=MSG,MESSAGE="#1: agent to superv.",MSGCAT=SPV,MSGNUM=1; CHA-ACDSD: TYPE=MSG,MESSAGE="#8: agent to superv.",MSGCAT=SPV,MSGNUM=8;
Emergency short message CHA-ACDSD:TYPE=MSG,MESSAGE="Help required!!!",MSGCAT=EMER;
Alerting tone Deactivate: Activate: CHA-SDAT:STNO=x...x,TYPE=ATTRIBUT,DATTR=,AATTR=DNDSR; CHA-SDAT:STNO=x...x,TYPE=ATTRIBUT,DATTR=DNDSR;
3-39
Setting up ACD in Hicom Configuring short messages and emergency messages
Display DIS-ACDSD:TYPE=MSG,MSGCAT=AGENT; ACD SHORT MESSAGES MSGCAT AGENT ... MSGNUM 1 MESSAGE Supervisor to agent
3-40
4
1.
ACD numbers (Service numbers) This refers to the numbers which the customer dials. The properties of an ACD number are defined in the DNIT table.
Set up "incoming call => agent telephone" link
2. 3. 4.
DNIT tables (DNIT => Directory Number Information and Translation) RCG (Route Control Groups) Calendar for a) b) each of the 7 days of the week special days and national holidays
5. 6.
Shift numbers which can be assigned to the weekdays and special days. ART (ACD Routing Tables) Each shift is linked to an ACD Routing Table. The shift numbers define the routing table assigned to a shift. Several shift numbers can also be linked to a single ACD Routing Table.
4-1
Overview of tables processed for FlexRouting Primary DNIT table (Type=DNI) ACD number (with source no. if applicable) The starting point is generally the primary DNI table, where the INTRTDN parameter = ACD number.
The result is a: Route Control Group (RCG) RCG (index)
Specific calendar days and weekdays Check the shift number which applies to this Route Control Group (RCG)
The result is a Shift number Shift number and time DNI tables for "destinationbased routing only" DNI tables for "destination/ source-based routing" Primary DNI table DNI GDTR rules Secondary DNI table Shift numbers ACD Routing Tables page 4-11 page 4-13 page 4-24 page 4-21 page 4-20 page 4-35 page 4-26 The ART which was created for this shift number and time is executed ACD Routing Table (ART)
4-2
Structural overview: searching for the ACD Routing Table which applies to the caller
ACD call
DNI table Number analysis AMO WABE
AMO DNIT : TAB=DNI INTRTDN x (primary table) ROUTING=DRTSA or DRTD GDTRRULE DISPLAY
Type of number analysis Destination
Destination and source number

ROUTING = DRTSA GDTRRULE = d
RCG PRI OVRPRI
AMO DNIT : TAB=GDTR
number only
ROUTING = DRTD AMO DNIT GDTRRULE DGTSTR Rule for source analysis ROUTING INTRTDN i ROUTING Internal routing address number
AUDSRCID THRSHLD e f INTRTDN i INTRTDN i (secondary table) ROUTING = SA GDTRRULE DISPLAY RCG RCG (Route Control Group) ..........
Calendar routing
AMO ACDRS : TYPE = CR SUN MON z x x x x y z
Has todays date been programmed in CR?
CR=Calendar Routing
AMO ACDRS : TYPE = RS
No
RCG, weekday
Shift number
AMO ACDRS : TYPE = DS Yes DSNUM x, Time DSNUM x, Time
TUE WED THU FRI SAT
DSNUM DSNUM xx Shift Set A (End of shift) SHIFT EOSART Time c ART 1 00:00-07:59 EOF = YES/NO 08:00-15:59 SHIFT EOS Time ART d ART x
y z ART c routing steps ACTION (Announcement1) Step 1 Value routing steps Step 2 Value ACTION (Announcement...) Step 3 Value Step24 ACTION Step Step 5 max. 64 max. 16 Value Value e
ACD Routing Tables for shifts

AMO ACDRT
EOS = YES/NO Shift Set
max. 1020
max. 4000
4-3
Configuring FlexRouting Configuring Route Control Groups and ACD numbers
4.1
Configuring Route Control Groups and ACD numbers
Incoming ACD calls are routed to a DNIT table. RCG and ACD numbers must already exist in order to set up the DNIT tables. ACD call ACD number: 93511 RCG address 9620 with RCG 100 ACD number => RCG (index) The ACD number is used to access the DNIT table. The call is subsequently routed with RCG.
4.1.1
Configuring ACD numbers
ACD numbers are the numbers dialled by the customer to access ACD. Use the AMO WABE to configure ACD numbers as follows: ADD-WABE:CD=93501,DAR=STN,CHECK=NO; ADD-WABE:CD=93502,DAR=STN,CHECK=NO; ADD-WABE:CD=93503,DAR=STN,CHECK=NO; .... ADD-WABE:CD=93511,DAR=STN,CHECK=NO;
CD=station number
4-4
4.1.2
Configuring Route Control Groups
The Route Control Group is a table of the AMO ACDSD, TYPE=RCG. Each Route Control Group comprises
q q
the RCG address (internal number of RCG for CAF) and the RCG index (also referred to as RCG). The RCG index determines the shift number which applies to a given call.
Explanation
The ACD numbers are subsequently assigned to the RCGs in the DNIT tables (see page 4-7). An incoming call with an ACD number is routed to the DNIT table which lists this ACD number as INTRTDN. The DNIT table assigns (amongst other things) an RCG (RCG index) to the call. The next routing step is based on the RCG identified for the call. In conjunction with the day and time, the RCG determines the shift number which applies to the call in question. A joint RCG can also be assigned to several ACD numbers (see page 4-10) Procedure Configuring an RCG address in the WABE ADD-WABE:CD=9260,DAR=RCG,CHECK=NO; ADD-WABE:CD=9261,DAR=RCG,CHECK=NO; ADD-WABE:CD=9262,DAR=RCG,CHECK=NO; e.g. RCG address 9260 e.g. RCG address 9261 e.g. RCG address 9262
Configuring a Route Control Group

CHA-ACDSD:TYPE=RCG,RCG=100,CAFDN=9260; CHA-ACDSD:TYPE=RCG,RCG=101,CAFDN=9261; CHA-ACDSD:TYPE=RCG,RCG=102,CAFDN=9262; TYPE=RCG RCG=<1...1020> CAFDN=1-6-digit Create RCG table Range of RCG index: 1-1020 RCG address or RCG number Users with CAF require this number in order to set up call forwarding for the RCG (see also page 3-31 and page 1-9). add RCG 100 add RCG 101 add RCG 102
4-5
Changing an RCG address It is not possible to modify an RCG address (e.g. 9260) directly. Proceed as follows to change an RCG (RCG index e.g. 100):
q q
delete CAFDN (e.g. 9260) and RCG (CHA-ACDSD:RCG,100,*;) then create the RCG index (e.g. 100) with the new CAFDN value (e.g. 9280).
4-6
Configuring FlexRouting Configuring DNIT tables
4.2
Configuring DNIT tables
In general, a separate DNIT table (TYPE=DNI) is provided for each ACD number. 2 tables can be set up with the AMO DNIT:
q
DNI table (Directory Number Information) DNIT table, TAB=DNI ACD call INTRTDN 93511 ACD number: 93511 RCG 100 with RCG address 9620 ROUTING - DRTD GDTRRULE - 0 DISPLAY "ACD 93511" RCG - 100 (RCG index) PRI - 10 OVRPRI - 5 AUDSRCID THRSHLD - *
The DNI table contains routing and display information to identify the calling and called parties. The AUDSRCID field for Audible Source Identification (see page 2-1). The customer does not hear this announcement. It is used to audibly identify the source of the call when the agent answers the call (e.g. "call from Spain").
q
GDTR table (General Digit Translation) see from page 4-13 onwards GDTR tables are set up if routing is based on the source number. A source number or source numbering plan can be recorded in each GDTR rule. An individual DNIT table can also be assigned as the destination. Using the country code on the agent display, a message such as "Call from USA" for example, can thus appear on the agent display.
4-7
Configuring DNIT tables ADD-DNIT:TAB=DNI,INTRTDN=93511,ROUTING=<PARAM>,GDTRRULE=<NO.>, Display="ACD VIA 95511",RCG=100,Pri=10,Ovrpri=5,AUDSRCID=1,THRSHLD=*; INTRTDN<NO. ACD number to which the parameters of this DNIT table are to be assigned.
ROUTING=<PARAM> DRTD: destination-based routing (see page 4-11) DRTSA: destination/source-based routing (see page 4-13) SA: the table is a continuation of DRTSA GDTRRULE=<no.> DISPLAY=<TEXT> RCG=100 PRI=10 OVRPRI=5 AUDSRCID=1 GDTRRULE must be =0 if ROUTING=SA GDTRRULE must not be equal to 0 if ROUTING=DRTSA Text which appears on the agent display RCG index which is entered in the calendar routing (ACD number => RCG index) and the daily routing tables <1...64> Priority determining position of the call in the call queue (1=max. priority). <1...64> Priority of call if it is routed to an overflow group (1=max. priority). Number of announcement port for "audible source identification". If an announcement number is specified here, this announcement is played to that agent when the agent answers a call (e.g "Call from USA") Use the announcement number set up with the AMO RCSU (see page 2-1). Max. number of simultaneous callers to a DNI, see also page 4-25 THRSHLD=* This value extends the ACD routing functions to all callers who use this ACD number. This is generally the case, as all callers should hear at least one ACD announcement rather than a busy tone. This also ensures that all callers using this ACD number are included in the ACD statistics. These statistics are analysed by ACDApp on the ACD server. THRSHLD=<no.> This value limits the number of calls that can be added to the call queue under a given ACD number. If the number of calls in the queue for this ACD number corresponds to <no.>, all subsequent callers hear a busy tone. Calls which were not answered (busy tone) are not included in the statistics.
THRSHLD
4-8
Automatic increase in priority A meter automatically increases the priority of the waiting callers at a programmable interval (between 0 and 300 seconds). This interval is set with the AMO ACDSD (see page 3-7). CHA-ACDSD:TYPE=SYS,QFACTOR=<no.>; 0 = no increase, 110 at intervals of 1 second, 15300 at intervals of 5 seconds . . . the next step Incoming ACD calls are forwarded to the DNIT table where the INTRTDN corresponds to the ACD number. Further routing is determined by the configuration of the corresponding DNIT table (destinationbased or destination/source-based). ... see following pages for subsequent procedures: 1. 2. Notes on assigning a joint RCG to several ACD numbers, see page 4-10. DNIT tables for destination-based routing Set up the following: 3. DNIT tables with TYPE=DNI: only primary DNI tables, ROUTING=DRTD, see page 411
DNIT tables for destination/source-based routing Set up the following: DNIT tables with TYPE=DNI: secondary DNI tables, ROUTING=SA, see page 4-20 DNIT tables with TYPE=GDTR: GDTR rules, see page 4-21 DNIT tables with TYPE=DNI: primary DNI tables, ROUTING=DRTSA, see page 4-24
The source number (if available) is analysed with these DNIT tables.
4-9
Assigning a joint RCG to several ACD numbers If several ACD numbers have the same routing destination, it may be advisable to use the same RCG in the DNIT tables with these ACD numbers. If the same RCG is entered in several DNIT tables for different ACD numbers, each individual ACD number retains its own priority, display text etc. via the DNIT table. Example: you wish to assign a joint RCG to several ACD numbers ... Assign the same RCG to the following DNIT tables to simplify call forwarding for the supervisor:
q
INTRTDN = 93511 is assigned RCG=100 Announcement="Call from Portugal", PRI=10, OVRPRI=5, AUDSRCID=7, THRSHLD=* INTRTDN = 93512 is assigned RCG=100INTRTDN Announcement="Call from Spain", PRI=10, OVRPRI=5, AUDSRCID=6, THRSHLD=* INTRTDN = 93551 is assigned RCG=100 Announcement="Siemens VIP", PRI=1, OVRPRI=1, AUDSRCID=1, THRSHLD=*
>
The call forwarding destination can also be another ACD number!
4-10
4.2.1
Configuring DNIT tables for destination-based routing
This section describes how to set up DNIT tables for destination-based routing without source number analysis. Prerequisit: The ACD numbers and RCG tables must already be set up in Hicom (see page 4-4).
+-----------------------------------------------------------------------+ | INTRTDN - 93511 | | GDTRRULE - 0 DISPLAY - ACD 93511 ROUTING - DRTD | | RCG - 100 PRI - 10 OVRPRI - 5 AUDSRCID - 7 THRSHLD - * | +-----------------------------------------------------------------------+ | INTRTDN - 93512 | | GDTRRULE - 0 DISPLAY - ACD 93512 ROUTING - DRTD | | RCG - 100 PRI - 5 OVRPRI - 5 AUDSRCID - 6 THRSHLD - * | +-----------------------------------------------------------------------+ | INTRTDN - 93551 | | GDTRRULE - 0 DISPLAY - ACD VIA 93513 ROUTING - DRTD | | RCG - 100 PRI - 1 OVRPRI - 1 AUDSRCID - 1 THRSHLD - * | +-----------------------------------------------------------------------+
ACD call Number dialled: 93511 ROUTING=DRTD No source number check GDTRRULE=0 GDTR rules are not applied in the case of destination-based routing.
AMO DNIT : TAB=DNI INTRTDN 93511 ROUTING=DRTD (primary only) GDTRRULE=0 DISPLAY "ACD 93511" RCG (index) - 100 PRI - 10 OVRPRI - 5 AUDSRCID - 7 THRSHLD - * INTRTDN 93512 ROUTING=DRTD (primary only) GDTRRULE=0 DISPLAY "ACD 93512" RCG (index) - 100 PRI - 2 OVRPRI - 1
Calendar routing AMO ACDRS: TYPE = CR
AUDSRCID - 6 THRSHLD - *
4-11
Configuring DNIT tables for destination-based routing The DNIT table is executed once in the case of destination-based routing. The parameters entered in this table determine subsequent routing. Set up a separate DNIT table for each ACD number. ADD-DNIT:TAB=DNI,INTRTDN=93511,ROUTING=DRTD,GDTRRULE=0,DISPLAY="ACD VIA 95511",RCG=100,PRI=10,OVRPRI=5,AUDSRCID=7,THRSHLD=*; ROUTING=DRTD GDTRRULE=0 RCG=100 PRIO=10 OVRPRI=5 AUDSRCID=7 THRSHLD=* DRTD=destination-based routing No digit translation <1...1020> RCG index which is entered in the calendar routing and daily routing tables <1...64> Priority determining the position of the call in the call queue <1...64> Priority of call in overflow group Number of announcement port for "audible source identification" *=unlimited <no.> maximum number of calls which may be simultaneously waiting in the call queue
DISPLAY="ACD93511" Text which appears on the agent display
The DNIT parameters are described in more detail on page 4-7.
4-12
4.2.2
Configuring DNIT tables for destination/source-based routing
This section describes the DNIT tables for destination/source-based routing with source number analysis. Prerequisite: The ACD numbers and RCG tables must already be set up in Hicom (see page 4-4). The following tables must be set up with the AMO DNIT for destination/source-based routing (page 4-21): The following sequence must be observed when creating tables in Hicom: 1. Set up secondary DNI tables These are the DNIT tables with TYPE=DNI, parameter ROUTING = SA (DNI: Directory Number Information) These tables must be created first as their INTRTDN parameters are used as the destination in the GDTR rules. 2. Set up GDTR rules These are the DNIT tables with TYPE=GDTR (General Digit Translation Rules) The DNI tables with ROUTING=SA previously set up are used as the destination for the source numbers in question. 3. Set up primary DNI tables These are the DNIT tables with TYPE=DNI, parameter ROUTING=DRTSA The DNI tables with ROUTING=DRTSA are set up last as the GDTR rule previously created for the source number analysis is entered in these tables. An incoming ACD call is routed to the DNI table with ROUTING=DRTSA. The system checks to see if a GDTR rule exists for the source number. If a rule is found, the GDTR rule returns the INTRTDN of a DNIT table (SA) as the forwarding destination. The source number can be identified in a number of ways:
q
using the A subscriber number (if available) received via an analog line (e.g. MFC signalling) using the A subscriber number (if available) received via a digital line (e.g. ISDN signalling) internal source number.
4-13
Example: You are setting up FlexRouting at a retail company (see picture on next page). You wish to have the following appear on the display when handling queries:
q q
the name of the customer the customer number.
Procedure: 1. Create a DNIT table with the ROUTING parameter SA for the customer "ACD Siemens Muenchen", for example. Enter the following in this table: ADD-DNIT:TAB=DNI,ROUTING=SA,INTRTDN=93581,GDTRRULE=0, DISPLAY="ACD Siemens Muenchen"...; Also create a DNIT table with ROUTING=SA for customer number "N20142": ADD-DNIT:TAB=DNI,ROUTING=SA,INTRTDN=93522,GDTRRULE=0, DISPLAY="SNI N20142"...; 2. Create a separate GDTR rule for source number identification as several employees from this customer place orders: GDTR rule 1 for Siemens AG Muenchen ADD-DNIT:TAB=GDTR,GDTRRULE=1,DGTSTR=0897221233,INTRTDN=93581; ADD-DNIT:TAB=GDTR,GDTRRULE=1,DGTSTR=0897221234,INTRTDN=93581; ADD-DNIT:TAB=GDTR,GDTRRULE=1,DGTSTR=08972249429,INTRTDN=93581; GDTR rule 1 for SNI ADD-DNIT:TAB=GDTR,GDTRRULE=1,DGTSTR=089636151*,INTRTDN=93522; 3. The last step entails creating the DNIT table with the routing parameter "DRTSA". ADD-DNIT:TAB=DNI,ROUTING=DRTSA,INTRTDN=93521,GDTRRULE=1,...; 93521 is the number dialled by the customer Source number analysis: GDTR rule for the source number
q q
The primary DNIT contains rules governing source number analysis. The "primary DNIT" parameters are applied if no rules have been defined for the source number.
4-14
1.
2. 3.
+-----------------------------------------------------------------------+ | INTRTDN - 93581 | | GDTRRULE - 0 DISPLAY - ACD Siemens Muenchen ROUTING - SA | | RCG - 110 PRI - 2 OVRPRI - 2 AUDSRCID - 1 THRSHLD - * | +-----------------------------------------------------------------------+ ADD-DNIT:TAB=GDTR,GDTRRULE= 1,DGTSTR= 0897221233,INTRTDN=93581; ADD-DNIT:TAB=GDTR,GDTRRULE= 1,DGTSTR= 0897221234,INTRTDN=93581; +-----------------------------------------------------------------------+ | INTRTDN - 93521 | | GDTRRULE - 1 DISPLAY - ACD VIA 93521 ROUTING - DRTSA | | RCG - 100 PRI - 2 OVRPRI - 2 AUDSRCID - 4 THRSHLD - * | +-----------------------------------------------------------------------+
ACD call Dialled number: 93521 Source number: 089722-1234
AMO DNIT : TAB=DNI INTRTDN 93521 ROUTING=DRTSA (primary table) GDTRRULE= 1 GDTR rule 1 The parameters 0897221233,93581 of this DNIT are 0897221234,93581 used for routing if no GDTR rule has been defined GDTR rule 2 for this source #,93601 number 0044******,93610
Rule exists for source number
The call is routed to the DNIT table with the ACD number 93581.
INTRTDN 93581 ROUTING - SA (secondary table) GDTRRULE - 0 DISPLAY RCG index 110 PRI - 2 OVRPRI - 2 AUDSRCID - 4 THRSHLD - *
Calendar routing AMO ACDRS: TYPE = CR
4-15
Source number analysis: GDTR rule with numbering scheme

q q
The primary DNIT contains rules governing source number analysis. Part of the source number is defined as a GDTR rule.
4-16
1.
+-----------------------------------------------------------------------+ | INTRTDN - 93610 | | GDTRRULE - 0 DISPLAY - Call from England ROUTING - SA | | RCG - 144 PRI - 2 OVRPRI - 2 AUDSRCID - 1 THRSHLD - * | +-----------------------------------------------------------------------+ ADD-DNIT:TAB=GDTR,GDTRRULE= 2,DGTSTR= #,INTRTDN=93601; ADD-DNIT:TAB=GDTR,GDTRRULE= 2,DGTSTR= 0044******,INTRTDN=93610; ADD-DNIT:TAB=GDTR,GDTRRULE= 2,DGTSTR= 0044*******,INTRTDN=93610; +-----------------------------------------------------------------------+ | INTRTDN - 93521 | | GDTRRULE - 2 DISPLAY - ACD VIA 93521 ROUTING - DRTSA | | RCG - 100 PRI - 2 OVRPRI - 2 AUDSRCID - 1 THRSHLD - * | +-----------------------------------------------------------------------+
2.
3.
ACD call Dialled number: 93521 Source number: 0044 151 2241
AMO DNIT : TAB=DNI INTRTDN 93521 ROUTING=DRTSA (primary table) GDTRRULE= 2 GDTR rule 2 GDTR 2 contains a #,93601 rule with "#" 0044******,93610 As a result, no analysis of primary table 0044*******,93610 GDTR rule 3 .....
A rule exists for the source number INTRTDN 93610 ROUTING - SA (secondary table) The call is routed to the DNIT table with the ACD number 93610. GDTRRULE - 0 DISPLAY RCG index 144 PRI - 2 OVRPRI - 2 Calendar routing AMO ACDRS: TYPE = CR AUDSRCID - 1 THRSHLD - *
4-17
Source number analysis: GDTR rule "#" for general translation

q q
The primary DNIT contains rules governing source number analysis. The rule "#" is applied if no rule has been defined for the source number.
4-18
1.
+-----------------------------------------------------------------------+ | INTRTDN - 93610 | | GDTRRULE - 0 DISPLAY - Call from England ROUTING - SA | | RCG - 144 PRI - 2 OVRPRI - 2 AUDSRCID - 1 THRSHLD - * | +-----------------------------------------------------------------------+ ADD-DNIT:TAB=GDTR,GDTRRULE= 2,DGTSTR= #,INTRTDN=93601; ADD-DNIT:TAB=GDTR,GDTRRULE= 2,DGTSTR= 0044******,INTRTDN=93610; ADD-DNIT:TAB=GDTR,GDTRRULE= 2,DGTSTR= 0044*******,INTRTDN=93610; +-----------------------------------------------------------------------+ | INTRTDN - 93521 | | GDTRRULE - 2 DISPLAY - ACD VIA 93521 ROUTING - DRTSA | | RCG - 100 PRI - 2 OVRPRI - 2 AUDSRCID - 1 THRSHLD - * | +-----------------------------------------------------------------------+
2.
3.
ACD call Dialled number: 93521 Source number: 0043 179510
AMO DNIT : TAB=DNI INTRTDN 93521 ROUTING=DRTSA (primary table) GDTRRULE= 2 GDTR rule 2 GDTR 2 contains a #,93601 rule with "#" 0044******,93610 0044*******,93610 As a result, no analysis of primary GDTR rule 3 table .....
Rule # for this source number
INTRTDN 93601 As the # rule exists, the call is routed to the DNIT table with the ACD number 93600. ROUTING - SA GDTRRULE - 0 ANZEIGE RCG index 120 PRI - 2 OVRPRI - 2 AUDSRCID - 1 Calendar routing AMO ACDRS: TYPE = CR THRSHLD - *
4-19
4.2.2.1
Configuring secondary DNI tables (parameter ROUTING=SA)
First set up the secondary DNI tables. The GDTR rules refer to these tables when translating numbers. The parameter ROUTING=SA is assigned to secondary tables. Pseudo numbers The ACD numbers to be entered as the INTRTDN parameter in secondary DNI tables are pseudo numbers. These pseudo numbers must also be set up in the WABE. They must not, however, be disclosed externally. Set up a separate DNIT table for each GDTR rule. ADD-DNIT:TAB=DNI,INTRTDN=93601,ROUTING=SA,GDTRRULE=0, DISPLAY="ACD VIA 95521",RCG=100,PRI=10, OVRPRI=5,AUDSRCID=1,THRSHLD=*; ADD-DNIT:TAB=DNI,INTRTDN=93610,ROUTING=SA,GDTRRULE=0, DISPLAY="Please speak English",RCG=120,PRI=10, OVRPRI=5,AUDSRCID=1,THRSHLD=*; INTRTDN=<no.> ROUTING=SA GDTRRULE=0 DISPLAY=<Text> RCG=<1...1020> PRI=<1...64> OVRPRI=<1...64> AUDSRCID=1 THRSHLD=* PSEUDO ACD number SA=SIDANI entry No GDTRRULE in a secondary DNI table Text which appears on the agent display This entry is used to find the shift number which is valid for this call Priority determining the position of the call in the call queue Priority of call in overflow group Number of announcement port for "audible source ID" *=unlimited <no.>=max. no. of calls for this DNI.
The DNIT parameters are described in more detail on page 4-7.
4-20
4.2.2.2
Configuring GDTR rules
Each GDTR rule can comprise several entries. The AMO DIMSU, parameter GDTR defines the number of translation entries per GDTRRULE. The DNIT table GDTR lists the translation rules for destination/source-based routing. A maximum of 128 translation rules can be defined under one GDTRRULE.
q
Routing with GDTRRULE ACD calls are generally routed to the DNI table where the INTRTDN corresponds to the ACD number. This is a primary DNI table. If this primary DNI table states that ROUTING=DRTSA, the system checks the assigned GDTRRULE to see if a translation destination is available for the source number supplied (DRTSA=source-based routing). The call is routed on the basis of the parameters entered in the primary DNI table if no rule has been defined for the source number. If a rule has been defined for the source number, the secondary DNI table entered in the GDTR rule for this source number is assigned to the call.
GDTRRULE and GDTR rule The GDTR rule refers to the assignment of a source number to a secondary DNI table.
GDTRRULE with the entry # The system first checks whether an entry for the source number exists if # is entered in GDTRRULE. If no entry is available, the call is routed to the secondary table provided as the destination for the entry #.
GDTRRULE with the entry "*" (asterisk) The * dummy acts as a wild card (representing any digit). As the source numbers of incoming calls may vary in length, all possible source numbers must be entered in a GDTRRULE. Example of * entry in a GDTRRULE 089****** 089******* 089******** etc. The prepared A number is used when analysing the source number (Hicom Private Numbering Plan).
4-21
Example: GDTRRULE and its destination the secondary DNI table Set up one GDTRRULE to take orders in several languages. Define one GDTR rule for each possible country code in this GDTRRULE:
q
ACD group 101 contains agents who speak English and French. RCG 112 routes to an ART with group 101. ACD group 102 contains agents who speak Spanish and Portuguese. RCG 117 routes to an ART with group 102. Interworking of GDTRRULE and associated destination DNI tables Entries in GDTRRULE=1 Source no. 001********* 0044******** 0033******** 0034******** 00351******** Destination DNI 97001 97002 97003 97021 97022 Destination DNI tables (SA) INTRTDN 97001 97002 97003 97021 97022 Display Call from USA Call from GB Call from France Call from Spain Call from Portugal RCG 112 112 112 117 117
Further processing of RCG RCG from page 47 onwards Calendar/daily routing page 4-39 Defines the shift number valid for the day and RCG in question Shift number page 4-37 The shift number specifies the time and the ACD Routing Table valid for the caller in question 2.
ART page 4-26
Configuration sequence: 3.
1.
It may be advisable to configure a joint GDTR rule for each RCG if several ACD numbers have been merged under a joint RCG (s. page 4-10). Exception: if you are only configuring one single GDTR rule in total.
q
No general translation (no "DGTSTR = #") In this instance, all source-based calls where a GDTR rule has been defined for the source number are routed to the destination of the GDTR rule. Routing is carried out irrespective of the ACD number dialled. Calls without a GDTR rule are routed on the basis of the primary DNI table.
4-22
With general translation ("DGTSTR= #") In this instance, the ACD number dialled is not analysed if no GDTR rule has been defined for the source number.
AMO DNIT, GDTR table ADD-DNIT:TAB=GDTR,GDTRRULE= 1,DGTSTR= #,INTRTDN=2224; GDTRRULE=<1..128> Index entered in the primary DNI table. DGTSTR INTRTDN The number of entries is determined by the entry in the DIMSU parameter "GDTR".Translate GDTRRULE. Refers to the INTRTDN of the destination DNI. Only secondary DNI tables may be specified (i.e. DNI tables with parameter "ROUTING=SA".
Example: Configuring GDTR tables All calls with source numbers "001" and "0044" are to be answered by an English-speaking agent. Calls with source number "0033" are to be answered by a French-speaking agent. Prerequisite: You have already set up the secondary DNI tables INTRTDN=2224, INTRTDN 2201 and INTRTDN=2233, which further differentiate the calls appropriately with the RCG entries. ADD-DNIT:TAB=GDTR,GDTRRULE= 1,DGTSTR= #,INTRTDN=2224; ADD-DNIT:TAB=GDTR,GDTRRULE= ADD-DNIT:TAB=GDTR,GDTRRULE= ADD-DNIT:TAB=GDTR,GDTRRULE= ... ADD-DNIT:TAB=GDTR,GDTRRULE= ADD-DNIT:TAB=GDTR,GDTRRULE= ADD-DNIT:TAB=GDTR,GDTRRULE= ADD-DNIT:TAB=GDTR,GDTRRULE= ... ADD-DNIT:TAB=GDTR,GDTRRULE= ADD-DNIT:TAB=GDTR,GDTRRULE= ADD-DNIT:TAB=GDTR,GDTRRULE= ADD-DNIT:TAB=GDTR,GDTRRULE= ... ADD-DNIT:TAB=GDTR,GDTRRULE= 1,DGTSTR= 001*,INTRTDN=2201; 1,DGTSTR= 001**,INTRTDN=2201; 1,DGTSTR= 001***,INTRTDN=2201; 1,DGTSTR= 001*********,INTRTDN=2201; 1,DGTSTR= 0044*,INTRTDN=2201; 1,DGTSTR= 0044**,INTRTDN=2201; 1,DGTSTR= 0044***,INTRTDN=2201; 1,DGTSTR= 0044*********,INTRTDN=2201; 1,DGTSTR= 001*,INTRTDN=2233; 1,DGTSTR= 001**,INTRTDN=2233; 1,DGTSTR= 001***,INTRTDN=2233; 1,DGTSTR= 001*********,INTRTDN=2233;
The primary DNI table with the parameter ROUTING=DRTSA must then be set up. This refers to GDTRRULE=1. 4-23
4.2.2.3
Configuring primary DNI tables (parameter ROUTING=DRTSA)
The last step entails setting up the primary DNI tables. These are the first tables to be assigned to incoming ACD callers.
>
Destination/source-based routing The parameter ROUTING=DTRSA must be set in the case of destination/source-based routing. A GDTR rule must be specified in DNI tables with ROUTING=DRTSA.
Prerequisite: The ACD numbers and RCG tables have already been set up in Hicom (see page 4-4). GDTRRULE has already been set up. Procedure: Set up a primary DNIT table for each ACD number. ADD-DNIT:TAB=DNI,INTRTDN=93521,ROUTING=DRTSA,GDTRRULE=1, DISPLAY="ACD VIA 95521",RCG=120,PRI=10,OVRPRI=5,AUDSRCID=1,THRSHLD=*; INTRTDN=<no.> ROUTING=DRTSA GDTRRULE=1 DISPLAY=<Text> RCG=<1...1020> PRI=<1...64> OVRPRI=<1...64> AUDSRCID=1 ACD number disclosed externally Destination/source-based DNI table Number of GDTR rule specified Text which appears on the agent display RCG index entered in the calendar routing tables Priority determining the position of the call in the call queue Priority of call in overflow group Number of announcement port for "audible source ID"
The DNI parameters are described in more detail on page 4-7.
4-24
Configuring FlexRouting Configuring the ACD call threshold
4.3
Configuring the ACD call threshold
The threshold defines the maximum number of incoming ACD calls. There are 2 ways of dealing with an overload situation (i.e. too many simultaneous ACD calls) with FlexRouting: Trunk limitation ACDTHRH=20 Trunk limitation ACDTHRH=18 DNIT table INTRTDN 93511 ROUTING=DRTD GDTRRULE=0 DISPLAY ACD VIA 93511 Trunk limitation ACDTHRH=12 In the above example, the 26th caller who dialled the ACD number 93511is not included in the queue. The caller hears a busy tone. 1. AMO BUEND, parameter ACDTHRH CHA-BUEND:TGRP=<x1>,ACDTHRH=<y1>; <y1>: Max. no. of lines in a trunk group for ACD calls This defines the maximum number of callers who can reach ACD via a given trunk group. The AMO BUEND is generally used to restrict the number of incoming calls for the ACD system. 2. AMO DNIT, parameter THRSHLD You can also define the maximum number of callers that can be queued for a given ACD number in the ACD DNIT tables (see page 4-4). RCG index - 100 PRI - 10 OVRPRI - 5 AUDSRCID - 1 THRSHLD - 25
>
Set the threshold for calls to be rejected with the busy tone as high as possible. Callers prefer to hear a message advising them that they may have to wait for a few minutes than to hear a busy tone. Calls which have exceeded the threshold are not included in ACD statistics. An ACD trunk group must be set up for incoming trunk lines in order to apply the threshold to these lines.
q
q
4-25
Configuring FlexRouting Configuring ART (ACD Routing Tables)
4.4
Configuring ART (ACD Routing Tables)
On completion of the DNIT tables, configure the ACD Routing Tables (ART). Further processing of RCG RCG
from page 4-7 onwards
Calendar/daily routing page 4-39 Defines the shift number valid for the day and RCG in question
Shift number page 4-37 The shift number specifies the time and the ACD Routing Table valid for the caller in question 2.
ART
Configuration sequence: 3. ART ACD Routing Tables
1.
The ART defines the routing steps which can be applied to an ACD call. Example: 1. 2. 3. 4. Delay ringback if no agent is available (DELAYRB) Route to recorded announcement (RTREC) Route to ACD group (RTGRP) Route to music (RTMUS) From this point on, the system searches in the group for a free agent while music is played to the caller. 5. 6. 7. Wait x seconds (WTSEC x, 0=unlimited) Route to overflow group x (RTGRP) ...
Number of routing steps in an ART An ART can comprise up to 64 routing steps. ART memory is allocated in blocks of 16 steps. Hence an ART with 17 entries occupies the same amount of memory as 32 steps. Number of ACD Routing Tables in Hicom A maximum of 4000 ARTs can be set up if each ART contains an average of 16 steps.
4-26
The AMO ACDRT is used to set up ACD Routing Tables.
*17 *18 *19 *20 *21 *22 *23 *24 *25
DIS-ACDRT:ART=19; H500: AMO ACDRT STARTED +------------------------------------------------------------+ | ART 19 MAXSTEP 32 ACDRS REFERENCES 1 | +-----+---------+---------+----------------+-----+----+------+ | | | | | DES.|TEST| | |STEP |ACTION |PARAMETER|VALUE |COND.|COND|VALUE | +-----+---------+---------+----------------+-----+----+------+ | 1 DELAYRB 5 | | 2 RTREC AUDSRCID 2 | | 3 RTGRP ACDGRP 1 | | 4 RTGRP ACDGRP 2 | | 5 RTGRP ACDGRP 3 | | 6 RTGRP ACDGRP 4 | | 7 RTGRP ACDGRP 5 | | 8 RTGRP ACDGRP 6 | | 9 RTGRP ACDGRP 7 | | 10 RTGRP ACDGRP 8 | | 11 RTGRP ACDGRP 9 | | 12 RTGRP ACDGRP 10 | | 13 RTGRP ACDGRP 11 | | 14 RTGRP ACDGRP 12 | | 15 RTGRP ACDGRP 13 | | 16 RTGRP ACDGRP 14 | | 17 RTGRP ACDGRP 15 | | 18 RTGRP ACDGRP 16 | | 19 RTGRP ACDGRP 17 | | 20 RTGRP ACDGRP 18 | | 21 RTGRP ACDGRP 19 | | 22 RTGRP ACDGRP 20 | | 23 RTGRP ACDGRP 21 | | 24 RTGRP ACDGRP 22 | | 25 RTGRP ACDGRP 23 | | 26 RTGRP ACDGRP 24 | | 27 RTGRP ACDGRP 25 | | 28 RTMUS MUSNUM 1 | | 29 WTSEC SEC 0 | | 30 SKIP | | 31 SKIP | | 32 SKIP | +------------------------------------------------------------+ max. 64 steps
Note RTGRP 1-16 and *17 - *25

The call is inserted in the queue of all groups if no agent is free in groups 116. The system only checks groups 17 to 25 once to see if an agent is free as a call can only be entered in a maximum of 16 queues. If no agents are free in groups 17 to 25, the system continues to look for a free agent only in groups 116.
4-27
4.4.1
Action steps of ACD routing table
The routing steps listed in the following can be applied in any order. Certain conditions must be observed with some of the steps, however. ART 1 to 15 are reserved for Service: 1. ART 1
q q
is preassigned the entry "DISCON" and cannot be modified.
2.
ART 2 to 15
q q
are preassigned the entry "DISCON" and can be modified using a SET command and password level 4.
3.
ARTs from 16 onwards can be administered as required and used for the application. Explanation Delay ringback
q q q
Parameter DELAYRB
This should be the first step in an ACD routing table. Can be used for external, CORNET and internal ACD calls. If the step DELAYRB is followed by: the step RTGRP, the caller hears a ringing tone (ringback). the steps RTGRP and RTREC and the ACD group is not available, the caller hears an announcement. the steps RTGRP and RTMUS and the ACD group is not available, the caller hears music. the steps RTGRP and DISCON and the ACD group is not available, the line is disconnected.
DISCON
Disconnect
q q q
The system disconnects the line. Used to handle calls outside office hours. This step should follow the "Route to recorded announcement" (RTREC) step. It should be the last logical step in the routing table.
4-28
Parameter COND
Explanation Conditional routing (COND): Used for a conditional GOSTEP.

q
If the condition produces the result "True", routing continues with the specified step "False", routing continues with the next step.
q q
Is based on dynamic values (status) of an ACD group. Possible values the number of available agents for comparison (VALAGT), the number of logged on agents (AGTLGN), the number of queued calls (CALQED), the oldest queued call in minutes and seconds (OLDINQ).
These values can be checked for =, , < or >.

q
Cannot refer to a step which exceeds the maximum number of steps in the ART. Number of available agents Number of logged on agents Number of queued calls Oldest call in queue (in minutes and seconds)
VALAGT AGTLGN CALQED OLDINQ GOSTEP
GOTO step xx
q q
The system routes the call to the specified step number. If step xx comes before the current step, the following actions must not take place between the current step and the target step: Delay ringback (DELAYRB) or Route to ACD group (RTGRP).
This ensures that a call is not inserted several times in a queue.
4-29
Parameter RTAGT
Explanation Route to agent

q q q q
The call is routed to the logon ID of the specified agent. The logon ID of the agent is checked. Routing continues with the next step if the agent cannot be reached. The RTGRP step must not be followed by RTAGT, if this agent is assigned to the same group! Forwards the call to the specified extension. The AMO checks that the specified extension is valid. The AMO stores the digit sequence. Routing continues with the next step if the extension cannot be reached. The destination can be an ACD routing address, a non-ACD extension or an ACD extension. Routing tables with type SA are not permitted (see page 4-20). An error is output if the extension number is not in the same ACD WABE group (AMO ZAND, standard value = 0), is not an extension number or routing address with digit analysis result STN, ATND, HUNT or ATNDIND (via ADD-WABE) or DNI (ADD-DNIT, TAB=DNI).
RTEXT
Route to extension
q q q q q
ACD extensions with digit analysis result ATND must be assigned an attendant code via the AMO VFGKZ. STN or ATNDIND must be assigned a device with the AMO SCSU/ SBCSU/SSCSU or ACSU.
Otherwise an error will be output.
4-30
Parameter RTGRP
Explanation Route to ACD group x

q q
The call is routed to the specified group number. The caller is placed on hold if no agents are available. Routing continues with the next step. A group must only be entered once in an ART. The "RTGRP" step must not be followed by a step routing the call to an agent in this group. The group number is checked.
q q
Maximum number of RTGRP entries in the routing table Each caller may be inserted in a maximum of 16 group queues (primary groups plus a maximum of 15 overflow groups).
Entering more than 15 overflow groups in the routing table

Routing can also be set up to search for free agents in more than 15 overflow groups. If the number of RTGRPs entered in a routing table exceeds 16, the system checks the subsequent groups only once to see if an agent is free. If these groups do not contain a free agent, the system continues to search only in the first 16 groups for a free agent. RTMUS Route to music
q
The system routes the call to the specified music-on-hold number (1 .. 32). The RTMUS step should be followed by the WTSEC x step (defines how long the caller hears music before routing continues with the next step). The music-on-hold number is checked.
4-31
Parameter RTOFF
Explanation Route to offsite number

q
Routes the call to an offsite number. Routes the call to a user number in a networked Hicom. Routes a call to a PhoneMail server (2 digit strings possible) Digit string for digital PhoneMail server with mailbox number: aaaaaaACDmm...m aaaaaa ACD mm...m 1-6 digits for PhoneMail number Routing ID for PhoneMail or VoiceMail server 1 to n digits for PhoneMail mailbox number
RTEXT RTVMS
q q
ADD-Richt:PM,X,,,aaaaaa; PM : address type (PhoneMail) X : index available for server access number aaaaaa: SAN (server access number) Digit string for digital PhoneMail server with CP mailbox (general mailbox number): aaaaaaACD aaaaaa ACD 1-6 digits for PhoneMail number. Routing ID for PhoneMail or VoiceMail server
ADD-Richt:PM,X,,,aaaaaa; PM : address type (PhoneMail) X : index available for server access number aaaaaa: SAN (server access number)
4-32
Parameter
Explanation continued: Route to offsite number

q
routes a call to a PhoneMail server (2 digit strings are possible) Digit string for analog PhoneMail server and mailbox number and analog PhoneMail server with CP mailbox (general mailbox number) aaaaaaACDmm....m aaaaaa ACD mm..m 1-6 digits for PhoneMail number. Routing ID for PhoneMail or VoiceMail server 1 to n digits for mailbox number
ADD-Ziel:EVMTAB,FWDANS,aaaaaa; EVMTAB FWDANS aaaaaa

q
: seizure type table for the VMX server : seizure after no answer forward : VMX server number (master hunt group)
Routes a call to a VoiceMail server (1 digit string possible): Digit string for VoiceMail with mailbox number: X...XACDmm...m aaaaaa ACD mm...m 1-6 digits for VoiceMail Routing ID for PhoneMail or VoiceMail server 1 to n digits for VoiceMail mailbox number
ADD-Ziel:SERVER,VOICE,X..X; X..X: VM Access Number (number of WABE DAR VMOWN).

q q q
The AMO does not check the number. The AMO stores the digit sequence. A special access code is required for the public network. The system routes the call to the specified announcement. The announcement must be defined with OPTYPE = FIXED. The recorded announcement number is checked.
RRTREC
Route to recorded announcement

q q q
4-33
Parameter WTSEC)
Explanation Wait x seconds

q q
The connection stops for x seconds at the previous step. If this step is the first step in a routing table, the caller hears the ringing tone during the programmed delay. The delay is entered in steps of 5 seconds to max. 300 seconds. (110 s in 1-second intervals, 10300 s in 5-second intervals.) The caller waits for the call to be answered, picked up, disconnected etc. if 0 seconds is entered.
Skip
Skip to the next step Does not affect the connection routing continues with the next step.
4-34
Configuring FlexRouting Configuring daily/calendar routing and shift numbers
4.5
RCG = 100
Configuring daily/calendar routing and shift numbers

Todays date has been configured in calendar routing
+----+------+------------+---------+ |RCG |DSNUM |START DATE |END DATE | +----+------+------------+---------+ |100 | 7 | 01.01.* | 01.01.* | +----+------+------------+---------+ |100 | 22 | 06.01.* | 06.01.* | ... |100 | 7 | 25.12.* | 26.12.* | +----+------+------------+---------+ |100 | 22 | 31.12.* | 31.12.* | +----+------+--max. 32,000 entries
The RCG identified for the call is transferred to the daily or calendar routing tables.
DISPLAY "ACD 93511" PRI - 10 OVRPRI - 5 AUDSRCID - 1 THRSHLD - *
e.g. DSNUM=7
+----+------+------+------+------+------+------+------+ | |DSNUM|DSNUM|DSNUM|DSNUM|DSNUM|DSNUM|DSNUM| |RCG | SUN | MON | TUE | WED | THU | FRI| SAT | +----+------+------+------+------+------+------+------+ |100 | 7 | 5 | 5 | 5 | 5 | 5 | 7 | +----+------+------+------+------+------+------+------+ |101 | 7 | 2 | 2 | 2 | 2 | 2 | 7 | +----+------+------+------+------+------+------+------+ |102 | 7 | 11 | 11 | 11 | 11 | 11 | 7 | +----+------+------+------+------+------+------+------+ |... | | | | | | | | +----+------+------+------+------+------+------+------+ Shift indices: 0-5120
SHIFT NUMBERS
+--------+--------+------+------+ | DSNUM | SHIFT | ART | EOS | +--------+--------+------+------+ Shift no. from | 5 | 07:00 | 16 | YES | 00:00 to 07:00 +--------+--------+------+------+ Shift no. from | 5 | 20:00 | 32 | NO | 07:01 to 20:00 +--------+--------+------+------+ Shift no. from | 5 | 23:59 | 32 | NO | 20:01 to 23:59 +--------+--------+------+------+ +--------+--------+------+------+ | DSNUM | SHIFT | ART | EOS | +--------+--------+------+------+ Shift no. from | 7 | 23:59 | 32 | YES | 00:00 to 23:59 +--------+--------+------+------+
ACD Routing Tables ART 32
4-35
If todays date has not been configured in calendar routing. RCG - 100 DISPLAY "ACD 93511" PRI - 10 OVRPRI - 5 AUDSRCID - 1 THRSHLD - * Todays date has not been configured in calendar routing
Daily routing table

+----+------+------+------+------+------+------+------+ | |DSNUM|DSNUM|DSNUM|DSNUM|DSNUM|DSNUM|DSNUM| |RCG | SUN | MON | TUE | WED | THU | FRI | SAT | +----+------+------+------+------+------+------+------+ |100 | 7 | 5 | 5 | 5 | 5 | 5 | 7 | +----+------+------+------+------+------+------+------+ |101 | 7 | 2 | 2 | 2 | 2 | 2 | 7 | +----+------+------+------+------+------+------+------+ |102 | 7 | 11 | 11 | 11 | 11 | 11 | 7 | +----+------+------+------+------+------+------+------+ |... | | | | | | | | +----+------+------+------+------+------+------+------+ Shift indices: 0-5120
e.g. DSNUM=5
SHIFT NUMBERS
+--------+--------+------+------+ | DSNUM | SHIFT | ART | EOS | +--------+--------+------+------+ Shift no. from | 5 | 07:00 | 16 | YES | 00:00 to 07:00 +--------+--------+------+------+ Shift no. from | 5 | 20:00 | 32 | NO | 07:01 to 20:00 +--------+--------+------+------+ Shift no. from | 5 | 23:59 | 32 | NO | 20:01 to 23:59 +--------+--------+------+------+ +--------+--------+------+------+ | DSNUM | SHIFT | ART | EOS | +--------+--------+------+------+ Shift no. from | 7 | 23:59 | 32 | YES | 00:00 to 23:59 +--------+--------+------+------+
ART 16 ART 16 ACD Routing Table
4-36
4.5.1
Configuring shift numbers
The AMO ACDRS (ACD Route Selection) is used to administer the shift numbers, daily and calendar routing. Further processing of RCG RCG
Calendar/daily routing page 4-39 Defines the shift number valid for the day and RCG in question
Shift number The shift number specifies the time and the ACD Routing Table valid for the caller in question
ART page 4-26
Configuration sequence: 3. First configure the shift numbers. This diagram illustrates the routing sequence. The tables are set up in the opposite direction however. A shift number generally starts at 00:00 hours.
2.
1.
The 1st entry in the shift number indicates that this shift starts at 00:00 hours and ends at the time specified.
H500: AMO ACDRS STARTED +--------+--------+------+------+ | DSNUM | SHIFT | ART | EOS | +--------+--------+------+------+ | 5 | 07:00 | 16 | YES | Shift +--------+--------+------+------+ | 5 | 20:00 | 32 | NO | Shift +--------+--------+------+------+ | 5 | 23:59 | 32 | NO | Shift +--------+--------+------+------+ +--------+--------+------+------+ | DSNUM | SHIFT | ART | EOS | +--------+--------+------+------+ | 6 | 08:00 | 18 | YES | Shift +--------+--------+------+------+ | 6 | 16:00 | 32 | NO | Shift +--------+--------+------+------+ | 6 | 23:59 | 32 | NO | Shift +--------+--------+------+------+ +--------+--------+------+------+ | DSNUM | SHIFT | ART | EOS | +--------+--------+------+------+ | 7 | 23:59 | 17 | YES | +--------+--------+------+------+ +--------+--------+------+------+ AMO-ACDRS-85 ACD - ROUTE SELECTION
no. from 00:00 to 07:00 no. from 07:01 to 20:00 no. from 20:01 to 23:59
no. from 00:00 to 08:00 no. from 08:01 to 16:00 no. from 16:01 to 23:59
4-37
The shift number defines the ART which is valid for the caller. The ART determines
q q q q
which greeting announcement is played which group should be checked for a free agent which overflow groups (if applicable) should be checked for a free agent which announcement is played while the caller is on hold.
Set up shift numbers ADD-ACDRS:TYPE=RS,DSNUM=1,SHIFT=07-00,ART=16,EOS=NO,ARTDEF=32; CHA-ACDRS:TYPE=RS,DSNUM=1,SHIFT=20-00,ART=31,EOS=YES; CHA-ACDRS:TYPE=RS,DSNUM=1,SHIFT=23-59,ART=31,EOS=YES; ADD-ACDRS:TYPE=RS,DSNUM=2,SHIFT=23-59,ART=31,EOS=YES,ARTDEF=32; ADD-ACDRS:TYPE=RS,DSNUM=3,SHIFT=08-00,ART=10,EOS=NO,ARTDEF=32; CHA-ACDRS:TYPE=RS,DSNUM=3,SHIFT=16-00,ART=32,EOS=YES; CHA-ACDRS:TYPE=RS,DSNUM=3,SHIFT=23-59,ART=32,EOS=YES; DSNUM SHIFT ART Shift number The time when the shift ends. A shift always starts at the end of the previous shift plus 1 minute. ACD Routing Table Defines the ART to which the call is to be routed if this shift number has been assigned. ART see page 4-26. End-of-shift function
q
EOS
YES When the shift ends, calls in the queue must not be processed. IMPORTANT! Callers in the queue are rerouted in accordance with the calendar and daily routing steps. As a result, the time-based priority assigned to certain call is lost.
NO When the shift ends, calls in queue must still be processed by the agents.
ARTDEF
ACD Routing Table ART Preset ART, routing for remaining final shift up to 23.59 hours.
4-38
4.5.2
Configuring daily and calendar routing (AMO ACDRS)
The AMO ACDRS (ACD Route Selection) is used to administer daily and calendar routing. Further processing of RCG RCG
Calendar/daily routing Defines the shift number valid for the day and RCG in question
Shift number page 4-37 The shift number specifies the time and the ACD Routing Table valid for the caller in question 2.
ART page 4-26
Configuration sequence: 3. Day-dependent and date-dependent routing
1.
The AMO ACDRS can be used to set up day or date-dependent routing for any Route Control Group by assigning a shift number to a weekday or to a date. Daily routing (TYPE=RS) The shift numbers of a regular 7-day week are defined with daily routing. A shift number must be assigned for each weekday. ADD-ACDRS:TYPE=RS,RCG=100,DSNUMSO=1,DSNUMMO=1,...DSNUMSA=1; ADD-ACDRS:TYPE=RS,RCG=101,DSNUMSO=2,DSNUMMO=2,...DSNUMSA=2; ADD-ACDRS:TYPE=RS,RCG=102,DSNUMSO=3,DSNUMMO=3,...DSNUMSA=3; ADD-ACDRS:TYPE=RS,RCG=103,DSNUMSO=4,DSNUMMO=4,...DSNUMSA=4; ... DSNUMSO, ..MON, ...TUE, ...WED, ...THU, ..FRI, ...SAT Calendar routing (TYPE=CR) Calendar routing is used to define the shift numbers on national holidays and special days. A maximum of 32,000 entries are possible in the calendar routing table. ADD-ACDRS:TYPE=CR,RCG=100,STARTMON= 12,STARTDAY= 25,ENDMON= 12,ENDDAY= 25, DSNUM= 2; ADD-ACDRS:TYPE=CR,RCG=101,STARTMON= 7,STARTDAY= 28,STARTYR= 1997,DSNUM= 2; ADD-ACDRS:TYPE=CR,RCG=102,STARTMON= 12,STARTDAY= 28,STARTYR= *,ENDMON= 1, ENDDAY= 2,ENDYR= *,DSNUM= 3;
4-39
Siemens
Informativo Tccnico
BATCHPARACRIAOBSICADEGRUPOSACD 1) WABE ADDWABE:*00,,,ACDLOGON,N,,,,,,,,;/*logon*/ ADDWABE:#00,,,ACDLOGOF,N,,,,,,,,;/*logoff*/ ADDWABE:*01,,,ACDAV,N,,,,,,,,;/*disponivel*/ ADDWABE:#01,,,ACDNAV,N,,,,,,,,;/*indisponivel*/ ADDWABE:*02,,,ACDWORK,N,,,,,,,,;/*pausa*/ ADDWABE:*03,,,MONSLNT,N,,,,,,,,;/*monitoraosilenciosa*/ ADDWABE:*04,,,WHISANN,N,,,,,,,,;/*sussurro*/ ADDWABE:793021,,,RCG,N,,,,,,,,;/*cdigovirtualparagrupodecontrolederoteamento*/ ADDWABE:783021,,,STN,N,,,,,,,,;/*PILOTODOGRUPOACD*/ ADDWABE:6666,,,STN,N,,,,,,,,;/*PILOTODOGRUPOACD*/ 2) ZAND CHANGEZAND:ACD,YES,NO,,NO,NO,NO,YES; CHANGEZAND:ACD,NO,,0,,NO,NO,YES; CHANGEZAND:ACD,YES,,,,NO,NO,YES;/*liberaaplicaoFlexrouting*/ setzand:yes;/*liberamonitoraosilenciosa(DIGITAREMMNSCULO!!!)*/ 3) ZANDE CHANGEZANDE:TYPE=ACD,WHISANN=YES;/*liberaafacilidadesussurro*/ 4) TAPRO(ramaldosupervisor) ADDON,MONTONE,ACDPGS,WHISANN 5) TAPRO(ramaldoagente) ACDLOG,ACDAV,ACDNAV,ACDWORK
6) SDAT(atributodoramaldoagente) CHANGESDAT:1101,ATTRIBUT,AGENT&CBSTMON; 7) SDAT(atributodoramaldosupervisor) CHANGESDAT:2100,ATTRIBUT,AGENT&SUPER&CASTMON; 8) ACDSD(comprimentodassenhasdosagentesemdodemonitorao) CHANGEACDSD:SYS,4,10,ID,3,500,YES,NO,NO,NO; /*associaodocontroledefacilidadeaocdigovirtualdercgcriadonoWABE*/ CHANGEACDSD:CAFRCG,31,793021; 9) ACDGP /*criaodogrupoACDassociandooramalsupervisor2100*/ ADDACDGP:31,NORMAL,FIFO,2100,YES,NO; 10) AGENT /*criaodossenhasdelogonparaogrupo31*/ ADDAGENT:1001,31,1,NORMAL,0,,0; ADDAGENT:1002,31,2,NORMAL,0,,0; ADDAGENT:1003,31,3,NORMAL,0,,0; 11) RCSU /*criaodaPENparamusicaemespera1dogrupoACD31*/ ADDRCSU:1168,1,YES,CONT,RANDOM,0,,G711&G729AOPT&ML&VIAHHS,ACDMUS,1;
12) ACDRT /*criaodospassosdachamadaparaogrupo31*/ ADDACDRT:31,6; CHANGEACDRT:31,ARTSTEP,1,DELAYRB; CHANGEACDRT:31,ARTSTEP,2,RTGRP,31; CHANGEACDRT:31,ARTSTEP,3,RTMUS,1; CHANGEACDRT:31,ARTSTEP,4,WTSEC,300; CHANGEACDRT:31,ARTSTEP,5,GOSTEP,3; CHANGEACDRT:31,ARTSTEP,6,SKIP; 13) ACDRS /*criaodobasicdayshift*/ ADDACDRS:DS,31,2359,31,NO,31; ADDACDRS:RS,31,31,31,31,31,31,31,31; 14) DNIT /*criaodospilotosparaogrupoACD31associadoaRCG31combloqueiodechamadasacobrar*/ ADDDNIT:DNI,783021,DRTD,0,"PILOTOPARATESTE",YES,31,64,0,0,*,FORB; ADDDNIT:DNI,6666,DRTD,0,"PILOTOVERDADEIRO",YES,31,64,0,0,*,FORB;
hwdin4000install.fm Configurando o PABX HiPath 4000 Pressuposies
4 Configurando o PABX HiPath 4000

Este captulo proporciona instrues e exemplos para configurar o PABX HiPath 4000 V2.0, V3.0 e V4.0 para se comunicar com o HiPath ProCenter. Os exemplos de PABXs foram criados para orient-lo nos fluxos de roteamento simples, incluindo o roteamento de emergncia, que corresponde s faixas de telefonia padro predefinidas no HiPath ProCenter. Nota: Se precisar configurar fluxos mais complexos ou estratgias de roteamento de emergncia, siga os exemplos dados no captulo e defina os valores adicionais. Para obter mais informaes sobre seu ambiente, entre em contato com seu representante de atendimento ao cliente. Complete as sees neste captulo. Aps ter configurado o PABX HiPath 4000, continue com a implementao, seguindo as diretrizes a seguir no Guia de Instalao e Manuteno.
4.1 Pressuposies
Supe-se que: O PABX est operacional e totalmente funcional. Teste para certificar-se de que o PABX pode fazer e receber chamadas externas. Os tcnicos de manuteno tenham acesso irrestrito ao PABX. Isto necessrio para configurar o PABX. Cuidado: Somente pessoal devidamente treinado deve tentar configurar este PABX. Tentativas de configurar o PABX por pessoal que no seja devidamente treinado podem afetar de forma negativa a operao do HiPath ProCenter.
55
hwdin4000install.fm Configurando o PABX HiPath 4000 Antes de comear
4.2 Antes de comear

Antes que seja possvel configurar o PABX, ser necessrio fazer o seguinte: Obtenha um endereo de IP para UNIX. Se voc estiver usando o recurso Config-Sync (sincronizao da configurao), no ACDAPP, crie um nome e senha de usurio para o HiPath ProCenter.
Cuidado: Ao criar senhas, certifique-se de seguir as diretrizes de segurana apropriadas para seu ambiente.
Confirme se a conexo da rede atravs da rede local do PABX est disponvel. Apenas para o PABX V2.0, confirme se o PABX est licenciado atravs de um dongle para usurios e supervisores do HiPath ProCenter. (Use o AMO CODEW para verificar.) Confirme se o PABX est executando o patch correto para o nvel do software. Para obter mais informaes, entre em contato com seu representante do Servio de Atendimento ao Cliente. Conecte o servidor no qual voc pretende instalar o HiPath ProCenter rede local do PABX e rede local do cliente. Para obter diretrizes, veja Seo 4.3, Configurao da rede do HiPath 4000, na pgina 57.
56
hwdin4000install.fm Configurando o PABX HiPath 4000 Configurao da rede do HiPath 4000
4.3 Configurao da rede do HiPath 4000

O diagrama abaixo mostra como o HiPath ProCenter e o PABX HiPath 4000 se comunicam. Nota: O PABX HiPath 4000 tambm pode ser usado em um ambiente de alta disponibilidade (standby a quente) do HiPath ProCenter. Para obter mais informaes, consulte a Seo 4.10, Configurando um ambiente de alta disponibilidade (standby a quente), na pgina 69.
Figura 8
Configurao da rede
Conforme mostrado em Figura 8, h dois caminhos de comunicao que o HiPath ProCenter utiliza para se comunicar com o PABX: O primeiro caminho a ligao entre o PABX e o HiPath ProCenter pela rede local (parte inferior do diagrama). Esta rede local reservada somente para as aplicaes do PABX. A sub-rede nesta rede local, automaticamente, 192.0.2.0/24.
57
hwdin4000install.fm Configurando o PABX HiPath 4000 Compreendendo a configurao ACD
O segundo caminho a ligao entre o PABX e o HiPath ProCenter pela rede do cliente (parte superior do diagrama).
4.4 Compreendendo a configurao ACD

O seguinte fluxo proporciona um exemplo de configurao do ACD para o PABX HiPath 4000. Os nmeros entre parnteses so os nmeros padro criados pelo HiPath ProCenter.
Figura 9
Fluxo de configurao da ACD
O fluxo de configurao ACD mostrado na Figura 9 o seguinte: 1. Uma chamada chega ao PABX por um nmero discado, que traduzido a um DNIT (Dialed Number Identification Table). Um DNIT um cursor no PABX. O nmero entrante pode ser um nmero 0-800 discado diretamente ou um nmero transferido por um dispositivo front-end, como o Xpressions. Nota: Vrios nmeros piloto podem ser usados para esta etapa, todos entrando neste fluxo no PABX. 2. Para o HiPath ProCenter, o DNIT deve apontar para um RCG (Grupo de Controle de Roteamento) do HiPath ProCenter. 3. O RCG faz referncia a um Grupo de Turnos. O grupo de turnos determina o fluxo da chamada do PABX durante as horas do dia. Certifique-se de que este Grupo de Turnos esteja configurado apropriadamente para seus turnos, como uma operao 24x7x365.
58
4. O Grupo de turnos faz referncia a uma ART, que a Tabela de roteamento do ACD no PABX. A TRA configurada para fazer verificaes especiais que asseguram que o aplic encontra-se em funcionamento. Para obter mais informaes, consulte o Seo 4.4.1, Sobre o mecanismo de heartbeat, na pgina 60. 5. Se o heartbeat estiver operacional, o PABX roteia a chamada para um grupo ACD do HiPath ProCenter. As chamadas deste grupo so monitoradas pelo HiPath ProCenter. Aps a chamada chegar neste grupo, o HiPath ProCenter roteia a chamada de acordo com o fluxograma configurado no aplicativo HiPath ProCenter Manager (para obter mais informaes, veja o Guia de Administrao do Manager). Se a chamada ainda estiver na fila do PABX aps 15 segundos, o PABX verificar novamente o status do HiPath ProCenter. Se ele estiver em funcionamento, a chamada permanecer na fila, esperando que o HiPath ProCenter faa o roteamento. 6. Se o heartbeat no est em estado operacional, o PABX precisar rotear a chamada. No caso padro, deve-se adicionar uma etapa aps o ART instruir o PABX para enviar todas as chamadas para um DNIT alternativo at que a comunicao seja restabelecida entre o PABX e o HiPath ProCenter. 7. O DNIT alternativo aponta para um GCR de emergncia. 8. O GCR de Emergncia aponta para um Grupo de Turno de Emergncia. O Grupo de Turno de Emergncia pode ser configurado no PABX de maneira a corresponder com a abertura ou fechamento da central de contatos. O padro definido para uma central de contatos 24x7x365. Para obter mais informaes, veja Seo 4.7, Configurao do roteamento de emergncia, na pgina 62. 9. Se a central de contatos estiver aberta, ento as chamadas sero roteadas para a ART de Emergncia. A ART de Emergncia far o PABX rotear todas as chamadas para o Grupo ACD de Emergncia. Este grupo onde todos os usurios so configurados no PABX. Observe que no existe roteamento inteligente dentro deste grupo no PABX. 10. Se voc configurar o Grupo de Turnos para refletir quando a central de contatos estiver fechada, as chamadas sero roteadas para o destino na ART de Emergncia Alternativa. Sugestes para o destino incluem HiPath Xpressions ou um operador.
59
4.4.1 Sobre o mecanismo de heartbeat

Um mecanismo de monitorao (heartbeat) usado por todos os PABXs para determinar se o HiPath ProCenter est funcionando adequadamente. Se o PABX detectar que o HiPath ProCenter no est funcionando corretamente, o PABX rotear as chamadas usando a lgica de emergncia configurada no PABX. O mecanismo de monitorao (heartbeat) usar mensagens do CSTA rede local de PABX. A TRA que contm o grupo ACD do HiPath ProCenter (padro 100), contm ART steps que fazem o monitoramento do grupo ACD de heartbeat. As etapas da ART asseguram que as chamadas estejam sendo feitas para o Grupo do ACD do heartbeat e que as chamadas sejam desconectadas no intervalo adequado. Se houver um problema na comunicao entre o HiPath ProCenter e o PABX, o PABX rotear as chamadas de acordo com as etapas definidas no exemplo de tabela TRA. Exemplo de tabela TRA As etapas predefinidas de roteamento das chamadas do HiPath ProCenter com verificao de heartbeat so:
Etapa 1 CHANGE-ACDRT:100,ARTSTEP,1,HEARTCND,HPPC,20,6; Etapa 2 CHANGE-ACDRT:100,ARTSTEP,2,RTGRP,100; Etapa 3 CHANGE-ACDRT:100,ARTSTEP,3,WTSEC,15; Etapa 4 CHANGE-ACDRT:100,ARTSTEP,4,HEARTCND,HPPC,20,6; Etapa 5 CHANGE-ACDRT:100,ARTSTEP,5,GOSTEP,3; Etapa 6 CHANGE-ACDRT:100,ARTSTEP,6,RTEXT,7891;
Observe que 100 o grupo ACD padro para o HiPath ProCenter que criado pelo arquivo de macro e 7891 o nmero DNIT padro que faz referncia estratgia de emergncia para o cliente. No exemplo acima, o PABX esperar 20 segundos para que o HiPath ProCenter envie uma mensagem ao CSTA pela rede de PABX. Se a mensagem for recebida, o PABX roteia a chamada para um grupo ACD do HiPath ProCenter. Se a chamada no for roteada a um usurio em 15 segundos, o PABX verificar o sinal de monitorao (heartbeat) novamente. As etapas 3 e 4 so repetidas at a chamada ser roteada para um usurio. Se por qualquer motivo o heartbeat falhar, o PABX passar para a etapa 6 (e quaisquer etapas subseqentes, conforme desejar), que relaciona a estratgia de emergncia.
60
hwdin4000install.fm Configurando o PABX HiPath 4000 Carga das configuraes da CSTA no PABX
4.5 Carga das configuraes da CSTA no PABX

O HiPath ProCenter e o PABX comunicam-se atravs de CSTA. O PABX notificar o HiPath ProCenter sobre chamadas que necessitem de roteamento e, depois, o HiPath ProCenter instruir o PABX sobre como rotear as chamadas. As configuraes do CSTA padro, que so carregadas pelo representante do suporte tcnico do cliente, so mostradas abaixo. Nota: Se voc estiver conectando mais de uma mquina do servidor principal do HiPath ProCenter a um nico PABX HiPath 4000, as configuraes de CSTA (como o nmero do aplicativo) configurado no PABX e no Adaptador de Conectividade (CA4000) devem ser exclusivas para cada mquina do servidor HiPath ProCenter.
Configuraes de CSTA do HiPath 4000 ADD-CPTP:DPCON,55,"PROCID5","192.0.2.25"; ADD-CPTP:APPL,55,"ACM55","PROCID5","APPL55",YES,102,102,"ACM55","APPL55"; ADD-ACMSM:,55,ACLAPPL,"APPL55","ACM55","PROCID5",CB,"CSTAGW",Y,1020,1020; ADD-XAPPL:55,"APPL55","APPLICATION_55",,Y; CHANGE-XAPPL:SUBAPPL,55,D25,ACCOUNT&AGASSIGN&AGENT&ABANDON&QUEUED,; CHANGE-XAPPL:SUBAPPL,55,D25,REDIRECT&LOGON&RCGDISC&RCGSEL&DIGDIALD,; CHANGE-XAPPL:MONCB,55,D25,RCG,; EXE-UPDAT:BP,ALL; EXE-UPDAT:A1,ALL;
4.6 Carregando as configuraes da ACD no PABX

O HiPath ProCenter foi projetado para trabalhar com as configuraes padro (mostradas abaixo), que so carregadas pelo representante de atendimento ao cliente. Nota: Se voc estiver conectando mais de uma mquina do servidor principal do HiPath ProCenter a um nico PABX HiPath 4000, o nome do aplicativo (HPPC padro) e os recursos (ramais, grupos ACD, etc.) devem ser exclusivos para cada mquina do servidor do HiPath ProCenter. Alm disso, o nome do aplicativo deve corresponder ao nome do aplicativo de heartbeat configurado no aplicativo HiPath ProCenter Manager.
61
hwdin4000install.fm Configurando o PABX HiPath 4000 Configurao do roteamento de emergncia
Configuraes de ACD do HiPath 4000 CHA-SDAT:<Supervisor Extension>,ATTRIBUT,AGENT&SUPER; ADD-ACDGP:100,NORMAL,FIFO,<Supervisor Extension>,YES,YES,5,20,30; /* HPPC's basic ACD group ADD-ACDGP:110,NORMAL,FIFO,<Supervisor Extension>,YES,YES,5,20,30; /* fallback ACD group ADD-WABE:7890,,,STN; ADD-WABE:7891,,,STN; ADD-WABE:7895,,,RCG; ADD-WABE:7896,,,RCG; CHA-ACDSD:CAFRCG,100,7895; CHA-ACDSD:CAFRCG,110,7896; ADD-ACDRT:100,6; CHANGE-ACDRT:100,ARTSTEP,1,HEARTCND,HPPC,20,6; CHANGE-ACDRT:100,ARTSTEP,2,RTGRP,100; CHANGE-ACDRT:100,ARTSTEP,3,WTSEC,15; CHANGE-ACDRT:100,ARTSTEP,4,HEARTCND,HPPC,20,6; CHANGE-ACDRT:100,ARTSTEP,5,GOSTEP,3; CHANGE-ACDRT:100,ARTSTEP,6,RTEXT,7891; ADD-ACDRT:110,3; CHANGE-ACDRT:110,ARTSTEP,1,RTGRP,110; ADD-ACDRS:DS,100,23-59,100,NO,100; ADD-ACDRS:DS,110,23-59,110,NO,110; ADD-ACDRS:RS,100,10,10,10,10,10,10,10; ADD-ACDRS:RS,110,11,11,11,11,11,11,11; ADD-DNIT:DNI,7890,DRTD,0,"HPPC MAIN",YES,100; ADD-DNIT:DNI,7891,DRTD,0,"HPPC BACKUP",YES,110; EX-UPDAT:BP,ALL;
4.7 Configurao do roteamento de emergncia

Se o HiPath ProCenter no estiver funcionando devidamente, imperativo que as chamadas continuem a ser atendidas pelos usurios. Os usurios os podem continuar a atender chamadas atravs do roteamento de emergncia. O conceito do roteamento de emergncia principal do HiPath ProCenter que se o HiPath ProCenter ficar indisponvel, o PABX passar a ser responsvel pelo roteamento das chamadas para os usurios disponveis que tiverem feito logon no PABX at que o HiPath ProCenter seja restaurado.
62
Como mostrado no Seo 4.4, Compreendendo a configurao ACD, na pgina 58, existe a possibilidade de se definir um roteamento de emergncia para que quando o HiPath ProCenter esteja indisponvel, as chamadas sejam roteadas para um destino predeterminado, em vez de seguirem para a central de contatos onde no haver nenhum usurio ativo.
4.7.1 Exemplo de ambiente comercial

O dilogo a seguir representa um exemplo de ambiente comercial. O formato de perguntas e respostas reflete as perguntas tpicas feitas durante uma entrevista de projeto: Pergunta: A que horas e dias a central de contatos tem usurios que fizeram logon e esto ativos? Resposta: Nossa central de contatos possui trs departamentos: vendas, suporte tcnico e faturamento. O expediente de vendas e faturamento das 09h00 s 17h00. Segunda a sexta-feira. O departamento de suporte tcnico trabalha 7 dias por semana das 7:00 h s 23:00 h. Pergunta: Para onde devem ser encaminhadas as chamadas quando a central de contatos estiver fechada? Resposta: As chamadas podem ir para o HiPath Xpressions ou para um operador disponvel 24 horas. Estes so apenas dois exemplos possveis. Aps estas perguntas terem sido respondidas, voc estar pronto para configurar o fluxograma. Para obter mais informaes, consulte Guia de Planejamento e Projeto.
4.7.2 Modificando o horrio da central de contatos

Para modificar o horrio da central de contatos para as configuraes de roteamento de emergncia no PABX, execute os AMOs de acordo com o exemplo desta seo. Cuidado: Antes de executar os AMOs, certifique-se de que o ComWin esteja conectado ao PABX e que esteja sendo executado e ativo. Para obter mais informaes sobre o ComWin, veja a documentao do PABX Hicom.
Para modificar o horrio da central de contatos: 1. Defina os nmeros do turno no PABX (cada dia com horrios diferentes). Por exemplo, execute o AMO: ADD-ACDRS:DS,100,<Shift time Start>,120,NO,120;
63
onde <Shift time Start> quando o turno termina. Deve ser inserido no formato <HH-MM> para o relgio de 24 horas. Nota: O texto Shift time Start refere-se ao horrio efetivo em que o turno termina. O parmetro AMO, no entanto, chamado de shift end. O turno vai de meia-noite at o horrio do turno comear. Supe-se que a central de contatos esteja fechada durante este tempo e que todas as chamadas que chegarem quando a central de contatos estiver fechada sejam enviadas Tabela de Roteamento da ACD 120. 2. Defina quando a central de contatos est aberta. Por exemplo, execute o AMO: CHA-ACDRS:DS,100,<Shift time End>,110,NO; onde <Shift time End> quando o turno terminar. Deve ser inserido no formato <HH-MM> para o relgio de 24 horas. Este turno vai de <shift time start> a <shift time end>. As chamadas so enviadas para a ART 110 para fins de roteamento de emergncia quando a central de contatos aberta. Ela contm uma etapa que roteia as chamadas para o Grupo ACD do Agente no PABX. 3. Feche o turno. Por exemplo, execute o AMO: CHA-ACDRS:DS,100,23-59,120,YES; Isto muda as execues de <shift time end> at o final do dia. 4. Modifique o turno. Por exemplo, execute o AMO: CHA-ACDRS:RS,110 5. Aps executar o AMO acima, ser solicitado que voc insira o seguinte: Sun = <Inserir no nmero do Turno criado para o horrio de Domingo> Mon = <Inserir no nmero do Turno criado para o horrio de Segunda-Feira>, etc. 6. Aps voc ter inserido os dias apropriados, configure o destino aps o horrio comercial na Tabela alternativa de roteamento do ACD de emergncia. Por exemplo, execute o AMO: CHA-ACDRT:120,ARTSTEP,1,RTEXT,<After hours destination number>; onde <After hours destination number> um nmero que corresponde ao destino aps o horrio comercial no projeto do HiPath ProCenter.
64
hwdin4000install.fm Configurando o PABX HiPath 4000 Configurar nmeros discveis adicionais e redirecionar destinos em fila
4.7.2.1 Exemplo de AMOs de um turno dirio de uma central de contatos

Um exemplo de um dia de um turno para uma central de contatos aberta das 7:00 s 18:00 h : Etapa 1: ADD-ACDRS:DS,120,07-00,120,NO,120; Etapa 2: CHA-ACDRS:DS,120,18-00,110,NO; Etapa 3: CHA-ACDRS:DS,12,23-59,120,YES; onde Etapa 1 define que a central de contatos est fechada das 24h00 at as 07h00, que quando ela abre. As chamadas so encaminhadas para a TRA 120 que faz a correspondncia relativa ao destino ps-expediente. Etapa 2 define o fim do horrio em que a central de contatos est aberta. No exemplo acima, a central de contatos est aberta das 07h00 s 18h00. As chamadas so enviadas para a ART 110, que envia os chamadores ao Grupo ACD do Agente. Etapa 3 fecha as 23h59. No exemplo acima, a central de contatos est fechada das 18h00 s 23h59 naquele dia. As chamadas so encaminhadas para a TRA 120. Se voc tiver horrios diferentes em dias diferentes (por exemplo, nos fins de semana), ser necessrio criar diferentes turnos para esses dias. Para fazer isso, execute os trs AMOs acima novamente, mas aumente o nmero 12 para 13, em seguida para 14, e assim por diante, para cada dia que tiver horrios diferentes.
4.8 Configurar nmeros discveis adicionais e redirecionar destinos em fila

No HiPath ProCenter, qualquer DNIT que aponte para um RCG (Grupo de controle de roteamento) monitorado pode ser utilizado como um nmero discvel ou um destino do redirecionamento em fila. Os nmeros usados para criar esses destinos devem ser criados para trabalhar dentro do plano de discagem. Nmeros discveis adicionais podem ser utilizados como nmeros de trnsito de rede para rede. Execute o AMO em cada nmero discvel ou destino de reenfileiramento que desejar criar. ADD-DNIT:DNI,<DIALABLE NUMBER>,DRTD,0,<DESCRIPTION>,YES,100;
65
hwdin4000install.fm Configurando o PABX HiPath 4000 Configurando ramais
onde <DIALABLE NUMBER> um nmero discvel no plano de discagem; <DESCRIPTION a descrio do nmero; e 100 o nmero GCR padro do HiPath ProCenter que criado pelo arquivo de macros.
4.9 Configurando ramais

Esta seo descreve como configurar ramais dos usurios e ramais do Call Director. possvel configurar ramais dos usurios, ramais do Call Director, ou ambos, dependendo de sua configurao.
4.9.1 Configurando ramais dos usurios

Se voc estiver configurando ramais dos usurios, certifique-se de que o telefone esteja devidamente configurado, executando os AMOs especificados nesta seo. Para obter mais informaes, veja a documentao do PABX HiPath 4000. Para configurar o telefone: 1. Execute o AMO TAPRO para configurar os seguintes botes no telefone: Logon/Logoff da ACD ACD Disponvel ACD Indisponvel Pausa
2. Execute o AMO SDAT para certificar-se de que os atributos do ramal contenham uma marca de classe do agente.
4.9.2 Como configurar os ramais do Call Director

Esta seo descreve como configurar ramais do Call Director. necessrio configurar os ramais do Call Director se voc planeja usar a funo Call Director para ativar mensagens interativas para chamadores. necessria uma licena para usar a funo Call Director. Nota: No configure os ramais do Call Director como logon automtico do agente porque o Call Director pode ter problemas.
66
hwdin4000install.fm Configurando o PABX HiPath 4000 Configurando ramais
Para configurar os ramais do Call Director: 1. Configure os ramais do Call Director no PABX. Isto deve ser feito por um tcnico do PABX. Para obter detalhes, consulte a Seo 4.9.2.1, Configurao de ramais analgicos e a Seo 4.9.2.2, Configurao de ramais OPST1. 2. Usando o aplicativo HiPath ProCenter Manager, configure o processador de voz. Para obter detalhes, consulte a Ajuda do Manager. 3. Usando o aplicativo HiPath ProCenter Manager, configure os ramais do Call Director. Para obter detalhes, consulte a Ajuda do Manager. Nota: Quando o sistema estiver configurado para alta disponibilidade (standby a quente), sero necessrios processadores de voz redundantes. Portanto, necessrio configurar o processador de voz de backup e um segundo conjunto de ramais do Call Director separadamente na mquina do servidor de backup. Para obter detalhes, consulte a Ajuda do Manager.
4.9.2.1 Configurao de ramais analgicos

Esta seo descreve como configurar ramais analgicos do Call Director no PABX. Para configurar ramais analgicos para o Call Director: 1. Adicione uma placa analgica (se no houver nenhuma presente). Por exemplo, execute o AMO: ADDBCSU:MTYPE=PER,LTG=1,LTU=<SHELF>,SLOT=<SLOT>,PARTNO="Q2246 -X", FCTID=0,LWVAR="0",HWYBDL=A; 2. Adicionar um ramal analgico a cada porta analgica qual se deseja conectar o Call Director. Por exemplo, execute o AMO: ADD-SCSU:STNO=<STNO>,PEN=<BOARD LOCATION>,DVCFIG=ANATE, DPLN=0,ITR=0,COS1=<COS>,COS2=<COS>,LCOSV1=1,LCOSV2=1,LCOSD1=1 ,LCOSD2=1,COSX=0,SPDI=0,COFIDX=0,SPEC=SUFDIAL, DIAL=VAR,DHPAR=DTMFST,INS=YES,SSTNO=NO, HMUSIC=0,CONN=DIR,FLASH=YES,DTMFBLK=NO; Nota: Observe que Flash = yes e DTMFBLK = NO so configuraes crticas dos ramais, necessrias para o funcionamento do Call Director. 3. Os atributos dos ramais contm a marca de classe do agente. Use o ComWin com o AMO SDAT. Para obter mais informaes, veja a documentao do PABX HiPath 4000.
67
Uw7 Assistant
7. Uw7 Assistant
Uw7 Assistant
UW7 Assistant and Tools
Siemens
Contents
1 1.1 1.2 1.3 2 2.1 2.2 2.3 HiPath 4000 Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Informations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 UBA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 HiPath 4000 Assistant menu structure and its contents . . . . . . . . . . . . . . . . . . . 7 Handling of the applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Main menu (LAP2) of the HiPath 4000 Assistant (all applications activated) . . . . . . . . 8 Contents and brief description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.3.1 Software management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.3.2 Access management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.3.3 Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.3.4 Base administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.5 Expert mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.3.6 System management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.3.7 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.3.8 chese wizart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.3.9 Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.3.10 Performance Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 2.3.11 Collecting Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Access Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Access Management Security Levels and User Accounts . . . . . . . . . . . . . . . . . . . . . 44 3.2.1 Security Levels and Predefined User Accounts . . . . . . . . . . . . . . . . . . . . . . . 44
3 3.1 3.2
BR0038
09/17/2009
Page 1 of 67
Siemens
3.2.2 4 4.1 4.2 4.3 4.4 4.5 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 6 7
System Accounts and Accounts for Network Single Logon (NSL) . . . . . . . . 46 49 49 50 51 53 55 57 57 58 59 60 61 63 64
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server and Application Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Account Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Account Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access Right Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access Right Group Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access to the HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HiPath 4300/4500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access via the Customer LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMO access via the HiPath 4000 Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Direct AMO access via the customer LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Direct AMO access via the Atlantic LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Direct AMO access via V.24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exercise for User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Solution for User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
BR0038
09/17/2009
Page 2 of 67
Siemens
1
1.1
HiPath 4000 Assistent

General
With HiPath 4000 assistent was created a new service platform apartfrom a board possibility at system entrances also many tools. The new platfrom is WEB based and automates many procedures.With the operating system Unixware 7 can be net far used now also many standards such as Telnet and FTP. Thus an almost complete integration is possible into the data world. Service access for HiPath 4300 und 4500
HTS via VPN Server
Service Techniker
TAP
The entrance of external is made by virtual private net (VPN). Each System and each Server receive a clear VPN IP-address with 10 begin
ISDN
PPP-Link
MTS
SNS-Server WAML Controller 8 RMX 9 10 UNIX 11

FAMOS
for HTS
Kunden-LAN
SNS-Server
Terminal V24 oder
SCSI
SL100
TAP
V24 to RMX
192.0.2.222 PPP-Link
Skript: Siemens.CPPP
221
.5 .3 .4 192.0.2.0 SNS-Server
Atlantic LAN .6
Access to Applcationen overr Port-Server
At least as a rule the SL100 (SL200) receives one IP adress from the customer LAN. With the delivered condition has it the IP adress 192.1.2.5
BR0038
09/17/2009
Page 3 of 67
Siemens
Service access for HiPath 4000

HTS via VPN Server
Service Technicer
TAP
The entrance of external is made by virtual private net (VPN). Each System and each Server receive a clear VPN IPadresse with 10 begin
ISDN
PPP-Link
MTS
SNS-Server Kunden-LAN
WAMLSTMI2
for HTS
TAP
Controller DSCXL Service-LAN Customer -LAN

(10)
(8/11)
SNS-Server
.3/5 Atlantic LAN 192.0.2.0
TAP over Atlantic-LAN
At least as a rule the SL100 (SL200) receives one IP adress from the customer LAN. With the delivered condition has it the IP adress 192.1.2.5
BR0038
09/17/2009
Page 4 of 67
Siemens
1.2

Informations
In each case a user may connect itself with the HiPath 4000 assistant. User furnished by UW7
GESTARTET
Disp-USER; H500: AMO USER
BENUTZER-TABELLE +---+----------+----------------+----------+---------------+-------+-------+ |UID| NAME | RECHTE | STATUS | ZUSATZ | VER- | SPERR-| | | |111111 | | | | | | | | | | SUCHE | ZEIT | | | |5432109876543210| |L|R|C|F|P|E|T|I| | (MIN) | +===+==========+================+==========+=+=+=+=+=+=+=+=+=======+=======+ | 2 | SYSTEM |.....XXXXXXXXXXX| INIT. |X X X X X| 99 | 0 | +---+----------+----------------+----------+---------------+-------+-------+ | 3 | ENGR1 |.....XXXXXXXXXXX| INIT. |X X X X | 99 | 0 | +---+----------+----------------+----------+---------------+-------+-------+ | 4 | ENGR2 |.....XXXXXXXXXXX| INIT. |X X X X | 99 | 0 | +---+----------+----------------+----------+---------------+-------+-------+ | 9 | ENGR3 |.....XXXXXXXXXXX| INIT. |X X X X | 99 | 0 | +---+----------+----------------+----------+---------------+-------+-------+ |10 | ENGR4 |.....XXXXXXXXXXX| INIT. |X X X X | 99 | 0 | +---+----------+----------------+----------+---------------+-------+-------+ |11 | ENGR5 |.....XXXXXXXXXXX| INIT. |X X X X | 99 | 0 | +---+----------+----------------+----------+---------------+-------+-------+
1.3
UBA configuration
In the UBA Unix-configurations made how:

IP-configuration. WAN-configuration. Chance the system time Server-Shutdown (only over V24 possible) and Server-Restart. The attittude of the IP-Adresse, the net mask as well as the Broadcast can be made also over the AMO UW7 after the system start. The following attitude is as standard before configures: 192.1.2.5 All IP attitudes for Unix has to be made except for few exceptions by UBA. In place of the local host list also DNS server can be used. If the IP-address is changed and / or an VPN address is furnished, then UW7 must again be started.
BR0038
09/17/2009
Page 5 of 67
Siemens
BR0038
09/17/2009
Page 6 of 67
Siemens
2
2.1
HiPath 4000 Assistant menu structure and its contents

Handling of the applications
Not all applications are activated in the standard menu structure of the HiPath 4000 Assistant. These applications must activated if required or deactivated if not required. Only activated applications are displayed in the menu system (LAP2) of the HiPath 4000 assistant. They can be created in a special main menu item or be integrated in an existing menu item as a sub menu. The activation or deactivation is carried out in the menu: Base Administration --> Application Control
Hint:
Activated application Deactivated application Its only possible to activate 2 applications in one step!
The application is located:

Utilities Separate menu Diagnostics Diagnostics Separate menu Utilities Diagnostics Utilities Separate menu Software Management Diagnostics Diagnostics Diagnostics Diagnostics
BR0038
09/17/2009
Page 7 of 67
Siemens
2.2
Main menu (LAP2) of the HiPath 4000 Assistant (all applications activated)
For content and brief description, see the following pages.
If you want to leave the HiPath 4000 Assistant, it is absolutely necessary to end the active session (closing the browser is not enough).
BR0038
09/17/2009
Page 8 of 67
Siemens
2.3 2.3.1
Contents and brief description Software management
List of all installed applications. Installation or update of applications. Deleting of applications. Detailed information of the applications. Backup and restore concepts of RMX and UNIX data. Configuration of a backup server. Configuration of an AP-Backup-Servers. GLA <-> PDS - handling. Preparation of a Recovery MOD Copy of PDS area to GLA area
Backup and restore log files. Transfer of new software (from server to HiPath 4000): - Complete RLCs or patch packages (PPs)
Immediate or time-controlled activation of the transferred software packages. VK activation (preliminary corrections). Transfer of new software (from server to HiPath 4000):With secure FTP connection - Complete RLCs or patch packages (PPs) Administration of a backup system (Hipath and switch) which is switched to in the case of a fault Administration of a Productive switch. A productive switch is a normal switch in the network and takes over the access points of another switch in the network, if this fails
BR0038
09/17/2009
Page 9 of 67
Siemens
2.3.2
Access management
Access management provides: - Management of application licenses - Management of sessions - HiPath 4000 user administration - Emergency access via the Unix user interface With the aid of the application license management, the administrator can inform himself about installed licenses and can install new licenses. This protects all HiPath 4000 applications and software subject to license that a customer would like to install. Changing the password of a registered login name. Checking the registered user. Ending the current session. Administration of HiPath4000 Assistant users. Establishing new or modifying existing HiPath 4000 Assistant users. Administration of the system users (pre-configured: engr, rsta, rcsa and cusa.) Allocation of a configured access right group to a user (what a user may do). Administration of access right groups that users can be allocated. 3 lists can be exported for the documentation on the client PC: 1. 2. 3. List of self-created login names List of login names with access right groups List of self-created access right groups with their contents
Note: Setting up a new Assistant user:

1. 2. Add a new user (User Account Administration). Set up a new access rights group or use an existing group (Access Right Group Configuration). Allocate an access right group to a user (Access Right Configuration).
Access can be made optionally via Unix login on a local console or via Telnet. Direct accesses via the Unix shell are intended for emergencies only.
3.
BR0038
09/17/2009
Page 10 of 67
Siemens
Management of the digital certificates via a secure connection to the Assistant
Creating, checking, activating and importing certificates for local systems
Existing certificates can be displayed and activated, contents can be displayed. (e.g. CA period of validity etc.
Own simple certificates can be created and then activated by menu. (without CA) Certificates issued by CA can be imported and activated. Creating through Certificate agreement contract and exporting for CA
Root certification authority for other users in the network. Sign External certificate requests Creating root certificate.
Signing of self issued certificates
BR0038
09/17/2009
Page 11 of 67
Siemens
2.3.3
Utilities
On the ACDAPP homepage, the ACDAPP application can be activated or deactivated from this Web page. In addition, the ACDAPP database can be synchronized with the HiPath 4000 PBX database. Log files for each of these actions can be displayed. The ACDAPP administrator application can be downloaded to the client PC in order to then install it on the PC (for configuration of data, e.g. ACD agents and ACD groups, used on HiPath 4000 PBX). Checking the status of the ACDAPP application (activated or deactivated). The ACD administrator application can be called up from the HiPath 4000 function window or from the Windows start menu. The ACD administrator application contains its own help information. The "Data Migration Tool (DMT)" application can be used to migrate already existing data from existing applications for the HiPath 4000 Assistant / Manager. Servers from the HiPath LAN as well as servers from a C-LAN can be monitored with the Local Alarm Agent (LAA) application. C-LAN servers must be reachable, i.e entries in the Routes table of the basic administration may be required. Use of predefined reports in the individual applications (e.g in the CM). Generation of a customer-specific report (e.g. for CM) by means of a Crystal Report (Layout Designer - chargeable software). Performance Management provides the possibility of defining reports, which appear here, without a Crystal Report. Checking of status announcements and debugging of PPP or LAN connections. Download of the API Export Table application and Interface DLL to the client PC in order to install them on the PC. This application can display HiPath 4000 tables (e.g. trunk groups, DIMSU......) on the screen or export them to the PC.
BR0038
09/17/2009
Page 12 of 67
Siemens
2.3.4
Base administration
LOGBOOK of UW7 events. Changing the VPN address which is set up by Unix Basis Administration -> WAN configuration. Modifying the VPN server address and HTS address. Settings of the: 1. LAN configuration - SL100/200 - Create Hosts table (Name <-> IP) - Enter DNS servers of the customer LAN - Define routes (Gateway) - Create Firewall entries (automatic entry (IP) as soon as a client PC has authenticated itself with user and password) WAN configuration - Set up VPN configuration with device pools (modem) for accesses System Administration - Date/time setting (Time server) - Shut down UW7 server - Activate TFTP servers for SW updates of HG2500 and HG3550
2.
3.
Activation or deactivation of applications (activated applications appear in the main menu). See also page 1.
BR0038
09/17/2009
Page 13 of 67
Siemens
2.3.5
Expert mode
Starts ComWin (must be installed on client PC) under a separate system login name (engr1-engr5) (AMO access).
File transfer to RMX (E-K areas). File transfer to UW7.
Install ComWIn application on a client PC (pay attention to revision level).
The HG3550 V2 manager offers the possibility to search for available HG3550 V2 boards.The list is created and a direct connection with WBM can be made to these boards
BR0038
09/17/2009
Page 14 of 67
BR0038
The HG 35xx Telnet/SSH application can be inserted to the support during the problem treatment and analysis by IP board into HiPath 4000 Systems. Application makes the remote access possible to the boards over a command line interface ( command line interface CLI ). The board types HG3530, HG3570 and HG 3575 are supported.
09/17/2009
Page 15 of 67
Siemens
Siemens
2.3.6
System management
Checking and, in some cases, modifying general system information and settings for the CM (only relevant for Manager), COL and PM applications. Call up of the Expert mode (direct access) for ComWin and file transfer accesses.
Checking and modifying general system information of the phone mail system. Configuration of administration access via modem or direct (Connection) with corresponding LOGIN (direct access). Entry of all HG3550 (STMI for IP trunking) installed in the system. The entry is used as a link in order to configure the corresponding HG.
BR0038
09/17/2009
Page 16 of 67
Siemens
2.3.7
Configuration Management
Display of the domain with the corresponding system.
1.
Management data (system (L) number, node number, customer name.......) and check (and, in some cases, change) status display (UPLOAD status) of the selected system. Check dimensioning (AMO DIMSU) Check COPIN settings (AMO PERSI) Check availability of languages for the digital terminals (AMO ZAND:ALLDATA2,TEXTSEL)
2. 3. 4.
BR0038
09/17/2009
Page 17 of 67
Siemens
Checking, modifying, deleting and reinstalling modules (no status display) (AMO BCSU). Checking, modifying, deleting and reinstalling of the Board Pools (STMI2) for the feature HFAStandby-Board (AMO BPOOL)
Checking, modifying, deleting and reinstalling Firewall entries (dependent on IP address) of the WAML module (AMO LANC). Checking, modifying, deleting and reinstalling Firemac (dependent on MAC- and IP address) of the WAML module (AMO LANC). Checking, modifying, deleting and reinstalling routing tables of the WAML module (AMO LANC). Checking, modifying, deleting and reinstalling ISDN-REMOTE terminals of the WAML module (AMO LANC). Checking, modifying, deleting and reinstalling network data of the WAML module (AMO LANC).
BR0038
09/17/2009
Page 18 of 67
Siemens
Checking, modifying, deleting and reinstalling COP classes (authorization for trunks). Checking, modifying, deleting and reinstalling COT classes (authorization for trunks). Administration of the overflow destinations and message waiting destination in a phone mail
Administration of the reference clock table (AMO REFTA). Control of the feature Screening (telephone number modifications) (AMO SCREN). Administration of analog and digital trunks and special trunks (AMO TACSU/TDCSU/TSCSU). Checking the code types (WABE: DAR=NETRTE) for closed numbering plan with routing information (AMO RICHT). (for UW7 database) Administration of the trunk group of the system (AMO BUEND). The T reference point is a defined interface (LTUCx) between system and the public network (country-specific) (not normally required) (AMO TREF)
BR0038
09/17/2009
Page 19 of 67
Siemens
Network definition with Ping functions of the relevant HiPath 4000 components (AMO SIPCO). AP administration with Ping functions in the system. (AMO UCSU/APRT). Partial and Complete Phone number for IPDA faults and IPDA Emergency cases dependent on the source group. (AMO APRT/SDAT) Administration of the survivability setup in the case of IP failure. (AMO SIPCO / APRT). Administration of an alternative routing to an AP for the HG3570 =STMI module (AMO APRT). Administration of an alternative routing starting from an AP for the HG3575 =NCUI module (AMO APRT).
BR0038
09/17/2009
Page 20 of 67
Siemens
Administration of ACD agents. This agent can be selected in advance (empty variants) or assigned to an ACD group already set up.
Administration of special devices for announcement/waiting music (AMO: RCSU). Administration of ACD groups. The agents are assigned to such a group. Administration of ACD numbers (WABE:DAR=RCG). As a result of this number, a call will be routed by means of the calling or called number. Administration of ACD-RCG. This references a daily routing table for the individual weekdays. Administration of ACD routing tables. These define the individual steps (e.g. 1. Announcement, 2. Allocation to a group.....) (ART). Administration of ACD shift scheduling. This defines a time plan of when which routing tables (ART) are used.
Modification and testing of general ACD system parameters.
BR0038
09/17/2009
Page 21 of 67
Siemens
Checking the status of all slots of the system. Modules can be switched in the pull down menu Action -> Execute (for details of the possible Action, see table) Also all actions for the feature HFA standby board are realized. (AMO BCSU / BSSU / BPOOL).
BR0038
09/17/2009
Page 22 of 67
Siemens
Checking the status of all slots of the system. Ports can be switched and signed off in the pull down menu, Action -> Execute (for details of the possible Action, see table) (AMO SDSU/DSSU)
Checking the status of all terminals of the system. Devices can be switched and signed on and off in the pull down menu, Action -> Execute (for details of the possible Action, see table) (AMO SDSU/DSSU).
BR0038
09/17/2009
Page 23 of 67
Siemens
Activation of module-specific features such as, e.g. call forwarding, do not disturb, voice call reject, terminal settings (volume, tone...), schedule function (AMO ACTDA). Activation of ITR group-dependent features (group do not disturb and restriction of internal traffic (ITR) (AMO ACTDA).
Selection of a night variant for the night switching of the attendant console (selected in advance in the AC group) (AMO ACTDA).
User feature activation for the feature Mobile HFA Stations can be Logged on and Logged off.Visited station and Logon Pin can be entered (DAR: MHFALGON / MHFALGOFF respectively AMO ACTDA)
BR0038
09/17/2009
Page 24 of 67
Siemens
Modification or checking of Cordless E setups. Settings of AMOs (BCSU, ZIEL etc.) that, otherwise, can only be administrated via the CAT tool are displayed. It is not possible to reset these settings. Only for a Unix database. Refers to Cordless E system data. Administration of analog and digital terminals of the system (initial configuration) with possible BUS configuration (AMO SCSU/SBCSU). In addition, the following points are administrated: 1. 2. Individual keyboard layout (AMO TAPRO). Group allocations such as call pick up group, hunt group, CHESE, COM group and key system) (AMO AUN / SA / CHESE / COMGR / KCSU). Name with organizational unit and PINs (AMO PERSI). Individual module authorizations, such as e.g. voice call, call waiting, language choice authorization... (AMO SDAT). Call forwarding control (AMO ACTDA). Adapter configurations and number of addon devices via Device combination parameter (AMO SBCSU).
3. 4.
5. 6.
Checking of a table with all portd of modules set up with status output (free or busy) and HVT data.
Checking, modifying, deleting and reinstalling of stations with the most important data (extract of AMO SBCSU / SCSU with PERSI). Checking, modifying, deleting and reinstalling of station Call Forwardings (AMO ZIEL / ACTDA).
Output of the name with department (organization) of all terminals set up in the system (AMO PERSI).
Administration of special terminals of the system such as MESSENGER, general answering (GENANS)...... (AMO SSC).
BR0038
09/17/2009
Page 25 of 67
Siemens
Checking, modifying, deleting and reinstalling module PINs of the corresponding COPIN classes (AMO PERSI:STN). Checking and modifying the three modulo procedures selected in advance for checking the PIN (AMO PERSI:MODULO). Checking and modifying general PIN data (display of the PIN of a COPIN class on the display, number of incorrect entries) (AMO PERSI: SYS/COPIN). Checking and modifying of COPIN settings, such as, e.g. pin length, type, duration, testing...) (AMO PERSI: SYS/COPIN).
Checking, modifying, deleting and reinstalling modules and VF station numbers of the system with its own status output (free or busy) (AMO WABE: DAR=STN/ATNDDID/ATNDIND). Reservation of station number ranges. Checking, modifying, deleting and reinstalling module station numbers of external nodes with their destination node numbers, destination number and traffic situation (CPS) (AMO WABE: DAR=STN). Checking, modifying, deleting and reinstalling code types for the network, such as codetypes: NETW / OWNNODE / FWDREM, with their destination node numbers and destination (AMO WABE).
BR0038
09/17/2009
Page 26 of 67
Siemens
Checking, modifying, deleting and reinstalling function directory numbers of the system, i.e. all codetypes which are not covered in the dial numbers and rote info directories (AMO WABE: DAR). Checking, modifying, deleting and reset of all virtual node numbers of the system with their ISDN and PNP entries (AMO KNDEF). Checking, modifying, deleting and reset of display subscriber number modifications (AMO KNMAT). Checking, modifying, deleting and reset of modification of the Calling Number in a specific format (Level) (AMO KNFOR). Checking, modifying, deleting and reset of the prefixes and CO exit for the numbering plans ISDN and PNP (AMO KNPRE). Conversion of a station number for which no connection level is furnished in the system to another station number (AMO RUFUM). Collection of station number digits before they are handed over to the dial plan (WABE) (AMO TWABE).
BR0038
09/17/2009
Page 27 of 67
Siemens
Checking, modifying, deleting and reinstalling authorization classes (content: Authorization and features) of the system (AMO COSSU). Not used (CHINA only) Checking and modifying the time-controlled authorization change-over (day/night) of COS1 <-> COS2 (LCOSx1/2) (AMO BERUZ). Day/night change-over of COSX groups of the system (COS1 <-> COS2) (AMO BERUM). Control of the accessibility of two modules which are assigned to different ITR groups (AMO VBZ). Checking, modifying and reinstalling ITR group-dependent features (witness and charge zone) (AMO VBZGR). Checking, modifying, deleting and reinstalling central speed dial lists (0-15) of the system and their destinations (AMO LRNGZ / ZRNGZ). Check of all key standards with associated modules (AMO TAPRO). Checking, modifying, deleting and reinstalling central device combinations, i.e. terminal type / number of add-on devices / adapter / headset / display / badge reader / hands-free... A device combination must be assigned to a module in the Module connection menu (part of AMO SBCSU / SCSU). Checking, modifying, deleting and reinstalling hotline and off-hook intercept destinations (index). The index can be assigned to the station in the Module station menu (AMO HOTLN).
BR0038
09/17/2009
Page 28 of 67
Siemens
Checking, modifying, deleting and reinstalling hunt groups of the system (AMO SA). Checking, modifying, deleting and reinstalling a call pickup group (PU group) of the system (AMO AUN). Checking, modifying, deleting and reinstalling a communication group (COM group) of the system (AMO COMGR). Checking, modifying, deleting and reinstalling night options which can be assigned to a AC group (with AMO VFGR) (AMO NAVAR). Checking, modifying, deleting and reinstalling a CHESE group of the system (AMO CHESE).
Station-specific data for the UNIX database. RMXPERSI data are accepted.
BR0038
09/17/2009
Page 29 of 67
Siemens
Management of the LCOSD in the AMO: COSSU Management of the LCOSV in the AMO: COSSU LAUTH meanings for Unix (info). Trunk groups overview with trunk group data and some trunk data. (AMO: BUEND+TDCSU). (Unix data only) Encryption procedure for LCR dialing rules (AMO:LAUTH). Management of the LCR directions for open (LCR) and closed (NWLCR) numbering plan (AMO:RICHT). Only the open numbering plan can be set up. Management of the LCR route elements for those LCR directions set up in the AMO:RICHT (AMO:LDAT). Summary of the most important LCR setups of the open numbering plan of the system (AMO:LDPLN/RICHT/LDAT). Management of the LCR dialing pattern (AMO:LDPLN). Management of the LCR dialing rules (AMO:LODR). Checking of the LCR time bands (AMO:LSCHD). Operating carrier data for Unix database. Management of forbidden digit strings in the LCR dialing patterns (AMO:LDSRT). Source group-dependent routing in different directions for the same dialing pattern (AMO:LPROF). Administration of the profile indexes Adding or deleting destination-dependent routing of LCR authorizations (LAUTH) for transit nodes (AMO:KNLCR).
BR0038
09/17/2009
Page 30 of 67
Siemens
HIM start page with system number, operating system version and hardware architecture Display of all technical data of the system, connected by links. Display of all technical data of the system in detail (single tabs of the menu item, Display all HIM Data). ????????
Dispaly from all administrat shelfs, IPDA and peripher boards (AMO BCSU)
Display from all SWU periphere, seriell line data and SCSI device (AMO ATCSM)
Display the shelf information (AMO CONSY) and memory from your HiPath 4000 system (AMO DIMSU) Display the hardware architecture and loadware information (AMO DBC) Reading the marketing licence (AMO CODEW) and technical feature (AMO FEASU)
Display the operating system (APS) and all patches in the HiPath 4000 system
Reading the software version in processor and Unix operating system
Starting or reading of REGEN files. Initial Backup and 9 additional backup files are available
BR0038
09/17/2009
Page 31 of 67
Siemens
BR0038
Configuration Wizard for the feature IPDA Configuring and/or modification of the Access Points (AMO UCSU/ APRT) Configuring the Payload and/or Signalling Survivability (AMO SDAT /APRT) Configuring the Access Point Emergency part in RMX (AMO APESU) Restart Control, Loadware loading operations, Board loading Configuring and/or modification of the STMI/STMI2 Boards (AMO BCSU) Configuring the System environment (AMO SIPCO)
09/17/2009
Page 32 of 67
Siemens
The scheduled batch created can now be used in the CM for any kind of modification or new creation, i.e. the modification or new creation is not immediately sent to RMX, but rather at the time it is generated. The assignment of the scheduled batch is carried out via the pull down menu Scheduled Batch. Protocol Log of all UW7 User actions in Configuration
Management
BR0038
09/17/2009
Page 33 of 67
Siemens
2.3.8
chese wizart
Are the HiPath 4000 V3.0 can Chesen into a run be worked on now ( e.g. Chese STN, Key Layout and allocation)
BR0038
09/17/2009
Page 34 of 67
Siemens
2.3.9
Diagnostics
The Dynamic Traffic Monitoring (DTM) application provides the option of measuring the loading (in percent) of the trunk groups set up in the system (4 trunk groups can be selected in one measurement task). The duration of the measurement can be individually specified. The ACLC-C Tracer application provides the ACL-C platform in order to transmit command from the Remote ACL-C to the system. (e.g to activate a call from STN A to STN B: $cmkcall 7140 7240 2) All available commands can be queried by entering the $chelp command. Possible control parameters for a command can be obtained with the $chelp <command>.
a) Monitoring of a digital station (optisets and optiPoints). b) Terminal take-over by the service technician from remote in order to check all functions that are to be performed on the terminal (service menu, dialing, keys, etc.) The Service Access provides the service technician with an up-to-date statement on the payload quality of the HG3530 and HG3550. Measurement values from the RTP/RTCP protocol are displayed: Package Loss, Delay Measurement, Jitter Variation. CQR: Snapshot MIB: Constant view of the RTP/RTCP measurements QoS: Graphic display over a measurement period
The HSD application provides the service technician with the option of reading error messages and alarm messages of the HiPath 4000, and to analyse and possibly to correct an error via switch functions.It is possible to call up the ALFE tool.
BR0038
09/17/2009
Page 35 of 67
Siemens
The Service Access provides the service technician with an up-to-date statement on the payload quality of the HG3570 and HG3575. Measurement values from the RTP/RTCP protocol are displayed: Package Loss, Delay Measurement, Jitter Variation. CQR: Snapshot MIB: Constant view of the RTP/RTCP measurements QoS: Graphic display over a measurement period
The RDS application provides the Service technician with the options of using trace and monitor functions. If an extension directory number is entered, this can only be monitored. If a location is entered (batch), this can be monitored or recorded with the ISDN trace. If a location (extension) is entered, this can be monitored or the Cornet-TS messages can be recorded with the ISDN tracer. Moreover, bit error rate tests and signal tests can
BR0038
09/17/2009
Page 36 of 67
Siemens
2.3.10
Performance Management
The PM application provides the option of performing selected load measurements which are based on the charge data sets (COL).
BR0038
09/17/2009
Page 37 of 67
Siemens
BR0038
09/17/2009
Page 38 of 67
Siemens
BR0038
09/17/2009
Page 39 of 67
Siemens
BR0038
09/17/2009
Page 40 of 67
Siemens
BR0038
09/17/2009
Page 41 of 67
Siemens
2.3.11
Collecting Agent
COL enables the recording of charge data which can be forwarded to the Accounting Management (AM) or the Performance Management (PM).
BR0038
09/17/2009
Page 42 of 67
Siemens
3
3.1
Access Management Overview

Introduction
Access Management is the access control component for HiPath 4000 servers. It controls which users are allowed to access a specific server, and which applications and access rights these users may use. Possible users are customer administrators and service technicians that manage HiPath/Hicom systems (e.g. HiPath 4000 and Hicom 300 releases). For those users, Access Management creates user accounts, manages their passwords, password attributes and other account-related data, and controls their access via a web browser. Further features of Access Management are:
Web Session Management Control of users that are currently logged on. Web sessions time out after a configurable amount of time the user is inactive. Web sessions can also be terminated explicitly by using the Logoff button, or the Web Session Manager.
Network Single Logon (NSL) Users can log on only once to a HiPath 4000 network server, being able to access connected HiPath 4000 systems without further authentication. Security and access control is managed via the NSL password configuration and appropriate access right configuration on the HiPath 4000 systems.
Integration of Windows (TM) Client and Server programs Windows (TM) programs are also integrated into the HiPath 4000 authentication and session concept.
Two ways are offered: Integration into the Start Page of HiPath 4000 Assistant/Manager: execution of the Windows (TM) client after web-based authentication via the Start Page of HiPath 4000 Assistant/Manager. Using an authentication library provided by Access Management that avoids the need to use a browser for log on.
BR0038
09/17/2009
Page 43 of 67
Siemens
Emergency access to Unix command shell During regular operation of HiPath 4000 servers, access to a Unix shell is not necessary, since all functions are offered via web-based or Windows (TM) client based user interfaces. For emergency cases, however, service technicians are able to access the server at Unix shell level, with the same authentication (username/password) as used for log on via a browser.
Control of system accounts For technical reasons, HiPath 4000 servers generate a predefined set of Unix accounts used internally by different applications, e.g. for accessing the Database with specific permissions, or to allow attached systems to connect. Access to these system accounts can also be controlled via Access Management. For a detailed list of system accounts please refer to Access Management Security Levels and User Accounts.
3.2 3.2.1
Access Management Security Levels and User Accounts Security Levels and Predefined User Accounts
Access Management provides five different Security Levels. Every user that logs on to a HiPath 4000 server belongs to exactly one of these levels. For four of them, predefined user accounts with initial passwords are created to grant immediate access to the HiPath 4000 server. For security reasons, the initial password must be changed when the user logs on for the first time. The table below provides a detailed overview of the Access Management security levels and predefined user accounts.
BR0038
09/17/2009
Page 44 of 67
Siemens
Security Levels Security Level PreInitial defined Password User Account

engr(1)
Unix Owner Remarks Shell Access

ICN Service Engineer (full system administration privileges). To be used in emergency cases only. Includes all other security levels Access to Unix Shell is with superuser rights (uid 0). Remote Service Technical Assistance (restricted system administration privileges). To be used by upper level service technicians. Includes security level rsca. Remote Service Customer Assistance (restricted system administration privileges). To be used by lower level service technicians. CUstomer Security Administrator (restricted system administration privileges). To be used by the customers "master" administrator(s). Includes security level cust. CUSTomer level (standard user). Individual accounts can be created at runtime to fit into the customer-specific environment.
engr
Siemens2000 yes
rsta
rsta
Siemens2000 yes
ICN Service
rsca
rsca
Siemens2000 yes
ICN Service
cusa
cusa
c.u.s.a
no
Customer
cust
--
--
no
Customer
(1) By default, logon to root is locked and can be unlocked only via engr.
Predefined User Accounts for HiPath 4000 HTS
Please note that if a HiPath 4000 Server is installed as "HTS" the predefined user names will change as follows: htssvc0 instead of engr htssvc1 instead of rsta htssvc2 instead of rsca htsadm instead of cusa Initial passwords of these users are the same as for engr, rsta etc. In case of update from a previous load, the new accounts inherit the passwords of their previous equivalent.
BR0038
09/17/2009
Page 45 of 67
Siemens
3.2.2
System Accounts and Accounts for Network Single Logon (NSL)
In addition, Access Management manages two other types of accounts that are not used for interactive logon:
System Accounts
and
Accounts for Network Single Logon (NSL)
These account types are shown and explained in the tables below.
System Accounts Account /Category System accounts syst

Unix accounts created for different purposes to assure proper operation of HiPath 4000 features and communication to their partner systems. These accounts are not used for interactive logon.
Icon
Description
BR0038
09/17/2009
Page 46 of 67
Siemens
Accounts for Network Single Logon (NSL) Account /Category Network single logon (NSL) accounts
nsl-syst
Icon
Description
Setting the password of these accounts avoids illegal access to this server via Network Single Logon (NSL). Communicate the passwords only to administrators of master systems (e.g. HiPath 4000 Manager or HiPath 4000 HTS for remote service access), where access via NSL is accepted from. System level - used for internal server-server communication of HiPath 4000 components like System Management, HiPath 4000 Expert Access/MPCID, Logging Management. Network single logon for remote access of service technicians at expert level for emergency cases (engr). Network single logon for remote access of service technicians at upper service level (rsta). Network single logon for remote access of service technician at lower service level (rsca). Network single logon for remote access of customer security administrator (cusa). Network single logon for remote access of standard (cust-level) users.
nsl-engr
nsl-rsta
nsl-rsca
nsl-cusa
nsl-cust
BR0038
09/17/2009
Page 47 of 67
Siemens
BR0038
09/17/2009
Page 48 of 67
Siemens
4
4.1
Functionality
Server and Application Access Control
Access Management ensures that every user has to authenticate against a HiPath 4000 server with a valid account name and password. In case of successful logon, a session is created. Within this session, the user is allowed to access HiPath 4000 applications according to his/her user profile only. The Access Management application itself is also included in this access control. For example, User Account Administration tasks are granted to administrators (security levels: rsta and cusa) only. By default, every user can change his/her password using. This privilege can be withdrawn by the administrator to keep passwords for certain accounts unchanged. The Web Session Manager is used to view and kill running sessions on the server. Depending on the security level of the logged-on user, sessions of other, lower-leveled users may also be listed. The main purpose of the Web Session Manager is to kill orphaned sessions that have not yet timed out. A session is orphaned if for example a user closes all browser windows without logging off explicitly. The Account Administration is only accessible for administrators. This section includes:
User Account Administration Create or delete individual (cust level) user accounts, and manage their password properties.
System Account Administration Change the password properties of HiPath 4000 server system accounts, predefined administrator accounts, and Network Security Levels (NSLs).
Access Right Configuration Assign or withdraw access right groups to/from these users, creating individual profiles.
Access Right Group Configuration Create and manage access right groups by sorting application access rights into them.
Export User Reports Display the current user and access right configuration data from the server in an HTML file. Export the data into a text file. Import the data into a spread sheet program for further editing or evaluation.
BR0038
09/17/2009
Page 49 of 67
Siemens
4.2
User Account Administration
The User Account Administration dialog is used to add users to or delete users from the system, or to modify the password properties of a selected user or group of users. All user accounts created here belong to the security level cust. To modify the access rights of these users, use the Access Right Configuration dialog.
Left Hand Side Area (User List) The columns in the left hand part of the dialog show the list of currently registered users and their account settings. Right Hand Side Area The right hand side of the User Account Administration dialog contains the following areas: Identification area, Actions area, Properties area. These areas are used to define or edit the properties of existing and new user accounts.User Accounts List, User Account Administration dialog.
BR0038
09/17/2009
Page 50 of 67
Siemens
4.3
System Account Administration
The System Account Administration dialog is used to administer a specific user group (NSL and system accounts), i.e. by adding, changing or deleting system accounts or by changing the password properties of a specific account or group of accounts. Modifications of access rights for specific user accounts or groups of accounts should be performed using the Access Right Configuration feature.
Left Hand Side Area The columns on the left hand side of the dialog show the list of accounts the current user is allowed to manage. This dialog offers the possibility to select multiple accounts and to set or change properties to the same value for multiple users with a single click. The user interface is similar to the User Account Administration dialog. When you click on Apply a dialog prompt will notify you that the password properties of multiple user accounts are being changed. To select multiple consecutive items or users, press and hold down the Shift key while selecting items/users with the left mouse key. To select multiple non-consecutive items or to de-select individual items, press and hold down the Ctrl key while selecting items/users with the left mouse key.
BR0038
09/17/2009
Page 51 of 67
Siemens
Right Hand Side Area The right hand side of the System Account Administration dialog contains the following areas: Identification area, Actions area, Properties area. These areas are used to define or edit the properties of existing and new system accounts. The list of displayed accounts is determined by the accounts that have been created on the server, and by the current users access rights, i.e.: which user is the caretaker or owner of which accounts. There are three different types of accounts, indicated by different icons:
System accounts: Unix accounts created for different purposes to assure proper operation of HiPath 4000 features and communication to their partner systems. These accounts are not used for interactive logon. Predefined administrator accounts: Accounts created for logon of other ("lower-leveled") administrators. Network Single Logon (NSL) accounts Setting the password of these accounts avoids illegal access to this server via Network Single Logon (NSL). Communicate the passwords only to administrators of master systems (e.g. HiPath 4000 Manager or HiPath 4000 HTS for remote service access), where access via NSL is accepted from. Note that all NSL accounts are open by default! This means that full access to the server via Network Single Logon is allowed without any password protection, as long as passwords are not set in the System Account Administration dialog!
BR0038
09/17/2009
Page 52 of 67
Siemens
4.4
Access Right Configuration
The Access Right Configuration dialog is used to assign available access right groups (for execution of applications) to users.
The process of assigning only some out of a large amount of access rights is simplified by assigning "access right groups. A set of predefined access right groups is available after installation. It may be expanded by new access right groups in the Access Right Group Configuration dialog. Changes in one of these access right groups will affect all users with that group assigned. The Access Right Configuration dialog is vertically divided into two panes, or areas: Users (Left Hand Side Area) The left hand side area, labeled Users, displays a two-level tree containing all available users (top level) and their assigned access right groups (lower level).
BR0038
09/17/2009
Page 53 of 67
Siemens
Access Right Groups (Right Hand Side Area) The right hand side area, labeled Access Right Groups, contains all assignable access right groups. Preview Panes Each window area has a Preview Pane (at the bottom of the window) that can be turned on and off. The Preview Panes - Access Right Configuration show the properties of the selected user or access right group. The height of the preview panes can be changed. Both the user tree and the group list have extended selection style, and menu functions are enabled depending on the selections made in these lists, both in the standard menus and in the Context menu. Selecting items To select multiple consecutive items (user accounts or access right groups, respectively), press and hold down the Shift key while selecting items/users with the left mouse key. To select multiple non-consecutive items or to de-select individual items, press and hold down the Ctrl key while selecting items/users with the left mouse key.
BR0038
09/17/2009
Page 54 of 67
Siemens
4.5
Access Right Group Configuration
The Access Right Group Configuration dialog is used to create and modify access right groups.
Access right groups are used to administer the rights of users to execute and use applications. The process of assigning only some out of a large amount of access rights is simplified by assigning pre-defined "access right groups", as described in Assigning/Withdrawing Access Rights, Access Right Group Configuration dialog. A set of predefined access right groups is available after installation. Additional access right groups can be created and modified in the Access Right Group Configuration dialog. Changes in one of these access right groups will affect all users with that group assigned. Use the Access Right Configuration dialog to assign access right groups to specific users.
BR0038
09/17/2009
Page 55 of 67
Siemens
BR0038
09/17/2009
Page 56 of 67
Siemens
Access to the HiPath 4000
With HiPath 4000 assistant a new service platform is created which offers also many new service tools besides an extended system access. The new platform is Web-based and automates many events. With the UW7 platform it is also possible to use existing network wide standards such as Telnet and FTP. Through it an almost complete integration into the data world is possible.
5.1
HiPath 4300/4500
Common Service Access for all Products
HTS via VPN Server
Service Technician
TAP
External access is achieved via a virtual private network (VPN). An explicit VPN address, starting with "10", is given to every system and server.
ISDN
PPP-Link
MTS
SNS-Server WAML Control 8 RMX 9 10 UNIX 11

FAMOS
Customer-LAN
for HTS
SNS-Server
Terminal V24 or
SCSI
SL200
TAP
V24 to RMX
192.0.2.222 PPP-Link
using Script: Siemens.CPPP
221
.5 .3 .4 192.0.2.0 SNS-Server
Atlantic LAN .6
Access to Applications via Port-Server
As a rule the SL200 receives an IP address from the customer LAN. On first installation it has the IP address 192.1.2.5.
BR0038
09/17/2009
Page 57 of 67
Siemens
5.2
HiPath 4000
Common Service Access for all Products

HTS via VPN Server
Service Technician
TAP
ISDN
PPP-Link
MTS
SNS-Server
WAML-
STMI2
Customer-LAN
for HTS
Steuerung DSCXL
TAP
Service LAN
SNS-Server
Customer LAN
10 8/11 .3/5 Atlantic LAN 192.0.2.0
As a rule the SL200 receives an IP address from the customer LAN. On first installation it has the IP address 192.1.2.5.
BR0038
09/17/2009
Page 58 of 67
Siemens
5.3
Access via the Customer LAN
Interfaces to use:
SL200 modul of the DSCX processor respectively DPC5 processor of the HiPath 4300/ 4500 - upper connector. Customer-LAN interface of the DSCXL processor of the HiPath 4000.
On first installation it has the IP address 192.1.2.5. The SL200 respectively the customer LAN interface will be reconfigured to the customer IP address as follows.
Base Administration --> Unix Base Administration --> LAN Configuration --> LAN Cards
Information about the IP settings you will get from the LAN administrator. Address: unique customer IP address Netmask: depends on the IP class of the LAN card, e.g. for class C: 255.255.255.0 Broadcast: depends on the IP address of the LAN card. For the LAN card address 1.30.31.5 the Broadcast address is 1.30.31.255 It is necessary to restart the UW7 server after changing IP parameters.
BR0038
09/17/2009
Page 59 of 67
Siemens
5.4
AMO access via the HiPath 4000 Assistant
Is the Customer LAN interface configured the system can be administrated via the Assistant 4000 or via AMOs with the Expert Access. Therefore the program HiPath 4000 Expert Access must be installed.
60
BR0038
09/17/2009
Page 60 of 67
Siemens
5.5
Direct AMO access via the customer LAN
Therefore the program HiPath 4000 Expert Access must be installed. The window Connect provides the configuration of profiles for the access via V.24 respectively LAN. Interfaces to use:
SL200 module of the DSCX processor respectively DPC5 processor of the HiPath 4300/ 4500 - upper connector. Customer LAN interface of the DSCXL processor of the HiPath 4000.
V.24
LAN
BR0038
09/17/2009
Page 61 of 67
61
Siemens
Profile for the AMO access via the customer LAN.
62
BR0038
09/17/2009
Page 62 of 67
Siemens
5.6
Direct AMO access via the Atlantic LAN
Interfaces to use:

Atlantic LAN access via the backplane of the HiPath 4300. Atlantic LAN access via the HUBC of the HiPath 4500. Atlantic LAN interface of the DSCXL processor of the HiPath 4000. Atlantic LAN access via the SF2X8
Profile for the AMO access via the Atlantic LAN:
BR0038
09/17/2009
Page 63 of 67
63
Siemens
5.7
Direct AMO access via V.24
Interfaces to use:
V.24-1 and V.24-2 (line 8 and line 9) with the HiPath 4300/4500 (DSCX respectively DPC5).
Profile for the AMO access via V.24 (line 8):
64
BR0038
09/17/2009
Page 64 of 67
Siemens
6
1. a)
Exercise for User Administration

Determine which clients are logged on. Which user ID is used?
_______________________________________________________________________ 2. Why is the same client present more than once?
_______________________________________________________________________ 3. Which is your own session?
_______________________________________________________________________ 4. Close all sessions (apart from your own one).
_______________________________________________________________________ 5. Set up a new access rights group for UW7 which only contains CM features with read-only rights.
_______________________________________________________________________ 6. Set up a new user for UW7 with read-only rights in CM.
_______________________________________________________________________
BR0038
09/17/2009
Page 65 of 67
65
Siemens
66
BR0038
09/17/2009
Page 66 of 67
Siemens
7
1. a) 2.
Solution for User Administration

Determine which clients are logged on. Which user ID is used? ACCESS ADMINISTRATION => Session Administration => Sessions Manager => read off the data
Why is the same client present more than once? A session is closed by quitting the window. A session is closed after 24 hours
3.
Which is your own session? The one marked "*".
4.
Close all sessions (apart from your own one). Update the client window => click the sessions and deactivate
5.
Set up a new access rights group for UW7 which only contains CM features with read-only rights. ACCESS ADMINISTRATION => Feature and User Administration => Access Rights Groups => Group => Add New Group Enter a random name and press OK. Open Configuration Management in the right part of the window, select all features only marked "Read" and assign the new group with "Edit".
6.
Set up a new user for UW7 with read-only rights in CM. ACCESS ADMINISTRATION => Feature and User Administration => User Administration => Users => Add Enter new account and description. Press the OK key. => Access Rights Configuration => assign the previously configured access rights group to the new user.
BR0038
09/17/2009
Page 67 of 67
67
HiPath 4000 Assistant
8. HiPath 4000 Assistant
Siemens
Contents
1 1.1 2 2.1 3 4 4.1 4.2 4.3 4.4 4.5 5 5.1 5.2 5.3 6 7 7.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Basics of Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 The use of templates to add a new subscriber. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Add an optiPoint 500/600 or optiset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Preparation of Extension Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Device Combination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 COS - Groups (Classes of Services Groups) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 LCRCOS - Groups (LCR - Classes of Services Groups). . . . . . . . . . . . . . . . . . . . . . . 20 Key Layout Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Add an IP-Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Add a STMI module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Restart of the STMI module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Add a subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Scheduled Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 7.1.1 Members for VOICE Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.1.2 Suppl. Data for VOICE Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 7.1.3 Common Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Call Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
7.2
BR0038
09/17/2009
Page 1 of 132
Siemens
7.3
7.4 8 8.1
7.2.1 Local PU Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.2 Extension Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3 Suppl. Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chese Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.1 Extension Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.2 Suppl. Data Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bulk selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1 Changes of bulky data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2 Deletion of bulky data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercises Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise System Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise ITR Group and Activation of Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise COS - Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise COS Changeover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise Key Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise Central/Individual Speed Dialing Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise Displayname and PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise Subscribers and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise Call Pick Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise Executive/Secretary Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exercise Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42 43 43 44 46 46 47 49 49 49 53 55 55 58 59 61 63 65 67 70 72 73 74 76 79
9 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 9.9 9.10 9.11 9.12 9.13 10 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 10.12 10.13
Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Solution Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Solution System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Solution System Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Solution ITR Group and Activation of Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Solution COS - Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Solution COS Changeover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Solution Key Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Solution Central/ individual Speed Dialing Facility . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Solution Displayname and PIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Solution Subscribers and Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Solution Call Pick Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Solution Executive/Secretary Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Solution Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
BR0038
09/17/2009
Page 2 of 132
Siemens
General
With HiPath 4000 assistant a new service platform is created which offers also many new service tools besides an extended system access. The new platform is Web-based and automates many events.With the UW7 platform it is also possible to use existing network wide standards such as Telnet and FTP. Through it an almost complete integration into the data world is possible. Common Service Access for all Products
HTS via VPN Server
Service Technician
TAP
ISDN
PPP-Link
MTS
SNS-Server WAML Control 8 RMX 9 10 UNIX 11

FAMOS
Customer-LAN
for HTS
SNS-Server
Terminal V24 or
SCSI
SL100
TAP
V24 to RMX
192.0.2.222 PPP-Link
using Script: Siemens.CPPP
221
.5 .3 .4 192.0.2.0 SNS-Server
Atlantic LAN .6
Access to Applications via Port-Server
As a rule the SL100 (SL200) receives an IP address from the customer LAN. On first installation it has the IP address 192.1.2.5.
1.1

General Information
Only a user may connect with the HiPath 4000 assistant. The Configuration Management is intended for a maximum 7560 Ports.
BR0038
09/17/2009
Page 3 of 132
Siemens
BR0038
09/17/2009
Page 4 of 132
Siemens
Overview
Ref. No. P31003-H3322-J001-54-4AA9 (Preliminary Version) Configuration Management (CM) enables the system and network-wide management of

System data Line data (trunk groups) Station data Least cost routing data Personal data
Schematic diagram see page 6 Variants The following variants of Configuration Management are available:
HiPath 4000 Assistant Configuration Management This CM installation runs locally on systems of the type HiPath 4000 (ADP Administration Data Processor). In addition to the administration of subscriber, personal and station data, it also makes it possible to administer boards, trunk groups and device data. HiPath 4000 Manager Configuration Management This CM installation runs on all servers of the type Primergy or RM. It is used for the network-wide administration of systems of different types (e.g. Hicom 300 E V 3.0, HiPath 4000, US-Hicom 300).
Both variants of the CM are practically identical as far as operation and the user interface are concerned. The online help will draw your attention to any differences. The entire range of features offered by Configuration Management is described in the online help. The features available may differ from those described. See the release notice for information on the range of features available for the product. The information in this document contains general descriptions of the technical options available, which do not always have to be present in individual cases. The required features should therefore be specified in each individual case at the time of closing the contract.
BR0038
09/17/2009
Page 5 of 132
Siemens
2.1
Basics of Administration
Schematic diagram
(1)
(2) (3)
(4)
Administration
CM Assistant database
(5)
Upload
Sequence (1) (2) (3) (4) (5) see page 6
Sequence (1) (2) (3) (4) (5)
BR0038
09/17/2009
Page 6 of 132
Siemens
1.
Each step is entered at the user interface (1) via the relevant menu item and the associated window. Selection tools are available for this purpose, you can also perform subscriber configuration searches. Each individual step is subject to extensive checks, e.g. on the reliability of the entries with regard to the value type and range and compatibility with the configuration that is to be expected at the time of execution. These checks also take into consideration the data which represents the administration steps already recorded but not yet executed. Invalid steps are cancelled.
2.
Once the formulation of an administration step has been concluded, the data that results from this step is entered in the CM database (2). If necessary, one or more AMO commands (these are commands for the administration of Hicom/HiPath systems) are generated from the administration step and entered in system-specific AMO batches (3).
3.
Once the AMO batches have been processed (4), the CM database is updated by means of a synchronization procedure (5). It is also possible to define several administration steps as a scheduled batch file. This scheduled batch file is automatically processed at a fixed time.
BR0038
09/17/2009
Page 7 of 132
Siemens
BR0038
09/17/2009
Page 8 of 132
Siemens
The use of templates to add a new subscriber
The menu action includes the option for the use of templates. Templates allow fast and simple storage of a subscribers configuration data, which can be used later on for adding a new subscriber. Procedure: Search for a subscriber with appropriate parameters, which can be used as a template:
BR0038
09/17/2009
Page 9 of 132
Siemens
Save the template: With the menu Action --> Save as template the template can be saved.
BR0038
09/17/2009
Page 10 of 132
Siemens
The template receives a name:
BR0038
09/17/2009
Page 11 of 132
Siemens
Select a template for the new subscriber:
After the selection of a template the extension number and PEN (Port Equipment Number) must be set. Of course the other parameters of the template can be changed. Click on Save to store the settings of the subscriber.
BR0038
09/17/2009
Page 12 of 132
Siemens
Add an optiPoint 500/600 or optiset
This document describes the configuration of optiset or optiPoint 500/600 devices with the HiPath 4000 Assistant . It handles the concerning parameters and cross references. There have to be checked respectively add groups and standards before an extension can be created:

Extension numbers (Dial numbers) Device combinations COS groups LCOS groups Standard keylayouts
BR0038
09/17/2009
Page 13 of 132
Siemens
4.1
Preparation of Extension Numbers
Before a subscriber can be added, the extension numbers, which you have got from the carrier have to be added to the WABE (dialing plan). An extension number can be added with the HiPath 4000 Assistant in the following directory: Configuration Management -> Tables -> Dial Plan -> Dial Numbers -> Dial Numbers
BR0038
09/17/2009
Page 14 of 132
Siemens
Procedure: Register Basic Data Push the button New. Select the Type STN. In this example the extension number is 1234. Push button Save. Register CPS/DPLN Data The default setting for the type station is CPS 2-12 and 22. The type STN is no member of a dialing plan group.
4.2
Device Combination
The field device combination is mandatory if you add a new subscriber. It handles the Device Family (e.g. optiPoint 500) and Layout Type (e.g. optiPoint 500 Advance). In addition there can be allocated the number of add-on devices and adapters.
BR0038
09/17/2009
Page 15 of 132
Siemens
A device combination that has been defined once in this window can be used to configure any number of stations. Therefore you have to look for an adequate entry with the button Search. Create a new device combination: Push the button New Device combination: This field contains a freely assignable name for a device combination. This name is used to assign the device combination in the Station window to a station. Layout Type: This field contains the precise name of the voice terminal type and number of times it is to be found on the underside of the device. Device Family: This field contains the name of the device class to which the voice terminal type belongs. The system derives the contents of this field from the entry in the Layout Type field. Add-on Dev.: This field contains the precise name of the add-on device. The device name for the optiset and optiPoint device families indicates the number of add-on devices:
1_OPTI_KEY_MODUL
BR0038
09/17/2009
Page 16 of 132
Siemens
2_OPTI_KEY_MODULES 3_OPTI_KEY_MODULES 4_OPTI_KEY_MODULES
If a device can be extended with add-on devices, then up to four add-on devices can be added; three when a card reader is installed. Adaptor1/Adaptor2: Adaptor can only be administered on Optiset or OptiPoint devices. There are different adaptors possible: e.g. optiset E phone adaptor (for connecting a slave device to an master device) optiset E ISDN adaptor (for connecting CorNeT - or functional terminals to a master device) optiset E data adaptor (= RS232 adaptor) optiset E control adaptor (adaptor dialing interface) optiset E ta/b adaptor
Save the configuration with the button Save.
For further information see the online help of the Assistant 4000 or the E-Doku.
BR0038
09/17/2009
Page 17 of 132
Siemens
4.3
COS - Groups (Classes of Services Groups)
The fields COS1 and COS2 are mandatory if you add a new subscriber. The classes of service contain combinations of services and features and are assigned to one or more users. The subscriber is allocated to two COS-groups - a day- and a night authorization. The COS-groups are handled in the menu: Configuration Management -> Tables -> COS
A COS group that has been defined once in this window can be used to any number of stations. Therefore you have to look for an adequate entry with the button Search. Create a new COS group: Push the button New Each COS group can handle the services voice, data and fax. There are 3 tabs for voice features, 1 tab for data and one for fax. Save the configuration with the button Save.
BR0038
09/17/2009
Page 18 of 132
Siemens
The language of the paramaters of the tabs voice, data and fax is german or english. The setting therefore is handled in the menu: Configuration Management -> User settings -> AMO language
BR0038
09/17/2009
Page 19 of 132
Siemens
4.4
LCRCOS - Groups (LCR - Classes of Services Groups)
The fields LCRCOS1 Voice, LCRCOS2 Voice, LCRCOS1 Data and LCRCOS2 Data are mandatory if you add a new subscriber. The LCRCOS groups are handled in the menu: Configuration Management -> Least Cost Routing -> LCR Authorizations -> LCR Classes of Service - Voice respectively Data
A LCRCOS group (voice or data) that has been defined once in this window can be used to any number of stations. Therefore you have to look for an adequate entry with the button Search. Create a new LCRCOS group (voice or data): Push the button Search Each LCRCOS has two tabs which handles authorizations. There you can add or delete LCR authorizations. Additionally you can handle LCR parameters (e.g. LCRET: LCR expensive route tone) Save the configuration with the button Save.
BR0038
09/17/2009
Page 20 of 132
Siemens
4.5
Key Layout Standards
The field Key Layout is a mandatory parameter if you add a new subscriber. The keylayout standards are handled in the menu: Configuration Management -> Tables -> Standard Key Layouts
The window standard key layout shows you the device name and the stations which are using this key layout standard.
BR0038
09/17/2009
Page 21 of 132
Siemens
A key layout standard that has been defined once in this window can be used to any number of stations. Therefore you have to look for an adequate entry with the button Search. Create a new key layout standard: Push the button Search Select a free key layout standard or a standard which you want to modify. Select the menu Action and Device Key Layout. Select in the table key layout the function. Select the function key which should have this function. Repeat this procedure until all key have the wanted assignment. Save the configuration with the button Save.
BR0038
09/17/2009
Page 22 of 132
Siemens
Add an IP-Phone
This document handles the configuration of IP-phones (e.g. optiPoint 400/410 and 600, opticlient 130) with the HiPath 4000 Assistant. Therefore the STMI/STMI2 module has to be used. The STMI/STMI2 module can be used for different IP features - the function-ID 3 is needed for the HFA feature (HiPath Feature Access).
5.1
Add a STMI module
You can add/modify a module (in general) with the menu Configuration Management -> System Data -> Board -> Board. Tab general board data:
Add a STMI module: Open the window board and click the button new. The fields LTU and slot offers the correspondent settings, where the modules are plugged or should be plugged. The HFA feature needs the function-ID 3.
BR0038
09/17/2009
Page 23 of 132
Siemens
Tab STMI board data:
BR0038
09/17/2009
Page 24 of 132
Siemens
Tab STMI feature access:
Here the IP-address, subnet mask, default gateway address and TCP-Port of the STMI/STMI2 board can be added. Additionally settings e.g. Quality of Service (QoS) can be set.
After the configuration of the board click the button Save to store the settings. A additional restart of the board is needed.
BR0038
09/17/2009
Page 25 of 132
Siemens
5.2
Restart of the STMI module
To restart the STNI-board use the menu Configuration Management -> System Data -> Maintenance -> Board Maintenance.
Procedure: Select the considering board. The menu Action --> Execute --> Restart allows a restart of the selected board.
BR0038
09/17/2009
Page 26 of 132
Siemens
5.3
Add a subscriber
An IP phone can be added with the men Configuration Management -> Station -> Station. Tab Basic1:
Open the window station and select the button New. Mandatory parameters are station number, connection type, device configuration, COS1, COS2, LCRCOSV1 Voice, LCRCOSV2 Voice, LCRCOSD1 Data, LCRCOSD2 Data and key layout. The parameter IP2 is used for IPphones connected to a STMI2-board. Click button Save. Tab Basic 2:
BR0038
09/17/2009
Page 27 of 132
Siemens
This tab handles e.g. a password. Moreover additional IP-settings can be allocated.
BR0038
09/17/2009
Page 28 of 132
Siemens
Tab Basic 3:
This tab handles e.g. the language of the service menu. Additional information about the parameters concerning the configuration of a board resp. phone have a look to the online help or service documentation.
BR0038
09/17/2009
Page 29 of 132
Siemens
BR0038
09/17/2009
Page 30 of 132
Siemens
Scheduled Batch
The scheduled batch allows batch jobs for performing configuration tasks (for example adding or deleting stations, changing subscriber features). A scheduled batch can be defined in the menu Configuration Management -> Scheduled Batch.
Adding a schuled batch Display the Scheduled Batch window and select New mode. User defaults to your user ID, Start Time (time of the time server) repectively Start Time at System defaults to the current date and time of the time server respectively HiPath system clock, and Status defaults to "o" ("Scheduled Batch opened"). Enter values in the fields Sched. Batch Name and Description. Delete the start time if neccessary or enter the start time into the Start Time field repectively Start Time at System. The start time must be later than the current time. The following example uses the Start Time at System. Therefore you have to fill out the field System. If you want to keep the batch file after execution, select the Store Job after Send checkbox.
BR0038
09/17/2009
Page 31 of 132
Siemens
Click Save. You now saved the attributes of the batch job (for example, the batch name and start time). Note that you did not "save" (close) the batch job for execution.
Possible values for the field status
o -- Scheduled batch opened u -- Execution time deleted (= start time not entered) s -- Scheduled time set v -- Scheduled batch verification c -- Scheduled batch closed
BR0038
09/17/2009
Page 32 of 132
Siemens
The tasks for a batch job are defined by opening the respective windows, and entering and saving the desired configuration data. Note that while a batch job is open, the Scheduled Batch icon in the menu bar changes its appearance from a file with a down-arrow to a file, a clock, and the batch job name. Clicking the Scheduled Batch icon while a batch job is open toggles between the two appearances and determines whether clicking Save for the current task is executed in a "normal" way or written to the batch job. Click Save. This writes the new configuration to the batch job. The following example shows a change at the site station while the batch job test is open.
33
BR0038 09/17/2009 Page 33 of 132
Siemens
Close batch job: Return to the Scheduled Batch window. Optionally, change the start time again (it must be later than the current time) and click Save. If the execution start time entered is not later than the current time the scheduled batch is executed immediately after closing. A corresponding message is displayed From the menu bar, select Action > Close Scheduled Batch. The Status field changes to "s" ("Scheduled for execution"), and the batch job will be executed at the defined time. If no execution start time has been entered the status field changes to "u" (undefined start time). The start time can be entered later.
BR0038
09/17/2009
Page 34 of 132
Siemens
Verify a Scheduled Batch: To check whether shortly before start time the defined batch tasks can still be performed. (Example of an un-executable task: A batch job contains the task to change class marks within the COS "21", but somebody removed COS "21" from the configuration after the batch job was closed.) To verify a batch job:

Search for the desired batch job and display it. From the menu bar, select Action > Verify Scheduled Batch. After running the verification, the user can open the Session Log window in the Logs folder and search for the respective log (Session Log).
If errors are found, the log will list them (for example, COS 21 does not exist), and the user can then do one of the following:
Nothing. The batch job will run at Start Time, perform the executable commands and ignore the un-executable ones. Correct the configuration so that the respective tasks can be performed (for example, recreate COS "21"). Delete the respective Scheduled Batch.
BR0038
09/17/2009
Page 35 of 132
Siemens
BR0038
09/17/2009
Page 36 of 132
Siemens
Groups
Hunt Group Call Pickup Chese Group Communication Group
The Groups folder in CM selection tree contains links to objects (windows):

7.1
Hunt Group
This window is available both locally (CM Assistant) as well as network-wide (CM Manager). A hunt group is a group of stations whose voice, data and fax terminals can be reached using a common extension number. This number can be a code number or it can be the extension number of the first station in the hunt group (HT). This is called the master hunt group.
BR0038
09/17/2009
Page 37 of 132
Siemens
Functions

Create a new hunt group Search for an existing hunt group based on random criteria Change the properties of a hunt group Delete a hunt group Add members to a hunt group Delete members from a hunt group
Internal/network-wide overflow You can configure the following numbers as overflow destinations:

network-wide and external dial-up numbers internal and network-wide VMS/PhoneMail numbers
BR0038
09/17/2009
Page 38 of 132
Siemens
Schematic diagram
Caller
Hunt Group
Overflow
Internal VMS
Network-wide VMS
External (CO)
Subscriber Hunt Group
Subscriber
Hunt Group
etc.
etc.
BR0038
09/17/2009
Page 39 of 132
Siemens
7.1.1
Members for VOICE Tab
This tab lists the members of the hunt group for the VOICE service. The extension, system and display name of the members are displayed. You can add, edit or delete members.
7.1.2
Suppl. Data for VOICE Tab
This tab allows you to define different settings, forexample, the overflow destination, for the selected VOICE hunt group.
7.1.3
Common Data Tab
This tab allows you to view the assignments for the dial plan group (DPLN) and call progress state (CPS) for the selected hunt group. To change the tab data, you must delete the hunt group and create a new one with the new CPS and DPLN data.
BR0038
09/17/2009
Page 40 of 132
Siemens
7.2
Call Pickup
This window is available both locally (CM Assistant) as well as network-wide (CM Manager). A call pickup group (PU group) is used to group subscribers who can pick up incoming calls on each others behalf.
Actions

Create a new PU group Search for an existing PU group based on random criteria Modify the properties of a PU group Delete a PU group Add members to a PU group Delete members from a PU group Add remote links to a PU group (Hicom V3.0 and later) Delete remote links from a PU group (Hicom V3.0 and later)
BR0038
09/17/2009
Page 41 of 132
Siemens
7.2.1
Local PU Group
A local pickup group (PU group) is used to group Hicom/HiPath node subscribers who can pick up incoming calls on each others behalf. The call is picked up by pressing a key or dialing a code number (PU) that is standard in the system. The code number *7 is used in this example:
*7
*7
*7
*7 *7
Restrictions:

A PU group may contain a maximum of 255 members (subscribers + remote links). Up to 255 digites are permitted in a group. Please note, however, that full signaling is not recommended if the PU group contains more than 25 digites. Up to 1000 PU groups may be configured. A subscriber may only belong to one PU group. The stations in a PU group may not be MASTER of a hunt group (HT). The stations in a PU group must not be connected to the analog port of a modem. The stations in a PU group may not be witness stations. Special stations may not be entered in a PU group. Stations that have already been configured as executive or secretary stations in an executive/secretary system may not be entered in a PU group.
BR0038
09/17/2009
Page 42 of 132
Siemens
A PU group must contain at least one station. A group with only one remote link is, therefore, not permitted. The alerting call (NOTRNG) only applies to digital terminals.
7.2.2
Extension Tab
The members of the call pickup group are listed in this tab. The extension, system and display name of the members are displayed. You can add, edit or delete members.
7.2.3
Suppl. Data Tab
This tab allows you to define different settings for the selected call pickup group, for example, signal settings.
BR0038
09/17/2009
Page 43 of 132
Siemens
7.3
Chese Group
This window is available both locally (CM Assistant) as well as network-wide (CM Manager). An integrated executive/secretary system is a subscriber group comprising executive telephones, secretary telephones and, if necessary, deputy telephones.
Features Every executive/secretary system can contain up to four executive telephones, two secretary telephones and one deputy telephone per secretary. All subscribers in an executive/secretary system must have digital devices (Optiset E or later). Actions This window provides the following functions for an executive/secretary system (executive/secretary group/CHESE group):

Create a new executive/secretary system Search for an existing executive/secretary system based on random criteria Modify the properties of an executive/secretary system Delete an executive/secretary system Add members to an executive/secretary system Delete members from an executive/secretary system Change the allocation of executives and secretaries in an executive/secretary system
BR0038
09/17/2009
Page 44 of 132
Siemens
Special functions keys Executive and secretary telephones require special function keys which are necessary for the CHESE group features:
for every executive telephone one RNGXFER key (ring transfer executive/secretary telephone) DSS key (direct station selection) for the secretary telephone (possibly also for the second secretary telephone)
for every secretary telephone one PUS key for every executive telephone (call pickup) one RNGXFER key for every executive telephone (ring transfer) one DSS key for every executive telephone (direct station selection) one REP key (deputy) to activate or deactivate the deputy telephone
Adding/deleting members Adding a new member Click the New button on the right-hand side of the table: A new line appears underneath the selected one. You can enter the data of the new member here. Click the Save button and confirm the changes with OK. Deleting a member Click the line that describes the member to be deleted. Click the Delete button on the right-hand side of the table: Click the Save button and confirm the changes with OK. The member is now deleted from the executive/secretary group.
BR0038
09/17/2009
Page 45 of 132
Siemens
7.3.1
Extension Tab
This tab allows you to display and edit a list of the members of the selected executive/secretary (Chese) group.
7.3.2
Suppl. Data Tab
This tab allows you to display and edit supplementary data for the selected executive/secretary group.
BR0038
09/17/2009
Page 46 of 132
Siemens
7.4
Communication Group
This window is available both locally (CM Assistant) as well as network-wide (CM Manager). Members of a COM group can communicate using abbreviated dial-up procedures. An index that comprises the last two digits of the subscriber extension is used for this purpose.
The Communication Group dialog box allows you to:

create a Communication Group add members to a Communication Group display a Communication Group change a Communication Groups membership delete a Communication Group or its members synchronize a Communication Group (copy to a selected system)
BR0038
09/17/2009
Page 47 of 132
Siemens
BR0038
09/17/2009
Page 48 of 132
Siemens
8
8.1 8.1.1
General Changes
Bulk selection Changes of bulky data
Changes of bulky data can be done in the table Object data in one step. A data record has to be selected and has to be edited. This record is used as the master record for the mass changes, that means the changes of the master record are taken over for all selected data records. The master record is the only record, which could be edited. All the other marked records, which are selected, are shown in a brighter blue and may not be edited until the mass change has been executed or the whole procedure has been stopped. In the first column of the records (status of the mass data change) it will be shown, if the changes were executed without error or not. Possible displays in the mass data column:
The change was executed successfully.
The change was erroneous and was not executed.
An open question has to be answered to continue the change for this data record.
Change was executed successfully, but there is a warning or a message for this data record.
BR0038
09/17/2009
Page 49 of 132
Siemens
For this example the DPLN-group of stations 7112 (Master Record), 7240, 7243, 7246 and 7250 has to be changed from 0 to 1
Step 1: Select Master data record and change DPLN-group from 0 to 1
BR0038
09/17/2009
Page 50 of 132
Siemens
Step 2: Select all stations, which should be changed at the same time with the Ctrl-Key (the Shift-key can also be use) and save them.
BR0038
09/17/2009
Page 51 of 132
Siemens
BR0038
09/17/2009
Page 52 of 132
Siemens
8.1.2
Deletion of bulky data
To delete mor than one data records at the same time, select the records with the Ctrl-key resp. Shift-key and start the delete action the the Delete-button. All data records will be deleted, if the security question is answered by Yes.
BR0038
09/17/2009
Page 53 of 132
Siemens
BR0038
09/17/2009
Page 54 of 132
Siemens
9
9.1
1.
Exercises
Exercises Hardware
Find out the Hardware configuration of your system (LTG/LTU module configuration with names and part numbers). The following illustration is an example for an HiPath 4300.
Note: ____________________________________________________________
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno: Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
EBT
16
19
22
25
31
37
43
49
55
61
67
73
79
85
91
97
103 109 115 121 127
Basic unit (CC80F) (LTG = _____; LTU = _____)
BR0038
09/17/2009
Page 55 of 132
Name:
Partno:
Siemens
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno:
Partno: Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
EBT
16
19
22
25
31
37
43
49
55
61
67
73
79
85
91
97
103 109 115 121 127
Expansion unit (L80XF) (LTG = _____; LTU = _____)
2.
Find out what station numbers have been set up and what their status is on the SLMA and SLMO modules. How many ports are free respectively used?
Note: ____________________________________________________________
3.
Determine which S0 connections are free on your system.
Note: ____________________________________________________________
BR0038
09/17/2009
Page 56 of 132
Name:
Partno:
Siemens
4.
How many analog and how many digital trunks are set up?
Note: ____________________________________________________________ Note: ____________________________________________________________
Which PENs are affected, what are the destination nodes of the trunks, which protocol (digital) is used, what is the type (of device) and to which trunk group (digital) the line is assigned?
PEN 1st analog line: 2nd analog line: 1st digital line: 2nd digital line: 3rd digital line: 4th digital line: 5th line:
DESTINATION NODE
PROTOCOL
DEVICE
TRUNK GROUP
5.
How do you can find marked resp. blocked components in the HiPath 4000 V2.0 systems ?
Note: ____________________________________________________________
6. There are 4 modes in the codeword, which could be activated in a HiPath 4000 V2.0 systems. Which modes are realized ?
Note: ____________________________________________________________ Note: ____________________________________________________________
BR0038
09/17/2009
Page 57 of 132
Siemens
9.2
1.
Exercise System Data

Find out the switch number (L-number) of the HiPath 4000.
Note: ____________________________________________________________
2.
Which software version, release version and revision level has the system?
Note: ____________________________________________________________
3.
Check the available database memory allocations of the system.
Note: ____________________________________________________________
4.
Activate the following features for the whole system: Callback - LCR Expensive Tone - Central Speed Dialing Individual Speed Dialing COS changeover by attendant console
Values:____________________________________________________________ Note: _____________________________________________________________
BR0038
09/17/2009
Page 58 of 132
Siemens
9.3
1.
Exercise System Dialing Plan

Which Code Types are relevant for the DO NOT DISTURB feature?
Note: ______________________________________________________________ Code Type: _________________________________________________________
Which dial codes do these have? _______________________________________
Implement the feature. What has to be taken into account? How do you activate/ deactivate the do not disturb feature on the optisets/optiPoints?
Note: ____________________________________________________________
2.
Which Code Types are used for DISPLAY SUPPRESSION?
Note: ______________________________________________________________ Code Type: _________________________________________________________

Which dialcodes do these have? _______________________________________
Implement the feature; What appears on the B subscribers display and why?
Note: ______________________________________________________________
3.
Program a DO NOT DISTURB KEY on an optiPoint, so that it is only available to this subscriber.
Procedure: _________________________________________________________
__________________________________________________________________
BR0038
09/17/2009
Page 59 of 132
Siemens
4.
Which dialcodes do the Code Types have: LNR _____________ SNR _____________ SPLIT _____________ SIGNON _____________ SIGNOFF _____________
What is the difference between LNR and SNR?
Note: ____________________________________________________________
Implement both features.
Procedure:
LNR: ____________________________________________________________ SNR: ____________________________________________________________
Note: ____________________________________________________________
5.
What is the subscriber numbering scheme used by your own node?
Note: ____________________________________________________________
Which of the subscriber numbers are free? _________________________________________________________________
6.
Set up a Code Type = STN with number=5000 in such a form that it cannot be reached externally.
Note: ____________________________________________________________
_________________________________________________________________ Test your programming. (Possible external numbers: 0-00-49-40-40xxx-yyyy; xxx = Node number(100/200/300/400) yyyy = Extension
BR0038
09/17/2009
Page 60 of 132
Siemens
9.4
ITR group
Exercise ITR Group and Activation of Features
1.
Assign different ITR groups not equal to 0 to an optiPoint subscriber and an optiset subscriber.
Note: ____________________________________________________________
2.
Implement the following traffic restriction.
allowed OPTISET OPTIPOINT 500
prohibited
Note: ____________________________________________________________
3.
Assign the two subscribers to ITR group = 1.
Note: ____________________________________________________________
Activation of features
4.
Activate the do not disturb-group feature for these subscribers and then deactivate this again.
Note: ____________________________________________________________
_________________________________________________________________
Problem: _________________________________________________________
BR0038
09/17/2009
Page 61 of 132
Siemens
5.
Program and activate a fixed call forwarding for one of these subscribers on an administrative basis. Test this.
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________
Deactivate this.
Note: ____________________________________________________________
6.
Change the individual optiset settings for the optiset subscriber. Test this.
Note: ____________________________________________________________
BR0038
09/17/2009
Page 62 of 132
Siemens
9.5
1.
Exercise COS - Authorizations

Find out which COS classes have Mailbox (MB) authorization.
Note: ____________________________________________________________
2.
What authorizations are contained in COS 13?
Note: ____________________________________________________________
_________________________________________________________________
3.
Which subscribers use this class?
Note: ____________________________________________________________
4.
Set up a new COS with the following authorizations:
Subscribers with this COS should become LCR subscribers
Authorizations:______________________
The COS changeover can be made at the subscriber terminal
Authorization:______________
They should be able to use the mailbox
They should be able to use external call forwarding
Note: ____________________________________________________________
_________________________________________________________________
BR0038
09/17/2009
Page 63 of 132
Siemens
5.
What LCOSV classes are used in the system?
Note: ____________________________________________________________
6.
What LCR authorizations are contained in LCOSV class 5 and what is the purpose of these authorizations?
Note: ____________________________________________________________
7.
Set up a new LCOSV with the following content: LCR authorizations 1-8 LCR EXPENSIVE TONE (LCRET)
Note: ____________________________________________________________
8.
Assign this LCOSV to a subscriber, so that he can use the higher LCR authorizations in daytime COS.
Note: ____________________________________________________________
BR0038
09/17/2009
Page 64 of 132
Siemens
9.6
1.
Exercise COS Changeover

Assign one optiPoint and one optiset subscriber in a COS group that is not equal to 0.
Note: _____________________________________________________________
2.
Assign these subscribers a COS2 without mailbox authorization.
Note: _____________________________________________________________
__________________________________________________________________
3.
Now change over the COS group to the night-time class of service.
Note: _____________________________________________________________
__________________________________________________________________
4.
Test behavior with and without mailbox authorization.
Note: _____________________________________________________________
5.
How does a subscriber know if he/she is in daytime or night-time service?
Note: _____________________________________________________________
6.
Subscribers change over themselves. What does this require?
Note: _____________________________________________________________
__________________________________________________________________ __________________________________________________________________
65
BR0038 09/17/2009 Page 65 of 132
Siemens
7.
Implement active, timed switching of COS groups 0-4 and 6-15 as follows: from night to day: Mon. Fri.: 8.00 a.m. Sat. + Sun.: 9.00 a.m. from day to night: Mon. Fri.: 6.00 p.m. Sat.: 3.00 p.m. Sun.: 12.oo p.m.
Note: _____________________________________________________________
__________________________________________________________________ __________________________________________________________________ __________________________________________________________________
8.
Program a deactivated (prepared) timed changeover for COS group 5 as follows: from night to day: Mon. Sun.: 8.00 a.m. from day to night: Mon. Sun.: 11.00 a.m.
Note: _____________________________________________________________
__________________________________________________________________
BR0038
09/17/2009
Page 66 of 132
Siemens
9.7
1.
Exercise Key Programming

Install and activate an optiset Add-on-terminal.
Note: ____________________________________________________________
2.
How are the additional 15 keys assigned?
Note: ____________________________________________________________
_________________________________________________________________
3.
Program 2 function keys on an administrative basis, a VC key and an VCR key, on keys 1 and 2 of the add-on-terminal.
Note: ____________________________________________________________
For which feature are these two keys required?
Note: ____________________________________________________________
4.
Program 2 destinations (name keys) on an administrative basis, on keys 3 and 4 of the key module.
Note: ____________________________________________________________ Note: ____________________________________________________________ Note: ____________________________________________________________ Note: ____________________________________________________________ Note: ____________________________________________________________
5.
Program 2 destinations on key 5 of the key module at the terminal.
Note: ____________________________________________________________
BR0038
09/17/2009
Page 67 of 132
Siemens
6.
Program a direct station selection key on an administrative basis. What has to be taken into account?
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________
7.
How does subscriber B know that he is being called directly? _________________________________________________________________
8.
Implement the feature CONFERENCE.
Note: ____________________________________________________________
_________________________________________________________________
9.
Implement the LAST NUMBER REDIAL FEATURE with the appropriate key.
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________ _________________________________________________________________ 10. Change an assigned key standard from an optiset subscriber and an optiPoint subscriber.
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________ _________________________________________________________________
11. Which subscribers use optiset-Standard 4?
Note: ____________________________________________________________
12. Which optiPoint standards are used in the systems?
Note: ____________________________________________________________
BR0038
09/17/2009
Page 68 of 132
Siemens
13. Program the function BUZZ on an administrative basis.
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________
BR0038
09/17/2009
Page 69 of 132
Siemens
9.8
1.
Exercise Central/Individual Speed Dialing Facility

Set up 5 speed dialing lists (list: 0+1-4). Group 1 (terminal 1): Lists 0 + 1 + 2 Group 2 (terminal 2): Lists 3 + 4 Dimension the list so that 100 destinations can be added at a later point.
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________ _________________________________________________________________
2.
Assign lists 0 + 1 (3) to a subscriber 1 and lists 0 + 2 (4) to a subscriber 2.
Note: ____________________________________________________________
_________________________________________________________________
3.
Fill the lists with destinations.
Note: Possible destination pattern:0-00-49-40-40xxx-y

0-0-40-40xxx-y 0-40xxx-y xxx = Node numbers (100/200/300/400) y = Extensions (7zzz)
Assign names for the destinations and set supplementary dial (SUPDIAL) so that each extension of each node can be reached.
Note: ____________________________________________________________
_________________________________________________________________
BR0038
09/17/2009
Page 70 of 132
Siemens
4.
Delete a SPDNO area.
Note: ____________________________________________________________
_________________________________________________________________
5.
Add a further 50 destinations to one of the lists you use.
Note: ____________________________________________________________
_________________________________________________________________
6.
Program destinations on the numeric keys of the telephone (analog and optiset). Check these by means of the administration.
Procedure: ___________________________________________________
_________________________________________________________________
ANATE:
Note: ____________________________________________________________
_________________________________________________________________
optiset:
Note: ____________________________________________________________
_________________________________________________________________
BR0038
09/17/2009
Page 71 of 132
Siemens
9.9
1.
Exercise Displayname and PIN

Assign a displayname and an organization name to an optiPoint. Test this function.
Note: ____________________________________________________________
2.
Check which identification with PIN is possible (internal or network-wide)?
Note: ____________________________________________________________
3.
What requirements must be met so that a subscriber can identify himself at any terminal on the node?
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________
Test this.
Procedure: _______________________________________________________
4.
For how long does the identification remain active?
Note: ____________________________________________________________
_________________________________________________________________
Arrange that identification should only be activated for a single call.
Note: ____________________________________________________________
BR0038
09/17/2009
Page 72 of 132
Siemens
9.10
1.
Exercise Subscribers and Features

Note: ____________________________________________________________
Check that all the requirements for setting up optiPoint terminals are met.
2.
Take any optiPoint. Store this optiPoint as a template. Store this template without authorizations, display entries and speed dial lists.
Note: ____________________________________________________________
3.
Set up an optiPoint terminal with the help of the template.
Note: ____________________________________________________________
4.
Set up an optiset terminal with an AMO.
Note: ____________________________________________________________
5.
Protect the terminal with the feature reject call back on no answer.
Note: ____________________________________________________________
BR0038
09/17/2009
Page 73 of 132
Siemens
9.11
1.
Exercise Call Pick Up
Set up a call pickup group as described below and monitor it:

1 x optiPoint + 1 x optiset + 1 x ANATE The station number of the calling party should not be displayed 3 alerting tones, only when there is no answer Pick up of second call disabled
Note: _____________________________________________________________ Note: _____________________________________________________________ Note: _____________________________________________________________ Note: _____________________________________________________________
2.
Include a fourth subscriber in the call pickup group.
Note: _____________________________________________________________
3.
Change the following characteristics of the call pickup group and monitor these:

The station number of the calling party should be displayed 3 periodical alerting tones Enable pick up of second call
Note: _____________________________________________________________
What restrictions apply to alerting tones?
Note: _____________________________________________________________
4.
Implement the call pickup group PARK feature.
Note: _____________________________________________________________
BR0038
09/17/2009
Page 74 of 132
Siemens
5.
Allow the analog subscriber in the call pickup group also to receive an acoustic signal when a call is received for another call pickup group subscriber. Enable the analog subscriber to activate/deactivate the acoustic signal himself. Test this.
Procedure: _______________________________________________
______________________________________________________________ ______________________________________________________________ ______________________________________________________________ ______________________________________________________________ ______________________________________________________________ ______________________________________________________________ ______________________________________________________________ ______________________________________________________________ ______________________________________________________________
BR0038
09/17/2009
Page 75 of 132
Siemens
9.12
1.
Exercise Executive/Secretary Group
Set up a 2 executive <-> 1 secretary configuration. a) What requirements need to be met before the executive /secretary group is set up? The SECRETARY device has to have an add-on device (key module) and the TOGGLE feature is to be enabled in the SECRETARY device at the press of a button.
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________
Write your key assignment in the following graphics. Key assignment, SECRETARY device:
Service menu
Redial
Mailbox
Speaker
1 4 7
2 5 8 0
3 6 9 # < >
BR0038
09/17/2009
Page 76 of 132
Siemens
Key assignment, EXECUTIVE devices:
Service menu
Redial
Mailbox
Speaker
1 4 7
2 5 8 0
3 6 9 # < >
Characteristics of the required executive /secretary group: 2 executives <-> 1 secretary; Representative = yes; Special ringing rhythm for executive <-> secretary calls; Alerting tone = ON3
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________ _________________________________________________________________ _________________________________________________________________
BR0038
09/17/2009
Page 77 of 132
Siemens
b)
Adapt the REP device to the SECRETARY device. What executive /secretary group functions can be implemented?
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________ _________________________________________________________________
2.
Enable the executive to use the VOICE CALLING facility to speak to the secretary by pressing a single button.
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________ _________________________________________________________________ _________________________________________________________________
3.
Set up a conference corner telephone for EXECUTIVE 1.
Note: ____________________________________________________________
_________________________________________________________________
4.
Program a name key with a destination number that cannot be deleted.
Note: ____________________________________________________________
BR0038
09/17/2009
Page 78 of 132
Siemens
9.13
1.
Exercise Hunt Group
Set up a voice hunt group with one of the following settings: hunt group access code: 6000 name of hunt group: Hunt group 1 3 subscribers in hunt group (1 x optiPoint, 1 x optiset, 1 x ANATE); only subscribers from own node search type: cyclical forward if no answer should be used the call queue should be dimensioned at 1 no overflow after a cycle overflow destination to a terminal of another node if the call queue is full call forwarding from hunt group should not be possible
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________ _________________________________________________________________ Test your programming.
2.
Remove the optiset subscriber from the hunt group.
Note: ____________________________________________________________
3. Add the optiset subscriber to the hunt group again.
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________
BR0038
09/17/2009
Page 79 of 132
Siemens
4.
Set up a MASTER hunt group with the same settings as described in exercise 1. Do not delete the hunt group you have set up! What settings cannot be transferred or implemented?
Note: ____________________________________________________________
_________________________________________________________________ _________________________________________________________________
5.
Change the search type to LINEAR and allow the size of the call queue to be defined by the HiPath 4000.
Note: ____________________________________________________________
_________________________________________________________________
How large is the call queue set by the HICOM and why? _________________________________________________________________
BR0038
09/17/2009
Page 80 of 132
Siemens
10
10.1
1.
Solutions
Solution Hardware
Find out the Hardware configuration of your system (LTG/LTU module configuration with names and code numbers).

menu Configuration Management menu System Data menu Board page Board button Search: 1st board will be shown button Goto Next/Previous Object for selecting module or view Object List: all boards will be shown
AMO: DISPLAY-BCSU:TYPE=TBL; 2. Find out what station numbers have been set up and what their status is on the SLMA and SLMO modules. How many ports are free respectively used?

menu Configuration Management menu System Data menu Maintenance page Device Maintenance button Search: 1st station will be shown button Goto Next/Previous Object for selecting module or view Objectlist: all stations will be shown
To see additionally the free ports (status NOGEN):

menu Configuration Management menu System Data menu Maintenance page PEN Maintenance button Search: 1st PEN will be shown button Goto Next/Previous Object for selecting module
BR0038
09/17/2009
Page 81 of 132
Siemens
or view Objectlist: all stations will be shown
The view Search Object allows to select the parameter NOGEN respectiveley specific slots. AMO: DISPLAY-SDSU:STATUS=ALL,TYPE=PEN,LEVEL=PER3,LTU=1,SLOT=79; DISPLAY-SDSU:STATUS=ALL,TYPE=PEN,LEVEL=PER3,LTU=1,SLOT=85; DISPLAY-SDSU:STATUS=ALL,TYPE=STNO,LEVEL=PER3; DISPLAY-SDSU:STATUS=NOGEN,TYPE=PEN,LEVEL=PER3,LTU=1,SLOT=79; DISPLAY-SDSU:STATUS=NOGEN,TYPE=PEN,LEVEL=PER3,LTU=1,SLOT=85;
3.
Determine which S0 connections are free on your system.

menu Configuration Management menu System Data menu Maintenance page Device Maintenance button Search: 1st station will be shown-button Goto Next/Previous Object for selecting module or view Objectlist: all stations will be shown
AMO: DISPLAY-SDSU:STATUS=NOGEN,TYPE=PEN,LEVEL=PER3,LTU=1,SLOT=79; DISPLAY-SDSU:STATUS=NOGEN,TYPE=PEN,LEVEL=PER3,LTU=1,SLOT=85;
4.
How many analog and how many digital trunks are set up? Which PENs are affected, what are the destination nodes of the trunks, which protocol (digital) is used, what is the type (of device) and to which trunk group (digital) the line is assigned?
menu Configuration Management menu System Data menu Trunk
BR0038
09/17/2009
Page 82 of 132
Siemens
page Trunk button Search button Goto Next/Previous Object for selecting trunks or view Objectlist: all trunks will be shown
The field device has the option: S0COD: central office trunk BRI S2COD: central office trunk PRI S0CONN: tie line BRI S2CONN: tie line PRI
REGENERATE-TDCSU:; Display-TDCSU:;
5.
How do you can find marked resp. blocked components in the HiPath 4000 V2.0 systems ?
DISPLAY-SDSU:STATUS=LICMARK,TYPE=PEN,LEVEL=PER3; DISPLAY-SDSU:STATUS=LICBLOCK,TYPE=PEN,LEVEL=PER3;
6.
There are 4 modes in the codeword, which could be activated in a HiPath 4000 V2.0 systems. Which modes are realized ?
Solution: 1. 2.
Normal Mode, Trail mode, Emergency mode, Escalated Emergency mode
3. 4.
BR0038
09/17/2009
Page 83 of 132
Siemens
10.2
1.
Solution System Data
Find out the switch number (L-number) of the HiPath 4000.

menu Configuration Management menu HiPath Inventory Management page HIM Welcome Button Search
2.
Which software version, release version and revision level has the system?

menu Configuration Management menu HiPath Inventory Management page Show All HIM Data button Search button Show All HIM Data Welcome Page
3.
Check the available database memory allocations of the system.

menu Configuration Management menu HiPath Inventory Management menu HIM - System Data menu Central Switch Data page Memory Scaling button Search view Object List
BR0038
09/17/2009
Page 84 of 132
Siemens
4.
Check the following features for the whole system:

Callback - LCR Expensive Tone - Central Speed Dialing Individual Speed Dialing COS changeover by attendant console
Solution:

menu Configuration Management menu HiPath Inventory Management menu HIM - System Data menu Features page Technical Features button Search view Object List
Features: callback = CBK LCR Expensive Tone = LCRET Central Peed Dialing=SPDC Individual Speed Dialing=SPDI COS changeover by attendant console=COSXATND
BR0038
09/17/2009
Page 85 of 132
Siemens
10.3
1.
Solution System Dialing Plan
Which Code Types are relevant for the DO NOT DISTURB feature?

menu Configuration Management menu Tables menu Dial Plan page Dial Codes view Search Criteria Code Type: ADND (activate do not disturb) button Search view Search Criteria Code Type: DDND (deactivate do not disturb) button Search
AMO: DISPLAY-WABE:TYPE=GEN,DAR=ADND&DDND;
see also --> feature Do Not Disturb has to be activated:

menu Configuration Management menu Hipath Inventory Management menu HIM System Data menu Features page Technical Features button Search view Object List: DND (Do Not Disturb) --> State: yes
To activate/deactivate the feature DND you have to use the AMO FEASU: CHANGE-FEASU:TYPE=A,CM=DND; CHANGE-FEASU:TYPE=D,CM=DND;
BR0038
09/17/2009
Page 86 of 132
Siemens
Optiset/ optiPoint: activation or deactivation by service menu of the terminal.

Program/Service Feature Settings Do Not Disturb Activate/ Deactivate
2.
Which Code Types are relevant to DISPLAY SUPPRESSION?

menu Configuration Management menu Tables menu Dial Plan page Dial Codes view Search Criteria Code Type: DISUON (display suppression on) button Search view Search Criteria Code Type: DISUOFF (display suppression off) button Search
At the display of the called party appears XXX, because DISPLAYZAND:TYPE=ALLDATA2; --> parameter DISPNUUN = XXX
AMO: DISPLAY-WABE:TYPE=GEN,DAR=DISUOFF&DISUON;
3.
Program a DO NOT DISTURB KEY on an optiPoint, so that it is only available to this subscriber.

menu Configuration Management menu Tables menu Dial Plan page Dial Codes
BR0038
09/17/2009
Page 87 of 132
Siemens
button New Code Type: DNDKY Dial Code: e.g. *40 DPLN: e.g. 15 button Save
AMO: ADD-WABE:CD=*40,DAR=DNDKY,CHECK=N;
allocation of terminal to DPLN group 15:

menu Configuration Management menu Stations page Station button Search button Goto Next/Previous Object for selecting terminal field DPLN Group: 15 button Save
AMO: CHANGE-SBCSU:STNO=7340,DPLN=15;
4.
Which numbers do the code types SNR, LNR, SPLIT, SIGNON, SIGOFF have?
Whats the difference between SNR and LNR? Implement both features.

BR0038
09/17/2009
Page 88 of 132
Siemens
view Search Criteria Code Type: SNR (saved number redial) button Search
You have to look for each Code Type separately. SNR (saved number redial) LNR (last number redial) SPLIT SIGNON sign on a terminal with PIN SIGNOFF sign off a terminal with PIN difference between SNR and LNR SNR: storage of the last dialed number (key or dial code) LNR: automatically storage of the last dialed number (key or dial code) see also --> feature SNR has to be activated. AMO: DISPLAY-WABE:TYPE=GEN,DAR=SIGNOFF&SIGNON&SPLIT&SNR&LNR; CHANGE-FEASU:TYPE=A,CM=SNR; ADD-WABE:CD=**6,DAR=LNR,CHECK=N; CHANGE-ZAND:TYPE=ALLDATA2,LNR=YES;
5.
What is the subscriber numbering scheme used by your own node?
Which of the subscriber numbers are free?

menu Configuration Management menu Tables menu Dial Plan menu Dial Numbers page Dial Numbers button Search view Object List --> status: free or used
BR0038
09/17/2009
Page 89 of 132
Siemens
AMO: DISPLAY-WABE:TYPE=STN,DESTNO=0; DISPLAY-WABE:TYPE=GEN,CD=7300&&7399,DAR=STN; DSTNO=0 respectively * has the meaning own node R means reserved --> available extension number
6.
Set up a Code Type = STN with number=5000 in such a form that it cannot be reached externally. Test your programming. (Possible external numbers: 0-00-49-40-40xxx-yyyy; xxx = Node number(100/200/300/400) yyyy = Extension
menu Configuration Management menu Tables menu Dial Plan menu Dial Numbers page Dial Numbers button New field Station Number: 5000 field Type: STN - Number tab CPS/DPLN Data checkbox CPS: select 2 - 4 and 6 -12 button Save
AMO: ADD-WABE:CD=5000,CPS=2&3&4&5&7&8&9&10&11&12,DAR=STN; REGENERATE-SBCSU:STNO=7340; ADDSBCSU:STNO=5000,OPT=OPTI,CONN=DIR,DVCFIG=OPTIP500,COS1=33,COS2=30,LCOSV1=9, LCOSV2=1,LCOSD1=9,LCOSD2=1,DPLN=0,ITR=0,SSTNO=N,COSX=0,STD=100,INS=Y;
BR0038
09/17/2009
Page 90 of 132
Siemens
10.4
ITR group
Solution ITR Group and Activation of Features
1.
Assign different ITR groups not equal to 0 to an optiPoint subscriber and an optiset subscriber.

menu Configuration Management menu Stations page Station button Search button Goto Next/Previous Object for selecting terminal field ITR: fill out group number button Save
AMO: DISPLAY-SBCSU:STNO=7340&7345; CHANGE-SBCSU:STNO=7340,ITR=1; CHANGE-SBCSU:STNO=7345,ITR=2;
2.
Implement the following traffic restriction.
allowed OPTISET OPTIPOINT 500
prohibited
menu Configuration Management menu Tables page Traffic Restriction
BR0038
09/17/2009
Page 91 of 132
Siemens
page Search activate checkbox for allowed directions button Save
AMO: CHANGE-VBZ:ITRSRC=1,ITRGR=AD,ITRDEST=2; DISPLAY-VBZ;
3.
Assign the two subscribers to ITR group = 1.

menu Configuration Management menu Stations page Station button Search button Goto Next/Previous Object for selecting station field ITR: 1 button Save
AMO: CHANGE-SBCSU:STNO=7340,ITR=1;
Activation of features
4.
Activate the do not disturb-group feature for these subscribers and then deactivate this again.

menu Configuration Management menu System Data menu Maintenance page User Feature Activation For ITR - Group button New
BR0038
09/17/2009
Page 92 of 132
Siemens
select Specific ITR - group field ITR group: 1 button Search select check box DNDGR button Save
AMO: ADD-ACTDA:TYPE=ITR,ITR=1,FEATCD=DNDGR;
5.
Program and activate a variable call forwarding for one of these subscribers on an administrative basis. Test this.

menu Configuration Management menu System Data menu Maintenance page User Feature Activation For Station field Station No.: 4711 button Search tab Call Forwarding Call Forwarding Type: STATIONV Diversion Type: CFU Call type: Gen Service Indicator: VCE Destination: 0815 button Save
AMO: ADDACTDA:TYPE=STN,STNO=7340,FEATCD=FWD,CFVAR=STATIONV,DTYPE=CFU,ITYPE=GEN,SI=V CE,DESTNO=7345; DISPLAY-ACTDA:TYPE=STN,STNO=7340;
BR0038
09/17/2009
Page 93 of 132
Siemens
6.
Change the individual optiset settings for the optiset subscriber. Test this.

menu Configuration Management menu System Data menu Maintenance page User Feature Activation For Station field station number:4711 button Search tab Other Features Optiset Features: select checkbox e.g. Optiset Ringer Volume
AMO: ADD-ACTDA:TYPE=STN,STNO=7340,FEATCD=OPTISET,RINGVOL=7,ROOMCHAR=ECHO; DISPLAY-ACTDA:TYPE=STN,STNO=7340;
BR0038
09/17/2009
Page 94 of 132
Siemens
10.5
1.
Solution COS - Authorization
Find out which COS classes have Mailbox (MB) authorization.

menu Configuration Management menu Table page COS tab Voice 2 view: Search Criteria check box MB button Search
AMO: DISPLAY-COSSU:TYPE=AUTH,COND=SUBSET,VCE=MB;
2.
What authorizations are contained in COS 13?

menu Configuration Management menu Table page COS field COS: 13 button Search
AMO: DISPLAY-COSSU:TYPE=COS,COS=13;
3.
Which subscribers use this class?

menu Configuration Management menu stations page station field COS1 and COS2: searched number button Search
AMO: DISPLAY-COSSU:TYPE=COS,COS=13,FORMAT=REF;
BR0038
09/17/2009
Page 95 of 132
Siemens
4.
Set up a new COS with the following authorizations:

Subscribers with this COS should become LCR subscribers; The cos changeover can be made at the subscriber terminal; They should be able to use the mailbox; They should be able to use external call forwarding;
solution:

menu Configuration Management menu Table page COS button New field COS: free COS class AMO - description: name of new COS - class tab voice 1/ voice2/ voive3: select parameter button Save
AMO: ADD-COSSU:NEWCOS=50,AVCE=TA&COSXCD&MB&TNOTCR&FWDNWK;
5.
What LCOSV classes are used in the system?

menu Configuration Management menu Least Cost Routing menu LCR - Authorization page LCR Class of Service - Voice button Search view Object List
AMO: DISPLAY-COSSU:TYPE=LCOSV,FORMAT=REF;
BR0038
09/17/2009
Page 96 of 132
Siemens
6.
What LCR authorizations are contained in LCOSV class 5 and what is the purpose of these authorizations?

menu Configuration Management menu Least Cost Routing menu LCR - Authorizations page LCR Class of Service - Voice button Search button Goto Next/Previous Object for selecting LCOSV Group
AMO: DISPLAY-COSSU:TYPE=LCOSV,LCOSV=5;
Classmarks determinate the way through the LCR: a) permission to dial a dial plan b) permission to use a trunk
7.
Set up a new LCOSV with the following content: LCR authorizations 1-8 LCR EXPENSIVE TONE (LCRET)

menu Configuration Management menu Least Cost Routing menu LCR - Authorizations page LCR Class of Service - Voice button Search button Goto Next/Previous Object for selecting LCOSV Group select checkbox 1 - 8 and LCRET button Save
AMO: CHANGE-COSSU:TYPE=LCOSV,LCOSV=15,ALAUTH=1&&8,ALCROPT=LCRET;
BR0038
09/17/2009
Page 97 of 132
Siemens
8.
Assign this LCOSV to a subscriber, so that he can use the higher LCR authorizations in daytime cos.

menu Configuration Management menu stations page station field COS1 and COS2: fill in number button Save
AMO: CHANGE-SDAT:STNO=7340,TYPE=DATA,LCOSV1=15;
98
BR0038 09/17/2009 Page 98 of 132
Siemens
10.6
Solution COS Changeover
1.
Assign one optiPoint and one Optiset subscriber in a COS group that is not equal to 0.

menu Configuration Management menu Stations page Station button Search button Goto Next/Previous Object for selecting station field COS1: fill in group field COS2: fill in group button Save
AMO: CHANGE-SBCSU:STNO=7340&7345,COSX=10;
2.
Assign these subscribers a COS2 without mailbox authorization.

menu Configuration Management menu Tables page COS tab Voice 1: select checkbox MB button Search view Object List --> overview about all COS groups with MB page COS button Search view Object List without selecting a parameter --> overview about all COS groups menu Configuration Management menu stations page station button Search
BR0038
09/17/2009
Page 99 of 132
Siemens
button Goto Next/Previous Object for selecting station field COS2 - Group: fill in group without MB
AMO: DISPLAY-COSSU:TYPE=COS; CHANGE-SBCSU:STNO=7340&7345,COS2=30;
3.
Now change over the COS group to the night-time class of service.

menu Configuration Management menu Tables page Active COS Groups page Search field Switchover Group: see exercise 1 tab Active COS field Active COS: 2 button: Save
See also: feature COSXCD has to be activated

menu Configuration Management menu Hipath Inventory Management menu HIM System Data menu Features page Technical Features button Search view Object List: COSXCD --> State: yes
AMO: CHANGE-BERUM:TYPE=COSX,COSX=10,COSACT=2;
BR0038
09/17/2009
Page 100 of 132
Siemens
4.
Test behavior with and without mailbox authorization.
subscriber in COS2: message will be signalled by mailbox but you wont get an output.
5.
How does a subscriber know if he/she is in daytime or night-time service?
special dial tone in the state of night time service
6.
Subscribers change over themselves. What does this require?
feature COSXCD has to be activated (see also exercise 3) AMO: CHANGE-FEASU:TYPE=A,CM=COSXCD;
subscriber need a COS1 and COS2 group with the authorization COSXCD (COS changeover with code)

menu Configuration Management menu stations page station button Search button Goto Next/Previous Object for selecting station field COS 1: fill in group field COS 2: fill in group link to COS1 and COS2
AMO: CHANGE-COSSU:TYPE=COS,COS=30&33,AVCE=COSXCD;
Code Types ACOSX and DCOSX has to be configured

BR0038
09/17/2009
Page 101 of 132
Siemens
view Search Criteria Code Type: ACOSX button Search
same for DCOSX AMO: DISPLAY-WABE:TYPE=GEN,DAR=ACOSX&DCOSX;
to configure a Code Type see chapter system dialing plan COPIN 7 has to be configured

menu Configuration Management menu stations page station button Search button Goto Next/Previous Object for selecting station tab PIN
AMO: DISPLAY-WABE:TYPE=GEN,DAR=ACOSX&DCOSX;
7.
Implement active, timed switching of COS groups 0-4 and 6-15 as follows: from night to day: Mon. Fri.: 8.00 a.m. Sat. + Sun.: 9.00 a.m. from day to night: Mon. Fri.: 6.00 p.m. Sat.: 3.00 p.m. Sun.: 12.oo p.m.
feature COSXT has to be activated (see also exercise 3)
menu Configuration Management
BR0038
09/17/2009
Page 102 of 132
Siemens
menu Tables page COS switchover page Search field COSX Group: select Group fill in COS1and COS2 times select check boxes Active button: Save
AMO: ADD-BERUZ:COSX=0&&4&6&&15,DAY=1&&5,COS1T=08-00,COS1=ON,COS2T=18-00,COS2=ON; ADD-BERUZ:COSX=0&&4&6&&15,DAY=6,COS1T=09-00,COS1=ON,COS2T=15-00,COS2=ON; ADD-BERUZ:COSX=0&&4&6&&15,DAY=7,COS1T=08-00,COS1=ON,COS2T=12-00,COS2=ON; DISP-BERUZ;
8.
Program a deactivated (prepared) timed changeover for COS group 5 as follows: from night to day: Mon. Sun.: 8.00 a.m. from day to night: Mon. Sun.: 11.00 a.m.
see exercise 7 dont tack checkbox Active AMO: ADD-BERUZ:COSX=5,DAY=1&&7,COS1T=08-00,COS1=OFF,COS2T=23-00,COS2=OFF; DISP-BERUZ:COSX=5;
BR0038
09/17/2009
Page 103 of 132
Siemens
10.7
1.
Solution Key Programming
Install and activate an Optiset Add-on-terminal.

menu Configuration Management menu Stations menu Station field Extension: fill in extension number button Search link Device combination Layout Type: select type with one key module button Save
AMO: CHANGE-SBCSU:STNO=7341,OPT=OPTI,REP=1;
2.
How are the additional 15 keys assigned?

menu Configuration Management menu Stations menu Station field Extension: fill in extension number button Search button Indiv. Keylayout tab Add-on device
AMO: DISP-SBCSU:STNO=7341; DISPLAY-TAPRO:TYPE=STD,STD=4,DIGTYP=OPTISET;
BR0038
09/17/2009
Page 104 of 132
Siemens
3.
Program 2 function keys on an administrative basis, a VC key and an VCR key, on keys 1 and 2 of the add-on-terminal.

menu Configuration Management menu Stations menu Station field Extension: fill in extension number button Search button Indiv. Keylayout tab Add-on device Keyfunctions: VC (voice-call key) click key which should get this function Keyfunctions: VCR (voice-call reject key) click key which should get this function button Save
AMO: CHANGE-TAPRO:STNO=7341,DIGTYP=OPTIA1,KY01=VC,KY02=VCR;
4.
Program 2 destinations (name keys) on an administrative basis, on keys 3 and 4 of the key module.
see exercise 3

Keyfunctions: NAME click key which should get this function field Destination: fill in destination button Save
AMO: CHANGE-TAPRO:STNO=7341,DIGTYP=OPTIA1,KY03=NAME,KY04=NAME; ADD-ZIEL:TYPE=NAME,SRCNO=7341,KYNO=3,DESTNON="7300",DEV=AD1,LEVEL=1; ADD-ZIEL:TYPE=NAME,SRCNO=7341,KYNO=3,DESTNON="7310",DEV=AD1,LEVEL=2; ADD-ZIEL:TYPE=NAME,SRCNO=7341,KYNO=4,DESTNON="7320",DEV=AD1,LEVEL=1; ADD-ZIEL:TYPE=NAME,SRCNO=7341,KYNO=4,DESTNON="7330",DEV=AD1,LEVEL=2;
BR0038
09/17/2009
Page 105 of 132
Siemens
5.
Program 2 destinations on key 5 of the key module at the terminal.

Program/Service Destinations Direct dest. select Enter new number Save Storing two numbers with one key you have to use the key shift (key 16)
AMO: CHANGE-TAPRO:STNO=7341,DIGTYP=OPTIA1,KY05=NAME;
6.
Program a direct station selection key on an administrative basis. What has to be taken into account?
see exercise 3 keyfunction DSS see also: DSS has to be activated:

menu Configuration Management menu Hipath Inventory Management menu HIM System Data menu Features page Technical Features button Search view Object List: DSS --> State: yes
AMO: CHANGE-FEASU:TYPE=A,CM=DSS; CHANGE-TAPRO:STNO=7341,DIGTYP=OPTIA1,KY09=DSS; ADD-ZIEL:TYPE=DSS,SRCNO=7341,KYNO=9,DESTNOD=7342,DEV=AD1;
BR0038
09/17/2009
Page 106 of 132
Siemens
7.
How does the called party know that it is being called directly?
special tone
8.
Implement the feature CONFERENCE.
see exercise 3 key function CONF see also feature CONF has to be activated AMO: CHANGE-FEASU:TYPE=A,CM=VARCONF; CHANGE-TAPRO:STNO=7341,DIGTYP=OPTISET,KY05=CONF;
9.
Implement the LAST NUMBER REDIAL FEATURE with the appropriate key.
see exercise 3 key function LNR see also feature LNR has to be activated AMO: CHANGE-ZAND:TYPE=ALLDATA2,LNR=YES; CHANGE-TAPRO:STNO=7341,DIGTYP=OPTIT12,KY06=LNR;
10. Change an assigned key standard from an optiset subscriber and an optiPoint subscriber.

menu Configuration Management menu Stations menu Station field Extension: fill in extension number button Search button Indiv. Keylayout: used standard is shown link to Keylayout menu Action: assign keylayout
BR0038
09/17/2009
Page 107 of 132
Siemens
Keyfunctions: select new function click key which should get this function button Save
AMO: DISPLAY-SBCSU:STNO=7341,TYPE=TERMDATA; DISPLAY-TAPRO:TYPE=STD,STD=4,DIGTYP=OPTISET; CHANGE-TAPRO:STD=4,DIGTYP=OPTIT12,KY11=PU; CHANGE-TAPRO:STNO=7341,STD=4;
11. Which subscribers use optiset-Standard 4?

menu Configuration Management menu Tables page Standard Key Layout field Standard Key layout: 4 button: Search
AMO: DISPLAY-TAPRO:TYPE=STN,STD=4,DIGTYP=OPTISET;
12. Which optiPoint standards are used in the system?

menu Configuration Management menu Tables page Standard Key Layout Layout Optiset button Search view Object List
--> all 128 standards will be shown

view Search Criteria Layout: optiPoint
BR0038
09/17/2009
Page 108 of 132
Siemens
button Search view Object List
--> all 128 standards will be shown
AMO: DISPLAY-TAPRO:TYPE=STD,DIGTYP=OPTIT19;
13. Program the function BUZZ on an administrative basis.

menu Configuration Management menu stations menu station field Extension: fill in extension number button Search button Indiv. Keylayout Keyfunctions: BUZZ click key which should get this function button Save
AMO: CHANGE-TAPRO:STNO=7345,KY08=BUZZ; ADD-ZIEL:TYPE=BUZZ,SRCNO=7345,DESTNOBZ=7341;
BR0038
09/17/2009
Page 109 of 132
Siemens
10.8
1.
Solution Central/ individual Speed Dialing Facility
Set up 5 speed dialing lists (list: 0+1-4). Group 1 (terminal 1): Lists 0 + 1 + 2 Group 2 (terminal 2): Lists 3 + 4 Dimension the list so that 100 destinations can be added at a later point.

menu Configuration Management menu Tables page Speed Dialing List button Search for listing list button Add Entry Speed Dial List: number of new list Start Index: first short number (3 letters) End Index: last short number (3 letters) button Save view Object List
AMO: ADD-LRNGZ:LST=0,SPDMIN=000,SPDMAX=049; ADD-LRNGZ:LST=1,SPDMIN=050,SPDMAX=199; ADD-LRNGZ:LST=2,SPDMIN=200,SPDMAX=399; DISPLAY-LRNGZ:TYPE=SYS; 2. Assign lists 0 + 1 (3) to a subscriber 1 and lists 0 + 2 (4) to a subscriber 2.

menu Configuration Management menu stations page station button Search button Goto Next/Previous Object for selecting terminal field Speed Dialing List 1: 0 field Speed Dialing List 2: preferred list (1 - 4)
BR0038
09/17/2009
Page 110 of 132
Siemens
AMO: CHANGE-SBCSU:STNO=7341,SPDC1=0,SPDC2=1; CHANGE-SBCSU:STNO=7342,SPDC1=0,SPDC2=2;
3.
Fill the lists with destinations.
Note: Possible destination pattern:0-00-49-40-40xxx-y

0-0-40-40xxx-y 0-40xxx-y xxx = Node numbers (100/200/300/400) y = Extensions (7zzz) Assign names for the destinations and set supplementary dial (SUPDIAL) so that each extension of each node can be reached.

menu Configuration Management menu Tables page Speed Dialing List button Search for listing list field Index: short number e.g. 000 field Number: e.g. 0 0049 40 40100 7400 field Truncate field description Add Entry for more abbreviation number button Save
BR0038
09/17/2009
Page 111 of 132
Siemens
AMO: ADD-ZRNGZ:LST=00,SPDNO=000,DESTNO=0004940404007410,SUPDIAL=7; ADD-ZRNGZ:LST=00,SPDNO=001,DESTNO=0004940404007400,SUPDIAL=7; ADD-ZRNGZ:LST=00,SPDNO=002,DESTNO=0004940404007420,SUPDIAL=7; ADD-ZRNGZ:LST=00,SPDNO=003,DESTNO=0004940404007430,SUPDIAL=7; ADD-ZRNGZ:LST=00,SPDNO=004,DESTNO=0004940404007440,SUPDIAL=7; ADD-ZRNGZ:LST=00,SPDNO=005,DESTNO=0004940404007441,SUPDIAL=7; DISPLAY-ZRNGZ:TYPE=LST,LST=0;
ADD-ZRNGZ:LST=01,SPDNO=000,DESTNO=0004940401007100,SUPDIAL=7; DISPLAY-ZRNGZ:TYPE=LST,LST=1;
CHANGE-FEASU:TYPE=A,CM=SPDC;
DISPLAY-WABE:TYPE=GEN,DAR=SPDC1&SPDC2;
4.
Delete a SPDNO area.

menu Configuration Management menu Tables page Speed Dialing List button Search for listing list button Goto Next/Previous Object for selecting list tag entries for deleting button Delete Entry button Save
AMO: DELETE-ZRNGZ:LST=0,SPDNO=10&&14; DISPLAY-ZRNGZ:TYPE=LST,LST=0;
BR0038
09/17/2009
Page 112 of 132
Siemens
5.
Add a further 50 destinations to one of the lists you use.

menu Configuration Management menu Tables page Speed Dialing List button Search for listing list button Goto Next/Previous Object for selecting list End Index: increase 3-digit abbreviated number button Save
AMO: CHANGE-LRNGZ:LST=0,TYPE=CNT,NO=50;
6.
Program destinations on the numeric keys of the telephone (analog and optiset). Check these by means of the administration.
analog telephone Program by terminal:

lift off handset dial dial code SPDIPROG push number key for programming dial long destination number
use speed dialing:

lift off handset dial dial code SPDIP push programmed number key
optiset:

Program/Service Destinations Speed Dialing Index: 01 number: e.g. 0-0049-89-722-0 Save
see also: page Station SPDI Entries: e.g. 10
BR0038
09/17/2009
Page 113 of 132
Siemens
10.9
1.
Solution Displayname and PIN
Assign a displayname and an organization name to an optiPoint. Test this function.

menu Configuration Management menu Stations menu Station field Extension: fill in extension number button Search field Display Name field Organization button Save
AMO: ADD-PERSI:TYPE=STN,STNO=7145,NAME="TEST",ORG="TI MUNICH";
2.
Check which identification with PIN is possible (internal or network-wide)?

menu Configuration Management menu Hipath Inventory Management menu HIM System Data menu Features page Technical Features button Search view Object List: PININT or PINNW --> State: yes
AMO: DISPLAY-FEASU; Activation fo PIN intern and Deactivation of PIN network-wide: CHANGE-FEASU:TYPE=A,CM=PININT; CHANGE-FEASU:TYPE=D,CM=PINNW;
BR0038
09/17/2009
Page 114 of 132
Siemens
3.
What requirements must be met so that a subscriber can identify himself at any terminal on the node?
station:

menu Configuration Management menu Stations menu Station field Extension: fill in extension number button Search tab PIN table Type: Manual PIN
system dialing plan:

menu Configuration Management menu Tables menu Dial Plan page Dial Codes button Search view Object List Code Type: APIN1 and DPIN has to be configured
AMO: DISPLAY-WABE:TYPE=GEN,DAR=APIN1&DPIN; DISPLAY-PERSI:TYPE=STN,STNO=7341;
BR0038
09/17/2009
Page 115 of 132
Siemens
4.
For how long does the identification remain active?
Arrange that identification should only be activated for a single call.

menu Configuration Management menu Tables menu PIN page Class of PIN button Search Type of PIN: Manual PIN Duration of the activated PIN: ONE
AMO: DISPLAY-PERSI:TYPE=STN,STNO=7341; CHANGE-PERSI:TYPE=COPIN,COPIN=1,PINDUR=ONE;
BR0038
09/17/2009
Page 116 of 132
Siemens
10.10
1.
Solution Subscribers and Features
Check that all the requirements for setting up optiPoint terminals are met.
Before you can configure a subscriber you need a free subscriber number and a free port. AMO-usage: AMO WABE concerning subscriber number and AMO BCSU and SDSU concerning free ports.
2.
Take any optiPoint. Store this optiPoint as a template. Store this template without authorizations, display entries and speed dial lists.

menu Configuration Management menu Stations menu Station field Extension: fill in extension number button Search Action: Save as Template button Save view: Search Criteria (empty mask appears)
3.
Set up an optiPoint terminal with the help of the template.

Action: Get Template complete parameters
4.
Set up an optiset terminal with an AMO.
ADD-SBCSU:STNO=7342,OPT=OPTI,CONN=DIR,PEN=1-2-552,DVCFIG=OPTISET,COS1=33,COS2=30,LCOSV1=9,LCOSV2=1,LCOSD1=9,LCOSD2=1,DPLN=0 ,ITR=0,SSTNO=N,COSX=0,SPDI=30,SPDC1=0,SPDC2=1,STD=100,SECR=NO,INS=Y,RCBKB=N O,RCBKNA=NO,DIGNODIS=NO,CBKBMAX=5,TEXTSEL=ENGLISH;
BR0038
09/17/2009
Page 117 of 132
Siemens
5.
Protect the terminal with the feature reject call back on no answer.

menu Configuration Management menu Stations menu Station field Extension: fill in extension number button Search tab Basic 1 select Callback-No. Ans Rej.
AMO: CHANGE-SBCSU:STNO=7342,RCBKNA=Y;
BR0038
09/17/2009
Page 118 of 132
Siemens
10.11
1.
Solution Call Pick Up
Set up a call pickup group as described below and monitor it:

1 x optiPoint + 1 x optiset + 1 x ANATE The station number of the calling party should not be displayed 3 alerting tones, only when there is no answer Pick up of second call disabled
solution: display:

menu Configuration Management menu Groups page Call Pick Up button Search --> overview about all pick up groups
set up of a new/further pick up group:

button New field PU Group: new group number tab Extension: number of first PU member button Add Entry tab Suppl. Data field Alerting Call: IDLE3 field Signal: All checkbox Display: dont select checkbox Pickup Second Call: dont select button Save
allocate keys to terminals --> see key programming see also: feature PU has to be activated
BR0038
09/17/2009
Page 119 of 132
Siemens
AMO: DISPLAY-AUN:TYPE=SYS; CHANGE-FEASU:TYPE=A,CM=PU; ADDAUN:GRNO=1,STNO=7145&7140&7100,DISTNO=YES,NOTRNG=ONIDLE3,PUSECOND=NO,SIGNAL =ALL; CHANGE-TAPRO:STNO=7140,KY05=PU; CHANGE-TAPRO:STNO=7145,KY05=PU; DISPLAY-WABE:TYPE=GEN,DAR=PU; DISPLAY-AUN:TYPE=SYS;
2.
Include a fourth subscriber in the call pickup group.

menu Configuration Management menu Groups page Call Pick Up button Search --> overview about all pick up groups Select PU group view object button: Add Entry field Extension: further PU member button Save
AMO: ADD-AUN:GRNO=1,STNO=7146; DISPLAY-AUN:TYPE=SYS;
BR0038
09/17/2009
Page 120 of 132
Siemens
3.
Change the following characteristics of the call pickup group and monitor these:

The station number of the calling party should be displayed 3 periodical alerting tones Enable pick up of second call
solution:

menu Configuration Management menu Groups page Call Pick Up button Search --> overview about all pick up groups Select PU group view object tab Suppl. Data Display: activate field Alerting Call: Period 3 field Pick Up: activate button Save
AMO: CHANGE-AUN:TYPE=GR,GRNO=1,DISTNO=YES,NOTRNG=PERIOD3,PUSECOND=YES; DISPLAY-AUN:TYPE=SYS;
4.
Implement the call pickup group PARK feature.
see exercise key programming key function PARK AMO: CHANGE-TAPRO:STNO=714&7145&7146,KY06=PARK;
BR0038
09/17/2009
Page 121 of 132
Siemens
5.
Allow the analog subscriber in the call pickup group also to receive an acoustic signal when a call is received for another call pickup group subscriber. Enable the analog subscriber to activate/deactivate the acoustic signal himself. Test this.

menu Configuration Management menu Table page COS field COS: COS - number of the analog terminal button Search checkbox GRPCAL: activate button Save
AMO: DISPLAY-SCSU:STNO=7100; DISPLAY-COSSU:TYPE=COS,COS=3; ADD-COSSU:COPYCOS=3,NEWCOS=33,AVCE=GRPCAL; CHANGE-SCSU:STNO=7100,COS1=3;
BR0038
09/17/2009
Page 122 of 132
Siemens
10.12
1.
Solution Executive/Secretary Group
Set up a 2 executive <-> 1 secretary configuration. a) What requirements need to be met before the executive /secretary group is set up? The SECRETARY device has to have an add-on device (key module) and the TOGGLE feature is to be enabled in the SECRETARY device at the press of a button. Characteristics of the required executive /secretary group: 2 executives <-> 1 secretary; Representative = yes; Special ringing rhythm for executive <-> secretary calls; Alerting tone = ON3
b)
Adapt the REP device to the SECRETARY device. What executive /secretary group functions can be implemented?
Solution 1a):
subscriber numbers in this protocol: secretary: executive 1: executive 2: representative: 7243 7240 7241 7261
requirements: features SPLIT, PU, DSS has to be activated AMO: CHANGE-FEASU:TYPE=A,CM=SPLIT&DSS&PU;
BR0038
09/17/2009
Page 123 of 132
Siemens
menu Configuration Management menu Groups page CHESE - Group button New field Executive/Secretary: new group number tab Members Extension: 7243 field Extension: Secr. field Allocation: 1 button New Entry Extension: 7240 field Extension: Exec. field Allocation: 1 button New Entry Extension: 7241 field Extension: Exec. field Allocation: 1 button New Entry Extension: 7261 field Extension: Subst. tab Suppl. Data Alerting Tone: ON3 Multiple Call: activate button Save
AMO: ADDCHESE:GRNO=1,EXEC=7240&7241,SECR=7243,ALLOC=E1S1&E2S1,MULTN=Y,REP=7261,NOTR NG=ON3; key programming
BR0038
09/17/2009
Page 124 of 132
Siemens
Secretary device
menu Configuration Management menu stations menu station field Extension: 7243 button Search button Indiv. Keylayout tab main device Keyfunctions: RNGXFER (ring transfer executive/secretary key) click key which should get this function Keyfunctions: REP (representative) click key which should get this function Keyfunctions: PUS (executive/secretary ring transfer key) click key which should get this function Keyfunctions: DSS (direct station selection key) click key which should get this function button Save field Destination: 7240 click empty field next to DSS - key button Save configure key function RNGXFER and DSS for executive 2
AMO: TAPRO and ZIEL Executive device:

menu Configuration Management menu stations menu station
BR0038
09/17/2009
Page 125 of 132
Siemens
field Extension: 7240 button Search button Indiv. Keylayout tab main device Keyfunctions: RNGXFER (ring transfer executive/secretary key) click key which should get this function Keyfunctions: DSS (direct station selection key) click key which should get this function button Save field Destination: 7243 click empty field next to DSS - key button Save
same procedure for second executive AMO: TAPRO and ZIEL Solution 1b) You can only configure key DSS (not PUS, RNGXFER, REP).
BR0038
09/17/2009
Page 126 of 132
Siemens
2.
Enable the executive to use the VOICE CALLING facility to speak to the secretary by pressing a single button.

menu Configuration Management menu Stations menu Station field Extension: 7243 button Search tab Class Marks select VC button Indiv. Keylayout tab main device Keyfunctions: NAME click key which should get this function button Save field Destination: dial code and destination number click empty field next to NAME - key button Save
AMO: CHANGE-FEASU:TYPE=A,CM=RNG; CHANGE-SDAT:STNO=7240&7241,TYPE=ATTRIBUT,AATTR=VC; CHANGE-TAPRO:STNO=7243,KY12=VCR; CHANGE-TAPRO:STNO=7240&7241,KY13=NAME; ADD-WABE:CD=**90,DAR=VOICECAL; ADD-ZIEL:TYPE=NAME,SRCNO=7240,KYNO=13,DESTNON="**907243"; ADD-ZIEL:TYPE=NAME,SRCNO=7241,KYNO=13,DESTNON="**907243";
BR0038
09/17/2009
Page 127 of 132
Siemens
3.
Set up a conference corner telephone for EXECUTIVE 1.

configure a new terminal combine executive terminal and conference corner terminal with a PU group
AMO: ADD-AUN:GRNO=25,STNO=7240&7200;
4.
Program a name key with a destination number that cannot be deleted.

menu Configuration Management menu Stations page Station field Extension: fill in extension number button Search button Indiv. Keylayout tab main device Keyfunctions: NAME click key which should get this function button Save field Destination: destination number click empty field next to NAME - key checkbox Protect: activate button Save
AMO: CHANGE-TAPRO:STNO=7240,KY14=NAME; ADD-ZIEL:TYPE=NAME,SRCNO=7240,KYNO=14,DESTNON="7241",PROTECT=YES;
BR0038
09/17/2009
Page 128 of 132
Siemens
10.13
1.
Solution Hunt Group
Set up a voice hunt group.
access code of the hunt group has to be configured in system dialing plan

menu Configuration Management menu Tables menu Dial Plan menu Dial Numbers page Dial Numbers button New field Station Number: 6000 field Type: Hunt button Save
AMO: ADD-WABE:CD=6000,DAR=HUNT;
configuration of the hunt group

menu Configuration Management menu Groups page Hunt Group button New field Extension Number: 6000 Name: Hunt 1 tab Members for Voice field Extension: first member of hunt group button: New Entry field Extension: further members tab Suppl. Data for Voice field Search Mode: cyclic
BR0038
09/17/2009
Page 129 of 132
Siemens
field Capacity: 1 field Overflow Dest. Type: Extension Overflow Dest. Type Number: Extension number
see also: feature PU has to be activated. AMO: CHANGE-FEASU:TYPE=A,CM=HTVCE; ADDSA:TYPE=VCE,CD=6000,STNO=7300&7320&7340,STYPE=CYC,CQMAX=1,NAME="SAMMEL1",FN A=Y,CSANS=N,LVAFTEXT=N,EXECCFW=N,OVFLCYCL=N,OVFLDEST=DESTEXT,NUMBER=7400;
2.
Remove the optiset subscriber from the hunt group.

menu Configuration Management menu Groups page Hunt Group button Search button Goto Next/Previous Object for selecting hunt group mark extension for delete button Delete Entry button Save
AMO: DELETE-SA:TYPE=STN,CD=6000,SVC=VCE,STNO=7340;
BR0038
09/17/2009
Page 130 of 132
Siemens
3.
Add the Optiset subscriber to the hunt group again.

menu Configuration Management menu Groups page Hunt Group button Search button Goto Next/Previous Object for selecting hunt group button Add Entry field Extension: new extension number button Save
AMO: ADD-SA:TYPE=STN,CD=6000,SVC=VCE,STNO=7340,POS=2;
4.
Set up a MASTER hunt group with the same settings as described 1. Do not delete the hunt group you have set up! What settings cannot be transferred or implemented?
The number of a master hunt group has the type station attributes which cant be implemented: members of the master hunt group can be reached by all extensions of the node code type station cant be configured in system dialing plans for configuration see exercise 1, checkbox Master has to be activated
AMO: ADDSA:TYPE=VCE,CD=7340,STNO=7300&7320,STYPE=CYC,CQMAX=1,NAME="SAMMEL1",FNA=Y,V ARCQ=N,CSANS=N,LVAFTEXT=N,EXECCFW=N,OVFLCYCL=N;
BR0038
09/17/2009
Page 131 of 132
Siemens
5.
Change the search type to LINEAR and allow the size of the call queue to be defined by the HiPath 4000. How large is the call queue set by the HICOM and why?

menu Configuration Management menu Groups page Hunt Group button Search button Goto Next/Previous Object for selecting hunt group tab Suppl. Data for Voice check box Variable Call Queue: activate button Save
The variable call queue has the same capacity as the number of active members of the hunt group. AMO: CHANGE-SA:TYPE=TYPE,CD=7340,SVC=VCE,STYPE=LIN,VARCQ=Y;
BR0038
09/17/2009
Page 132 of 132
Diagnsticos
9. Diagnsticos
Diagnsticos
Diagnosis
Siemens
Diagnosis
Contents
1 1.1 2 2.1 3 3.1 4 4.1 5 5.1 5.2 5.3 Diagnostics with UW7 (Assistant 4000). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 HiPath 4000 Assistant Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Dynamic Traffic Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 TSKA (Test Simulation of Key Function). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.1.1 Graphical Representation in TSKA Session tab . . . . . . . . . . . . . . . . . . . . . . . 9 HSD (Hardware and Symptom Diagnosis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 RDS (Real Time Diagnosis System). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 About Realtime Diagnosis System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Starting RDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Monitor Trunk/Line/Data Line and ISDN Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.3.1 Starting Monitoring/ISDN Trace: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.3.2 ISDN Trace Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.3.3 Monitor Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.3.4 Protocolle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Abbreviation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
BR0038
17/09/2009
Page 1 of 23
Siemens
Diagnosis
BR0038
17/09/2009
Page 2 of 23
Diagnosis
Siemens
1
1.1
Diagnostics with UW7 (Assistant 4000)

HiPath 4000 Assistant Menu
The Assistant 4000 contains different possibilities for diagnostic purposes. A lot of diagnostic tools are part of the menu Diagnostics. There are tools for analysing and controlling subscribers, trunks and trunk groups. After opening the assistant the menu tree is indicated. In the menu sublist differt diagnostic possibilities.
BR0038
17/09/2009
Page 3 of 23
Siemens
BR0038
17/09/2009
Page 4 of 23
Diagnosis
Siemens
2
2.1
Dynamic Traffic Monitoring

Overview
To start the Dynamic Traffic Monitoring application, select Diagnostics -> Dynamic Traffic Monitoring from the HiPath 4000 Assistant start page. DTM has the capability to measure the actual load of the trunk groups. It is possible to make a snapshot of the selected trunk groups or to start a monitoring job on them. For the snapshot function any number of trunk groups can be selected but a monitoring job allows only up to four trunk groups to contain. The number of monitoring jobs is also limited to 20 and the longest duration of the monitoring jobs is 24 hours. The benefits of DTM are especially in large Hicom networks where the nodes are strongly interconnected with each other. DTM provides a way to find bottlenecks in the network configuration, to detect possible misconfiguration or defect hardware, to identify peak load periods or just to make statistics of the traffic on the trunk groups.
BR0038
17/09/2009
Page 5 of 23
Siemens
BR0038
17/09/2009
Page 6 of 23
Diagnosis
Siemens
3
3.1
TSKA (Test Simulation of Key Function)

Overview
The TSKA application enables the HiPath 4000 Assistant user to display and simulate OptiSet or OptiPoint devices at a customers site. TSKA displays:

display messages, LED status, function key assignments.
The user can remotely simulate the pressing of function keys and keys of the keypad. Therefore, a graphical representation of the device in a browser window is provided.
>
Please note that only one TSKA user is allowed to start and work with TSKA at a time.
BR0038
17/09/2009
Page 7 of 23
Siemens
Diagnosis
TSKA Session
Simulation
HiPath 4000
HiPath 4000 Assistant -> Diagnostics
LAN/WAN
BR0038
17/09/2009
Page 8 of 23
Diagnosis
Siemens
3.1.1
Graphical Representation in TSKA Session tab
Depending on the setting in the Phone Layout field on the TSKA home page, the TSKA Session tab sheet contains a graphical representation of the devices layout.
BR0038
17/09/2009
Page 9 of 23
Siemens
BR0038
17/09/2009
Page 10 of 23
Diagnosis
Siemens
4
4.1
HSD (Hardware and Symptom Diagnosis)

Overview
The tool is designed to assist service personnel in:

debugging hardware problems isolating configuration or trunk problems providing relevant information for software problems in the CBX.
Starting the application To start the Hardware and Symptom Diagnosis application, select Diagnosis -> Hardware and Symptom Diagnosis from the HiPath 4000 Assistant start page. The following start page appears.
BR0038
17/09/2009
Page 11 of 23
Siemens
Diagnosis
With the HW and symptom diagnostic the current plant status and over the left menu tree is spent is given the possibilty the alarm and the expenditure for error message. HW and SW statistics are callable ( ANMO HISTA) over the error messages are haven adjustable. An interpretation assistance is given by the ALFE Tool.
BR0038
17/09/2009
Page 12 of 23
Diagnosis
Siemens
5
5.1
RDS (Real Time Diagnosis System)

About Realtime Diagnosis System
Realtime Diagnosis System (hereafter referred to as RDS) provides telephony fault localization for station and data lines and limited trunk fault reporting capabilities for trunk facility problems. It provides tools and features to help reduce the time of solving trunk problems, as well as enabling you to solve the problems more efficiently. The function shall be accessible entirely by internet browsers. Using internet browser allows remote control. Therefore the user interface is created using HTML, JAVASCRIPT and other webbased technologies. RDS provides the following features:
Monitoring Monitor trunk/line/data line - This feature allows you to view the call processing events as they occur. ISDN trace - This feature applies to ISDN trunk interfaces and ISDN devices and allows you to capture and display the decoded layer 3 messages.
On-demand facility tests -- These tests facilitate testing between the HiPath 4000 and the facility provider by providing standard transmission tests, such as sending and receiving test tones. The tests are: Bit Error Rate (BER) Test and Network-wide BER Test Echo Return Loss/Singing Return Loss (ERL/SRL) Test Send Signal Test Receive Signal Test Loopback Test
Trunk Rolling -- This feature is only available for specific boards. It enables you to exchange or roll trunk facilities on TMC16 boards. Once a trunk is rolled, you can observe the trunk tests to isolate the suspected trunk.
These features significantly enhance remote diagnostic efficiency of telephony problems, and reduce the need for test equipment. The RDS Help system displays the general information about RDS and its features. Help popup windows display auxiliary text. To access the help facility from any RDS control page, click the Help Icon in the header bar. The Help System appears in an applett which is independent from the browser. Error messages display for test failures, application errors, or user input errors.
BR0038
17/09/2009
Page 13 of 23
Siemens
Diagnosis
5.2
Starting RDS
After calling up the Real Time Diagnosis System the Startup-screen appears.
Before working with RDS you have to create a new session. Insert user name and a short description to give information to other users. Currently the system allows only one user a time. By clicking the button Logon the form is sent to the system.
BR0038
17/09/2009
Page 14 of 23
Diagnosis
Siemens
BR0038
17/09/2009
Page 15 of 23
Siemens
Diagnosis
5.3
Monitor Trunk/Line/Data Line and ISDN Trace
Monitor Trunk Line Data Line allows viewing the call processing and device handler events as they occur. Watch what dialing and how the switch is reacting, which numbers are outpulsed etc. This feature allows you to understand complex call scenarios online. ISDN Trace allows you to capture and display the decoded layer 3 messages as they occur. So you are able to identify protocol mismatches very fast, because of easy accessibility of the interpreted layer 3 ISDN Messages. From the RDS Session Management page you can choose Monitor Trunk Line/Data Line/ISDN Trace from the navigation bar. Click on the hyperlink. The Monitor Trunk/Line/Data Line Control Page will appear:
BR0038
17/09/2009
Page 16 of 23
Diagnosis
Siemens
5.3.1
Starting Monitoring/ISDN Trace:
You have to fill in the entry fields and to select from the list boxes. The state of the job is displayed as Idle, Pending or Active. 1. 2. 3. 4. 5. 6. 7. Enter the PEN or station number in the Station/PEN field Enter the desired TSI or BCH (B-Channel) number, if to apply. In the Type field, select Station Monitor, ISDN Tracer or Trunk Monitor from the list box. In the Service field, select Voice, DEE or FAX from the list box. This field is not applicable when selected Trunk Monitor or ISDN Tracer as Monitor type. Select the corresponding Start button. When you want to end trunk or line monitoring, select the Stop button. Alternatively you can stop all active jobs at the same time by clicking the Stop All button. Click the Monitor Display button or the ISDN Trace Display button to view the results.
This example shows in the first line a ISDN Trace, in the second line a data line monitoring. The state is indicated. In this example there are two more traces or Monitors possible.
BR0038
17/09/2009
Page 17 of 23
Siemens
Diagnosis
5.3.2
ISDN Trace Display
Click ISDN Trace Display gives you the ISDN Layer 3 Message Trace in a new browser instance.
When an ISDN span is traced, scores (hundreds) of messages come through for a 30 (23) channels of the span. You can stop the auto-scrolling by unchecking the check control auto scroll. To see all the messages related to a specific phone call, click on the CR header box. This will sort the messages by Call Reference (CR) number. To return to the sort by time, click on the Time header. In some cases the size of a Layer 3 ISDN message frame is too small for the information being transmitted with the Layer 3 message. These messages will be transmitted in segments. SEGMENT messages always belong to a group of messages. The real type of the message (e.g. SETUP or ALERTING) is indicated by the first message type which follows the preceding SEGMENT messages. Double-clicking on the real type offers details of the complete message.
BR0038
17/09/2009
Page 18 of 23
Diagnosis
Siemens
Double clicking an ISDN header gives the expanded Layer 3 details of that message. This page is printable via the browser print button:
BR0038
17/09/2009
Page 19 of 23
Siemens
Diagnosis
5.3.3
Monitor Display
Clicking on Monitor Display will show you the occuring states and activities on the line in a new browser instance.
For printing the monitoring and test data and test results a special print page will be used. Clicking the Print Button on the Monitor Display Page activates a new instance browser window. The monitor results will be displayed in formatted Hypertext Markup Language (HTML) in the browser window.
BR0038
17/09/2009
Page 20 of 23
Diagnosis
Siemens
With the Browser facilities (e.g. using the Printer icon from the browser toolbar or selecting from the menubar) you can send the HTML-File to the printer or alternatively save the file on the harddisk
BR0038
17/09/2009
Page 21 of 23
Siemens
Diagnosis
5.3.4
Protocolle
all results of measurement become secured over log files and are callable with date and time.
BR0038
17/09/2009
Page 22 of 23
Abbreviation
Siemens
Abbreviation
This table shows some important abbreviation. Abbreviation C CQR D DTM E EG H HFA HW I IGW IP IPDA L LAN M MIB Q QoS T TSKA W WBM Definition Call Quality Recording
Dynamic Traffic Monitoring
Endgert
HiPath Feature Access Hardware
Isochronous Gateway Internet Protocol Internet Protocol Distributed Architecture
Local Area Network
Management Information Base
Quality of Service
Test Simulation of Key Funtion
Web Base Management
BR0038
17/09/2009
Page 23 of 23
Backup and Restore
10. Backup and Restore
Backup and Restore
Backup and Restore
Siemens
Backup and Restore
Contents
1 1.1 HiPath Backup and Restore (HBR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Archive Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.1 MOD Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1.2 Hard disk/ MO disk drive holder SD3HX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Operating system for the Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2.1 SCSI ( up to HiPath 4000 V1.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2.2 SCSI-Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.2.3 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.4 HDMO module (HiPath 4000 cPCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.2.5 Hard Disk - Compact Flash (HDCF). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 HD - Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.3.1 HD - Layout HiPath 4000 V2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2.1 Archive Type: Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.2.2 Archive Type: MOD (MO Drive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.2.3 Archive Type: Backup Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.2.4 Archive Type: AP Backup Server (on HiPath 4000 Assistant only) . . . . . . . . 20 2.2.5 Archive Type: Buffer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Overview - Functionality of Backup Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.3.1 Backup Set of the Type "System" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.3.2 Backup Set of the Type "Data". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.3.3 Backup Set of the Type "Logical". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.2
1.3 2 2.1 2.2
2.3
BR0038
17/09/2009
Page 1 of 67
Siemens
Backup and Restore
2.3.4 Backup Set of the HD-Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.1 Restore List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5 Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1 Content List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8 Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9 Administration MO/TAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10 Administration Backup Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.11 Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1 3.2 3.3 3.4 4 5 6 Backup & Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GLA / PDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22 24 25 27 28 30 33 34 38 40 42 43 43 48 51 53
Backup to the Backup Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Exercise for Backup and Restore (GLA/PDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Solution for Backup and Restore (GLA/PDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Abbreviation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
BR0038
17/09/2009
Page 2 of 67
HiPath Backup and Restore (HBR)
Siemens
HiPath Backup & Restore (HBR) saves configuration data or software from RMX, UNIX and UNIX applications to a backup copy file, and restores the data upon request. HiPath Backup & Restore thus ensures that an accurate backup copy of the data and/or software will be available in the event of a system fault. HBR supports the following archive types (storage media):
1.1
Archive Types
MOD (MO drive): The archive on the MO drive (MOD) can accommodate the types system, data and locigal. The restore of Unix and RMX is only possible with a running system. Backup-Server: The Backup-Server has to be a NFS or FTP-Server. The archive on the MO drive (MOD) can accommodate the types system, data and locigal. The restore of Unix and RMX is only possible with a running system. HiPath Hard Disk: The archive on the MO drive (MOD) can accommodate the types system, data and locigal. The restore of Unix and RMX is only possible with a running system. The archive type Buffer is located in the UW7 directory /IO_BUF/OUTPUT.
BR0038
17/09/2009
Page 3 of 67
Siemens
1.1.1
MOD Device
The MO disk drive is a storage device that writes data using magnetic field and light (a laser beam) to write that resembles a CD-ROM disk. The MO disk can be used to backup hard disk data. The MO disk drive supports the ADS, ADP and SWU and has a capacity of 1.3 GB. The 3 1/2-inch MO disk drive holder is installed on a holder (SD3H or HDMO) in slot 22 of the HiPath 4300, slot 19 of HiPath 4500 and slot 3/4 of HiPath 4000.
BR0038
17/09/2009
Page 4 of 67
Siemens
1.1.2
Hard disk/ MO disk drive holder SD3HX
The hard disk drive functions as the mass storage device for system, application, and database software. The hard disk drive and MO-disk drives are mounted on an SD3HX drive holder that is installed in a single slot on the shelf (slot 22 for HiPath 4300 and slot 19 for Model HiPath 4500). Hard Disk drive Connectors The hard disk drive have one SCSI and one power connector. A SCSI ribbon cable connects the hard disk drive to the disk drive holder's electronic board. Mount the hard disk on the disk drive holder and install the drive holder into one of the following:

HiPath 4300 CC80F HiPath 4500 CCDAX
drive holder
MOD-device
yellow LED
green LED
drive holder
Fig. 1-1
SD3HX-module
BR0038
17/09/2009
Page 5 of 67
Siemens
1.2 1.2.1
Operating system for the Backup SCSI ( up to HiPath 4000 V1.0)
In the HiPath 4000 as storage medium 18 GB HD and 1,3 GB MO-drive on work are used.
BR0038
17/09/2009
Page 6 of 67
Siemens
1.2.2
SCSI-Bus
SCSI ID Device
Controller ID
System Harddisk
2 3
1 2
res. res. Service PC ext. MO-Drive ( only in the Hicom )
4 SCSI
Service PC SCSI Contoller
MO-Drive in the system
res. DSCX ( 4300 )
BR0038
17/09/2009
Page 7 of 67
Siemens
1.2.3
Controller
Controller Area Name Devicename
Storage areas Hard Disk

Volume label (furnished areas) defects sectors Loader BDIPL safety relevant data
Nr.
systemsarea Area 1
VOL-Etikett Area, Systemspez. Infoand Errorfield
Nutzbereich
User area Area 2 Area 3
UW7 Area 7
Area-Adresse Device-Adresse
A1H11 Devicenumber in the Kontrollers (1-7),
Controller numberr
H=Hard Disk / T=Band / C=Cartridge A1=ADP

V1=VMS 1 V2=VMS 2 T1=TCS 1 Area-Name Controller Nummer (1-7) look at HD Layouts
A1H1E
H=Hard Disk / T=Band / C=Cartridge A1=ADP

V1=VMS 1 V2=VMS2 T1=TCS 1
BR0038
17/09/2009
Page 8 of 67
Siemens
1.2.4
HDMO module (HiPath 4000 cPCI)
The HDMO board consists of an MO drive and a hard disk. This board may be plugged in and unplugged at any time during live operation. To prevent any loss of data, the drives should be deactivated by administration before removing.
IDE 1 -> HD IDE 2-> MOD
Fig. 1-2
HDMO-module
Hardware Version
HDMO board:S30810-Q2310-X-* 1.3 GB MO drive: Fujitsu MCM 3130 AP (S30122-X7635-X) 40 GB HD drive: Seagate ST340014A (S30122-X7685-X)
LEDs The front side of the board features two green LEDs (IDE1 = HD/IDE2 = MO) that indicate the status of the individual drives.
BR0038
17/09/2009
Page 9 of 67
Siemens
1.2.5
Hardware
Hard Disk - Compact Flash (HDCF)
The HDCF Board consists of a hard disk and a Compact Flash Card.
HDCF Board - Frontside
HDCF Board This unit may at every time under power plugged / are pulled. It is to bend forward around a possible data loss necessarily first the electronic access to interrupt the disk drives before this unit pulled.
BR0038
17/09/2009
Page 10 of 67
Siemens
Hardwaretyp:
S30810-K2319-X300 80 GB Drive: Western Digital (S30122-X8014-X11) 2 GB CF: Simple Tech (S30122-X8014-X13)
BR0038
17/09/2009
Page 11 of 67
Siemens
1.3 1.3.1
AREA HD A E F G H I J K
HD - Layout HD - Layout HiPath 4000 V2.0

Logical name MO A E F G H I --------Administration area PDS CGD DMS, DSY SCR GLA DIAG Size in 64k- blocks 3 3200 2400 1120 11217 3200 9868 in MB 1 200 62 150 70 701 200 616
DBDA, DBD, TMD, PAS, AMD, DMP 992
Description of Areas Area E F Logical Name PDS DBDA DBD TMD PAS AMD DMP G H I J K

Use Program and data system Data of different services are stored on this area, like DEBUG-, development-, error-, Logbook-, Regen-data.
CGD DMS DSY SCR ( MO-SCR) GLA DIAG
Charging CMWIN (Upload delta), Upload ACD, HiPathSystemDiadnose Uw7 installation files in packed form Is used for a copy of the E-area New area for Trace data.
The UW7 generating data (UW7 BIOS) is stored on the E-area. A system upgrade is only possible with Patch-Packets and/or Complete-Releases, not by changing the Harddisk.
BR0038
17/09/2009
Page 12 of 67
Siemens
Boot sequence: HD-E, MO-E, HD-J and then HD-E with empty data base (Rescue Mode). The I-area is used for the first installation of UW7.
BR0038
17/09/2009
Page 13 of 67
Siemens
BR0038
17/09/2009
Page 14 of 67
HiPath Backup & Restore (HBR)
Siemens
Backup
The Home Page of HiPath Backup & Restore (HBR) in HiPath 4000 Assistant/Manager (referred to as Home Page in this publication) is the entry-level page for HBR. In the navigation area on the left-hand side of the home page you can call up all of the basic functions of HBR. The content area on the right-hand side of the HBR home page displays information on the current system status .
The following information is displayed in the content area on the HBR home page:
Current Date The current date (format YYYY-MM-DD) and the current time (format hh:mm:ss) of the system are displayed here.
HBR Status Displays the current status of the HBR application.
Schedule Lists the schedule data (time, date, and archive) for automatic backups configured under "Schedule".
BR0038
17/09/2009
Page 15 of 67
Siemens
Last Automatic Backup Displays the date and archive of the last automatic backup procedure.
Last Manual Backup Displays the date and archive of the last manual backup procedure.
Last System Backup Displays the date and archive of the last system backup.
Last GLA Backup Displays the date of the last GLA backup. The status display Last GLA Backup is only displayed on the version of HBR installed on the HiPath 4000 Assistant. Last MO PDS Backup Displays the date of the last PDS backup on MO data media. The status display Last MO PDS Backup is only displayed on the version of HBR installed on the HiPath 4000 Assistant. Load Device Device from which the RMX system data is loaded (HD PDS, HD GLA, MO PDS or HD GLA RESC). HD GLA RESC stands for GLA area with rescue software on the hard disk. The status display Load Device is only displayed on the version of HBR installed on the HiPath 4000 Assistant.
BR0038
17/09/2009
Page 16 of 67
Siemens
2.1
Backup
To start the Backup process, please proceed as follows: 1. 2. Click on Backup on the Home Page of HiPath Backup & Restore (HBR). The Backup dialog is displayed. Select the Archive type that you want to specify as backup target by checking the corresponding radio button. You can choose between the following archive types:

Hard Disk MOD (MO Disk)
BR0038
17/09/2009
Page 17 of 67
Siemens
Tape MOD and/or Tape are only displayed if the hard disks physically exist. Buffer Backup Server Backup Server is only displayed if it is mounted.
AP Backup Server (only displayed with locally installed HBR on HiPath 4000 Assistant).
Underlined archives indicate that these archives have already run through the backup process (only on the Home Page). 3. Select a Backup Type by checking the corresponding radio button displayed in the Type area. You can choose between the following archive types:

System, Data, Logical, Access Point Emergency Data (only displayed with locally installed HBR on HiPath 4000 Assistant).
2.2
Archive
"Archive" is the term used to refer to the storage medium for backup copies (backups) under HBR. HBR supports the following archive types (storage media):

Hard Disk (HD) MOD (magneto-optical disk). Buffer (a logical area on the hard disk). Backup Server (also referred to as remote server) - if set up. AP Backup Server
Maximum values for the number of backup sets per type have been defined in the software for each storage medium.
BR0038
17/09/2009
Page 18 of 67
Siemens
2.2.1
Archive Type: Hard Disk
The archive on the hard disk can accommodate the following types of data:

Manually stored data (1), type: "data" Manually stored data (1), type: "logical" Manually stored system data (1), type: "system" Automatically stored data (10), type: "data" Can contain up to 10 automatic backup sets (generated on the basis of a specific algorithm).
First automatically stored data (generated with the first automatic backup; cannot be overwritten)
2.2.2
Archive Type: MOD (MO Drive)
A maximum of 4 backup sets is permitted. The archive on the MO drive (MOD) can accommodate the following types of data:

Manually stored data (1), type: "data" Manually stored data (1), type: "logical" Manually stored system data (1), type: "system" Automatically stored data (1), type: "data"
2.2.3
Archive Type: Backup Server
A maximum of 4 backup sets is permitted. The archive on the backup server can accommodate the following types of data:

BR0038
17/09/2009
Page 19 of 67
Siemens
2.2.4
Archive Type: AP Backup Server (on HiPath 4000 Assistant only)
The AP Backup Server has been introduced as a new type of HBR archive for Access Point Emergency Data (APE) type backup sets. Any Windows or Unix based server running FTP (server) or NFS can be used as AP Backup Server. Furthermore, the "Host" server itself or one of the AP servers can act as AP Backup Server. The archive "AP Backup Server" can hold only one Backup Set of type Access Point Emergency Data (APE). Backup Sets of other types (Data, System or Logical) are not permitted. In order to configure the software and data replication, the Unix IP address must be configured via UBA first. Afterwards software and data replication can be configured via the HiPath Backup & Restore user interface (GUI).
2.2.5
Archive Type: Buffer
Not more than 1 backup set is permitted. A new backup set overwrites a possibly existing backup set, even if the new back up set belongs to a different type. The archive on the buffer area can accommodate the following types of data:

2.3
Overview - Functionality of Backup Types
The following overview shows the varying functionality and modes of action of the individual backup types. Automatic Type Archive Comment Data HD, MO, Buffer, Server System HD, MO, Buffer, Server on MO not supported with 540type 1x each 1x each 1x each Data HD, MO, Buffer, Server Manual Logical HD, MO, Buffer, Server
Number of 10x for HD, different Backups 1x for others
BR0038
17/09/2009
Page 20 of 67
Siemens
A backup set is uniquely identifiable on the basis of the following parameters (this applies to all types): Date/Time: Backup Type: System no.: e.g. 2000-01-11 09:32 System, Data, Logical, AP Emergency Data
HiPath 4000 Assistant: "System" parameter of the AMO DBC If this parameter is not set, the system number from AMO ANUM will be used, e.g. GOPHER (from AMO DBC) L3101234567890123 (from AMO ANUM) HiPath 4000 Manager: IP addresses HiPath 4000 Assistant: RMX version e.g. HiPath 4000 V10 SA01 R201 HiPath 4000 Manager: Unix version e.g. P30358-D0002-A1D0-92
Software:
2.3.1
Backup Set of the Type "System"
A backup set of the type system contains all of the code (software) for RMX, UNIX and all UNIX applications as well as associated data. Data belonging to RMX is only saved in HiPath 4000 Assistant. A backup set of the type "system" stores the PDS (contains the RMX code and database), the UNIX operating system and all UNIX applications as well as their configuration data together with the backup information, which describes the backup set, in the required archive. The UNIX applications in question here are not software packages that can be installed but basic applications that form part of the operating system and which are included in the basic installation of the system. During the backup process RMX and UNIX data is always processed together, i.e. individual units cannot be selected. However, when the data is being restored, both units UNIX and RMX can be handled and processed separately. In the process a new backup set overwrites a backup set of the same type that has already been archived. The old backup set is only overwritten at the end of the procedure, i.e. if an error occurs the backup set already archived is retained. Backup sets of different types (except for tape and I/O buffer) can be stored together in the same archive.
A new backup set will overwrite an existing one in the archive if the software release and the archive type are identical.
BR0038
17/09/2009
Page 21 of 67
Siemens
2.3.2
Backup Set of the Type "Data"
A backup set of the type data contains the RMX database and configuration data (RMX, UNIX, UNIX applications). The RMX database (extracted by the AMO APS) and the configuration data of the UNIX applications is stored together with the backup information, which describes the backup set, in the archive that you have selected. Data belonging to RMX is only saved in HiPath 4000 Assistant. All data not associated with the RMX operating system is contained in the UNIX_APPL backup unit. During backup RMX and UNIX data is always processed together; in contrast however, the two units UNIX and RMX can be handled and processed separately when being restored.
2.3.3
Backup Set of the Type "Logical"
A backup set of the type logical is used to import/export data of your choice (e.g. CDB or the contents of the database). Backup units that are registered under HBR are displayed under this backup type (multiple selection is possible), e.g. CDB, HBR, RMX. Logical backup/restoration of data is executed in units. A unit consists of a group of interconnected applications. The term application is used here to refer to an installed software package or parts of such a package, or several parts of various packages that have been installed. A new backup overwrites an already archived backup set of the same type in an archive. Backup sets of different types can be stored together in the same archive except for tape and I/O buffer.
A new backup set will overwrite an existing one in the archive if the software release and the archive type are identical.
2.3.4
Backup Set of the HD-Image
A backup set of the type HD-Image is used, in order to put an image down of a non removable disk (RMX and UW7) on configured. This image is a 1:1 copy of the non removable disk and can only on a non removable disk of the same type and the same size be restored. The backup of the type HD Image can be started automatically or manually. For the Image backup the RMX ranges are deactivated, cousin Unix is driven down and mini Unix started. The re-establishment of the image is made by the mini Unix and started by the MO. The image can take place also with a tape mechanism (TAPE), attached over USB or SCSI, or a non removable disk (HD).
BR0038
17/09/2009
Page 22 of 67
Siemens
This solution is available for the HiPath 4000assistant under UnixWare 7 and cover 3 user interfaces components: In the HBR this type backup can configure and plan; the IX-Bios offers with boots of MO an option to boot of the mini Unix; Mini Unix again makes the user surface available for the re-establishment. The status of this type of backup set cannot be indicated during the mini Unix phase, since all applications are stopped and cousin Unix does not run. The status is indicated in the HBR dialogues status and minutes as soon as the transmission of the HD image is terminated to the backup server and cousin runs the Unix system again.
BR0038
17/09/2009
Page 23 of 67
Siemens
2.4
Restore
Software Management -> Backup & Restore -> Restore
The Archives MO-RMX indicate contents to a MOD, which is created with the menu GLA/PDS.
HD->MO HD-PDS -> MO-PDS HD-F-AREA -> MO-F-AREA HD-G-AREA -> MO-G-AREA HD-H-AREA -> MO-H-AREA RMX&UNIX DATA -> MO-SCR-AREA UNIX INSTALL PART -> MO-SCR-AREA
With the option Get original list of archives the archives information from selected archives one updates (again read in).
BR0038
17/09/2009
Page 24 of 67
Siemens
2.4.1
Restore List
The Restore List contains the individual backup units that can be selected for being restored. The RMX areas F, G, and H on MO-RMX are displayed, but can not be restored from this point.
To start the restore operation, click the Restore Set button. Once it has been confirmed by the user, the restore procedure runs in the foreground and is monitored by the user. When the restore operation has been concluded, a message indicating either the success or failure of the operation is displayed. If, during the restore process, the connection to the system should fail, restore will continue to run; the status can be displayed afterwards by clicking on the Status button.
BR0038
17/09/2009
Page 25 of 67
Siemens
A backup set is uniquely identifiable on the basis of the following parameters (this applies to all types): Date/Time: Backup Type: System no.: e.g. 2000-01-11 09:32 System, Data, Logical, AP Emergency Data
HiPath 4000 Assistant: "System" parameter of the AMO DBC If this parameter is not set, the system number from AMO ANUM will be used, e.g. GOPHER (from AMO DBC) L3101234567890123 (from AMO ANUM) HiPath 4000 Manager: IP addresses HiPath 4000 Assistant: RMX version e.g. HiPath 4000 V10 SA01 R201 HiPath 4000 Manager: Unix version e.g. P30358-D0002-A1D0-92
Software:
Restore Confirmation
On completing the restore operation, an appropriate message concerning success or failure is displayed. If, during the restore process, the connection to the system should fail, the procedure will continue to run; the status can be displayed afterwards by clicking on the Status button. Note The same version (release and revision level) of the RMX software and the UNIX software must be installed on the system. It is not permitted to save data from a new version to an older software version. If data is to be restored selectively for RMX and UNIX, the user will be responsible for the consistency of the data. If the restore process concludes with an error, the function will have to be repeated. You can check the status of the restore process by clicking the Status button .
BR0038
17/09/2009
Page 26 of 67
Siemens
2.5
Content
In the Content screen you can select one or more archives (storage media) as well as the type of the backup set whose content you would like to display. More than one archive and more than one backup set can be selected at the same time. When you click the List button, the content of the selected archive and backup set is displayed in a table - see Content List.
As an option, you can activate the Get original list from archive check box under the Options entry. By activating this check box you specify that the original lists of the selected archive and backup types be displayed. The local cache is overwritten and/or cleared, respectively; this process may take a bit longer.
BR0038
17/09/2009
Page 27 of 67
Siemens
2.5.1
Content List
When you click the List button in the Content screen, the backup sets stored in the selected archives are displayed in the Content List. If you want to edit a backup set, select it again.
A backup set is uniquely identifiable on the basis of the following parameters (applies to all types): Date/Time: Backup Type: System no.: e.g. 2000-01-11 09:32 System, Data, Logical, AP Emergency Data
HiPath 4000 Assistant: "System" parameter of the AMO DBC If this parameter is not set, the system number from AMO ANUM will be used, e.g. GOPHER (from AMO DBC) L3101234567890123 (from AMO ANUM) HiPath 4000 Manager: IP addresses HiPath 4000 Assistant: RMX version, e.g. HiPath 4000 V10 SA01 R201 HiPath 4000 Manager: Unix version, e.g. P30358-D0002-A1D0-92
Software:
BR0038
17/09/2009
Page 28 of 67
Siemens
Function of the Buttons Refresh Updates the screen contents. The backup status in the window is not automatically updated. When you select the Refresh function, the contents of the screen display are updated. Delete Deletes the marked backup set on the archive. Update Set Updates the marked backup set on the archive. The backup process is activated. Restore Set Restores the data from the marked backup set. The RMX areas F, G, and H on MO-RMX are displayed but can not be restored from this point.
BR0038
17/09/2009
Page 29 of 67
Siemens
2.6
Status
The status of the backup/restore cycle currently running or of the last one to be executed is displayed in the Status screen. The information displayed includes the overall status of HBR, the status of backup/restore operations currently running and previous backup/restore operations. The display is automatically updated every 20 seconds.
Status Display Messages: Idle Indicates that there are no backup/restore processes running at the moment. Backup running Indicates that a backup process is currently being executed. Restore running Indicates that a restore process is currently being executed.
BR0038
17/09/2009
Page 30 of 67
Siemens
Backup cancelled Indicates that a backup process has been cancelled. In this process, the backup process that is running is not cancelled immediately but only in the next backup step Locked by UBA Indicates that a backup process has been locked by UBA. Locked by USV Indicates that a backup process has been locked by USV. Locked by Other Application Indicates that a backup process has been locked by another application. Saving to archive Indicates that the data is currently being saved to an archive. The status display Success indicates that the saving process has concluded successfully. The status of a saved backup set is only set to Success when the full backup set has been completely saved on the selected archive. This is particularly important with MO and TAPE/DAT drives because in the case of these drives the backup set is first saved to a temporary directory on the hard disk before it is transferred to the final destination drive. If you want to check whether this transfer has already finished, click the Refresh button to refresh the screen. One line is added to the backup status for each backup step (e.g. backup of RMX database). Each line contains the following parameters: Operation: Date / Time: Type: Archive: Unit: Status: Mode: Additional Information Backup e.g. 2000-01-04 14:23 System, Data, Logical, AP Emergency Data HD, MO, Backup Server, AP Backup Server, Buffer, Tape Backup Unit (RMX, UNIX) or Save (last step in the backup procedure) Running, Success, Error, Cancelled, Backup Error Automatic, Manual Link to log file containing information on the last Backup/Restore operation executed.
BR0038
17/09/2009
Page 31 of 67
Siemens
Note Save indicates that data is being saved to the specified archive. The backup procedure has concluded without an error only when Save has executed successfully (status: Success). You must always verify the restore status because a system boot that is running sporadically could terminate the operation with errors. One line is added to the restore status for each restore step (e.g. restoring RMX data). Each line contains the following parameters: Operation: Date / Time: Type: Archive: Unit: Status: Mode: Additional Information Restore e.g. 2000-01-04 14:23 Data HD, MO, Tape, Backup Server, AP Backup Server, Buffer Backup Unit (RMX, UNIX) Success, Error Man Link to log file containing information on the last Backup/Restore operation executed.
Function of the Buttons Refresh Refreshes the screen. The status display is not refreshed automatically. This can be done by using the Refresh button. Cancel backup Cancels the current operation. Note Only backup operations can be cancelled. Restore operations cannot be cancelled or interrupted.
BR0038
17/09/2009
Page 32 of 67
Siemens
2.7
History
A status list of the last backup/restore operations to be carried out is displayed on the History screen. Up to 25 backup/restore cycles can be displayed.
BR0038
17/09/2009
Page 33 of 67
Siemens
2.8
Schedule
You can enter the data for several automated backup cycles in the Schedule dialog. You can define when and how often an automated backup cycle should be executed. For this purpose, new functions have been provided for adding, changing and deleting entries.
The following parameters are configured: Type Unit Status: Frequency: Time: Archive: System, Data, Logical, MO-RMX, HD-SCR, AP Emergency All software components (applications) installed on the system and relevant for Backup&Restore are listed here. Enabled, Disabled, Once Daily, Weekdays, Monday, ... Sunday hh:mm HD, MO, Buffer, Backup Server, AP Backup Server, Tape. MO, Tape, Backup Server, and AP Backup Server are only displayed if they are configured and if they physically exist. Yes / No If Synchronize has been enabled, the data is saved from the memory to the hard disk first, "exec-updat" is executed on the RMX side, and then the backup is executed. Yes / No If Yes has been set here, the transferred data will be verified (FTP server and Tape only).
S Synchronize:
V (Verify transferred data)
BR0038
17/09/2009
Page 34 of 67
Siemens
Type

System Data Logical mo-rmx hd-rmx AP Emergency
Unit The installed software units are listed depending on the Backup Type. The list displays the installed software components for which a Backup&Restore process per type can be executed. For the Backup Type Logical, for instance, the HBR, UBA, RMX software units are displayed. If you select the ALL entry, all software components of the selected Backup Type will be included in the Backup&Restore process. Status

Disabled Enabled Once Note If the status has been set to Once, the backup is only executed once at the specified time, and then the status is reset to Disabled.
Frequency

Daily Weekdays Sundays... Saturdays
Time (Select time) Format: HH:MM.
BR0038
17/09/2009
Page 35 of 67
Siemens
Archive

HD Backup Server - item is only displayed if a Backup Server is configured and if it physically exists AP Backup Server - item is only displayed if an AP Backup Server is configured Buffer MO - item is only displayed if it physically exists Tape (DAT) - item is only displayed if it physically exists MO-RMX (MO in RMX format) HD-SCR (RMX SCR area of the hard disk)
In the case of automatic backup cycles, the default setting for the type of backup set to be created should be Data. Note The edit line at the bottom of the table is not an entry in the schedule. The options that you have selected in the edit line are not accepted as an entry in the schedule until you click the Add New button. S - Synchronize

Y = Yes N = No
V - Verify transferred data

Y = Yes N = No
Function of the Buttons in the Schedule dialog Refresh (update) Click this button to update the contents of the screen. If you change existing entries, the contents of the screen are automatically refreshed. Start now Click this button to start the backup process immediately.
BR0038
17/09/2009
Page 36 of 67
Siemens
Delete Click this button to delete the selected entry. Change Click this button to change existing values in the selected entry. Add New Click this button to add a new entry to the schedule. Example To configure and start a scheduled automatic APE backup cycle, please follow the steps described in the Starting the Backup Process Automatically via Schedule section.
BR0038
17/09/2009
Page 37 of 67
Siemens
2.9
Administration MO/TAPE
Administration MO/TAPE is used for administering external MO and TAPE/DAT devices. The functions enable the user to initialize and test the external MO and TAPE/DAT devices and to update the RMX values (MO). Administration MO/Tape on HiPath 4000 Assistant (on the local ADP)
MO
Test This function is used to check the status of the MO device and of the MO disk. The messages output in the Additional Information field indicate the status, e.g. Not present, empty or not writable. If the test was passed successfully, the message "Operation was successful" is displayed.
Initialize The RMX part of the MO is also initialized on the HiPath 4000 Assistant with this function.
Update RMX Values Check MO medium size (1.3 GB / 540 MB) and update RMX values if necessary. The values of the current MO data medium (e.g. 540 MB or 1.3 GB) are verified, updated if necessary, and entered into the RMX database.
BR0038
17/09/2009
Page 38 of 67
Siemens
TAPE
Test This function is used to check the status of the TAPE/DAT device and of the TAPE/DAT tape. The messages output in the Additional Information field indicate the status, e.g. "TAPE not found.", Not present, Empty or Not writable. If the test was passed successfully, the message "Operation was successful" is displayed.
Initialize This function is used to initialize the TAPE/DAT tape.
Caution The Initialize feature deletes the content of the tape.
Function of the Buttons Refresh Updates screen display. Start Now The selected procedure (test, initialize or update) is started.
BR0038
17/09/2009
Page 39 of 67
Siemens
2.10
Administration Backup Server
The customer backup server is administered via the Administration Backup Server dialog. Depending on the protocol used not all of this information is required.
The following configuration data has to be defined: Transfer Protocols HBR supports the following transfer protocols:
NFS When you select the NFS Transfer Protocol, only the input fields IP Address, Host Name and Destination Directory are displayed, i.e. only these fields need to be filled in. Important: In order to use the NFS connection type, the UNIX operating system needs to be running on the backup server.
FTP When you select the FTP Transfer Protocol, the input fields IP Address, Host Name, Destination Directory, Login, Password and Account are displayed, i.e. additional information is required for login, password and account.
BR0038
17/09/2009
Page 40 of 67
Siemens
Input Fields
IP Address Enter the IP address of the remote server here. The input fields IP Address and Host Name are both used to identify the system. If you have entered the IP address, you must not enter the host name, and vice versa.
Host Name Enter the host name of the remote server here. The input fields IP Address and Host Name are both used to identify the system. If you have entered the IP address, you must not enter the host name, and vice versa.
Destination Directory Enter the destination directory on the remote server here.
Caution The subdirectory specified in this field is NOT created automatically by HiPath 4000; it has to be created manually on the FTP server. Dont specifiy the letter of the drive, e.g. C: Take into account that the FTP server on the Customer Backup Server may change the relative and absolute paths.
Examples: server1 Relative path: server1 is a directory in the indicated users home directory. Absolute path of the server directory
/backup/server
Login (only needed for FTP) Enter the user name here that is to be used for logging onto the remote server.
Password (only needed for FTP) Enter the password associated with the user name here that is to be used for logging onto the remote server.
Caution The subdirectory specified in this field is NOT created automatically by HiPath 4000; it has to be created manually on the FTP server. Dont specifiy the letter of the drive, e.g. C: Take into account that the FTP server on the Customer Backup Server may change the relative and absolute paths.
BR0038
17/09/2009
Page 41 of 67
Siemens
2.11
Log Files
Error Logs The debug and error log files for the system (UNIX) and RMX backup cycles of HBR are listed in the Log Files dialog under the following links: HBR System Backup Log Files Contains the debug and error log files for the system backup cycles (UNIX) of HBR. and HBR RMX Backup Log Files Contains the debug and error log files for the RMX backup cycles of HBR. Depending on whether HBR has been installed on the HiPath 4000 Assistant or on the HiPath 4000 Manager, different log files may be displayed.
Status Logs HBR System Backup Log Files Displays the current status of the Host system and of all CC AP systems (Survivability Units). This link is only displayed if the AP Backup Server is configured.
BR0038
17/09/2009
Page 42 of 67
Siemens
3
3.1
Backup & Restore

GLA / PDS
Software Management -> Backup & Restore -> GLA/PDS
HD-PDS -> GLA HD-PDS -> MO-PDS GLA -> HD-PDS MO-PDS -> HD-PDS
Copying Area E of the Harddisk to Area J of the Harddisk. Copying Area E of the Harddisk to Area E of the MOD. Copying Area J of the Harddisk to Area E of the Harddisk. Copying Area E of the MOD to Area E of the Harddisk.
BR0038
17/09/2009
Page 43 of 67
Siemens
HD-F-AREA -> MO-F-AREA
Copying Area F of the Harddisk to Area F of the MOD. There you can start a REGEN before copying, to save the REGEN-files (ADS&SWU) on MOD. Copying Area G of the Harddisk to Area G of the MOD. Copying Area H of the Harddisk to Area H of the MOD.
HD-G-AREA -> MO-G-AREA HD-H-AREA -> MO-H-AREA
RMX&UNIX DATA -> MO-SCR-AREA
Copying the RMX-Data bases and the UNIXData of the Harddisk to Area I (SCR) of the MOD (is equal to a DataBackup in the menu Backup). Copying the UNIX Install Partition of the Harddisk to Area I (SCR) of the MOD. In this way the SCR-Area of the MOD can be actualized.
UNIX INSTALL PART -> MO-SCR-AREA
BR0038
17/09/2009
Page 44 of 67
Siemens
The data of the menus RMX&UNIX DATA and UNIX INSTALL PART to the MOD-SCR-AREA can be saved on the same MOD!
BR0038
17/09/2009
Page 45 of 67
Siemens
HD -> MO
Copying Areas E - H of the Harddisk to MOD (Area E -H). Additional the RMXData bases and the UNIX-Data (like a Data Backup) and the Unix-Install Partition in packed form are copied to the SCR-Area (I) of the MOD. There you can start a REGEN before copying, to save the REGEN-files (ADS&SWU) on MOD. The generated MOD (Recovery MOD) is bootable. The content of the MOD is shown in the menu Restore and Content in the archive MO-RMX. But it is only possible to restore the Type Data (UNIX und RMX).
BR0038
17/09/2009
Page 46 of 67
Siemens
UNIX INSTALL PART -> HD-SCR-AREA
Copying the UNIX Install Partition of the Harddisk to Area I (SCR) of the Harddisk. In this way the SCR-Area of the Harddisk can be actualized. The content of the SCR-Area of the Harddisk is shown in the menu Restore and Content in the archive HD-SCR. Copying SCR Area of the Harddisk to the UNIX Install Partition of the Harddisk. Copying SCR Area of the MOD to the UNIX Install Partition of the Harddisk.
UNIX-HD-SCR-AREA -> UNIX INSTALL PART UNIX-MO-SCR-AREA -> UNIX INSTALL PART
BR0038
17/09/2009
Page 47 of 67
Siemens
3.2
Restore
Software Management -> Backup & Restore -> Restore
The archive MO-RMX shows the content of a MOD, which was generated in the menu GLA/PDS with
HD->MO HD-PDS -> MO-PDS HD-F-AREA -> MO-F-AREA HD-G-AREA -> MO-G-AREA HD-H-AREA -> MO-H-AREA RMX&UNIX DATA -> MO-SCR-AREA UNIX INSTALL PART -> MO-SCR-AREA.
With the Option Get the original list from archive it is possible to actualize the Archive informations of the selected archive (actualizing the Informix data base).
BR0038
17/09/2009
Page 48 of 67
Siemens
Only the Units UNIX_CFDATA and RMX can be restored. All other Units can be copied by the AMO DDRSM from the MOD to the Harddisk. The Unit UNIX matches to the Area I and the Unit DATA is not useable. DATA is only information, that the UNIX-Data was backuped. Only the UNIX_CFDATA can be used for a restore operation.
BR0038
17/09/2009
Page 49 of 67
Siemens
The archive HD-SCR shows the content of the HD-SCR-Area of the Harddisk, which was backuped with the menu GLA/PDS using UNIX INSTALL PART -> HD-SCR-AREA.
The SCR-Area of the Harddisk is copied to the UNIX INSTALL PART and is restored.
BR0038
17/09/2009
Page 50 of 67
Siemens
3.3
Content
Software Management -> Backup & Restore -> Content
With the Option Get the original list from archive it is possible to actualize the Archive informations of the selected archive (actualizing the Informix data base).
BR0038
17/09/2009
Page 51 of 67
Siemens
BR0038
17/09/2009
Page 52 of 67
Siemens
3.4
Schedule
Software Management -> Backup & Restore -> Schedule

The schedule in menu Backup & Restore Men is extended by the Types MO-RMX, Logical, HD-SCR and System.
BR0038
17/09/2009
Page 53 of 67
Siemens
BR0038
17/09/2009
Page 54 of 67
Siemens
BR0038
17/09/2009
Page 55 of 67
Siemens
BR0038
17/09/2009
Page 56 of 67
Siemens
Backup to the Backup Server
To use a PC as a backup server a FTP-Server program is neccessary. The FTP program needs a profil with name, password (optional) and a directory.
Important are the following settings: Download for read access Upload for write access
The PC needs a directory (in this example C:\hipath and a subdirectory 69_100 for the node.
BR0038
17/09/2009
Page 57 of 67
Siemens
BR0038
17/09/2009
Page 58 of 67
Siemens
To check weather the settings are ok push the button Test.
BR0038
17/09/2009
Page 59 of 67
Siemens
BR0038
17/09/2009
Page 60 of 67
Siemens
5
1.
Exercise for Backup and Restore (GLA/PDS)

What does the abbreviation GLA mean?
_______________________________________________________________________ 2. Save the PDS HD on the GLA.
_______________________________________________________________________ 3. Save the PDS HD on the MOD.
_______________________________________________________________________ 4. Start a system reload and check the boot sequence of the system (MOD is inserted).
_______________________________________________________________________ 5. Which device is the active boot unit now?
_______________________________________________________________________ 6. Remove the MOD and start another system reload. a) Which device is the active charging unit now?
_______________________________________________________________________ 7. Review the latest backup data (times).
_______________________________________________________________________ 8. Insert a new backup (e.g. backup server or MO).
_______________________________________________________________________ 9. Restore the data. Monitor the restore operation with STATUS.
BR0038
17/09/2009
Page 61 of 67
Siemens
_______________________________________________________________________ 10. How is a Recovery MOD be created ?
_______________________________________________________________________ 11. Which RMX Areas of the HD are stored on the Recovery MOD ?
_______________________________________________________________________ 12. Which Unix Data are stored on the Recovery MOD ?
_______________________________________________________________________ 13. How do you can restore the Unix Data of the Recovery MOD ?
_______________________________________________________________________
BR0038
17/09/2009
Page 62 of 67
Siemens
6
1. 2.
Solution for Backup and Restore (GLA/PDS)

What does the abbreviation GLA mean? Golden Load Area
Save the PDS HD on the GLA. Menu: Software Management Backup and Restore GLA/PDSHD-PDS -> GLA
3.
Save the PDS HD on the MOD. Menu: Software Management Backup and Restore GLA/HD-PDS -> MO-PDS
4.
Start a system reload and check the boot sequence of the system (MOD is inserted). Boot seq. 1. HD-PDS 2. HD-PDS 3. MOD-PDS 4. GLA
5.
Which is the active load device now? MOD-PDS
6.
Remove the MOD and start another system reload. a) Which is the active load device now? HD-PDS
7.
Review the latest backup data (times). Access UW7 => Software Management => Backup & Restore
8.
Insert a new backup (e.g. backup server or MO). Backup Select archive (backup server or MO) Select type (RMX data and UNIX configuration data) Start backup
Attention: Backup progress can be monitored with the STATUS menu item. Please do not quit IE.
BR0038
17/09/2009
Page 63 of 67
Siemens
9.
Restore the data. Monitor the restore operation with STATUS. RESTORE Select archive (backup server or MO) Select type (RMX data and UNIX configuration data) Lists
Select restore data Attention: if UNIX_CFDATA and RMX are selected, the UNIX data is not complete.
Temporary solution: First reload UNIX, then RMX
If the archive data is selected Restore SET
Monitor with STATUS.
10. How is a Recovery MOD be created? Solution:
Hipath 4000 V2.0 Assistant -> Software Management -> Backup&Restore -> GLA/PDS
Select "HD -> MO"
BR0038
17/09/2009
Page 64 of 67
Siemens
11. Which RMX Areas of the HD are stored on the Recovery MOD ? Solution:
Area E, F, G, H
BR0038
17/09/2009
Page 65 of 67
Siemens
12. Which Unix Data are stored on the Recovery MOD ? Solution:
Install Partition of UW7 is stored on Area I of the MOD. Additionally the Unix DB and RMX DB are store as packed files on the same Area (Area I).
13. How do you can restore the Unix Data of the Recovery MOD ? Solution:
In the Menu Restore -> Select MO-RMX / Type all /
with Option "Get original list from archive"

-> Select UNIX_CFDATA without RMX
TAKE YOUR TIME AND BE PATIENT!
BR0038
17/09/2009
Page 66 of 67
Abbreviation
Siemens
Abbreviation
This table show some important Abbreviation. Abbreviation A ADP C CC CF F FTP H HBR I IDE IP L LED M MOD N NFS R RMX S SCSI U UW7 Definition Administration Processor
Common Control Compact Flash Card
File Tranfer Protocol/
HiPath Backup & Restore / Datensicherung & Rcksicherung
Integrated/Intelligent Drive Electronics / Plattenlaufwerk mit ATA-Protokoll Internet Protocol (TCP/IP)
Light Emitting Diode / Leuchtdiode;
Magneto Optical Disc
Network File Server
Realtime multitask executive
small computer system interface bus
UnixWare7
BR0038
17/09/2009
Page 67 of 67

Hip4advs BR

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Hip4advs BR

Enviado por

Direitos autorais:

Formatos disponíveis

s

HiPath 4000 V6.0

DTIM2 COT PROD E

temporiz. p/ CP, circuitos, AC, PSE

dados de converso de dgitos

restries para trfego interno

AMOs para troncos

circuitos de tronco analgicos TMCOW, TMLRB,

cd. do no. de DPLN

restries entre trfegos para rede

cdigo para uma/diversas rotas

Relao de AMOs para troncos

5) PRODE (Descritor de protocolo)

6) MFCTA (Tabela MFC para troncos R2Digital)

6) PTIME (Tabela de temporizadores para troncos analgicos)

Configurao de troncos digitais

S0 - tronco tie-line digital com protocolo ECMAV2

Exemplo de parametrizao mnima Tie Line S0

S0 - tronco digital com a central pblica

Exemplo de parametrizao mnima troncos acesso CO S0

3.3 DIUN2 : S2 (E1)

Exemplo de parametrizao mnima Tie Line S2

S2 - troncos digitais com a central pblica (EURO ISDN)

Exemplo de parametrizao mnima troncos ISDN acesso rede pblica

3.4 STMI4 : IP TRUNKING

Para adicionar canais B em um grupo existente

Configurao de Troncos Exemplo de parametrizao mnima para IP Trunking

TRTBL=GDTR ATNTYP=CO DEVTYPE=TC DEV=DIUCQ421 MFCVAR= DGTCNT=4 CIRCIDX= DIALTYPE=MFC-MFC DIALVAR=6-0

Exemplo de parametrizao mnima para R2 Digital MFCTA

BCSU (MDULO SIU)

Tabela de temporizao para os troncos DIU (DIUCQ421) DIS-PTIME:REST,DIUCQ421; REST TIMERS:

INIBLK TBLK LONGTIME: L1 = L2 = L3 =

L7 = 5000 MS Supervisao da confirmacao de ocupacao depois do envio de ocupacao

S10 = S11 = S12 = S13 = S14 =

SHORT-PARA: P1 = 2 Tipo de discagem : 0 = ,1 = MFV, 2 = MFC

0 Fim de discagem : s/ fim=0, c/ fim=1

Tronco analgico - BWA

TRTBL=GDTR ATNTYP=CO DEVTYPE=TC DEV=ANMOSIG

Exemplo de parametrizao mnima para troncos analgicos (TMANI & TM2LP)

ADD-BCSU:PER,1,1,3,"Q2327-X182",0,0,,,,,,A,,0; /*modulo TMANI*/ COS

PTIME ( modulo TM2LP)

PTIME ( modulo TMANI)

TACSU ( modulo TM2LP)

TACSU ( modulo TMANI)

ADD-TACSU:PEN=1-1-3-0,NO=1,COTNO=10,COPNO=10,COS=32,LCOSV=32,LCOSD=32,TGRP=3, CCT="TRK ANALOG",DESTNO=223,NNO=224,CARRIER=1,ZONE=EMPTY, CLASSMRK=EC&G711,ATNTYP=CO,INS=Y,DEVTYPE=TC,DEV=TMANIMSG, CIRCIDX=7,DIALTYPE=MOSIG-DTMF,DIALVAR=6-0;

Tabela de temporizao para os troncos ANALGICOS

DIS-PTIME:REST,ANMOSIG; H500: REST AMO PTIME STARTED TIMERS:

INIBLK TBLK LONGTIME: L1

= 200 MS, - Tempo de tx. de sinal de flash ou terra.

X=0 - Sem proteo contra DDC X=1 - Proteo contra DDC

= 0 - Simulao de comutao de tarifa (no utilizado) = 5 - Atraso na ativao da superviso de linha

Descrio dos parmetros COP

ABAN ABPD ACKB ACKF ANIC ANIO ANIW ANNC

ANS APPR ASEG

ASNM AST1 AST2 BR64

BTN1 BTN2 BTN3 BTOF CAUS CCM CCR

CCTN COCN COTT COEI CTGF

DT1A DT2A DTBR

DTM1 DTM2 DTM3 DTM4 DTMF DTN DTT

DTV EMOV EO10 EOD

IDP1 IDP2 IDP3 IDP4 IMEX

LWCC L3AR NBAR NO1A NOAN

NONA NOTO NOTR NSDL NTON PDP1

ADD-BCSU:PER,1,1,3,"Q2327-X182",0,0,,,,,,A,,0; /modulo TMANI/ COS