MM4 VASP Stops Sending

MM4 VASP Stops Sending SearchSearch
Author Message
Joseph Smith
New member
Username: Falangjoe

Post Number: 28
Registered: 08-2006
Posted on Tuesday, February 21, 2012 - 03:44 pm:   

Union Telephone
v2010.04.19


We receive are intercarrier MMS by a MM4 VASP. Several times now we have stopped receiving messages from the VASP for several days. During this time we are still able to send to them. When I restart the MMSC to turn on debugging, the problem goes away. I attached a wireshark trace that we did before restarting the MMSC today. Can you see anything?

Thanks,
Joseph Smith
application/octet-stream
iris-capture.pcap (140.7 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3804
Registered: 08-2008
Posted on Tuesday, February 21, 2012 - 04:42 pm:   

Hi Joseph,

Did you have MMSC Debug on when you restarted?

I'm just wondering what it would show during this time.

The first 22 seconds of the packet trace look like the other side is attempting to make a connection, but nothing is listening for the connection.

However, there are ACKs during this time period, which suggests there is some bidirectional communication, the capture just isn't recording it.

After 22 seconds, it starts looking a little more normal. At least to the extent that I'd be inclined to ignore the first 22 seconds as being incomplete captures.

Connections are being made ... the MMSC answers the connection by sending back a generic SMTP greeting "220 SMTP Ready". The other side replies with a greeting "EHLO irisme.net".

At that point, the MMSC seems to be proactively terminating the connection.

I am not aware of any condition that would cause a connection to be terminated at this stage of the conversation.

So I'd be curious if the MMSCDEBUG.LOG shows the EHLO message being logged. That would at least give us clues which way to look.

It's always possible that updating may resolve the issue, but I'm not while there are some issues resolved in later versions, I can't see how any of these issues could relate to this.

--
Des
NowSMS Support
Joseph Smith
New member
Username: Falangjoe

Post Number: 29
Registered: 08-2006
Posted on Wednesday, February 22, 2012 - 12:12 am:   

Des,

The first part of the trace was probably not complete. Here is the MSMCDEBUG from the last time we restarted it because of this issue. Thanks
application/octet-stream
MMSCDEBUG.LOG (1947.6 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3812
Registered: 08-2008
Posted on Wednesday, February 22, 2012 - 08:24 pm:   

Hi Joseph,

Apologies for the delay in response. One of my colleagues did download your log file late last night (and promptly removed it from the web site for potential privacy concerns).

The log didn't seem to provide any clues as it was from after the restart (as opposed to before).

But our hope is that if this happens again, you'll be ready to capture it.

--
Des
NowSMS Support