You are looking at the wrong endpoint 😃   It's under organization: https://developer.cisco.com/meraki/api-v1/#!create-organization-network ... View more

Wow I've almost missed this post! I've just activated it on my lab and it's working like a charm =D ... View more

@CarolineS  =D ... View more

Thats actually a bug in the meraki python library. You can get it fixed by downloading the current source from github or just wait until the next library version will get released. ... View more

Do I get any special treatment as I'm alone in Tier 2? I feel so lonely =( ... View more

I think I found the problem now. (re read your status messages)   You have a timeout with the cucm hostnames. There should be two options two fix this. Either set the dns search domain on the DNS server or specify the FQDN on the CUCM Nodes (CUCM Admin: System -> Server) See https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/211393-Change-CUCM-Server-Definition-from-IP-Ad.html for further details.   I would go for the second option. Since version 10.X it's the prefered way to use the FQDN for the servers as it is required for jabber, SSO, ... ... View more

I would check the different firewalls (don't forget the firewall on the dns server itself, if there is one), if there is really nothing blocking. You can also try to traceroute from the DNS server to the ip phone. Maybe you are missing a route somewhere in the setup ... View more

that's the issue with point 2, as soon as this is merged and released it should work fine with the new meraki library. The errors won't go away (in fact they will get printed in the cli), but the script itself should ignore them and continue with the other organizations.   ... View more

actually there are 2 problems with the disabled api.   1) the script didn't handle it correctly. I've fixed that now in the repo 2) the meraki library mistreated the disabled api as a "missing api key" response from the cloud and created an additional exception while creating the Async/APIError object. I've created a PR for this. We just have to wait until it gets merged and published. ... View more

the -o Parameter has to match the organization name exactly for the script to work.   you can ignore the 429 warning. The script will create many api call depending on the size of your organization. You just have to be patient for the script to finish.   about the exception you are getting at the end: You can ignore them for now. What I've found is that there is an error in one of the dependend libraries. ... View more

a reboot of the MX shouldn't be needed. I have an MX68W in my home office and I'm using a non meraki site2site VPN without any problems. My hardphone gets registered without any issues. The CUCM is probably configured via FQDN. What are the DNS settings of the subnet? Do they point to the correct DNS servers to resolve the FQDN?   I would check the status messages on the ip phone (Settings -> Admin Settings -> Status -> Status messages) You should see the issue there. It could also be some kind of trust list issue, if the phones were registered on a different cucm in the past. ... View more

please try python id_finder.py -o "API Demo" - Meraki -p.* -s ondcb ... View more

CCIE Collaboration here. as @Bruce & @DarrenOC already mentioned. The TFTP has to be set to the CUCM servers which are having the tftp service enabled. The quickiest way would be to check the configuration of a working phone.   The only reason to set it to the VoiceGW is, when you are running a callmanger express (NOT SRST) there.   Please also check your firewall settings. The tftp protocol is not really used anymore. The phones will get the correct servers via DHCP option 150 and then they will download the configuration & firmware files over HTTP/S over the Ports 6970/6972. If these are blocked, then the phones won't be able to download the correct settings ... View more

The PR is already merged. It is not yet in a released version, but you can use it on the  v1 api directly from github.   In the creation of the Async/DashboardAPI object you have to specify the parameter 'use_iterator_for_get_pages = True' examples: https://github.com/meraki/dashboard-api-python/blob/master/examples/get_pages_iterator.py & https://github.com/meraki/dashboard-api-python/blob/master/examples/aio_get_pages_iterator.py ... View more

The smartphone UV sanitiser (I saw it somewhere in a post a while back) ... View more

I think a better option would be to get an NVR on site which supports RTSP. The cameras will stream their image locally to the NVR which saves the video on disk. That way you won't have to worry about internet bandwith or even outages and you have a backup of the video just in case if the camera gets damaged. ... View more

Let the Point Hunt BEGIN! ... View more

Sadly this is still missing =( ... View more

Thank you very much 😃 ... View more

Just for Information: Pull Request is out ... View more

I'm struggling with the same issue. For the moment I can just say please be patient. I'm preparing a pull request for this, so that the methods will return an interator instead of the whole list/dict. This should be better for speed and ram usage.   I hope I can finish this one this week. So if everything goes right, then it probably could be merged into the library. ... View more

Hello,   you can call getNetworkMerakiAuthUsers for that. Just compare the email address of the users to get the correct id. ... View more

@jetaylorwhat kind of cameras are you using? The 2nd generation (MVx2) are supporting low-latency HLS (LHLS) with firmware 4.8 or higher. The delay here is normally about 2 seconds instead of 10. ... View more

I would enable RTSP on the cameras. Normally the agents support direct rtsp. ... View more