sending msg to own IR does not work any more?

skyeye said:

BTW: loop back messages do not stay in any kind of Garmin Ecosystem

My point is the Garmin/Iridium server loop.

Only when a message is received outside this environment, by the end recipient, I consider outgoing test complete.

I am unclear as to the symptoms. You are sending from an iR device with iR address  <me>@inreach.garmin.com TO that same iR address (<me>@inreach.garmin.com). You are doing this interactively from the device (no apps, no use of explore.garmin.com, no anything except the device). Is that correct? 

When you say, "does not work anymore", what does that mean? The sending device shows some error message when composing or sending the message? The sending device appears to send the message, but the message is never received? Something else?

Does the message show up in the Inbox at explore.garmin.com? 

This is an enterprise account, correct? There are not very many people who are going to be able to test that.

skyeye You are able to still send a message to your own inReach address. However, it would still need to be from either your own inReach device or another inReach device. It cannot originate from an SMS phone number or e-mail address. 

If it is not working as of late I would recommend syncing your device and testing it again Syncing an inReach Explorer/+, SE/+, or inReach Mini for Professional Users. 

I am not sure exactly what device you have but I would also recommend checking the tone settings on the device as well. 

all negative

as from October 1st, none of devices I was able to test and access can do a loop test

While communication between IR devices works fine as well as communication to other parties, loop test, meaning sending a message to own [me]@inreach.garmin.com can not be done any more. The message can be sent, but it will never arrive back at the device it was sent from.

Sync or other measures have no impact, this is first thing I did test for sure.

I did test on devices in our enterprise account, on other professional account and on 3 personal accounts. All have the same problem. The prof.account and the personal accounts have current price plan, the enterprise has an byte charged account.

Devices involved, number of delorme explorer (they have no own test included) , few Mini(1) and few 66i

Particularly for the fleet of our enterpeise account, this is very troublesome

btw: I have sent report on it to professional.support already, no feedback yet

1. yes

sending from device with [email protected] to [email protected] on the device, no phone etc involved

2.

the message is snet and it appers also as sent and is stored as such, but it never arrives on the device back as it did until end of September

3.

yes it is in the inbox on the explore website

4.

yes it is enterprise acc, but the same happends with all other accounts I had acces to in this weekend

I think you're going to have to wait for Garmin to process the support ticket. Since it also fails on a personal account with newer devices, you might also want to open a support ticket for the personal side. See which support organization gets to it first

skyeye said:

The test procedure is meant to test the devices ability to send and receive messages and demonstrate it clearly to the user. This is done each time the device is switched on for use.

I'm ex-military and we test comms based on how they are expected to behave operationally.

Assuming you are not only having dialogue with other inReach devices, your current procedure does not deliver a system test result for outgoing messages. My example does.

Under what circumstances do you need to have a routine that does an Iridium test every time the device is turned on?

Disclaimer: I have no idea how inReach Enterprise accounts or Inboxes work. 

Under what circumstances do you need to have a routine that does an Iridium test every time the device is turned on?

standard procedure for years as recommended by manufacturer

on some devices this is even appearing on the display while booting. This can be the build in test which is not very meaningful for most users, or for example a loop test on devices which works also on devices which have no build in test feature

as procedures to communicate with what you say outside of Garmin can not be accomplished, the given procedure has to do it

if you mean test can be done only with 3rd parties communication, then sure, also the build in test is useless. Where build in test is av it is OK, but users have problems in interpreting the result. And when there is more then one model ina fleet, common procedure is needed.

For procedure to leave Garmin and come back would mean to operate an extra answering server to replay inreach originated messages.

We have something like that for voice communication over iridium, thuzraya and inmarsat satphones. To build such thing for trackers as well is slight overkill as authentication for inreach answers is rather complex compared to voice parot.

skyeye said:

if you mean test can be done only with 3rd parties communication, then sure, also the build in test is useless.

Well, it tests that the device is working, has an active subscription, and is able to send/receive messages, including position, via the Iridium satellite network. Those are the major points of failure covered.

But in no way showing complete message functionality.