DeliveryReportReq instead DeliverReq

Author

Message

Sergio Álvarez
New member
Username: Xergio

Post Number: 2
Registered: 02-2007

Posted on Friday, May 11, 2007 - 05:29 pm:

I all.

We need that nowsms sent to the provider (sybase) a <DeliveryReportReq> instead the <DeliverReq>. How can we make it?

This is an example of the message we send to nowsms by IP:8801 :

POST /mm7 HTTP/1.1
Host: 172.16.21.60:8801
User-Agent: Jet Multimedia S.A./2.0
Authorization: Basic base64(user:pass)
Content-Type: multipart/related; boundary="----------section"; type=text/xml; start="</post-content/mm7-submit>"
Content-Length: 3595
SOAPAction: ""
Connection: close

------------section
Content-Type: text/xml; charset="utf-8"
Content-ID: </post-content/mm7-submit>

<?xml version="1.0" encoding="utf-8" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
<mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-M M7-1-3" env:mustUnderstand="1">
TrID_00001
</mm7:TransactionID>
</env:Header>
<env:Body>
<SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1 -3">
<MM7Version>5.6.0</MM7Version>
<SenderIdentification>
<VASPID>devusr</VASPID>
</SenderIdentification>
<Recipients>
<Bcc>
<Number>+34678653849</Number>
</Bcc>
</Recipients>
<MessageClass>Informational</MessageClass>
<TimeStamp>2007-05-11T16:24:03+0200</TimeStamp>
<ExpiryDate>2007-05-11T17:24:03+0200</ExpiryDate>
<DeliveryReport>true</DeliveryReport>
<Priority>Normal</Priority>
<Subject>Tiiiitulo</Subject>
<DistributionIndicator>true</DistributionIndicator>
<Content href="cid:info-1178893443@jetmultimedia.es" allowAdaptations="true"/>
</SubmitReq>
</env:Body>
</env:Envelope>

------------section
Content-Type: multipart/related; boundary="--------------------visible"
Content-ID:<info-1178893443@jetmultimedia.es>

----------------------visible
Content-Type: text/plain; charset="utf-8"

Este es el video aac30.3gp
----------------------visible
Content-Type: image/png
Content-ID:<logo.png>
Content-Transfer-Encoding: binary
Content-Length: 1661

[binary code here]
----------------------visible--
------------section--

With base64 image content we gets the same result.

We receibe all the MMS, but sybase need a DeliveryReportReq to can send us the callback about the mms status.

Thank you very much.

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7130
Registered: 10-2002

Posted on Wednesday, May 16, 2007 - 04:52 pm:

Hi Sergio,

I need to understand the transaction flow better.

Can you describe the flow and the protocol that is used each step of the way. And what you want to happen.

For example:

Message from provider to NowSMS - MM7 DeliverReq
NowSMS to application - ???
application to NowSMS - ???
NowSMS to provider - ???

Basically I need to understand your configuration better in order to offer any advice.

I know that we currently do not send Delivery reports across all protocol interfaces ... as they are not always expected depending on configuration.

-bn

Sergio Álvarez
New member
Username: Xergio

Post Number: 3
Registered: 02-2007

Posted on Wednesday, May 16, 2007 - 06:06 pm:

Hi Bryce.

This debug is sent from my script to nowsms via http post en mm7. Nowsms sends to the provider (sybase) this:

17:26:42:479 [9] InetServerConnect: Connected to mms.mobileway.com (203.117.144.22:80)
17:26:42:479 [9] ThreadProcessVASPQ: POST /mms/mm7 HTTP/1.1
Authorization: Basic base64 code
Host: mms.mobileway.com
SOAPAction: ""
Content-Length: 19852
Content-Type: multipart/related; boundary="---mime-boundary-B1B491D9.89EF151A---"; type="text/xml"; start="<mm7_msg>"
Connection: close

17:26:42:479 [9] ThreadProcessVASPQ: -----mime-boundary-B1B491D9.89EF151A---
Content-Type: text/xml; charset=utf-8
Content-ID: <mm7_msg>

<?xml version="1.0" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
<mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" env:mustUnderstand="1">20070514172642-A648F958@172.16.21.60</mm7:TransactionID>
</env:Header>
<env:Body>
<DeliverReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
<MM7Version>5.3.0</MM7Version>
<Sender>
<Number>VASP:devusr</Number>
</Sender>
<Recipients>
<To>
<Number>+34678653849</Number>
</To>
</Recipients>
<Priority>Normal</Priority>
<Subject>Tiiiitulo</Subject>
<Content href="cid:mms_cid"/>
</DeliverReq>
</env:Body>
</env:Envelope>

-----mime-boundary-B1B491D9.89EF151A---
Content-Type: multipart/related; boundary="---mime-boundary-C7F4131B.4D0B1BDC---"
Content-ID: <mms_cid>

-----mime-boundary-C7F4131B.4D0B1BDC---
Content-Type: text/plain; charset=utf-8
Content-location: 01098D9E.txt

Este es el video aac30.3gp
-----mime-boundary-C7F4131B.4D0B1BDC---
Content-Type: image/png
Content-ID: <90db34299acb4366156bc39d6ba0b129>
Content-location: 73C7BF5D.png
Content-Transfer-Encoding: base64

base64 code here

-----mime-boundary-C7F4131B.4D0B1BDC-----

-----mime-boundary-B1B491D9.89EF151A-----

17:26:44:057 [9] HttpResponseWait: Ok
17:26:44:057 [9] ThreadProcessVASPQ: mm7 - got http ok response
17:26:44:057 [9] ThreadProcessVASPQ: HTTP/1.1 200 OK
Date: Mon, 14 May 2007 15:32:46 GMT
Server: Apache/1.3.27 (Unix) mod_perl/1.27
Content-Length: 705
Content-Type: text/xml;charset="utf-8"
X-Cache: MISS from mms.mobileway.com
Connection: close

<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
<mm7:TransactionID env:mustUnderstand="1" xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">20070514172642-A648F958@172.16.21.60</mm7:TransactionID>
</env:Header>
<env:Body>
<mm7:DeliverRsp xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
<MM7Version>5.3.0</MM7Version>
<Status>
<StatusCode>1000</StatusCode>
<StatusText>Success</StatusText>
</Status>
</mm7:DeliverRsp>
</env:Body>
</env:Envelope>

17:26:44:057 [9] ThreadProcessVASPQ: mm7 - got status OK (1000)

Size values isn't exacts becouse I'm not used synced debug, but they are all identical, the log shows always a debug like this.

Do you need more information?

Thank you very much.

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7145
Registered: 10-2002

Posted on Thursday, May 17, 2007 - 06:11 pm:

Hi Sergio,

I am making some progress in understanding, but I'm not sure where the DeliveryReportReq would come into the picture yet.

It looks like you are performing an MM7 SubmitReq.

And then NowSMS is performing an MM7 DeliverReq to your provider.

I can see in your original SubmitReq that you are requesting a delivery report: <DeliveryReport>true</DeliveryReport>

When the message is submitted to your provider using DeliverReq, that attribute is no longer present. The reason that it is no longer present is because this attribute is supported only in a submit, not a deliver.

So let me ask this ... which of the following are you trying to accomplish?

1.) You want to send an MMS message via your provider and receive back a delivery report.

2.) You want to send back a delivery report to your provider when you receive a message.

Based on your original question, I was thinking that you wanted #2. But now I'm thinking that you are trying to accomplish #1.

To accomplish #1, you would have to change your "MMSC Routing" definition for the MM7 connection to your provider to be "Connection Type" = "To MMSC (submit format)". This way you would be sending SubmitReq instead of DeliverReq, and the attribute to request a delivery report would be supported.

Then, assuming that your provider supports delivery reports, you would receive a DeliveryReportReq back via MM7. To accomplish this, you need to be setup to receive MMS messages from your provider. This means that you need to have an "MMSC VASP" account defined on your system for the provider to connect to you to deliver messages (and to deliver delivery reports). The provider needs to configure their end to connect back to you to deliver these messages, connecting to http://nowsms:mmscHttpPort/mm7/vaspaccountname=password

-bn

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7146
Registered: 10-2002

Posted on Thursday, May 17, 2007 - 06:12 pm:

One more thing ... you need to configure a sender address for your "MMSC Routing" definition to allow the delivery reports to get routed back to that address.

Search

Last 30 Days

Login / Register

Logout

DeliveryReportReq instead DeliverReq

Now SMS/MMS NextGen runs on Linux

Purchase NowSMS

Now Supporting Android Phones as Modems for Sending & Receiving SMS+MMS

NowSMS Technical Bulletins