SMS Control does not work when sent from shortcodes (with allow-list)

General
1

When configuring SMS control, we are using our carrier’s Control Center platform to send the SMS messages as they do not allow external SMS. However, these messages send from a shortcode (four digits), and are not e.164 numbers. These messages are rejected by the Peplink device as they are not the number in the web admin allow list, which requires one to put a + in the string.

I have submitted a ticket (25070676), but wanted to highlight this as many people use IoT through various platforms and carriers that use shortcodes to send network messages (understanding USSDs) origination from the network back to the UE.

In short, anyone using SIMs from a carrier/platform that limit outside SMS but allow platform-generated SMS (i.e., through a portal) won’t work unless the origination number of that SMS is e.164 compliant, or you are not using the allow-list on the device.

1 Like
2

I disabled the white list for it to work from my provider , I asked about this before as verizon thing space sends also from a non E.164 number.

3

yeah, it’s easy to disable, but our client is gov and doesn’t want to remove a security feature because of a simple web validation issue.

2 Likes
4

Agreed, it’s more a work around for discussion, but I agree we should be allow NON E.164 entries.
@Eddy_Yeung can we get this added?

2 Likes
5

@ChristopherSpitler I believe we have already prepared a special build via support ticket to you and let’s see whether that help to maintain the security feature yet allow the shortcodes.

1 Like
6

Please share with us for testing as well.