Deliver to MM7 VASP: SubmitReq or DeliverReq?

Deliver to MM7 VASP: SubmitReq or DeliverReq? SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Deliver to MM7 VASP: SubmitReq or DeliverReq? « Previous || Next »
Author Message
Unregistered guest
Posted on Friday, March 05, 2004 - 01:25 pm:   


Hope you can help please:
I am testing your latest NowMMS 5.0
doing a Mobile Originated MMS routing to
a VASP, please find the following is the
snoop of the MM7 message being sent by
the NoMMS.

The question is, the field SubmitReq
shouldn't it be DeliverReq ?
since it is mobile originated to VASP.
I am using the 3GPP MMS functional description.
in section 8.7.2 Delivery Request.

SOAPAction: ""
Content-Length: 1313
Content-Type: multipart/related; boundary="---mime-boundary-8828FE7C.4FD9D9FD---"; type=text/xml; start="<mm7_msg>"
Connection: close

Content-Type: text/xml; charset=utf-8
Content-ID: <mm7_msg>

<?xml version='1.0' ?>
<env:Envelope xmlns:env="">
<mm7:TransactionID xmlns:mm7=" M7-1-2" env:mustUnderstand="1">
<SubmitReq xmlns=" -2">
<Subject>Multimedia Message</Subject>
<Content href="cid:mms_cid" />

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1972
Registered: 10-2002
Posted on Friday, March 05, 2004 - 02:06 pm:   

Hi Allan,

The scenarios for whether submitReq or deliverReq should be used for an MM7 connection can be extremely complicated.

By default, whether we use submitReq or deliverReq is dependent on how the message was routed into NowSMS. If NowSMS received it as a submit equivalent, then submitReq is used. If it was received as a deliver equivalent, then deliverReq is used.

Keep in mind that the MM7 connection that is defined could be used for a typical client VASP, but it could also be being used to connect to a service provider.

For situations where the default behaviour is not appropriate, we have configuration settings that can force messages being routed via MM7 to use either submitReq or deliverReq format.

You will find a configuration file named VASPOUT/accountname/VASP.INI. In this file, under the [VASP] section header, you can specify one of the following parameters:


Including either of these settings will force all messages routed out via that connection to be converted to deliverReq or submitReq format.

I believe that you need to be using v5.01 in order to support this feature.

You can download v5.01 from our web site, and install it over an existing installation to update the version.


Login Login / Register Logout Logout Search Last 30 Days Topics Topics