Displaying 3 results from an estimated 3 matches for "5103ms".
Did you mean:
103ms
2020 Jun 22
2
Voice broken during calls (again...)
Would you mind repeating the test with canreinvite=no set for all you
phones and mobile phones?
What is your upload bitrate? Is it guaranteed?
I would try also to test the PMTU:
Try:
ping -M do -s 2000 ${ip address of the sip server}
You should receive icmp asking for lowering the packet size.
The LTE phones could have lower MTU and thus overcome PMTU problem.
Marek
2020-06-22 21:48
2020 Jun 22
0
Voice broken during calls (again...)
...492
ping: local error: Message too long, mtu=1492
ping: local error: Message too long, mtu=1492
ping: local error: Message too long, mtu=1492
ping: local error: Message too long, mtu=1492
^C
--- tel.t-online.de ping statistics ---
6 packets transmitted, 0 received, +6 errors, 100% packet loss, time 5103ms
Mmmm... it seems not good, isn't it?
For information, here the output of ifconfig:
dsl0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1492
inet 93.241.x.y netmask 255.255.255.255 destination 62.156.z.k
inet6 fe80::9565:3024:4deb:ebc7 prefixlen 10 scopeid...
2020 Jun 22
2
Voice broken during calls (again...)
...too long, mtu=1492
> ping: local error: Message too long, mtu=1492
> ping: local error: Message too long, mtu=1492
> ping: local error: Message too long, mtu=1492
> ^C
> --- tel.t-online.de ping statistics ---
> 6 packets transmitted, 0 received, +6 errors, 100% packet loss, time 5103ms
>
> Mmmm... it seems not good, isn't it?
>
> For information, here the output of ifconfig:
>
> dsl0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1492
> inet 93.241.x.y netmask 255.255.255.255 destination 62.156.z.k
> inet6 fe80::9565:3...