Alcatel Unleashed

Hi Joao and Zero,

In a reply to your comments:

My OXE is generating ACC files normally as per checking Application/accounting, usr4/account and accview -tf can display all tickets of every day normally, but it seems my 4760 could not retrieve them.

NMCSyncLdapPbx_1.log is sent earlier in the attachment.

In the capture attached earlier (Directory1.JPG), you can note that Date Of Last Modification was on 10 April and when I checked the document, it says that it must correspond to the date of the last synchronization, I do not know may it related to the non retrieved accounting files from OXE to 4760 since that date, even I did manual synchronization many times after that date ?!

So briefly, Date Of Last Modification is 10 April and accounting files collected from OXE (stored in C:\4760\data\collector\network nb\PCX nb) till 10 April.

Hi Hany Abdel Baki,

I'm sorry if I overlook the screen capture (Directory1.jpg) but I am certain that the provided log file was not NMCSyncLdapPbx_1.log since I haven't found any "SyncLdapPbx" word or "date-time" stamp of execution in the log's contents.

Based on the Directory1.jpg, "Accounting Process" should be set to "Detailed Accounting" and please put a check-mark on the following: Load System Speed Dial Number, Load User Alias, Load Remote User, and Load Service Number. After, apply all the changes then perform a manual complete synchronization.



Thanks,
Zero

Hi all,

Without putting a check-mark on the following: Load System Speed Dial Number, Load User Alias, Load Remote User, and Load Service Number, but doing the synchronization again makes the accounting files retrieved in C:\4760\data\collector\network nb\PCX nb, so the synchronization is now ok and also reporting.

I did not know the exact reason of the synchronization problem from the beginning.

Thanks a lot all for your help.

Just to clarify
Date of last modification has nothing to do with last synchro
It is an oxe info
You have te raw database fetch by complete synchro
To avoid collecting everything again and again, 4760 access to oxe sub table of last modification done
A last modif can be corrupted, and the solution is to launch a complete synchro.
By changing some synchro option, like alias, you have I think trigger again the complete synchro

Complete synchro should happens once a week

Most of synchro failure happens on one item of oxe
In the past that was due to oxe bug
The mechanic on 4760 side is robust and it trust what oxe announce has it object model
If the object model presented does not follow the real database, then synchro problem occurs

If there is continuous issue with partial synchro , you can launch and schedule another synchro ( complete ) that will be able to get the data that partial synchro in dayly job is missing

Hope it helps and does not seems too complex as an explanation of DATE of LAST Modification and the orriginal meaning of complete and partial synchro

It may be that complete synchro has been changed in design to be in latest 4760 a partial synchro,

Hi corwin,

Thanks for this clarification ..

As you know, accounting files (tickets) are retrieved daily (automatically without doing manual sychro) from OXE (accview) to 4760 in the path C:\4760\data\collector\network nb\PCX nb, and these files are generated every hour on the OXE, my question is: can I control the time (hour) these files are retrieved per day or it is already retrieved hourly once its generated on OXE ?

Hi
4760 retrieve accounting file of oxe daily
It is a subjob of daily and weekly job
Open scheduler app
Browse in the tree you will see the accounting loading
It is not exactly the FTP get of accounting file

Ftpmget is done by synchro task
It retrieve a .lis ( list of files )
Compare with last file downloaded and proceed FTP transfer for new file
Just before proceeding to FTP get, it ask oxe to flush the accounting ticket not yet present in hourly file in a new file

After FTP the loading of accounting is done by looking at all file in a 4760 folder not yet loadaed in SQL database

Conclusion, you wish is fulfilled by default: only daily download or ondemand download by asking from system directory a synchro of oxe

Oxe is able to produce real time accounting ticket, to a printer or via Ethernet to an external app
But 4760 only use FTP transfer


Finally accounting is flush in a file almost every hour but not exactly every hour
In busy hour, you will get one file per hour
When no call during the night, the delay to generate an accounting file is a little bit longer.