-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Thorsten,
I suppose that every location has it's very own OTRS? You actually just need to share relevant tickets, e.g. those which have to be processed in another OTRS-instance, as well as successfully closed tickets and (maybe) FAQ-Entries. We built a quite similiar solution where we interfaced two OTRS-instances and implemented an OTRS-ticket process across multiple OTRS-instances. The first instance was used for entering and storing test protocols. The second instance was an established OTRS for 'common' ticket processing. The negative test protocols caused were transmitted and processed as trouble tickets in the second instance. For almost the similar reasons as mentioned by you (DMZ, firewalls, slow/unreliable connection) and due to the fact that there's no time aspect in transmitting those 'transfer-tickets' the systems where interfaced by encrypted, signed and structured emails. The interlink-protocol ensured that there were no losses. The solution worked quite well and we've plans to extend this solution to a more general and decentralized, non-master-slave approach. If this solution aroused your interest, please feel free to contact me. regards, Torsten Thau - -- Torsten Thau, Dipl. Inform. c.a.p.e. IT Labs GbR - Annaberger Str. 240 - D-09125 Chemnitz phone: +49 371 5347 623 cell: +49 176 66 680 680 pgp-key: 0x292F987D fax: +49 371 5347 625 http://www.cape-it.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGzrDfvXo8m5PgoXQRAsUQAJ0eWGLpvJDF/uFWb1XEuihjVQouTACfYaxN rRjy64O5x0aKksevj9wqqJE= =nq6P -----END PGP SIGNATURE----- _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/
