| MM4 vaspin problem with Nokia MMSC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | ||||
| Sharbat Goula New member Username: Sharbat Post Number: 3 Registered: 05-2010 |
I posted this to support@nowsms.com two weeks ago but did not receive any feedback, so I'll rephrase it again We recently launched Now MMS as a standalone MMSC and configured MM4 interworking with two national operators. Messages coming from Operator1 arrive and are delivered fine. With Opeator2 (two servers are configured) the incoming messages are not delivered. On MM4 level it looks fine, the MMS is received, routing callback is processed and MMSend with preauth is 200 O.K. but the messages are never delivered and no subsequent MMSSend callbacks are issued. The other direction works fine. Attached is MMSDEBUG.log, Wireshark trace, mmsc.ini and some other MMSC files. The sender is +38977772226
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2179 Registered: 08-2008 |
Hi, Based upon what I see in the debug log, I think there is a configuration issue with the "MMSC VASP" definition for 212.91.113.36. Specifically, I think the routing for received messages is set to "Receive to MMS-IN Directory" instead of "Standard MMS Delivery". Can you check that setting? -- Des NowSMS Support | ||||
| Sharbat Goula New member Username: Sharbat Post Number: 5 Registered: 05-2010 |
Hi Des, I checked this and it is (actually was) set as you said, but this is exactly as I read in the NowSMS/MMS Gateway 2009 Edition manual: "When defining a VASP account that is used to receive messages from a mobile operator, it is important that the "MMSC Routing for Received Messages" be set to any value other than "Standard MMS Delivery". This is because the "Standard MMS Delivery" option would specify that the messages should be routed for external delivery. However, when receiving messages from an operator MMSC, you would want to perform receive processing against the messages." I just don't understand the last sentence of the paragraph above. Btw, the vasp definition for Opeator1 is also set to receive in mms-in directory and it works just fine. I could try your proposal during the day and let you know what happened.} | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2183 Registered: 08-2008 |
Hi Sharbat, I don't think that text in the manual is good. I think it is referring to a different usage case (a usage case where you are a content provider connecting to a mobile operator). I can't explain why your other MM4 configuration is working properly, because it should not be. "Receive to MMS-IN Directory" means that any messages received are converted to a text format and written to the MMS-IN directory for separate application processing. You should definitely use the "Standard MMS Delivery" setting for the inbound receiving of messages from an MM4 interconnect. -- Des NowSMS Support | ||||
| Sharbat Goula New member Username: Sharbat Post Number: 6 Registered: 05-2010 |
Des, Thank you for your response. In the meantime, I have set all vasps to standard MMS delivery and indeed, all works fine, even the connection that worked well with MMS-IN directory. What a relief, thank you again. | ||||
| Sharbat Goula New member Username: Sharbat Post Number: 7 Registered: 05-2010 |
One reason why it worked with the first operator is that I noticed a problem with the GUI on Windows 2003. I might have initially clicked Standard MMSC Delivery and later changed this according to the information in the manual. I noticed two problems with the GUI one of them is sent already to now support (about a few weeks ago). 1. When choosing delete all users, the list is cleared but when returning to that tab gain later it is still populated, completely or partially. 2. I noticed that in a couple of occasions an already configured vasp or route later shows different options or blank fields than initially selected. Ic ouldn't reproduce this, so I din't report it. Regards, Sharbat | ||||
| Sharbat Goula New member Username: Sharbat Post Number: 8 Registered: 05-2010 |
Des, Can you plese check that this also has to do with the GUI observations: In the vasp definitions, in the accounting callbacks for the first operator the vaspin field is always populated with the name of the route (the one that is used for returning MM4 acks). For the other two vasps, the vaspin value is populated with the ipaddress (the name of the account). What is the source of this discrepancy? | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2192 Registered: 08-2008 |
Hi Sharbat, I looked at your previous log, and at least one of your MM4 connections (29401) is using SMTP AUTH to authenticate. So it's logging in with an account name, which would be reflected in the "VASPIN" parameter. I assume that the other connection does not SMTP AUTH, and is being identified by source IP address only, in which case the VASP account name is the IP address. Maybe this is the source of some of the previous confusion. You may have an "MMSC VASP" definition (IP Address associated with 29401) that is not actually being used because the SMTP AUTH was overriding the identity. -- Des NowSMS Support | ||||
| Sharbat Goula New member Username: Sharbat Post Number: 9 Registered: 05-2010 |
Hi Des, For the first connection I can notice them sending X-MMSC-Auth-User: VASP:29401. This could be remnant from the time we were trying to make authorized SMTP connection, but we gave up as it was not working. The current configuration doesn't have SMTP auth, so it's strange how the AUTH still works. Anyway, I'll ask them to remove this MMSC header. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2202 Registered: 08-2008 |
Hi Sharbat, I could see AUTH headers being sent in the SMTP dialog in your MMSCDEBUG.LOG. So maybe they figured out how to do it. -- Des NowSMS Support | ||||
Logs and config files
