Problem with acounting tickets synchronisation.

[thatawa]

I update my post beacause I have still the trouble and after further investigations I found this :
http://forum.intersyst.ru/read.php?7,4522
but, even with google translate I don't understand.

Maybe can you help me VAD ?

[vad]

This is - from russian forum (old/previous forum of our company).
Nothing intresting for your problem.

From my point of view (if ALU support cannot help you) the easiest way (as I remember - you have one good 4760 and one with problem):
- reinstall bad 4760 server;
- manage connection to PBX and check synchronisation.
- if Ok - manage everything (f.e. via export/import from good 4760).

[thatawa]

This is - from russian forum (old/previous forum of our company).
Nothing intresting for your problem.

The error is exactly the same that mine, so I think there's something common.

From my point of view (if ALU support cannot help you) the easiest way (as I remember - you have one good 4760 and one with problem):
- reinstall bad 4760 server;
- manage connection to PBX and check synchronisation.
- if Ok - manage everything (f.e. via export/import from good 4760).

ALU support is still working on the trouble, since 2 months now..., so I am looking for by my side.

Could you, please, translate me quickly.
Thanks.

[Tha Tawa'S]

Hi all,

I come with good news. for me at least. The problem has been solved.
Thanks to extended traces on 4760 main. We ve seen that a user on node 2 (on which synchronization did not work) has 2 keys with "Executive Call" who called the same boss. What is impossible in the real life.

After removing one "Executive Call", synchronization was succesfully.
I still wonder why 4760_replication_used successfully synchronized .....

Anyway, trouble is over. Thanks to all for your help.
See you later.