Error initializing MMSC Route '***'. MM4 - timeout during message t...

Error initializing MMSC Route '***'. MM4 - timeout during message t... SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Error initializing MMSC Route '***'. MM4 - timeout during message transmission « Previous || Next »
Author Message
svaore
New member
Username: Svaore

Post Number: 5
Registered: 03-2011
Posted on Monday, February 10, 2020 - 11:25 pm:   

Hello, we have since 23h52 had errors in Windows event logs of the nowsms type, with the following message "Error initializing MMSC Route '***'. MM4 - timeout during message transmission".

After each error I have the MMSC Route '***' information successfully initiated. Error condition resolved.

I attach the MMSC log file

Can you help us please?

application/octet-streamlog
MMSC-20200211.LOG (388.1 k)
svaore
New member
Username: Svaore

Post Number: 6
Registered: 03-2011
Posted on Tuesday, February 11, 2020 - 04:41 am:   

hello, thank you for ignoring my previous message. We have a problem with the connection of another operator.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 6091
Registered: 08-2008
Posted on Tuesday, February 11, 2020 - 08:30 am:   


quote:

hello, thank you for ignoring my previous message.




Hello. You are most welcome.

I can find no record of your having a 24x7 support agreement with us, but perhaps I am mistaken.

There appears to be a problem transmitting a particular message. The MM4 partner appears to be unexpectedly dropping the connection on each attempt. Eventually the retry attempts will be exhausted and the message delivery will fail. Meanwhile, other messages continue to process with no problems, and retries of this message are throttled so it does not create a backlog.

Unfortunately it’s a bit of a guessing game as the partner does not appear to be providing an error code or reason.

But, here is what I notice...

A number ending in 8170 has sent an MMS to at least 40 recipients that are routed via this partner connection. I suspect the partner is not willing (or not prepared to) accept a message addressed to so many recipients.

Or, another possibility is that the partner system does not like that NowSMS splits multiple recipients into separate message instances. See problem report similar to yours here: https://support.nowsms.com/discus/messages/485/70331.html

What to do?

The queued message can be found under the VASPQ directory. There will be an MMS and INI file. Please locate and email these files to nowsmstech@nowsms.com with Attention: Des in the subject line.

Check the configuration file VASPOUT/SRR/VASP.INI. Is there a MaxRecips=## setting under the [VASP] header?

Adjusting a MaxRecips=## setting in this file is likely the key to preventing future problems. But it may not resolve a problem with an already queued message.

Ask the partner if they have any guidance on limiting the number of recipients.

If you currently have a MaxRecips=40 setting, try a lower value.

If there is no setting, try a larger value such as MaxRecips=1000. But note that this may not resolve an issue with an already queued message. Changing the MessageID in the message’s INI file might allow the message to be accepted in this case.


Des
NowSMS Support

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics