Jump to content

Not receiving SMS - since upgrade to 68.0.30?


mcbsys

Recommended Posts

Customer just noticed that they are not receiving SMS, probably since the upgrade to 68.0.30 last week. 

Trying to deliver the SMS directly to an extension, which has ANI for SMS set to the customer's main number "(858) 333-4444" (number changed). Here's the log:

[9] 12:39:25.412	Tried to match recvsmsⓘ
[8] 12:39:25.412	Receive SMSⓘ
{"sms_id": "be70e0b4-7482-41e5-a9f6-6d53ea1835b1", "direction": "inbound", "from": "+16191112222", "to": "+18583334444", "body": "Another test"}
[8] 12:39:25.412	SMS not enabled by default (setting=, default=true)ⓘ
[7] 12:39:25.412	Closing connection smtp.google.com:465ⓘ
[9] 12:39:26.065	Message repetition, packet droppedⓘ
[7] 12:39:26.065	Closing connection smtp.google.com:465ⓘ
[9] 12:39:29.243	Last message repeated 2 timesⓘ
[8] 12:39:29.243	Packet authenticated by transport layerⓘ
[7] 12:39:30.071	Last message repeated 3 timesⓘ
[9] 12:39:30.071	Message repetition, packet droppedⓘ
[9] 12:39:30.300	Service flag 700: Use schedule 10:00-14:00ⓘ
[9] 12:39:30.300	Service flag 700: Schedule 10:00-14:00 is set because 10:00 <= 12:39:30 <= 14:00ⓘ
[8] 12:39:30.300	Service flag 700: Return positive trueⓘ

Shouldn't it show SMS delivered? And what does the Service Flag schedule have to do with it?

Also: the constant SMTP exchange with Google is very distracting when trying to read the logs. On one log page, "smtp.google.com" occurs 149 times even though not a single email is sent. Why?

Link to comment
Share on other sites

The "SMS not enabled by default" is most likely the problem here. There was some confusion when SMS is enabled for the tenant between the versions. The log message suggest that is should be enabled looking at the settings, but, well, it does not seem to be enabled. Does it work if you enable it in the domain? We will make another 68 build where this should be working as one would expect.

Link to comment
Share on other sites

"Some confusion" about SMS configuration is an understatement!

7 hours ago, Vodia PBX said:

Does it work if you enable it in the domain?

The message makes it sound like it's not set, so it will use the default of "true". Under Domain > Settings > Messaging > Notifications, I've got all the settings configured:

20230721.DomainSMSsettings.png.6cfa2c7337cc555af9cdce5f5ec2e5ff.png

The tenant is set to use the Default, so that should inherit from the domain, right? But then, what is the different between Default and Set up in domain?

20230721.TenantSMSsettings.png.5b55438833ce58afedf49e8954fe7793.png

I tried On and Set up in domain for the tenant. Got a "Status change on trunk Telnyx" email on each change, but never got an SMS. The log message always says it's not enabled by default:

----> Tenant SMS set to "On"
[9] 9:54:19.108	Tried to match recvsmsⓘ
[8] 9:54:19.108	Receive SMSⓘ
{"sms_id": "4ad14425-9033-4c26-8299-d50fd0cb279b", "direction": "inbound", "from": "+16191112222", "to": "+18583334444", "body": "SMS test 7"}
[8] 9:54:19.108	SMS not enabled by default (setting=, default=true)ⓘ

----> Tenant SMS set to "Set up in domain"
[9] 9:56:21.463	Tried to match recvsmsⓘ
[8] 9:56:21.463	Receive SMSⓘ
{"sms_id": "e3b236d4-c58b-4c77-82f9-7687396e5ad2", "direction": "inbound", "from": "+16191112222", "to": "+18583334444", "body": "SMS test 8"}
[8] 9:56:21.463	SMS not enabled by default (setting=, default=true)ⓘ

 

 

Link to comment
Share on other sites

29 minutes ago, mcbsys said:

I prefer not to run beta software especially on customer systems. Is there a way to subscribe to notifications for software releases?

Of course. Maybe you have a test system somewhere. Anyway, the plan is to release 68.0.32 on Tuesday or Wednesday next week.

Link to comment
Share on other sites

Reloaded a new install and did exactly the same thing.  Migrate from:

Software version 69.0.6 (Debian64)
Build date Jul 22 2023 05:08:39

To:
Version: 68.0.31.beta Debian64
Date: Jul 24 2023

 

.dat looks updated at the time I installed the beta..

 

No account can login.  The browser does nothing, no error.  The Windows App says incorrect login for extensions..

 

I can reinstall via CLI to 69.0.6 and migrate to 68.0.30 with no issue.  I can then update to 68.0.31.beta ok.  I then upgraded to 69.0.6 and tried again and it worked ... go figure?

Software version68.0.31.beta (Debian64)
Build dateJul 24 2023 15:55:53

Link to comment
Share on other sites

Hmm so you can move from 69.0.6 to 68.0.30, but not from 69.0.6 to 68.0.31.beta? Maybe you can double check that the upgrades went through with the --version option from command line and also make sure that the .dat files match. As for the login, please make sure that the browser cache is not playing tricks on us, especially if the welcome.htm page was modified. 

Link to comment
Share on other sites

  • 2 weeks later...
On 7/23/2023 at 3:05 PM, Vodia PBX said:

Anyway, the plan is to release 68.0.32 on Tuesday or Wednesday next week.

It's been several weeks now with SMS broken. What is the status of getting that fixed? Or is there some way to get it working with 68.0.30?

Link to comment
Share on other sites

Thank you. I was able to receive an SMS, but when I replied from the Vodia app, the SMS did not go out.

Did something change with logging? System Level > Status > Logfile is completely blank even though it is set up to keep 1000 events and all at level 9.

Link to comment
Share on other sites

17 minutes ago, mcbsys said:

Did something change with logging? System Level > Status > Logfile is completely blank even though it is set up to keep 1000 events and all at level 9.

Not aware of changes. Maybe the logging timed out? Try to set it e.g. to 24 hours (different from what it was before). There should be something in the log, SMS or not.

Link to comment
Share on other sites

Yes, the log had timed out. I was thinking "1 hour" meant only keep the last hour... Just had to click Save to re-activate it.

When sending SMS, I get "SMS provider unavailable", even after resetting the "Application secret" with the Telnyx API v1 Profile Secret.

Messaging settings:

20230809.Messagingsettings.png.6ebf291f35e3007d545cd6b697c3bcde.png

Link to comment
Share on other sites

1 hour ago, mcbsys said:

When sending SMS, I get "SMS provider unavailable", even after resetting the "Application secret" with the Telnyx API v1 Profile Secret.

Can you check the settings in reg_domains.htm for the domain for SMS? There must be something that makes the system believe it's a different provider.

Link to comment
Share on other sites

You mean this?

I had "Enable text messaging" set to "Set up in domain" (see my July 21 post above):

20230809.SMSsetupindomain.png.88a3a611abe0f32977bf2e439115768b.png

but had not done further setup under Domain > Settings > General Settings > SMS Settings:

20230809.SMSdomainsettings.png.3f89682c4cdb6b870ea736ded9490e71.png

In fact, I didn't even know that section exists inside the tenant--I just found it today by poking around. I don't think I've seen it in any docs, and the whole section disappears when you set Enable text messaging to On (which really means "Inherit from System"):

20230809.SMSOn.png.173f96e7d6335fb0ad4fa154cec6e69a.png

I wonder what "Default" does and how it is different from "On" or "Off".

Anyway with "Enable text messaging" set to On, I can send SMS from the tenant.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...