Error in xml when routing MM7 to operators MMSC

Error in xml when routing MM7 to operators MMSC SearchSearch
Author Message
Shimon
New member
Username: Daffy

Post Number: 2
Registered: 06-2004
Posted on Thursday, July 15, 2004 - 04:33 pm:   

Hi.

The operators MMSC will not accept my MM7 message and I belive that it is becase of an extra space in the body (<Content href="cid:mms_cid" /> between the second " and /) of the xml that is sent (see log).

Regards
Shimon Kupersmidt

--LOG-----------------------------------

16:14:29:644 [7] InetServerConnect: Connected to xxx.yyy.se (1.1.1.1:8090)
16:14:29:644 [7] ThreadProcessVASPQ: POST /mm7 HTTP/1.0
Host: xxx.yyy.se:8090
SOAPAction: ""
Content-Length: 1336
Content-Type: multipart/related; boundary="---mime-boundary-F032A15B.98A2DA1C---"; type="text/xml"; start="<mm7_msg>"
Connection: close


16:14:29:644 [7] ThreadProcessVASPQ: -----mime-boundary-F032A15B.98A2DA1C---
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">
20040715/11/D32E025B@172.16.92.22
</mm7:TransactionID>
</env:Header>
<env:Body>
<SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
<MM7Version>5.3.0</MM7Version>
<SenderIdentification>
<VASPID>INFOSYS</VASPID>
<VASID>INFOSYS</VASID>
</SenderIdentification>
<Recipients>
<To>
<Number>46701111111</Number>
</To>
</Recipients>
<DeliveryReport>False</DeliveryReport>
<Subject>subj</Subject>
<Content href="cid:mms_cid" />
</SubmitReq>
</env:Body>
</env:Envelope>

-----mime-boundary-F032A15B.98A2DA1C---
Content-Type: multipart/mixed; boundary="---mime-boundary-C97CAD9D.029FABDE---"
Content-ID: <mms_cid>

-----mime-boundary-C97CAD9D.029FABDE---
Content-Type: text/plain
Content-ID: <40F64F99.txt>
Content-location: 40F64F99.txt

test
-----mime-boundary-C97CAD9D.029FABDE-----

-----mime-boundary-F032A15B.98A2DA1C-----

16:14:29:674 [7] ThreadProcessVASPQ: mm7 - got unknown response
16:14:29:674 [7] ThreadProcessVASPQ: HTTP/1.1 500 Could not decode soap operation.
Date: Thu, 15 Jul 2004 16:13:28 +0200
Content-Type: text/plain
Connection: Close
Server: Nobill/R3
Content-Length: 32

Could not decode soap operation.
16:14:29:674 [7] ThreadProcessVASPQ: Outbound route Symsoft: setting retry for D32E025B.MMS
Kent Williams
Moderator
Username: Kent

Post Number: 88
Registered: 10-2003
Posted on Friday, July 23, 2004 - 03:36 am:   

This is better handled in the NowSMS area:

http://support.nowsms.com/discus/messages/485/5372.html