Route SIP calls through VPN connection
-
User reporting utter piss poor calls,.. the other party can't hear her, or it's so clipped, incomplete that the is worthless "ninety-percent" of the time. Of course in office it's fine. But she's inter to the PBX infrastructure.
Of course, she was using a 2.5mm iPhone headset or the internal Mic/Speaker of the laptop, on the vpn, at a rural location,.. over a wifi connection.
She reports having MetroNet - which should be fiber. So there is no reason there should be that bad a quality. Won't move closer to the AP, or even plug in a cable to test.
The Mitel Connector app has the option to forward calls to a defined number and instructions were given on how to setup and use,.. but that doesn't seem to 'work either'. Likely not turned on, set.
But the Mitel system is 'impossible' to connect to unless internal or on the VPN.
-
@gjacobse said in Route SIP calls through VPN connection:
Won't move closer to the AP, or even plug in a cable to test.
I think at this point it stops being IT issue and needs management involvement.
-
@marcinozga said in Route SIP calls through VPN connection:
@gjacobse said in Route SIP calls through VPN connection:
Won't move closer to the AP, or even plug in a cable to test.
I think at this point it stops being IT issue and needs management involvement.
Agreed.
Known.
Attempted to address. -
-
Ug - Mitel...
That said - we had a site to site tunnel between locations for 5 years with 7 phones on the remote side with little to no issues with Mitel phones. Of course, we did have a Mitel PBX on both sides, so it was PBX to PBX comms, not phone to PBX, not sure how much that would affect things.
In my case - there were zero trunks at the remote side - all outbound calls had to traverse the VPN to corp, then hope a trunk to the carrier - again, rarely had any issues with this.
Connections where 100/20 cable at corp
50/10 at remote location.
The VPN also handled all normal network traffic, file shares, AD logons, etc. I did everything I could to keep printing off that VPN.Good luck.
-
@gjacobse said in Route SIP calls through VPN connection:
What kind of QoS would one expect while using a softphone over the VPN?
None. VPNs don't provide for QoS. Once traffic hits the Internet, VPN or not, any attempt at QoS is gone.
-
@dashrender said in Route SIP calls through VPN connection:
depends - are there QoS flags for SIP/RTP traffic?
If not, then the same as all other traffic.
What's the issue?
Doesn't depend. Assuming that it is a VPN over the Internet, rather than through the LAN where it would make no sense.
Also, VPN strips the QoS flags even on the LAN. So while you could QoS tag the VLAN itself, it would be all VPN traffic set to a priority. Anything inside the VPN would be equal priority to each other as VPNs do not have QoS.
-
@gjacobse said in Route SIP calls through VPN connection:
on the vpn, at a rural location,.. over a wifi connection.
- VPN adds latency and generally hurts phone call quality a bit.
- WiFi doesn't support the latency needs of calls, calls should always be avoided on wifi if possible. DECT is the wireless protocol for voice calls, not wifi.
-
@gjacobse said in Route SIP calls through VPN connection:
She reports having MetroNet - which should be fiber. So there is no reason there should be that bad a quality.
Fiber is the connection media. It tells us nothing of the bandwidth or latency of the connection, its reliability, its oversubscription, or her utilization of it. Nothing in it being fiber suggests that it is better or worse than any other connection. The physical material of a network connection is immaterial to transmission quality.
-
@gjacobse said in Route SIP calls through VPN connection:
Won't move closer to the AP, or even plug in a cable to test.
You've identified the likely issues. Just report it as user unable to provide working home network.
-
@marcinozga said in Route SIP calls through VPN connection:
@gjacobse said in Route SIP calls through VPN connection:
Won't move closer to the AP, or even plug in a cable to test.
I think at this point it stops being IT issue and needs management involvement.
Exactly. Nothing IT can do here.
