Clarification on ModemManager Reconnection Behavior

Mon Aug 4 22:09:31 UTC 2025

On Fri, 2025-08-01 at 11:08 +0200, Armand Daussà wrote:
> You're right. I will try setting the value to 0 as discussed.
> 
> We are indeed able to reset the modem via GPIO. However, we may not
> be following the correct sequence. When we attempted a power cycle of
> the modem through GPIO, ModemManager detected an unexpected hangup.
> After that point, the modem was no longer recognized by the system.
> 
> Below are the logs captured immediately following the GPIO sequence:
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.826530] [modem0/ttyUSB0/qcdm] unexpected port hangup!
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.826649] [modem0/ttyUSB0/qcdm] forced to close port
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.826690] [modem0/ttyUSB0/qcdm] device open count is 0
> > (close)
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.826741] [modem0/ttyUSB0/qcdm] closing serial port...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.826853] [modem0/ttyUSB0/qcdm] serial port closed
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.829028] [modem0/ttyUSB2/at] unexpected port hangup!
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.829135] [modem0/ttyUSB2/at] forced to close port
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.829179] [modem0/ttyUSB2/at] device open count is 0
> > (close)
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.829253] [modem0/ttyUSB2/at] closing serial port...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.829381] [modem0/ttyUSB2/at] serial port closed
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.830744] [modem0/ttyUSB3/at] unexpected port hangup!
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.830842] [modem0/ttyUSB3/at] forced to close port
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.830881] [modem0/ttyUSB3/at] device open count is 0
> > (close)
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.830932] [modem0/ttyUSB3/at] closing serial port...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.831051] [modem0/ttyUSB3/at] serial port closed
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <info>
> >  [1752504056.842246] [base-manager] port ttyUSB0 released by device
> > '/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <info>
> >  [1752504056.845845] [base-manager] port ttyUSB1 released by device
> > '/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <info>
> >  [1752504056.852984] [base-manager] port ttyUSB2 released by device
> > '/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <info>
> >  [1752504056.855128] [base-manager] port ttyUSB3 released by device
> > '/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <info>
> >  [1752504056.867883] [base-manager] port ttyUSB4 released by device
> > '/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <info>
> >  [1752504056.878965] [base-manager] port wwan0 released by device
> > '/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: Cannot read from istream:
> > connection broken
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] QMI
> > endpoint hangup: removed
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <info>
> >  [1752504056.886650] [modem0] connection to qmi-proxy for /dev/cdc-
> > wdm0 lost, reprobing
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.887054] [modem0/bearer10] removing from bus
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.887137] [device
> > /sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4] unexported
> > modem from path '/org/freedesktop/ModemManager1/Modem/0'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.887197] [modem0/cdc-wdm0/qmi] Releasing client for
> > service 'wds'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] Releasing
> > 'wds' client with flags 'release-cid'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0]
> > Unregistered 'wds' client with ID '21'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > message...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > generic request (translated)...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.887566] [modem0/cdc-wdm0/qmi] Releasing client for
> > service 'wds'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] Releasing
> > 'wds' client with flags 'release-cid'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0]
> > Unregistered 'wds' client with ID '20'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > message...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > generic request (translated)...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.887814] [modem0/cdc-wdm0/qmi] Releasing client for
> > service 'voice'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] Releasing
> > 'voice' client with flags 'release-cid'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0]
> > Unregistered 'voice' client with ID '2'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > message...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > generic request (translated)...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.888064] [modem0/cdc-wdm0/qmi] Releasing client for
> > service 'pdc'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] Releasing
> > 'pdc' client with flags 'release-cid'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0]
> > Unregistered 'pdc' client with ID '1'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > message...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > generic request (translated)...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.888303] [modem0/cdc-wdm0/qmi] Releasing client for
> > service 'loc'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] Releasing
> > 'loc' client with flags 'release-cid'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0]
> > Unregistered 'loc' client with ID '1'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > message...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > generic request (translated)...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.888521] [modem0/cdc-wdm0/qmi] Releasing client for
> > service 'uim'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] Releasing
> > 'uim' client with flags 'release-cid'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0]
> > Unregistered 'uim' client with ID '1'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > message...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > generic request (translated)...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.888786] [modem0/cdc-wdm0/qmi] Releasing client for
> > service 'wms'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] Releasing
> > 'wms' client with flags 'release-cid'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0]
> > Unregistered 'wms' client with ID '1'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > message...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > generic request (translated)...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.889007] [modem0/cdc-wdm0/qmi] Releasing client for
> > service 'nas'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] Releasing
> > 'nas' client with flags 'release-cid'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0]
> > Unregistered 'nas' client with ID '2'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > message...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.889203] [modem0/cdc-wdm0/qmi] Releasing client for
> > service 'dms'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] Releasing
> > 'dms' client with flags 'release-cid'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0]
> > Unregistered 'dms' client with ID '1'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: [/dev/cdc-wdm0] sent
> > message...
> > [REMOVED]
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.890077] [modem0] cleaning up port 'usb/cdc-wdm0'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.890245] [modem0] cleaning up port 'tty/ttyUSB0'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.890286] [modem0] cleaning up port 'tty/ttyUSB2'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.890316] [modem0] cleaning up port 'net/wwan0'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.890343] [modem0] cleaning up port 'tty/ttyUSB4'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.890372] [modem0] cleaning up port 'tty/ttyUSB1'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.890399] [modem0] cleaning up port 'tty/ttyUSB3'...
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.890604] [modem0/ttyUSB4/audio] forced to close port
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.890782] [modem0/ttyUSB1/gps] forced to close port
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.891233] [modem0] completely disposed
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <info>
> >  [1752504056.891727] [base-manager] port cdc-wdm0 released by
> > device '/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4'
> > Jul 14 16:40:56 fonts2 ModemManager[498]: <debug>
> > [1752504056.891828] [base-manager] removing empty device
> > '/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.4' 
> > 
> 
> shut down here 
> > Jul 14 17:09:17 fonts2 ModemManager[498]: <info>
> >  [1752505757.887496] caught signal, shutting down...
> > Jul 14 17:09:17 fonts2 ModemManager[498]: <debug>
> > [1752505757.887656] [base-manager] stopping connection in object
> > manager server
> > Jul 14 17:09:17 fonts2 systemd[1]: Stopping Modem Manager...
> > Jul 14 17:09:17 fonts2 ModemManager[498]: <info>
> >  [1752505757.892868] ModemManager is shut down
> > Jul 14 17:09:17 fonts2 ModemManager[498]: <debug>
> > [1752505757.893227] [sleep-monitor] singleton disposed
> > Jul 14 17:09:17 fonts2 ModemManager[498]: <debug>
> > [1752505757.893357] [sleep-monitor] dropping systemd sleep
> > inhibitor
> > Jul 14 17:09:17 fonts2 ModemManager[498]: <debug>
> > [1752505757.894059] [auth-provider] singleton disposed
> > Jul 14 17:09:18 fonts2 systemd[1]: ModemManager.service: Succeeded.
> > Jul 14 17:09:18 fonts2 systemd[1]: Stopped Modem Manager.
> > 
> > Jul 14 17:09:18 fonts2 systemd[1]: ModemManager.service: Consumed
> > 1min 50.097s CPU time. 
> > 
> 
> 
> As shown, all interfaces (ttyUSB0-4, cdc-wdm0, wwan0, etc.) are
> released and the modem is removed from the system. However, despite
> waiting over 30 minutes, ModemManager does not attempt to probe or
> re-detect the device again. No additional logs are produced until
> ModemManager is manually stopped.

