Any one having issues with one way audio using MS teams to PSTN network with MX64 ?   I have a number of customers using TEAMS voice to the PSTN network.   If you dont make any calls for a while when you make the call you get 1 way audio  Called party can not hear the calling party.   You hang up and then call again and it works.  and keeps working till you  don't make calls for a while (say 30 minutes)   customer are now ringing there mobiles first before ringing person so they know it will work.   if I remove the meraki and put in a cisco router running NAT  it works fine..   It is like something gets setup on first calls and then stays there and then times out after no use...   tried a sip phone via MX and it works fine.   just seems to effect MS Teams   Any one else seeing this ??   ... View more

I have had a bad day today.  I had MX64 with   FW15.34  Insight was not working (not uploading data) Case 05530983  I was told that the next firmware update would fix this.  MX 15.36 was released  I upgraded  unit went into an end less reboot loop.      Red light….  Then rainbow lights   then solid  white   then flashing white.   And then reboots back to red                 If I disconnect all cables  and  reboot and ONLY plug in the LAN cable  I get the normal  Meraki local status page  with internet problem  (rainbow lights)                 If I then plug in the internet  the light goes solid white  and I get the Green tick connected to meraki on local status page                 The light then goes  flashing white..  ( 2-3 min)  and then reboots and goes red.                 I tried to get a diag log from the device when connected to cloud but the unit reboots before it completes.                 I rebooted  the device  with no internet   and can connect via the LAN  but the device still reboots even with no internet  and I am unable to get it to download local support data before a reboot.   I rang support and they could see it connecting but did not know what was happening  and RMA the unit   CASE 05593909.   Network was down  (and MX is the DHCP server) BUT I was prepared I had another MX64.   I removed the old MX from the network and  and cold swapped  and the new unit connected to the cloud  (it was running  MX15.34)    I then got the error  "Unable to fetch configuration"  contact support  {I have been getting this alot lately with various customers, very annoying}    Support worked their magic  CASE 05594042  and fixed this connection issue.      The unit then connected to the cloud loaded config  and then started working.   This was short lived as this unit then went into the reboot loop after about 10 minutes of working.   I went into the console and rolled back the firmware to  MX15.34    this did not help  still stuck in the reboot loop  support could see the device connecting to the cloud  and then it started to do a download.  they even blocked the download but still it did the download.   I factory reset both units and still they connected to the cloud  again with the   "Unable to fetch configuration"  contact support  support then fixed this again and again  they both went back into the reboot firmware down loop   Support tried to force a stable 14 version download  but this did not work either just kept rebooting.   I have the RMA device coming tomorrow but I am scared this unit is just going to have the same issue  (it might not now as the firmware has been downgraded  finger crossed)   It was a real pain as the network was down most of the day until I configured and OLD Cisco ASA to replace the meraki.   Any way  this is the reason I usually test firmware on my network before loading on customer network  but this got me worried.  I have so many customers on meraki now  if something like this happened to them I would not be very popular !!   Does any one have any idea what is going on here ????     ... View more

I reported this bug  on 10 Feb 2020  Case 04855962  it took a lot of wasted and un-chargable time to get this through the Meraki Support firewall with support insisting the MX64 was just following the RFC.  Eventually after 7 hours of my own lab work they agreed with me and sent to development.   Meraki even closed the case and re-open a new one 04955618  which no one can explain to me (was this the keep the KPI's looking good ?   Months and months later still getting nowhere and I am sure there are other having this issue to and do not even know it due to the client fall back doing a new broadcast after getting no renewal response from MX64   I have written up a very detailed explanation on my blog for others to understand. https://blog.cie.net.au/2020/05/dhcp-relay-issue-meraki-mx64.html   If other could please open cases if you suffer from this issue so meraki can get this fixed.   I did expect meraki to fix such a fundamental issue with DHCP quickly and other models may be effected to.  I have ONLY tested the MX64.     ... View more