displayOnly recipients equivalent using web form mms sending?"

displayOnly recipients equivalent using web form mms sending?" SearchSearch
Author Message
Robert Barretto
New member
Username: Barretto

Post Number: 38
Registered: 09-2019
Posted on Friday, December 11, 2020 - 02:15 pm:   

Hi,

When the NowSMS MMSC sends out a group message via an MM7 DeliverReq message, I get a list of "recipients", with one recipient being the actual receiving party, and the others listed as "displayOnly".

...
<DeliverReq ...>
<Sender>
<Number>+12145551212</Number>
</Sender>
<Recipients>
<To>
<Number>+14698880001</Number>
</To>
<To>
<Number displayOnly="true">+14698880002</Number>
</To>
<To>
<Number displayOnly="true">+14698880003</Number>
</To>
</Recipients>
...

Is there an analogous way of doing this on using the NowSMS web interface POST form-data method? I can see that I can provide a comma separated list "recipients" in the "PhoneNumber" parameter, but the resulting MM7 DeliverReq message in this case will lists all the To parties as straight numbers, and none of them are display only.

...
<DeliverReq ...>
<Sender>
<Number>+12145551212</Number>
</Sender>
<Recipients>
<To>
<Number>+14698880001</Number>
</To>
<To>
<Number>+14698880002</Number>
</To>
<To>
<Number>+14698880003</Number>
</To>
</Recipients>
...


Is there are way to have displayOnly recipients via the web form interface? Without the displayOnly, this could mess up threading on the end devices, or result in some devices getting the same message multiple times.

Thanks,
//Robert
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 6202
Registered: 08-2008
Posted on Friday, December 11, 2020 - 06:02 pm:   

Hi Robert,

Unfortunately, no.

The web form interface uses the MM1 protocol to interface with the MMSC, and there is no concept of a "displayOnly" attribute in MM1.

With MM7, it is possible, as you describe. And with MM4, the "actual receiving party" is specified in the SMTP ENVELOPE with the "RCPT TO:" command. Any To/CC recipients that appear only in the message header are assumed to be "displayOnly".

I'm asking our engineering team if there is anything that I am overlooking. EAIF is a Nokia defined protocol based on MM1, and it supports "display only" recipients by adding an HTTP header that functions similar to "RCPT TO" in MM4. Unfortunately, I do not see anyway for the web form interface to generate this extra header. But, maybe it would be a simple change to provide an option to use this extra header. We will investigate this.

Regards,

Des
NowSMS Support
Robert Barretto
New member
Username: Barretto

Post Number: 40
Registered: 09-2019
Posted on Friday, December 11, 2020 - 09:37 pm:   

Hi Des,

Thanks for the reply. I was trying a group mms origination, so the mobile was sending in via MM1 MMSE[m-send-req has two TO parties in it. The MMSC is converting the MM1 into an MM7[DeliverReq] and sending that to my application server with two TO numbers (no displayOnly on either number).

If I do a group mms termination, an MM4 message comes into the MMSC (where the RCPT TO is the real terminating party and the To header shows multiple parties. In this case, the MMSC is creating and routing an MM7[DeliverReq] to my application server with the RCPT TO as the real TO party, and the other party shows as "displayOnly").

I was trying to leverage the web interface because it didn't require much code at all to send the MMS event and it allowed my application server to immediately provide the outbound route for where the MMS message should go to It also meant that I didn't have to implement MM7[SubmitReq] functionality in my application. Also, if I went the MM7 way, then I would have to have the MMSC re-dip to the server via the MMSRoutingURL to get the route (which it already knew when the MM7[DeliverReq] comes in). This would prevent me from having to do call-typing and run policy twice.

Essentially I have two use cases.
1. MMS terminations - these go:
Bandwidth --MM4--> MMSC --MM7[DelvReq]--> AppSrvr/term --WebPost(w/route)--> MMSC --SMPP[MMS_notif]--> SMSC --SMS--> mobile

2. MMS originations - these go:
mobile --MM1[m-send-req]--> MMSC --MM7[DelvReq]--> AppSrvr/orig --WebPost(w/route)--> MMSC --MM4--> Bandwidth

Cheers,
//Robert

Add Your Message Here, or click here to start a new topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message
Action: