| MMS Messages in Outbound Queue with no details |  Search
|
|
NowSMS Support Forums ⬆ NowSMS NextGen Support ⬆ |
◄ ► |
| Author | Message | |||
| Rohan Power New member Username: Rohp Post Number: 1 Registered: 01-2023 |
Hi Support, We have quite a number of MMS messages sitting in the Outbound Queue with no details (no TO or FROM). We're unsure what they are because the actual MMS message appears to be delivered (to our external HTTP endpoint). Is there any way to look into these messages further to understand what they are and why they're there? Thanks .  | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8502 Registered: 10-2002 |
Hi, I see from another post that you are using a database connection. Unfortunately, there is not yet a quick way to understand what these message are when using a database connection. How many of these messages are in the queue? Is the number of messages growing? There should also be a column to the right with a date/time for the message. Are these messages from a particular time period? What is the NowSMS version? Do you have multiple front-end servers? You mention an external HTTP endpoint, is this defined as an "MM7 connection", and if so, is "Max Connections" set to a value higher than 1? Regards, Bryce Norwood NowSMS Support | |||
| Rohan Power New member Username: Rohp Post Number: 3 Registered: 01-2023 |
Hi Bryce, Thanks for getting back to me. Yesterday the number was up around the 500+ mark, but we're clearing out the queue on a daily basis at the moment, so it's back down around 100 at the moment. No particular time period, but it just seems as though when a MMS comes in, it's being delivered to our HTTP endpoint, but then its dropped into the queue. This is speculation however because I can't see any details about the messages. We're running the latest release, 2023.10.20, with only one front-end server but it is sitting behind a load balancer. The HTTP endpoint is configured as a MM7 endpoint, set as 10 max connections. It was set to 1 but we upped it to 10 recently, but haven't seen any change. We've configured our inbound MMSC connections to forward MMS's via the "Force via Route" setting. Thanks. | |||
| Rohan Power New member Username: Rohp Post Number: 4 Registered: 01-2023 |
Hi Bryce, Following up on this thread. I can't see if I've replied to you because there doesn't seem to be a way in the forum to tell, but I'm quite sure I've replied. Thanks. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8505 Registered: 10-2002 |
Hi Rohan, I'm probably going to need to get a debug log from your system to understand. But before we take this step, we have recently been troubleshooting a similar problem at another customer installation, where delivery reports were getting stuck in the queue. So, I would like to have you try an update first. The crux of the problem is that when an MM7 client submits a message, NowSMS remembers the inbound connection's route name. When a delivery report is received, NowSMS looks at the message-id and will try to route the delivery report to this same route name. If there is not an outbound connection with this route name, the delivery report gets stuck in the queue. We have resolved this issue and addressed some other performance issues related to the processing of this queue when using database mode. So, I would like to ask you to update first to the latest version in the beta channel (see instructions here: https://support.nowsms.com/discus/messages/113328/114192.html). Delete the blank messages from the outbound queue. Enable the SMSDEBUG.LOG by adding Debug=Yes under the [SMSGW] header in SMSGW.INI. Should blank messages reappear, send the SMSDEBUG.LOG to nowsmsech@nowsms.com. It would also help if you could download and include a CSV file of recent message log activity, so that we can better understand the message flow on your system. Regards, Bryce Norwood NowSMS Support | |||
