> > > >>AFAIK, trunk=yes is not a global option. You set it within a context. > >>Also, using the jitter buffer with trunk=yes is not recommended since > >>its broken right now. > >> > >> > > > >The jitter buffer itself is broken, or only in combination with > >trunking? > > > > > The jitter buffer itself could use improvement, but it's not broken. > > I think that the patch in > http://bugs.digium.com/bug_view_advanced_page.php?bug_id=0003400 solves > the trunk + jitterbuffer problem..
As the OP of this thread, I was more concerned that trunk=yes was not actually placing two simultanous calls in the same packet and I had included the parameter jitterbuffer=yes in that same post. Having been on the list for over a year, I've read your (and other) postings relative to the jitterbuffer, but I've not seen much in terms of whether trunking is or is not working in cvs head. Looking at sniffer traces of two simultanous calls, its apparent that two calls use two different udp packets. However, since I'm routing the two calls via simple extensions.conf entries without reference to an iax context, I was wondering if that _might_ be the root cause for this. (Or, could it be that jitterbuffer=yes disables trunking.) Any feel for that? Rich _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
