Hello -- as a general rule, I've always felt that DAIP gateways "need more tools" to insure their reliable operation.
As it stands, if your remote device frequently changes WAN IP, the DAIP function is as frustrating at minimum -- and kraco and "throw it out the window" at worst.
I have various 1500 devices configured as DAIP objects and they are frequently moved around depending on their use. They are used for ELECTIONS and necessarily placed behind home office consumer routers when in operation. The DAIP mechanism is not reliable and source on constant frustration, poking, and prodding.
The customer wants to throw thirty-odd 1500-series boxes in trash and buy Cradlepoint because they know that works (and it does).
To make matters worse, add Smart1-Cloud to the mix (managment-as-a-service) and you get the distinct impression that no-one in R&D and product mgmt has ever tested this combination of mechanisms in any way-shape-or-form.
It's basically unusable. DAIP doesn't update in predictable manner and MaaS tunnel never recovers in predictable way. Neither have good command-line resources to change/debug/poke/configure their behavior.
In our case, device is configured at central location and then placed in new location. the placement is done by non-technical person and it's ridiculous to expect high-tech command-line person to be at Church in rural America because the MaaS+DAIP combination is not fully vetted and tested by vendor.
CP sales will tell everyone it works all day long. CP TAC will get engaged and get SME on line (after various escalations). Ultimately, we get to point where it's obvious that operational requirements are indeed different for what is being QA'ed.
Thus, the development and functional requirements using by CP R&D are different what what we need and expect. However, we never get to point where someone states "that will never work", but we never get solid and reliable solution where it DOES work.
Per comments in original post, the addition of some very basic config options and real-time tools could solve 80% of the problem. Tools and Logic on gateway to help insure MaaS tunnel resumes. Tools and config options to help DAIP be more a) predictable, and (b) reliable when updating SMS service.
The fact these small tools and tweaks not available reflects simply how often QA and R&D actually using and testing these boxes (ie. not much).