MM7 SOAP specifications

MM7 SOAP specifications SearchSearch
Author Message
Latitude De
New member
Username: Latitudede

Post Number: 23
Registered: 07-2009
Posted on Wednesday, August 19, 2009 - 01:25 pm:   

Hi,

Please review the following MM7 SOAP message whihc I am getting from some MMSC. Its is very different to what I get from NowSMS. Does this follow the standard?

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<mm7p550:TransactionID soap:mustUnderstand="1" soap:encodingStyle="" xmlns:mm7p550="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">70DJZ789J6P9D9NQ342449489OZ93UA0</mm7p550:TransactionID>
</soap:Header>
<soap:Body>
<mm7p550:DeliverReq xmlns:mm7p550="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" xsi:type="mm7p550:deliverReqType" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<mm7p550:MM7Version>5.3.0</mm7p550:MM7Version>
<mm7p550:MMSRelayServerID>Nokia MMS Center MC4.0</mm7p550:MMSRelayServerID>
<mm7p550:LinkedID>SovEXwqEzioAAEE0AAAAIAAAw_EAAAAA</mm7p550:LinkedID>
<mm7p550:Sender>
<mm7p550:Number>+123456789/TYPE=PLMN</mm7p550:Number>
</mm7p550:Sender>
<mm7p550:Recipients>
<mm7p550:To>
<mm7p550:Number>8001/TYPE=PLMN</mm7p550:Number>
</mm7p550:To>
</mm7p550:Recipients>
<mm7p550:TimeStamp>2009-08-19T09:22:40Z</mm7p550:TimeStamp>
<mm7p550:Priority>Normal</mm7p550:Priority>
<mm7p550:Subject>Fw: Hhtoo@ngc.com.my</mm7p550:Subject>
<mm7p550:Content href="cid:1DQ7800U-B7JI-FAL93873" allowAdaptations="1">
</mm7p550:Content>
</mm7p550:DeliverReq>
</soap:Body>
</soap:Envelope>

Regards.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7838
Registered: 10-2002
Posted on Thursday, August 20, 2009 - 06:19 pm:   

Hi,

Maybe it would help me if you explained what you thought was wrong with this message.

Without performing an extensive evaluation of it, it looks ok to me.

Are you confused about the different XML name space prefixes?

-bn
Latitude De
New member
Username: Latitudede

Post Number: 24
Registered: 07-2009
Posted on Wednesday, August 26, 2009 - 11:52 am:   

Hi,

Yes the name spaces prefixes were confising but I feel they should not matter. Right?

Also what is different is that this was sent as a DeliveryDequest:

...
<mm7p550:DeliverReq ...
...

Whereas with Now SMS/MMS server, I get it as SubmitReq:

...
<SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
...

This difference is confusing me. Kindly advise.

Regards.
Latitude De
New member
Username: Latitudede

Post Number: 25
Registered: 07-2009
Posted on Wednesday, August 26, 2009 - 12:19 pm:   

Adding to my last post:

I can see under Now SMS/MMS MMS 'Outbound Routing' that the Connection Type is Default. Which is the preferred settings here?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1171
Registered: 08-2008
Posted on Wednesday, August 26, 2009 - 04:52 pm:   

Ah ... I understand your confusion.

Whether it is SubmitReq or DeliverReq depends on the direction of the connection.

In NowSMS, we refer to this as "To MMSC" or "To VASP".

When submitting a message to an MMSC, SubmitReq is used.

When an MMSC delivers a message to a VASP, DeliverReq is used.

The "Default" setting in NowSMS means that either could be used, depending on how the message entered NowSMS.

If the message was submitted to NowSMS (like via the web interface), this implies that the message is to be sent out ... and SubmitReq is used.

If the message was received via a VASP connection to an MMSC connection (or modem), then DeliverReq is used.

It is confusing because NowSMS can be used in different types of configurations.

--
Des
NowSMS Support