Hi, We created our own clock source using the patched ztdummy approach ( http://bugs.digium.com/view.php?id=8896). It seems to working well, with ztdummy receiving our clock each specified time.
During our tests, we created the following scenario: >From SIP Phone we made an outgoing call using a trunk port that was extended to another trunk port (same card) that answered the call and transferred it to another SIP phone. The first analysis shown a good latency time, but after 1 hour we got about 600ms of latency and after 12 hours we got 11 seconds of latency! It is a unique long duration call. (Asterisk 1.2.22 was used) I had done the same test before create the clock source and I thought that this huge latency was caused by different clocks. Now, if the clock implemented, I got the same results than before. Do I misunderstood the problem with SIP/Trunk latency? It is caused by another problem? Any help will be appreciated! Thanks! -- -------------- Paulo Garcia
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
