Hello, we have been testing WTware as a substitute to our current platform with Ubuntu and xfreerdp
We have some issues and questions that would be nice to get oriented
Note: sorry to chat about many topics in same thread, a moderator could split the message if thinks is necessary.
1- It's possible to connect more than 1 sip account with the command SIP = user:
password@sip.linphone.org ?
Tried adding another SIP but just does not work
2-How to select between a 2.4 or 5 Ghz network in the wifi set-up ? (is common this days to have the same ESSID for both).
2.1- We have noticed ping delays through WiFi:
This is WTware v.6.0.2/RPi
Code: Select all
Reply from 192.168.101.122: bytes=32 time=80ms TTL=64
Reply from 192.168.101.122: bytes=32 time=37ms TTL=64
Reply from 192.168.101.122: bytes=32 time=129ms TTL=64
Reply from 192.168.101.122: bytes=32 time=23ms TTL=64
Reply from 192.168.101.122: bytes=32 time=950ms TTL=64
Reply from 192.168.101.122: bytes=32 time=14ms TTL=64
Reply from 192.168.101.122: bytes=32 time=67ms TTL=64
Reply from 192.168.101.122: bytes=32 time=53ms TTL=64
Reply from 192.168.101.122: bytes=32 time=48ms TTL=64
Reply from 192.168.101.122: bytes=32 time=25ms TTL=64
Reply from 192.168.101.122: bytes=32 time=62ms TTL=64
Reply from 192.168.101.122: bytes=32 time=5ms TTL=64
Reply from 192.168.101.122: bytes=32 time=64ms TTL=64
Reply from 192.168.101.122: bytes=32 time=523ms TTL=64
Reply from 192.168.101.122: bytes=32 time=8ms TTL=64
Reply from 192.168.101.122: bytes=32 time=31ms TTL=64
Reply from 192.168.101.122: bytes=32 time=22ms TTL=64
Reply from 192.168.101.122: bytes=32 time=144ms TTL=64
Reply from 192.168.101.122: bytes=32 time=16ms TTL=64
This is the same Raspberry, in the exact same location and to same WiFi network but with Ubuntu 20.04 for ARM
Code: Select all
Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=4ms TTL=64
Reply from 192.168.101.95: bytes=32 time=5ms TTL=64
Reply from 192.168.101.95: bytes=32 time=5ms TTL=64
Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=5ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
There is any known issue on wifi driver that can cause this ? The issue is consistent, after reboot, working on remote desktop, without remote desktop, the behavior is the same.
3-It is possible to change the name of certain machine in WTWarecenter ? (mac address is not to friendly if you have this deployed along the country with VPN)
4- Main pipe close errors: we are having this issue when the lines sound = on, hw:1:0 microphone = on, hw:1:0 AND the linphone is configured with a SIP account
According to this thread
viewtopic.php?t=50468 is related with sound problems. It seems like linphone is "kidnapping" the USB headset and when the remote session tries to reproduce a sound, it chrash.
This does not happen in Ubuntu with xfreerdp
freerdp2-x11/focal,now 2.0.0~git20190204.1.2693389a+dfsg1-2build2 armhf [installed]
In where we can use the SIP phone and the remote sound / mic without issues.
Hello, we have been testing WTware as a substitute to our current platform with Ubuntu and xfreerdp
We have some issues and questions that would be nice to get oriented
Note: sorry to chat about many topics in same thread, a moderator could split the message if thinks is necessary.
[b]1- [/b]It's possible to connect more than 1 sip account with the command SIP = user:password@sip.linphone.org ?
Tried adding another SIP but just does not work
[b]2-[/b]How to select between a 2.4 or 5 Ghz network in the wifi set-up ? (is common this days to have the same ESSID for both).
[b]2.1-[/b] We have noticed ping delays through WiFi:
This is WTware v.6.0.2/RPi
[code]Reply from 192.168.101.122: bytes=32 time=80ms TTL=64
Reply from 192.168.101.122: bytes=32 time=37ms TTL=64
Reply from 192.168.101.122: bytes=32 time=129ms TTL=64
Reply from 192.168.101.122: bytes=32 time=23ms TTL=64
Reply from 192.168.101.122: bytes=32 time=950ms TTL=64
Reply from 192.168.101.122: bytes=32 time=14ms TTL=64
Reply from 192.168.101.122: bytes=32 time=67ms TTL=64
Reply from 192.168.101.122: bytes=32 time=53ms TTL=64
Reply from 192.168.101.122: bytes=32 time=48ms TTL=64
Reply from 192.168.101.122: bytes=32 time=25ms TTL=64
Reply from 192.168.101.122: bytes=32 time=62ms TTL=64
Reply from 192.168.101.122: bytes=32 time=5ms TTL=64
Reply from 192.168.101.122: bytes=32 time=64ms TTL=64
Reply from 192.168.101.122: bytes=32 time=523ms TTL=64
Reply from 192.168.101.122: bytes=32 time=8ms TTL=64
Reply from 192.168.101.122: bytes=32 time=31ms TTL=64
Reply from 192.168.101.122: bytes=32 time=22ms TTL=64
Reply from 192.168.101.122: bytes=32 time=144ms TTL=64
Reply from 192.168.101.122: bytes=32 time=16ms TTL=64[/code]
This is the same Raspberry, in the exact same location and to same WiFi network but with Ubuntu 20.04 for ARM
[code]Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=4ms TTL=64
Reply from 192.168.101.95: bytes=32 time=5ms TTL=64
Reply from 192.168.101.95: bytes=32 time=5ms TTL=64
Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=3ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=5ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64
Reply from 192.168.101.95: bytes=32 time=2ms TTL=64[/code]
There is any known issue on wifi driver that can cause this ? The issue is consistent, after reboot, working on remote desktop, without remote desktop, the behavior is the same.
[b]3-[/b]It is possible to change the name of certain machine in WTWarecenter ? (mac address is not to friendly if you have this deployed along the country with VPN)
[b]4-[/b] Main pipe close errors: we are having this issue when the lines sound = on, hw:1:0 microphone = on, hw:1:0 AND the linphone is configured with a SIP account
According to this thread https://forum.wtware.com/viewtopic.php?t=50468 is related with sound problems. It seems like linphone is "kidnapping" the USB headset and when the remote session tries to reproduce a sound, it chrash.
This does not happen in Ubuntu with xfreerdp
freerdp2-x11/focal,now 2.0.0~git20190204.1.2693389a+dfsg1-2build2 armhf [installed]
In where we can use the SIP phone and the remote sound / mic without issues.