Well, finally have a solution!   Turns out it was 100% the Meraki Firewall. O have an MX250, and it was a bug in Firmware MX 18.211.2...related to some changes in the way traffic is routed. One of the issues specifically cited SIP/RTP traffic internally potentially being dropped.   The fix was to upgrade the Firmware to MX18.211.3 where the bug was fixed.    They also indicated that there was a workaround before the newest version was released that could also resolve the issue. The workaround, was to go to QoS rules for VoIP traffic and if you had it set to High or Low, change it to Normal and the problem should go away.   Now why on earth did Meraki Support not suggest either of those options to me 6 weeks  ago as a first thing to try, given they have known about this for at least 4 months?   Who knows, but it seems that when I had packet captures on and off the meraki network and could prove the issue only exists when on the meraki network, then and only then did they cough up an answer.   I'm just glad this nightmare is over and I can back to enjoying a quiet, and smooth network.   Hope this info helps someone else who may run Into this issue. ... View more

Well, I would be inclined to agree about rejecting their explanation, however, we have removed a couple fo phones off our Meraki Network entirely, and hooked them directly to a backup internet source that is not connected to our network at all, and the phones work flawlessly with no problems.  If we hook up that internet source to WAN 2 and hook the phones back up to ports on the MX250 firewall in out network, and force those phones to use WAN 2 (and VLAN 88, it's own voice vlan) the problem presents again. This would suggest thebproblem is our network and not the phones.  I want it to be their problem, but it seems it's within our network, sadly.   The next thing I want to attempt, os to see if I can get packet captures of these two phones when they are outside our network, on the backup internet, when they are working fine, and compare packet captures.   Any ideas on how to find this gremlin and fix it would be greatly appreciated!! ... View more

So I m back again. We have tried literally everything we can think of hilariously, my last google search brought me right back here, and I was like.. hey this looks familiar!  Any chance you might be able to offer me advice exactly how to forward UDp to my voip vendors ip address within meraki firewall?   What I have discovered with packet captures, is that our phones are requesting to register every 30 seconds. Here is the breakdown: 1.  Phone send request: REGISTER to external Server 2.  External server sends back  Status: 407 Proxy Authentication Required 3.  Phone sends second request: REGISTER to external Server 4.  External server sends back  Status: 200 OK (REGISTER) (1 binding)   Voip company confirmed that is not expected behavior. They say it should ask to register, their server then asks for username and password, the phone sends it, and then it registers...it shouldnt be asking twice to register. They seem to think somewhere along the way, within our network, packets are getting dropped/lost.  We have ruled out SIP ALG, so it must be some sort of port forwarding/DSCP tagg type issue.   In any case, Using Meraki Firewall, is there a way to do some sort of port forward rule that ensures "UDP/10000-20000 -> Forward to <external IP of my VOIP Provider>" as well as any applicable forwards for port 5060?   I do have QoS rules setup under traffic shaping that is set to tag VOIP traffic as EF 46 with highest priority.   Any help is appreciated! ... View more

10-4 Thanks so much for the quick and thorough explanation! I greatly appreciate that! ... View more

I know this is an old thread, but I am having same issue. How did you go about implementing this resolution exactly, if you dont mind sharing?  Also, we use a VOIP service for our phones, so I am wondering what exactly is the "<ip pbx>" you mentioned? ... View more

I disagree with the assessment that it does not affect functionality.   Here is my scenario..... I connect to the network using the correct password and have selected "Auto Connect".  I open a web browser and go to a website. The website loads. Everything working. Nice...I can get some work done.... Oh wait... Wifi connection just dropped, and I am no longer online. I try to connect to Wifi network again, and it will not let me connect... says Bad Password.... try again, nope. Bad password.  Keep trying... finally it connects and im online. Get back to work, and then boom, dropped wifi again. Logs all show Bad password as the culprit, even though the password was typed in correctly.   How is that "not affecting functionality" ? By the way, that even happened on a brand new computer as well as established devices that had been on the network for some time.   I would like this to be properly investigated by the meraki Support Engineers. We took our entire Campus of 350,000 Square feet (and over 100 Meraki AP) away from Ruckus to Meraki because of how well the system seemed to work and the level of support we were getting.... not instilling confidence at the moment. ... View more

Also having this issue.. we have over 100 MR33 APs, running 26.6.1 Firmware   Surely there is a solution to this issue?? ... View more

Okay, yeah that makes sense.   I plan on tagging an empty port (19 i think) as VLAN 2.  That port will lead to all the AP's and hard lined devices that will be using the Charter internet.   So what you are saying,(correct me if im wrong) is that once I make that physical link, and tag that port as VLAN 2, the current settings we talked about in above replies, are good to go and the Clients that will be using Charter should be good. ... View more

I guess Im having an issue understanding the purpose of the MX I.P then....   I only have the one MX250 and it has an IP of 172.20.0.1   So how is setting VLAN 2, with an MX IP of 10.20.0.1 going to do anything? 10.20.0.1 doesnt actually exist, I just made up that subnet....   Also, currently, the MX250 (172.20.0.1) is acting as the DHCP server. With this is mind, and having Charter traffic go across WAN 2, how will they get IP addresses in to 10.20.0.1/20 ranges?     Maybe this is a case of a lack of understanding on my part, of how this works ? ... View more

I put the subnet in as the MX I.P. for now so I could save it..... If I try and put the actual I.P of the MX (172.20.0.1) it gives an error (which makes sense, because it is on the other VLAN).... ... View more

Hey Phillip, I have another question about this one....   Under Routing, What do I put as the MX I.P. for my leased out internet, on WAN 2, using a subnet of 10.20.0.1/20?  I tried using the true IP address of the MX and it threw an error....         ... View more

  Realized I had to put "Any" in Destination instead of leaving it blank ... View more