Podrška #18820
Zatvoren
voip latency - asterisk iax2 (test bhingco i fbde trunk)
0%
Povezani tiketi 1 (0 otvoreno — 1 zatvoren)
Izmjenjeno od Ernad Husremović prije više od 15 godina
http://blog.wl0.org/2009/06/discovering-the-cause-of-asterisk-jitter-delays/
Finally it seems (and I’m still not 100% sure), though the signs are promising, that the problem is something as simple as the SPA3102, PAP2T and SPA941’s default configuration having a high network jitter configuration.
This is to improve things on an internet based voip call. However this adds loads of extra latency and if the phones are connected directly to Asterisk this default configuration adds a lot more latency than you would expect: latency from the phone to asterisk and then latency from the phone to the PSTN number (via the SPA3102), the combination being enough to destroy the usability of the call.
I’ve changed this now to low network latency and the results are promising, but I’m surprised not to have seen this problem mentioned in the Asterisks books I’ve bought, nor various forums and mailing lists I’ve been following.
Izmjenjeno od Ernad Husremović prije više od 15 godina
Izmjenjeno od Ernad Husremović prije više od 15 godina
- Naslov promijenjeno iz voip latency u voip latency - asterisk iax2 (test bhingco i fbde trunk)
setovao na iax.conf atom-2
timestamps=yes jitterbuffer=yes
na granstream telefonu stavio jitterbuffer low (inače je medium)
Testing and monitoring
You can test the effectiveness of PLC and the new jitterbuffer’s detection of loss by using the new CLI command ”iax2 test losspct <n>”. This will
simulate n percent packet loss coming in to chan iax2. You should find that with PLC and the new JB, 10 percent packet loss should lead to just a
tiny amount of distortion, while without PLC, it would lead to silent gaps in your audio.
”iax2 show netstats” shows you statistics for each iax2 call you have up. The columns are ”RTT” which is the round-trip time for the last PING, and
then a bunch of s tats for both the local side (what you’re receiving), and the remote side (what the other end is telling us they are seeing). The remote stats may not be complete if the remote end isn’t using the new jitterbuffer.
The stats shown are:
• Jit: The jitter we have measured (milliseconds)
• Del: The maximum delay imposed by the jitterbuffer (milliseconds)
• Lost: The number of packets we’ve detected as lost.
• %: The percentage of packets we’ve detected as lost recently.
atom-2*CLI> iax2 show netstats
-------- LOCAL --------------------- -------- REMOTE --------------------
Channel RTT Jit Del Lost % Drop OOO Kpkts Jit Del Lost % Drop OOO Kpkts FirstMsg LastMsg
IAX2/bhingco-7144 25 17 89 45 1 11 0 1 0 40 0 0 0 0 0 Rx:NEW Tx:ACK
IAX2/10.8.0.191:4569-8861 55 -1 0 -1 -1 0 -1 0 0 40 0 0 0 0 0 Tx:NEW Rx:ACK
IAX2/192.168.11.6:4569-12 96 -1 0 -1 -1 0 -1 0 0 40 0 0 0 0 0 Tx:NEW Rx:ACK
3 active IAX channels
interesantno da bhingco ide preko dva kanala (odlaz i dolaz) a fbde samo preko jednog kanala
razlog je sigurno to što smo stavili da je 10.8.0.191 pristup bringout->bhingco a u suprotnom smjeru
root@atom-2:~# ping asterisk.bhingco.ba
PING asterisk.bhingco.ba (10.8.0.191) 56(84) bytes of data.
ide preko 192.168.58.x rute pa on to tretira kao dva trunk-a
Izmjenjeno od Ernad Husremović prije više od 15 godina
vidi razlike čovječe
atom-2*CLI> iax2 show netstats
-------- LOCAL --------------------- -------- REMOTE --------------------
Channel RTT Jit Del Lost % Drop OOO Kpkts Jit Del Lost % Drop OOO Kpkts FirstMsg LastMsg
IAX2/bhingco-7144 21 390 451 328 3 206 5 11 0 40 0 0 0 0 0 Rx:NEW Tx:ACK
IAX2/10.8.0.191:4569-8861 27 -1 0 -1 -1 0 -1 0 0 40 0 0 0 0 0 Tx:NEW Rx:ACK
reko 10.8.0.x nema nijednog izgubljenog paketa a preko 192.168.58.xxx 328 izgubljenih paketa !!!
Izmjenjeno od Ernad Husremović prije više od 15 godina
nema pucanja veze nakon jitterbuffer=yes, timestamps=yes¶
međutim sada nema pucanja veze kako je to bio slučaj do sada
Izmjenjeno od Ernad Husremović prije više od 15 godina
evo odmah sam se opovrgao :(
atom-2*CLI> iax2 show netstats
-------- LOCAL --------------------- -------- REMOTE --------------------
Channel RTT Jit Del Lost % Drop OOO Kpkts Jit Del Lost % Drop OOO Kpkts FirstMsg LastMsg
IAX2/10.8.0.191:4569-5086 23 -1 0 -1 -1 0 -1 0 0 40 0 0 0 0 0 Tx:NEW Rx:ACK
IAX2/bhingco-6444 19 336 627 36 2 11 0 1 0 40 0 0 0 0 0 Rx:NEW Tx:ACK
sada je veza skroz pukla i vidi se da je na ovom bhingco-6444 lost veliki, delay ogroman a right in time vrlo mali ...
Izmjenjeno od Ernad Husremović prije skoro 15 godina
- Status promijenjeno iz Novo u Zatvoreno