Jump to content

Recommended Posts

Posted (edited)

We've just had our first VOIP system installed at this site.

 

It's Yealink handsets on a splicecom map with Gamma & Voiceflex as the upstream providers through a reseller.

 

We've had quite a lot of poor quality calls - roughly 15% of entire call volume. It's worse between 11 & 3, always external calls and more issues with mobiles than landlines.

 

Anyone else experiencing a similar issue with Gamma or Voiceflex this week?

 

I've reported it to the provider but I'm trying to establish the likelihood of it being an internal issue, an issue with our initial internet connection, or an upstream trunk issue.

Edited by Oaktech
Posted

Where's the pbx? Is it hosted?

 

If a call is internal does it a) get routed only internally or go to the internet and back, and b) if only internally does it ever sound bad?

 

What's your internet connection, and how busy is it?

  • Thanks 1
Posted
Where's the pbx? Is it hosted?

 

If a call is internal does it a) get routed only internally or go to the internet and back, and b) if only internally does it ever sound bad?

 

What's your internet connection, and how busy is it?

 

PBX is internal, local to local calls don't touch the internet.

 

Internet is 200mb and has not been maxxed out at the times we've had issues reported.

Posted

We have gamma sip trunks, not been told of any problems, I heard they're moving people to a new platform but they've not emailed me about this yet

 

Do local to local calls go via the pbx?

 

I suggest talking to Gamma, they were very good when I had issues.

  • Thanks 1
Posted

 

Internet is 200mb and has not been maxxed out at the times we've had issues reported.

 

Became of how you are looking at this. What is the refresh interval on the monitoring. For example, a speedtest will max out a line but can go unnoticed on a many monitoring systems.

 

I would check if your firewall has SIP ALG, if so disable it. Causes more harm than good!

 

Also consider setting up QOS if you haven’t already.

  • Thanks 1
Posted
They are, and the VLAN is set up for Voip as far as you can with Unifi switches.

 

I use Unifi switches but I have a different switch make for the core doing the intervlan routing (HP Aruba) if you have a different switch that is doing your layer 3 routing, check there for it to also be set as the voice VLAN.

 

I also made a config profile for Phone Ports, where the default is the wired VLAN and it has access to the voice VLAN, making sure the VLAN ID is set on the Phone for the phone itself (as then you can use the passthrough for PCs) and declared the Phone VLAN for the Voice Network there too.

voip.png

  • Thanks 1
Posted
I use Unifi switches but I have a different switch make for the core doing the intervlan routing (HP Aruba) if you have a different switch that is doing your layer 3 routing, check there for it to also be set as the voice VLAN.

 

I also made a config profile for Phone Ports, where the default is the wired VLAN and it has access to the voice VLAN, making sure the VLAN ID is set on the Phone for the phone itself (as then you can use the passthrough for PCs) and declared the Phone VLAN for the Voice Network there too.

[ATTACH=CONFIG]69780[/ATTACH]

 

That's exactly how I have it set up.

 

Does anyone know if it's possible to set phone QOS on a Smoothwall?

 

I've spoken to the provider and they are applying an update to the server tonight. Helpfully the call quality to the supplier was poor so they had something to look at!

Posted
Glad to have helped with a bit of double-checking there. I have Yealink handets but they are cloud hosted, and I am afraid I do not have smoothwall, but it would surprise me if smoothwall didn't have settings for it somewhere
  • Thanks 1
Posted

Ok, So, update on this, bit a few days of it...

 

Supplier confirmed they were accepting there was an issue at 3pm Thursday, but couldn't immediately identify where the issue lay.

 

They Rebooted and resynced some of their internal infrastructure and did several remote updates and settings adjustments on our Splicecom MAP overnight on Thursday, but approx half of the handsets then didn't come back up on friday morning. Friday is not my day to be on that site and I really couldn't stop what I was doing to drive over there. The school was without those handsets until about 11am when the supplier managed to find that the upgrade script had an issue and was causing the handsets to continually loop installing a failing update. The supplier cancelled the script and I got one of our office staff to reboot all the phones which then came up - except one. The supplier then requested that I attend site on Saturday for a couple of hours to work through the handset updates, which is fine, Management coughed for 2hr30 overtime and everything went to plan, but my god, I did some walking, 68 extensions over 4 blocks had to be rebooted manually 3 times each - once to factory reset, once to provision on original firmware and onece to provision on updated firmware.

  • Thanks 1
Posted
Ooof that is crazy, for future reference, if all your switches are unifi, you can restart PoE devices on the port manager page of the console (port by port I'm afraid)
  • Thanks 1
Posted
Ooof that is crazy, for future reference, if all your switches are unifi, you can restart PoE devices on the port manager page of the console (port by port I'm afraid)

 

I have found that, but they required interaction on the first 2 reboots - a factory reset, and then a manual VLAN selection. :rolleyes:

Posted
We've just moved to Yealink phones, using Teams and Gamma.

 

Already had to swap out all Yealink handsets once....

 

Were using about 300 various models with 3cx and ive probably replaced 5-10 phones in 4 years

Posted
Were using about 300 various models with 3cx and ive probably replaced 5-10 phones in 4 years

 

What model have you got?

 

They decided here to go with absolute base model (MP52). Turns out it just couldn't handle anything, calls cut off etc.

 

Going two models up (MP56) seems to sort most things but they decided to go with the middle one (MP54).

 

Wish I could rip them out and go a different route.

Posted
What model have you got?

 

They decided here to go with absolute base model (MP52). Turns out it just couldn't handle anything, calls cut off etc.

 

Going two models up (MP56) seems to sort most things but they decided to go with the middle one (MP54).

 

Wish I could rip them out and go a different route.

 

 

we use SIP-T40G SIP-T42U and SIP-T48U

Posted

We're using a few T48, a few T46 but the bulk of them are T43.

 

The handsets all seem OK, the error was with the tolerances for timing in the original script from the supplier

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...