Two cvs-head asterisk boxes with iax2 working fine (without register
statements).
When two calls are placed simultanously from system A -> B and the packets
are sniffed on the wire, I see the two calls using two different udp
packets. At the top of iax.conf I have trunk=yes and jitterbuffer=yes
(at both ends).
I was expecting to see both calls handled within a single udp packet,
but that's not happening. Each iax2 packet is 79 bytes using ethereal.
I've tried the trunk=yes both within the inbound context and at the top
of the iax.conf file (assuming the one at the top would be used for all
outbound iax calls that don't reference a context). Calls are placed
with:
exten => _2.,1,Dial(IAX2/user:passwd@1.2.3.4/${EXTEN:1})
Is trunking dependent upon the use of 'register'? Or, dependent on the
above exten=>_2., referencing a context (instead of the IP directly)?
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. -mark On Feb 6, 2005, at 12:45 PM, Rich Adamson wrote:> > Two cvs-head asterisk boxes with iax2 working fine (without register > statements). > > When two calls are placed simultanously from system A -> B and the > packets > are sniffed on the wire, I see the two calls using two different udp > packets. At the top of iax.conf I have trunk=yes and jitterbuffer=yes > (at both ends). > > I was expecting to see both calls handled within a single udp packet, > but that's not happening. Each iax2 packet is 79 bytes using ethereal. > > I've tried the trunk=yes both within the inbound context and at the top > of the iax.conf file (assuming the one at the top would be used for all > outbound iax calls that don't reference a context). Calls are placed > with: > exten => _2.,1,Dial(IAX2/user:passwd@1.2.3.4/${EXTEN:1}) > > Is trunking dependent upon the use of 'register'? Or, dependent on the > above exten=>_2., referencing a context (instead of the IP directly)?-- Mark Eissler, mark@mixtur.com Mixtur Interactive, Inc. -@- http://www.mixtur.com
There is a new patch in the mantis for jitter buffering together with trunking. On 6 Feb 2005 at 18:45, Mark Eissler wrote:> 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. > > -mark > > On Feb 6, 2005, at 12:45 PM, Rich Adamson wrote: > > > > > Two cvs-head asterisk boxes with iax2 working fine (without register > > statements). > > > > When two calls are placed simultanously from system A -> B and the > > packets > > are sniffed on the wire, I see the two calls using two different udp > > packets. At the top of iax.conf I have trunk=yes and jitterbuffer=yes > > (at both ends). > > > > I was expecting to see both calls handled within a single udp packet, > > but that's not happening. Each iax2 packet is 79 bytes using ethereal. > > > > I've tried the trunk=yes both within the inbound context and at the top > > of the iax.conf file (assuming the one at the top would be used for all > > outbound iax calls that don't reference a context). Calls are placed > > with: > > exten => _2.,1,Dial(IAX2/user:passwd@1.2.3.4/${EXTEN:1}) > > > > Is trunking dependent upon the use of 'register'? Or, dependent on the > > above exten=>_2., referencing a context (instead of the IP directly)? > -- > Mark Eissler, mark@mixtur.com > Mixtur Interactive, Inc. -@- http://www.mixtur.com > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
Mark Eissler <mark@mixtur.com> wrote:>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? Doug -- Doug Meredith (doug.meredith@systemguard.com) SystemGuard - Oracle remote support 877-974-8273 (87-SYSGUARD) 506-854-7997 www.systemguard.com