This is usually a kernel hotplug issue rather than a ModemManager one. 
> 
> Our next steps will include reviewing the modem's internal logs and
> carefully verifying the GPIO reset sequence. The current behavior
> suggests the modem is not properly re-enumerating on USB after power
> cycling, which may be a result of either the reset timing or an
> incomplete power cycle.

Yes, my thought too.

Just for testing, what happens if you "rmmod" and "modprobe" each of
the USB-related drivers that the modem's ports use? If that fails, are
you able to rmmod/modprobe the xhci controller modules?

That might be enough to re-initialize things, depending on how the
modem is connected to the main CPU in your system.

Dan

> 
> Thanks again for your support! 
> 
> On Thu, Jul 31, 2025 at 2:23 PM Dan Williams <dan at ioncontrol.co>
> wrote:
> > 
> > 
> > > On Jul 28, 2025, at 3:26 AM, Armand Daussà
> > > <adaussa at cactusiot.com> wrote:
> > > 
> > > Hi Dan,
> > > 
> > > Thank you for your reply!
> > > 
> > > In our case, NetworkManager is the service responsible for
> > > managing the connections. I’ve checked the configuration of the
> > > cellular_connection, which is the entry in NetworkManager for our
> > > WWAN interface. Here are the relevant details:
> > > 
> > > connection.id:                          cellular_connection  
> > > connection.uuid:                        dea368fe-e05d-4dad-b8bf-
> > > 37e67e47fe56  
> > > connection.type:                        gsm  
> > > connection.autoconnect:                 yes  
> > > connection.autoconnect-retries:         -1 (default)  
> > > connection.auth-retries:                -1  
> > > ... (rest omitted for brevity)
> > > 
> > > My understanding is that the values connection.autoconnect-
> > > retries: -1 and connection.auth-retries: -1 should allow for
> > > infinite reconnection attempts. Is there any additional
> > > configuration we might be missing to ensure that reconnections
> > > always occur after transient modem or network issues?
> > 
> > Looking at the nm-settings manpage I see two things. First it says
> > auth-retries is only for 802.1x so that probably doesn’t matter
> > here. But second it says that -1 uses the global default number of
> > retries of 4 which is probably pretty low for you. 0 is supposed to
> > be “forever”; can you try that value instead of -1?
> > 
> > > 
> > > Regarding the modem disconnection messages: we have observed
> > > multiple devices experiencing disconnects. However, the
> > > <CR><LF>+SIMCARD: NOT AVAILABLE<CR><LF> message appears only on
> > > the device included in the logs I shared.
> > > 
> > > Other devices report different verbose call end reasons such as:
> > >      • [internal] ip-version-mismatch
> > >      • [cm] no-service
> > >      • [internal] mmgdsi-card-event (also on the same device with
> > > the SIMCARD error)
> > >      • [cm] emm-detached
> > >      • [internal] pdn-ipv6-call-disallowed
> > >      • [cm] emm-t3417-expired
> > >      • [cm] detach-with-reattach-lte-nw-detach
> > 
> > The ip-version-mismatch and pdn-ipv6-call-disallowed ones may
> > indicate that the APN you’re using isn’t configured for IPv6, but
> > MM is requesting either V6 or V4V6 activation. That can be changed
> > in the NM settings.
> > 
> > > 
> > > From your perspective, do these messages generally point toward
> > > modem hardware issues or even physical/network instability,
> > > rather than issues with ModemManager itself?
> > 
> > The SIM card errors may point to either a bad SIM or bad SIM slot
> > on that specific modem. The two IP-related ones may be
> > configuration, and the rest look like fairly normal causes that a
> > reconnect should eventually be able to recover from. Note that
> > networks sometimes have backoff timers to prevent reconnect
> > spamming; not sure if that is the case for yours.
> > 
> > > 
> > > Lastly, the modem does not support hot swap, so unfortunately we
> > > cannot reinsert the SIM card once removed.
> > 
> > Are you able to power cycle the modem via GPIO or some other
> > method? I’ve had cases where it would be helpful to do that based
> > on a couple factors, like whether the modem hasn’t been registered
> > in a given amount of time even though you know there should be an
> > available network.
> > 
> > Dan
> > 
> > > 
> > > Thanks again for your help!
> > > 
> > > On Sat, Jul 26, 2025 at 5:29 AM Dan Williams <dan at ioncontrol.co>
> > > wrote:
> > > On Wed, 2025-07-16 at 17:35 +0200, Armand Daussà wrote:
> > > > Hi,
> > > > 
> > > > We’ve encountered an issue with modem disconnections and have
> > > > reviewed the ModemManager logs to better understand the
> > > > behavior.
> > > > What we observed is that after a disconnection, ModemManager
> > > > attempts
> > > > to reconnect but then shuts down and does not attempt to
> > > > reconnect
> > > > again. It only resumes connection attempts after the operating
> > > > system
> > > > is rebooted.
> > > > 
> > > > In situations where the modem experiences issues and cannot
> > > > establish
> > > > a connection, ModemManager appears to stop trying entirely
> > > > until the
> > > > next system reboot. Eventually, after a reboot, ModemManager is
> > > > able
> > > > to successfully initialize the modem and re-establish a
> > > > connection.
> > > > 
> > > > Could you please confirm if this is the expected behavior? If
> > > > not, is
> > > > there a recommended way to ensure that ModemManager continues
> > > > trying
> > > > to reconnect without requiring a system reboot?
> > > 
> > > ModemManager itself does not actually start/stop the data
> > > connection.
> > > 
> > > That's typically done by a connection manager, like
> > > NetworkManager,
> > > distro network scripts, or custom scripting.
> > > 
> > > In the NetworkManager case, it will stop asking MM to reconnect
> > > after a
> > > configurable number of failures. It will then start a timer and
> > > when
> > > the timer expires, retry until the configurable number of
> > > failures.
> > > Repeat.
> > > 
> > > Do you know what connection manager you're using to drive
> > > ModemManager?
> > > If we can figure that out we can nail down the reconnect
> > > behavior.
> > > 
> > > > 
> > > > Is it something fixed in more recent releases?
> > > > 
> > > > Key timestamps:
> > > > 16:37:24 -> Modem sends '<CR><LF>+SIMCARD: NOT
> > > > AVAILABLE<CR><LF>'
> > > > Five OS Reboots are performed
> > > > 19:19:21 -> Modem manager starts following last reboot and a
> > > > successful initialization is completed
> > > > 
> > > > Logs are attached.
> > > 
> > > I do notice:
> > > 
> > > Jul 14 16:37:24 fonts2 ModemManager[498]: <info> 
> > > [1752503844.286189]
> > > [modem0/bearer1] bearer call end reason (1): 'generic-
> > > unspecified'
> > > Jul 14 16:37:24 fonts2 ModemManager[498]: <info> 
> > > [1752503844.286265]
> > > [modem0/bearer1] bearer verbose call end reason (2,218):
> > > [internal]
> > > mmgdsi-card-event
> > > 
> > > The call here gets terminated by mmgdsi-card-event which I think
> > > is
> > > *actually* GSDI = Generic Sim Driver Interface card event. Which
> > > correlates to the +SIMCARD message and indicates that the SIM
> > > card or
> > > the modem's SIM interface decided to hiccup and that terminated
> > > the
> > > call.
> > > 
> > > I'm not surprised things are broken until a reboot, but if this
> > > is a
> > > physical SIM card you might try removing and re-inserting the SIM
> > > and
> > > see if that makes things work more quickly.
> > > 
> > > In any case, if you're able to determine what connection manager
> > > you
> > > use, then we can figure out the reconnect behavior.
> > > 
> > > Dan
> > > 
> > > 
> > > 
> > > > 
> > > > Thanks in advance!
> > > > 
> > > > System info:
> > > > OS: 
> > > > Linux fonts1 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16
> > > > BST
> > > > 2023 aarch64
> > > > > PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
> > > > > 
> > > > 
> > > >   
> > > > Hardware 
> > > > > manufacturer: QUALCOMM INCORPORATED
> > > > > model: 0 (doesn't show but its a SIMCOM S2-107EQ)
> > > > > firmware revision: LE11B12SIM7600M22
> > > > > carrier config: ROW_Gen_NonVoLTE
> > > > > carrier config revision: 05010813 
> > > > > 
> > > > > h/w revision: 10000
> > > > > supported: gsm-umts, lte
> > > > > current: gsm-umts, lte 
> > > > > 
> > > > 
> > > > 
> > > > ModemManager version
> > > > 1.14.12
> > > 
> > > 
> > > 
> > > -- 
> > > Armand Daussà
> > > RD
> > > +34 644 552 758
> > > linkedin.com/company/cactusiot
> > > cactusiot.com
> > > Sant Joan de la Salle 42, 08022 Barcelona
> > > Aquest missatge de correu electrònic i els seus documents adjunts
> > > estan dirigits EXCLUSIVAMENT als destinataris especificats. La
> > > informació continguda pot ser CONFIDENCIAL i/o estar LEGALMENT
> > > PROTEGIDA i no necessàriament reflecteix l'opinió de Cactus
> > > Engineering S.L. Si vostè rep aquest missatge per ERROR, si us
> > > plau comunicar-ho immediatament al remitent i ELIMINI'L, ja que
> > > vostè NO ESTÀ AUTORITZAT al seu ús, revelació, distribució,
> > > impressió o còpia de tota o alguna part de la informació
> > > continguda. Gràcies.
> > > 
> > > Este mensaje de correo electrónico y sus documentos adjuntos
> > > están dirigidos EXCLUSIVAMENTE a los destinatarios especificados.
> > > La información contenida puede ser CONFIDENCIAL y/o estar
> > > LEGALMENTE PROTEGIDA y no necesariamente refleja la opinión de
> > > Cactus Engineering S.L. Si usted recibe este mensaje por ERROR,
> > > por favor comuníqueselo inmediatamente al remitente y ELIMÍNELO
> > > ya que usted NO ESTÁ AUTORIZADO al uso, revelación, distribución,
> > > impresión o copia de toda o alguna parte de la información
> > > contenida. Gracias.
> > > 
> > > This message and any attached documents are intended ONLY for the
> > > use of the individual or entity to which they are addressed. It
> > > may contain CONFIDENTIAL and/or LEGALLY PRIVILEGED information
> > > and may not necessarily represent the opinion of Cactus
> > > Engineering S.L. If you have received this email in error, please
> > > notify the sender immediately and DELETE it, as you ARE NOT
> > > AUTHORISED to use, disclose, distribute, print, or copy all or
> > > any part of the contained information. Thank you.
> > 