Good evening gents. Im working as a custom service agent. We connect to the company’s PC through Forticlient VPN and the program we use to communicate with our clients is Bria. The issue im facing is that i ve a lot of complains that my voice is cracking. I can hear them very well, but my voice doesnt reach them as it should be. I ve tested my device and its not a hardware issue on microphone or anything. Below im attaching my config and few tests on bufferbloat before and after application of simple queues. Clients some time say that my voice is fine after applying the queue, but other times its not fixing the issue. If you ve any thoughts please let me know. Thanks in advance.
It's mostly users' forum, managed by volunteers. If someone wants to help, then helps, if not, then topic gets stalled. There is no SLA Maybe there is noone who knows the answer?
Do you use forticlient to connect to Mikrotik's router? Have you tried other options?
Why are you tweaking packets' TTL?
If you publish only a part of a config then it gets even harder to guess what could be the problem
You might want to apply to the WAN via target. Currently it appears to be "", which is odd. Also, you could use an interface queue instead with fq_codel to the WAN interface, which only capture outbound. Both a simple to try.
Personally, I'd use a /queue/tree so that SIP traffic has a limit-at while other traffic does not, and can set a max-limit for all LTE traffic You apply similar using a simple queue too but this IMO get more confusing than /queue/tree. In either case, you need to mark packets to identify the SIP traffic, so the limit-at only applies to SIP. Normal traffic should not have a limit-at. The terms are confusing but "limit-at" should be read as guaranteed
Additionally, appear your using LTE. So anything you can do to improve the LTE signal quality may help too. Are the drop calls happen around "primetime" when cell networks might be congested? Also since LTE bandwidth is variable, so setting max-limit get tricky - either you set to the lowest speed you expect (and "waste" bandwidth when speeds are higher), or you set it the average speed you expect (in which case the queue will not drop packet to prevent bufferbloat if speed is low since queue won't trigger).
Finally, you can try to disable the ALG in /ip/firewall/service-port/set sip disabled=yes as it's not likely needed (unless you have local PBX and it crosses LANs)
First if all thanks for your answers and your time and . Forticlient is running on my pc, dunno if i can run this on mikrotik and how. Tomorrow im gonna ask my IT, if i can change SSL into ipsec, cause from what i heard tcp connections are trash when they come though tunnels along with 4G/5G connectivity. TTL are tweaking in order supposedly to make my router looking as a cellphone and trick the provider to not cut my speeds. The ALG you are suggesting is it gonna make a difference, dont know whats PBX etc, probably i dont need ALG. Below im posting my latest config. Thanks again.
You didn't mention this is going via a VPN upstream...
That's mostly right. IPSec be better than some TCP-based VPN. 4G/5G network have some recovery mechanism internal to network, but it adds latency to retry packets. Since TCP also does recovery, and also slows down if errors, it does make it a double-whammy.
But I tend to believe your SIP troubles are not in queues - although they help if you have a lot of local traffic.
@amm0 ,so any other suggestions if this isnt possible? Cant stop thinking that i hear them fine and they dont. Of course i dont know how its working overall, but still. Thats why im seeking a solution for this.
I asked of TTL as you set it arbitrarily to 64, you do not decrease it by one to fool ISP's network. How do you know that it is a proper value?
On the other hand ISP perfectly knows brands of devices you use to access their network.
I did notice that too. I'd recommend remove the TTL. Although I doubt that's the cause since traffic seems to work.
Typically the TTL adjustment is needed for LTE carriers that use it to block tethering (hotspot on smartphone). But unless you're sure it's need (historically T-Mobile in US, which does not do this anymore), it's better not to set it. Various security schemes might see an unusual TTL and take some action.
I can remove it, tho its not the issue, cause im experiencing the crackling issue from the beginning of my employment at which time i didnt ve ttl set up.
Maybe there is noone who knows the answer?