You must set trunk=yes in the context of the relevant provider. Not all
providers support it. The benefit of trunking grows exponentially with
the number of calls in progress.
-mark
On Jan 31, 2005, at 2:24 AM, Spencer Nassar wrote:
The test results that Philipp pointed out show some protocol
On January 31, 2005 08:57 am, Mark Eissler wrote:
You must set trunk=yes in the context of the relevant provider. Not all
providers support it. The benefit of trunking grows exponentially with
the number of calls in progress.
Isn't it just a linear savings?
1 call: UDP overhead + voice data
2
Isn't it just a linear savings?
1 call: UDP overhead + voice data
2 calls: UDP overhead + voice data + voice data
3 calls: UDP overhead + 3xvoice data
etc...
without trunking the UDP overhead is repeated for each voice call
I know nothing about the IAX protocol but I wont let that
Yes, you are correct. Instead of separating the RTP streams for each
call, trunking combines them in order to save on overhead.
-mark
On Jan 31, 2005, at 9:38 AM, Andrew Kohlsmith wrote:
On January 31, 2005 08:57 am, Mark Eissler wrote:
You must set trunk=yes in the context of the relevant
Has anyone benchmarked Asterisk on a dedicated single versus dual
processor machine?
http://www.astertest.com/
Cheers, Philipp
The test results that Philipp pointed out show some protocol
comparisons that include iax2 trunking / alaw and iax2 / alaw and
concludes that IAX2 trunking is more than
