| MM4 to SMPP notification source addr manipulation? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Robert Barretto New member Username: Barretto Post Number: 1 Registered: 09-2019 |
I have an MMS termination coming into the MMS Gateway via MM4. When the MMS Gateway sends an SMS for MMS Notification over the SMSC connection, the SMPP message does not include the SOURCEADDR parm, rather the from party is specified in the MMS Message Encapsulation, Type: m-notification-ind, of the message. For example: X-Mms-Message-Type: m-notification-ind (0x82) X-Mms-Transaction-ID: D0Bd3eD4 X-Mms-MMS-Version: 1.2 From: +12145551234/TYPE=PLMN@mms-dfw.*********.com X-Mms-Message-Class: Personal (0x80) ... Is there any way to have the MMS Gateway alter the From header before sending the SMS MMS notification message out? What I'm seeing is that the receiving mobile shows the entire string as the calling line ID: +12145551234/TYPE=PLMN@mms-dfw.*********.com I was expecting to see just: +12145551234 I believe if the From header stopped after the /TYPE=PLMN, it would also work as the mobile should ignore that, but I can't confirm that. Any ideas? Please ignore the bold, I don't know what that's happening. Thanks, //Robert | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8333 Registered: 10-2002 |
Hi Robert, Apologies for the delay in response. It has been extremely challenging to understand the problem that you are describing. Thank you for sending in the e-mail with additional detail. The problem is being caused by an error with your MM4 provider. The From header in the SMTP/MM4 message is: From: +12145551234/TYPE=PLMN@mms-dfw.*********.com For a phone number, the format is supposed to be: From: +12145551234/TYPE=PLMN They are likely confused because the MAIL FROM command at the SMTP transport level uses the format: MAIL FROM: +12145551234/TYPE=PLMN@mms-dfw.*********.com For more information, refer to Section 8.4.5.1 in 3GPP TS 23.140. SMTP-address = MMS-address "@" MMSE-domain MMS-address = "+" E.164 "/TYPE=PLMN" E.164 = 1*DIGIT SMTP-address (with the @domain) is used only at the SMTP transport level in MAIL FROM/RCPT TO commands. MMS-address (without the @domain) is used in the message headers. The MMSC is treating +12145551234/TYPE=PLMN@mms-dfw.*********.com as an e-mail address, because the domain name should not be present in the MM4/SMTP From header. With that said, the chances of getting the MM4 internetworking provider to fix this error are probably slim. So, we are going to see if we can make a change to work-around this. -bn Bryce Norwood Now SMS/MMS Support | |||
| Robert Barretto New member Username: Barretto Post Number: 2 Registered: 09-2019 |
Hi Bryce, Thanks for the reply. Yes. I tried to explain to our MM4 provider that they were doing it wrong, and you are correct, they are saying they're doing it like this for other customers and they're fine, so it must be a problem on our end. I will continue to push on them though. Thanks for the spec references, I will provide those back to them as well. I sure hope y'all are able to help me get this working. Cheers, //Robert | |||
| Robert Barretto New member Username: Barretto Post Number: 3 Registered: 09-2019 |
Hi Bryce, I wrote a quick plugin to massage the bad From header in the SMS notification. I stripped off the @ domain stuff. Unfortunately, that didn't make a difference. The phone is using the content from the .MMS file in grabs from the MMS Gateway to determine the "calling address" to display in the text messaging. That file has the original bad From header that came from the originating MM4 provider: +12145551234/TYPE=PLMN@mms-dfw.*********.com bummer. I was kind of hoping the phone would use the address from the SMS[m-notification-ind] message and then go download the content from the provided link. Unfortunately it's only use the content from the provided link to display the entire message, including the bad from party. bummer. //Robert | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8334 Registered: 10-2002 |
Hi Robert, We should be able to produce a quick update to work around this issue. It's easy to see why this mistake would occur, because it doesn't really make sense why the specifications would use these different formats. It might be quick, it might take a couple days, but this would appear to be a simple issue to deal with. -bn Bryce Norwood Now SMS/MMS Support | |||
| Robert Barretto New member Username: Barretto Post Number: 4 Registered: 09-2019 |
Hi Bryce, That's good news to hear. I'll focus on integrating MMS originations working while we wait for this. Thanks a bunch! fyi. The MM4 carrier refuses to make this change because they're using this format with other customers and no one is complaining. oh well. //Robert | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8336 Registered: 10-2002 |
Hi Robert, Assuming that we have stimulated the problem properly, this update will accept the MM4 addressing variation described in previous messages. This should resolve the address problem that you experienced, which was preventing replies. https://www.nowsms.com/download/nowsms20190925.zip This is a full install that can be used to upgrade an existing installation. DO NOT uninstall the previous installation. In the unlikely event of problems with this version. Previous version installers can be used to downgrade to an earlier version. -bn Bryce Norwood Now SMS/MMS Support | |||
| Robert Barretto New member Username: Barretto Post Number: 8 Registered: 09-2019 |
Hi Bryce, Just installed the new version. Works like a champ! The From party is in MMS-address format instead of SMTP-address format in the Submit_SM[MMS notification] and now displays on the mobile device properly (i.e., just the sending party digits). Thanks for such a quick turn around on this. Cheers! //Robert | |||
