| MM4 - timeout during message transmission |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
| Author | Message | ||||
| Andy Rank New member Username: Arank Post Number: 9 Registered: 05-2010 |
Hello, Sorry if you have already covered this in a different thread but I was unable to find anything. We seem to get this alert several times a week (Error initializing MMSC Route 'Syniverse'. MM4 - timeout during message transmission). We will get the alert email and within about 5-10 seconds we will receive the cleared alert (MMSC Route 'Syniverse' successfully initiaized. Error condition resolved.) Could you tell me what causes this error and also is there any way of increasing the "timeout" so that we don't get these messages unless there is really an issue? Thank you, Andy | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3314 Registered: 08-2008 |
Hi Andy, That is a strange one. The timeout in question is 2 minutes, which is over-generous. And it takes 10 consecutive transmission failures to trigger an alert. So it does concern me a little. The timeout message is also generated if the other end aborts the connection. My best guess is that either the other server is overloaded, or maybe some users are submitting messages larger than this provider will accept, and instead of returning an error, they are aborting the connection. I'd like to see the MMSC-yyyymmdd.LOG to inspect for MMSOUT records that indicate a failure, and look for a pattern. -bn | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7966 Registered: 10-2002 |
I'm not sure why Des' credentials are stuck on the tablet I am using. This is a test to fix credentials. | ||||
| Andy Rank New member Username: Arank Post Number: 10 Registered: 05-2010 |
Hi Bryce, Thank you for the explanation. I have attached the log file from yesterday. We received the MM4 alerts at 15:17 & 15:19 and they both cleared within about 10 seconds (according to the email alert). It looks like it was happening with one specific user sending multiple messages at one time. Thank you, Andy
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7976 Registered: 10-2002 |
Hi Andy, I guess I need to know the time of the alerts to put the pieces together. The failed messages that I have seen mostly appear to be messages addressed to invalid phone numbers. Have you identified which ones seem to trigger the alert situation? -bn | ||||
| Andy Rank New member Username: Arank Post Number: 11 Registered: 05-2010 |
Hi Bryce, The time of the alerts are what I had posted above. We received the alert emails at 3:17PM & 3:19PM CST. I checked the log and this is what i see during that time. 2011-06-28 15:15:26,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+19203628214,Retry Pending - Unable to deliver message,7F81D397.MMS 2011-06-28 15:15:26,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+19203716919,Retry Pending - Unable to deliver message,7F81D397.MMS 2011-06-28 15:15:26,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+19205308382,Retry Pending - Unable to deliver message,7F81D397.MMS 2011-06-28 15:15:26,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+15093786625,Retry Pending - Unable to deliver message,7F81D397.MMS 2011-06-28 15:15:26,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+19205408976,Retry Pending - Unable to deliver message,7F81D397.MMS 2011-06-28 15:17:11,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+19203628214,Retry Pending - MM4 - timeout during message transmission,7F81D397.MMS 2011-06-28 15:17:11,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+19203716919,Retry Pending - MM4 - timeout during message transmission,7F81D397.MMS 2011-06-28 15:17:11,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+19205308382,Retry Pending - MM4 - timeout during message transmission,7F81D397.MMS 2011-06-28 15:17:11,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+15093786625,Retry Pending - MM4 - timeout during message transmission,7F81D397.MMS 2011-06-28 15:17:11,MMSOUT,VASP:Syniverse,+19207130656/TYPE=PLMN,+19205408976,Retry Pending - MM4 - timeout during message transmission,7F81D397.MMS We just received another alert this morning at 9:38AM, and this is what our log is showing: 2011-07-01 09:37:42,MMSOUT,VASP:Syniverse,+19203317600/TYPE=PLMN,+19202875516,Retry Pending - Unable to deliver message,9CF2959D.MMS 2011-07-01 09:37:42,MMSOUT,VASP:Syniverse,+19203317600/TYPE=PLMN,+19206271473,Retry Pending - Unable to deliver message,9CF2959D.MMS 2011-07-01 09:38:08,MMSOUT,VASP:Syniverse,+19203317600/TYPE=PLMN,+19202875516,Retry Pending - MM4 - timeout during message transmission,9CF2959D.MMS 2011-07-01 09:38:08,MMSOUT,VASP:Syniverse,+19203317600/TYPE=PLMN,+19206271473,Retry Pending - MM4 - timeout during message transmission,9CF2959D.MMS 2011-07-01 09:38:16,MMSOUT,VASP:Syniverse,+19203317600/TYPE=PLMN,+19202875516,Retry Pending - MM4 - timeout during message transmission,9CF2959D.MMS 2011-07-01 09:38:16,MMSOUT,VASP:Syniverse,+19203317600/TYPE=PLMN,+19206271473,Retry Pending - MM4 - timeout during message transmission,9CF2959D.MMS There are more timeout alerts during these times in the log but i didn't want to post all of it and make a mess of things. This only seems to be happening when a user is sending an MMS to multiple people at one time. Let me know if there is any other information i can provide for you. Thank you, Andy | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3321 Registered: 08-2008 |
Hi Andy, Sorry for the delay in response ... I was on holiday last week and I've noticed it takes me a couple of days to process all that I missed while away. I'm going to go with your theory about a problem with one message going to multiple recipients. I'm also curious if you can recreate it on demand by sending to multiple remote recipients. If this is the problem, I have a potential solution for you. Edit the VASPOUT\Syniverse\VASP.INI file, and under the [VASP] header add: MaxRecips=20 You can try other values as well. This specifies the maximum number of recipients sent per transaction. I am guessing that this provider does not like the same message/message ID being sent to different recipients in separate transactions. By default, with MM4 connections, we perform a separate transaction per recipient, because this was a requirement we observed with one of our early customers that had an MM4 interconnect. But this behaviour can be tuned with the MaxRecips setting. Please let me know the results, and whether or not a problem with multiple recipients can be created on demand. -- Des NowSMS Support | ||||
