omnivista 8770 installation with OXO

This application replaces the OmniVista 4760
Post Reply
anisbou
Member
Posts: 28
Joined: 19 Oct 2012 04:25

omnivista 8770 installation with OXO

Post by anisbou »

hi
i installled the omnivista 8770 R2.6 on a Win10 VM .I declared the OXO with the following settings:
network number =1
subnetwork number =1
node number=1
ip address =192.168.4.11
currently i can connect to the PBX from the 8770 server but i can't get the tickets and in sheduled work i have this error:

[21/12/2020 11:02:07] Planificateur: la tâche est démarrée
[21/12/2020 11:02:14] Cible : OXO,SOT,SOTUCHOC
Nouvel état : Chargement complet
[21/12/2020 11:02:14] Cible : OXO,SOT,SOTUCHOC
Nouvel état : Récupération des fichiers de tickets
[21/12/2020 11:02:17] Cible : OXO,SOT,SOTUCHOC
Erreur : Connexion refusée
[21/12/2020 11:02:17] Cible : Certains PCX n'ont pas été complètement chargés !
OXO,SOT,SOTUCHOC
[21/12/2020 11:02:20] Planificateur: la tâche a échoué
ACFE Alcatel OmniPcx Enterprise
haroun
Senior Member
Posts: 1056
Joined: 29 Mar 2010 11:09

Re: omnivista 8770 installation with OXO

Post by haroun »

see omnivista 8770 log file
anisbou
Member
Posts: 28
Joined: 19 Oct 2012 04:25

Re: omnivista 8770 installation with OXO

Post by anisbou »

[21/12/2020 12:40:39] 9808 SyncLdapPbx: Start of Job (compl_synchro)
[21/12/2020 12:40:39] 9808 SyncLdapPbx: Notification to Loader : Taxa 4400(SynchroStarted)
[21/12/2020 12:40:39] 9808 SyncLdapPbx: Notification to Loader : PTP (SynchroStarted)
[21/12/2020 12:40:39] 9808 SyncLdapPbx: Notification to Loader : Taxa Alize(SynchroStarted)
[21/12/2020 12:40:39] 9808 SyncLdapPbx: Notification to Loader : Taxa 4200(SynchroStarted)
[21/12/2020 12:40:39] 9808 SyncLdapPbx: Notification to Loader : (Loader/Voip/Load) IP ticket (SynchroStarted)
[21/12/2020 12:40:39] 9808 SyncLdapPbx: SYNC_STARTED to loaders Notified
[21/12/2020 12:40:41] 9808 SyncLdapPbx: Error: SYNC_STARTED to Audit notification failed
[21/12/2020 12:40:41] 9808 SyncLdapPbx:

Load (SubnetworkNodeNumber=101, SubnetworkNumber=1, NetworkNumber=1, o=nmc) RetryPhasis=0 Request=2
[21/12/2020 12:40:41] 9808 SyncLdapPbx: Error: Configuration license not available[21/12/2020 12:40:41] 9808 SyncLdapPbx: The value of the attribute: pcsticketcollection = 1
[21/12/2020 12:40:41] 9808 SyncLdapPbx: The value of the attributes: AuditProcess and MinOxeRelease = 0 and f5.401.14
[21/12/2020 12:40:46] 9516 SyncLdapPbx: pbxDn:SubnetworkNodeNumber=101, SubnetworkNumber=1, NetworkNumber=1, o=nmc
status_sync : complete_load
[21/12/2020 12:40:46] 9516 SyncLdapPbx: pbxDn:SubnetworkNodeNumber=101, SubnetworkNumber=1, NetworkNumber=1, o=nmc
status_sync : polling
[21/12/2020 12:40:49] 9516 SyncLdapPbx: Error: ftplib: read errno:No such file or directory WSAGetLastError:Une connexion existante a dû être fermée par l’hôte distant. (10054)
[21/12/2020 12:40:49] 9516 SyncLdapPbx: Error: ftplib: Control socket read failed errno:No such file or directory WSAGetLastError:Une connexion existante a dû être fermée par l’hôte distant. (10054)
[21/12/2020 12:40:49] 9516 SyncLdapPbx: pbxDn:SubnetworkNodeNumber=101, SubnetworkNumber=1, NetworkNumber=1, o=nmc
error : connexion_refused
[21/12/2020 12:40:49] 9808 SyncLdapPbx: Notification: Filter 5 updated
[21/12/2020 12:40:49] 9808 SyncLdapPbx: Setting notification filter: 'Id < 0' ~ $objectHierarchy
[21/12/2020 12:40:49] 9808 SyncLdapPbx: Notification to Loader : Taxa 4400(SynchroStopped)
[21/12/2020 12:40:49] 9808 SyncLdapPbx: Notification to Loader : PTP (SynchroStopped)
[21/12/2020 12:40:49] 9808 SyncLdapPbx: Notification to Loader : Taxa Alize(SynchroStopped)
[21/12/2020 12:40:49] 9808 SyncLdapPbx: Notification to Loader : Taxa 4200(SynchroStopped)
[21/12/2020 12:40:49] 9808 SyncLdapPbx: Notification to Loader : (Loader/Voip/Load) IP ticket (SynchroStopped)
[21/12/2020 12:40:49] 9808 SyncLdapPbx: SYNC_STOPPED to Loaders Notified
[21/12/2020 12:40:51] 9808 SyncLdapPbx: Error: SYNC_STOPPED to Audit notification failed
[21/12/2020 12:40:51] 9808 SyncLdapPbx: RTUM's property: (/NmcJavaService/RTUM/SynchroStatus)
[21/12/2020 12:40:51] 9808 SyncLdapPbx: End of Job (compl_synchro)
ACFE Alcatel OmniPcx Enterprise
haroun
Senior Member
Posts: 1056
Joined: 29 Mar 2010 11:09

Re: omnivista 8770 installation with OXO

Post by haroun »

network number =1
subnetwork number =1
node number=1
[21/12/2020 12:40:46] 9516 SyncLdapPbx: pbxDn:SubnetworkNodeNumber=101, SubnetworkNumber=1, NetworkNumber=1, o=nmc

2-Error: Configuration license not available[21/12/2020 12:40:41] 9808 SyncLdapPbx: The value of the attribute: pcsticketcollection = 1

3-21/12/2020 12:40:49] 9516 SyncLdapPbx: Error: ftplib: read errno:No such file or directory WSAGetLastError:Une connexion existante a dû être fermée par l’hôte distant. (10054)
[21/12/2020 12:40:49] 9516 SyncLdapPbx: Error: ftplib: Control socket read failed errno:No such file or directory WSAGetLastError:Une connexion existante a dû être fermée par l’hôte distant. (10054)
[21/12/2020 12:40:49] 9516 SyncLdapPbx: pbxDn:SubnetworkNodeNumber=101, SubnetworkNumber=1, NetworkNumber=1, o=nmc
error : connexion_refused

good credential for ftp? ov8770 as trust for oxo?!
Last edited by haroun on 21 Dec 2020 15:52, edited 1 time in total.
anisbou
Member
Posts: 28
Joined: 19 Oct 2012 04:25

Re: omnivista 8770 installation with OXO

Post by anisbou »

even if i put the SubnetworkNodeNumber=1 there is the same essue
ACFE Alcatel OmniPcx Enterprise
User avatar
alex
Senior Member
Posts: 1422
Joined: 06 Jul 2004 07:27
Location: Russia
Contact:

Re: omnivista 8770 installation with OXO

Post by alex »

anisbou wrote: 21 Dec 2020 05:05 hi
i installled the omnivista 8770 R2.6 on a Win10 VM .I declared the OXO with the following settings:
network number =1
subnetwork number =1
node number=1
ip address =192.168.4.11
For OXO these parameters do not matter if you don't have OXEs configured on the same 8770.
Looks like you declared OXO as OXE in Networks.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
anisbou
Member
Posts: 28
Joined: 19 Oct 2012 04:25

Re: omnivista 8770 installation with OXO

Post by anisbou »

Thank you all i found the issue,it s in the nmc password of oxo that must be the same as in 8770 installation.
ACFE Alcatel OmniPcx Enterprise
Post Reply

Return to “OmniVista 8770”