Good morning
I would like to know what these errors mean
I have an oxe 4400 R10 duplicated two processors
cpub> checkdb
Data base checking in progress ...
/...........ERROR 1006 : DPNSS Prefix Missing. No DPNSS prefix added.
...ERROR 4351 : DATA INCONSISTENCY, Table TYPNBAB, Inconsistency Translator=0
ERROR 4351 : DATA INCONSISTENCY, Table TYPNBAB, Inconsistency Translator=1
ERROR 4351 : DATA INCONSISTENCY, Table TYPNBAB, Inconsistency Translator=2
ERROR 4351 : DATA INCONSISTENCY, Table TYPNBAB, Inconsistency Translator=3
ERROR 4351 : DATA INCONSISTENCY, Table TYPNBAB, Inconsistency Translator=4
ERROR 4351 : DATA INCONSISTENCY, Table TYPNBAB, Inconsistency Translator=5
ERROR 4351 : DATA INCONSISTENCY, Table TYPNBAB, Inconsistency Translator=6
ERROR 4351 : DATA INCONSISTENCY, Table TYPNBAB, Inconsistency Translator=7
ERROR 4351 : DATA INCONSISTENCY, Table TYPNBAB, Inconsistency Translator=8
.ERROR 4351 : DATA INCONSISTENCY, Table TABRAL, function=mark_reptype nulog=569 invalid ext_info=5
ERROR 4351 : DATA INCONSISTENCY, Table TABRAL, function=mark_reptype nulog=561 invalid ext_info=5
ERROR 4351 : DATA INCONSISTENCY, Table TABRAL, function=mark_reptype nulog=366 invalid ext_info=3
ERROR 4351 : DATA INCONSISTENCY, Table TABRAL, function=mark_reptype nulog=567 invalid ext_info=5
checkdb : ERROR 4351 : DATA INCONSISTENCY
Re: checkdb : ERROR 4351 : DATA INCONSISTENCY
is this the same cpu wich getting issue in other post(did ....)?
run checkdb on cpua and past the results may be a db restore can solve the issue
run checkdb on cpua and past the results may be a db restore can solve the issue
Re: checkdb : ERROR 4351 : DATA INCONSISTENCY
Yes, it's the same cpu and now it's stopped
I ran the master copy of the cpub (the faulty one) and it went fine, but then the cpua remains in "REG NOT INIT" mode and when I pick up the handset on my 4039 it automatically displays "please hang up" and other digital and analog sets have these problems. When I restart the cpua manually and switch over, it's impossible to receive calls on DID numbers.
so I'm wondering :
- What if I also had to perform a mastercopy on the cpua?
- how can I be sure that the databases of the two cpus are identical?
I ran the master copy of the cpub (the faulty one) and it went fine, but then the cpua remains in "REG NOT INIT" mode and when I pick up the handset on my 4039 it automatically displays "please hang up" and other digital and analog sets have these problems. When I restart the cpua manually and switch over, it's impossible to receive calls on DID numbers.
so I'm wondering :
- What if I also had to perform a mastercopy on the cpua?
- how can I be sure that the databases of the two cpus are identical?
Re: checkdb : ERROR 4351 : DATA INCONSISTENCY
hi
about your DDI do you receive calls on them if cpub is main ?
are them from E1ISDN , E1PCMR2, SIP etc ...? we need traces , the config of the TRKGP and DID used
cpu a in reg not init , auto start is managed?
Databases of the two CPUs should be same if you perform the master copy and the process was finished on the good way with no issue
about your DDI do you receive calls on them if cpub is main ?
are them from E1ISDN , E1PCMR2, SIP etc ...? we need traces , the config of the TRKGP and DID used
cpu a in reg not init , auto start is managed?
Databases of the two CPUs should be same if you perform the master copy and the process was finished on the good way with no issue
Re: checkdb : ERROR 4351 : DATA INCONSISTENCY
is this related
-------------------------------------------------------------------+
| Cr | cpl| cpl type | hw type | cpl state | coupler ID |
|----|----|------------|-----------|--------------|-----------------|
| 2 | 0 | GD3|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 1 | SLI2 16(Z)|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 2 | UAI 16|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 3 | SLI2 16(Z)|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 4 | SLI2 16(Z)|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 5 | SLI2 16(Z)|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 6 | PRA T2|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 7 | APA 8|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 8 | CS2|---------- | CALL SERVER | BAD PCMS CODE |
+-------------------------------------------------------------------+
-------------------------------------------------------------------+
| Cr | cpl| cpl type | hw type | cpl state | coupler ID |
|----|----|------------|-----------|--------------|-----------------|
| 2 | 0 | GD3|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 1 | SLI2 16(Z)|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 2 | UAI 16|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 3 | SLI2 16(Z)|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 4 | SLI2 16(Z)|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 5 | SLI2 16(Z)|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 6 | PRA T2|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 7 | APA 8|---------- | REG NOT INIT | BAD PCMS CODE |
| 2 | 8 | CS2|---------- | CALL SERVER | BAD PCMS CODE |
+-------------------------------------------------------------------+
Re: checkdb : ERROR 4351 : DATA INCONSISTENCY
Stop both CPU.
Start PBX with one CPU (from more correct working from your point of view).
Check that you have no problem - real works, checdb etc.
Start second CPU without telephone application.
Perform mastercopy (via swinst) and start telephone application.
Chect that duplication works (twin command).
Check, when you make someting on main CPU - you have no incident from twin CPU (and about twin CPU).
Re: checkdb : ERROR 4351 : DATA INCONSISTENCY
I used to receive calls on the cpub, but after I did a mastercopy (from the cpub) and it ended without a hitch, I realized that I couldn't receive calls on the cpua anymore.
for calls there's a trunk with a gateway ( dinstar )haroun wrote: ↑10 Oct 2023 15:28 are them from E1ISDN , E1PCMR2, SIP etc ...? we need traces , the config of the TRKGP and DID used
cpu a in reg not init , auto start is managed?
Databases of the two CPUs should be same if you perform the master copy and the process was finished on the good way with no issue
Consultation/Modification: Passerelles Externes──────────────────────────────────────────┐
│ │
│ No noeud-r▒seau (r▒serv▒ soft) : 0 │
│ Instance (r▒serv▒e soft) : 1 │
│ Instance : 10 │
│ │
│ Nom de la passerelle : GATEWAY SIP │
│ Domaine distant : 131.107.3.246 │
│ Adresse IP PCS : ----------------------------------------------- │
│ Num▒ro de port : 5060 │
│ Type de transport + UDP │
│ Domaine d'appartenance : -------------------------------------------------- │
│ Id d'enregistrement : -------------------------------------------------- │
│ Id d'enreg. dans P_Asserted + Non │
│ Timer d'enregistrement : 0 │
│ Proxy : -------------------------------------------------- │
│ Timer de supervision : 0 │
│ Num▒ro de faisceau : 10 │
│ Num▒ro de pool : -1 │
│ Domaine sortant : -------------------------------------------------- │
│ Nom de l'utilisateur sortant : -------------------------------------------------- │
│ │
│ Mot de passe Sortant : -------------------- │
│ Confirmer : -------------------- │
│ │
│ Nom de l'utilisateur entrant : -------------------------------------------------- │
│ │
│ Mot de passe entrant : -------------------- │
│ Confirmer : -------------------- │
│ │
│ RFC 3325 support▒ par le distant + Non │
│ Type de DNS + DNS A │
│ Adresse IP du DNS primaire : ----------------------------------------------- │
│ Adresse IP du DNS secondaire : ----------------------------------------------- │
│ SDP dans 18X + Non │
│ Authentification minimale + Aucun │
│ M▒thode INFO pour remote extension + Non │
│ Envoyer uniquement algo faisceau + Non │
│ Vers EMS + Non │
│ SRTP + RTP │
│ Application de routage + Non │
│ Ignorer inactive/black hole + Non │
│ Contact avec adresse IP + Non │
│ Type de payload dynamique (dtmf) : 97 │
│ 100 REL pour les appels sortants + Support▒ │
│ 100 REL pour appel entrant + Non demand▒ │
│ Type de gateway + Type standard │
│ Re-Trans No. for REGISTER/OPTIONS : 2 │
│ P-Asserted-ID dans No Appelant + Non │
│ Ent▒te P-Asserted-ID certifi▒ + Oui │
│ Info. de renvoi ext. fourni par + History Info │
│ Sp▒cialis▒ d▒part + Non │
│ Relai SDP sur renvoi ext▒rieur + Default │
│ Ent▒te From certifi▒ + Non │
│ Supporte le Re-invite sans SDP + Non │
│
tell me what you need
since these problems, some 4039 and 4029 sets, when you press a key, you get a direct "please hang up", it's not a card problem because on the same UA32 card, some sets work well while others do not.
i don't know if i should make a mastercopy of the cpua now
Re: checkdb : ERROR 4351 : DATA INCONSISTENCY
PLEASE PAST the trkgp associated to that sipgateway and the related DDI translator.
make a motortrace with incoming call and may be an mtracer with filter for sip and ddi on
and when you say sets hangup it happens for external call or internal ?
make a motortrace with incoming call and may be an mtracer with filter for sip and ddi on
and when you say sets hangup it happens for external call or internal ?
Re: checkdb : ERROR 4351 : DATA INCONSISTENCY
Consultation/Modification: Faisceaux──────────────────────────────────────────────┐
│ │
│ No noeud-r▒seau (r▒serv▒ soft) : 0 │
│ No faisceau : 10 │
│ │
│ Type faisceau + T2 │
│ Nom du faisceau : SIPGTW │
│ Nom du faisceau en UTF-8 : ------------------------------------------- │
│ Num▒rotation compatible avec : 0 │
│ R▒seau adjacent : 12 │
│ Faisceau r▒parti + Non │
│ Exploitations particuli▒res + Rien │
│ No du noeud : 0 │
│ Faisceau transcom + Non │
│ R▒servation auto.op. + Non │
│ No faisceau d▒bordement : -1 │
│ Tonalit▒ sur prise + Non │
│ Faisceau priv▒ + Non │
│ Variante signalisation Q931 + ABC-F │
│ Variante signalisation SS7 + Aucune │
│ Type s▒lection canaux + Quantit▒ │
│ Num.Q23 auto.sur appel sortant + Non │
│ Sp▒cificit▒ T2 + SIP │
│ R▒seau homog▒ne pour RTP direct + Non │
│ Cat▒gorie acc▒s r▒s.public : 18 │
│ Transcodage SDA + Non │
│ Accepte SUU dans le SETUP + Oui │
│ Ext gateway SIP associ▒e : -1 │
│ │
│ Priorit▒ implicite │
│ │
│ Mode activation : 0 │
│ Niveau de priorit▒ : 0 │
│ │
│ Pr▒emptable + Non │
│ Cat. restriction d'appels entrants : 10 │
│ Cat. restriction d'appels sortants : 10 │
│ num▒rotation mpt1343 + Non │
│ Num▒rotation par chevauchement + Oui │
│ Renvoi d'appel sur ISDN + Non │
│
where can I find the DDI translator?
Re: checkdb : ERROR 4351 : DATA INCONSISTENCY
If the trunkgroup is used for DDI SOURCE, go down in hierarchy and select.
Trunk group NPD selector
but things are wrong with your trkgp config
1-as per system doc if the sip trkgp is toward public network q931 signaling variant should be ISDN ALL COUNTRIES not ABCF or it's specific cause links to MS TEAM (HOPE YOU HAVE SBC)
2-IF TRANSCODAGE SDA (dDDI) is used this parameter should be SET to yes Transcodage SDA + Non------->yes AND BY THE WAY PAS PAST ROUTING TABLE FRO NETW= 12
3-your system is r9.1 or no ? Ext gateway SIP associ▒e : -1 │
see my config bellow.
Q931 Signal variant + ISDN all countries x
x SS7 Signal variant + No variant x
x Number Of Digits To Send : 0 x
x Channel selection type + Quantified x
x Auto.DTMF dialing on outgoing call + NO x
x T2 Specification + SIP x
x Homogenous network for direct RTP + NO x
x Public Network COS : 2 x
x DID transcoding + True
Trunk group NPD selector
but things are wrong with your trkgp config
1-as per system doc if the sip trkgp is toward public network q931 signaling variant should be ISDN ALL COUNTRIES not ABCF or it's specific cause links to MS TEAM (HOPE YOU HAVE SBC)
2-IF TRANSCODAGE SDA (dDDI) is used this parameter should be SET to yes Transcodage SDA + Non------->yes AND BY THE WAY PAS PAST ROUTING TABLE FRO NETW= 12
3-your system is r9.1 or no ? Ext gateway SIP associ▒e : -1 │
see my config bellow.
Q931 Signal variant + ISDN all countries x
x SS7 Signal variant + No variant x
x Number Of Digits To Send : 0 x
x Channel selection type + Quantified x
x Auto.DTMF dialing on outgoing call + NO x
x T2 Specification + SIP x
x Homogenous network for direct RTP + NO x
x Public Network COS : 2 x
x DID transcoding + True