MM7 Submissions

MM7 Submissions SearchSearch
Author Message
Kerry Reid
New member
Username: Dagga

Post Number: 1
Registered: 04-2009
Posted on Monday, July 20, 2009 - 12:05 pm:   

Hi All

I have a test account with my provider (Vodacom in South Africa), I have set up now mms according to every instruction I can find but when I submit I don't receive an MMS.

Below is the MMSC DEBUG log which doesn't look like there are any problems but that is only my untrained eye!

Could someone have a look and see if they can spot anything please?

Log:

<?xml version="1.0" encoding="UTF-8"?><E:Envelope xmlns:E="http://schemas.xmlsoap.org/soap/envelope/" xmlns:s="http://www.w3.org/2001/XMLSchema-instance" xmlns:y="http://www.w3.org/2001/XMLSchema"><E:Header><ns1:TransactionID xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0">20090720115319-BC74196B-x40x-localhost</ns1:TransactionID></E:Header><E:Body>< m:SubmitRsp xmlns:m="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0"><MM7Version>5.3.0</MM7Version><Status><StatusCode>1000</StatusCode></Status><M essageID>R0pkTKEAEkpEAHTAqAx2</MessageID></m:SubmitRsp></E:Body></E:Envelope>
11:53:20:265 [10] ThreadProcessVASPQ: MM7 - got MessageID
11:53:51:265 [10] ThreadProcessVASPQ: closing keep-alive connection
11:58:46:281 [10] ThreadProcessVASPQ: C:\PROGRA~1\NowSMS\VASPOUT\Vodacom\VASP.INI
11:59:29:593 [11] InternalProcessConnection: Thread started
11:59:29:593 [11] ThreadProcessConnection: Processing connection from 127.0.0.1...
11:59:29:593 [11] ThreadProcessConnection: Packet Length is 580 bytes
11:59:29:593 [11] ThreadProcessConnection: 50 4F 53 54 20 2F 6C 6F 63 61 6C 53 79 73 74 65 POST /localSyste
11:59:29:593 [11] ThreadProcessConnection: 6D 3D 4D 4D 53 43 20 48 54 54 50 2F 31 2E 30 0D m=MMSC HTTP/1.0
11:59:29:593 [11] ThreadProcessConnection: 0A 43 6F 6E 74 65 6E 74 2D 74 79 70 65 3A 20 61 Content-type: a
11:59:29:593 [11] ThreadProcessConnection: 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 2E 77 pplication/vnd.w
11:59:29:593 [11] ThreadProcessConnection: 61 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 65 0D 0A ap.mms-message
11:59:29:593 [11] ThreadProcessConnection: 43 6F 6E 74 65 6E 74 2D 6C 65 6E 67 74 68 3A 20 Content-length:
11:59:29:593 [11] ThreadProcessConnection: 34 37 37 0D 0A 0D 0A 8C 80 98 34 41 35 41 45 39 477 4A5AE9
11:59:29:593 [11] ThreadProcessConnection: 37 34 00 8D 90 97 2B 32 37 37 32 38 32 30 32 30 74 +277282020
11:59:29:593 [11] ThreadProcessConnection: 33 31 2F 54 59 50 45 3D 50 4C 4D 4E 00 96 54 65 31/TYPE=PLMN Te
11:59:29:593 [11] ThreadProcessConnection: 73 74 00 89 0E 80 2B 32 37 38 32 39 38 39 39 39 st +278298999
11:59:29:593 [11] ThreadProcessConnection: 39 31 00 86 81 90 81 8F 81 8A 80 84 1F 24 B3 8A 91 $
11:59:29:593 [11] ThreadProcessConnection: 3C 34 41 35 41 45 39 37 33 2E 73 6D 69 6C 3E 00 <4A5AE973.smil>
11:59:29:593 [11] ThreadProcessConnection: 89 61 70 70 6C 69 63 61 74 69 6F 6E 2F 73 6D 69 application/smi
11:59:29:593 [11] ThreadProcessConnection: 6C 00 02 45 82 03 1F 22 61 70 70 6C 69 63 61 74 l E "applicat
11:59:29:593 [11] ThreadProcessConnection: 69 6F 6E 2F 73 6D 69 6C 00 85 34 41 35 41 45 39 ion/smil 4A5AE9
11:59:29:593 [11] ThreadProcessConnection: 37 33 2E 73 6D 69 6C 00 81 EA C0 22 3C 34 41 35 73.smil "<4A5
11:59:29:593 [11] ThreadProcessConnection: 41 45 39 37 33 2E 73 6D 69 6C 3E 00 8E 34 41 35 AE973.smil> 4A5
11:59:29:593 [11] ThreadProcessConnection: 41 45 39 37 33 2E 73 6D 69 6C 00 3C 73 6D 69 6C AE973.smil <smil
11:59:29:593 [11] ThreadProcessConnection: 3E 0D 0A 3C 68 65 61 64 3E 0D 0A 3C 6C 61 79 6F > <head> <layo
11:59:29:593 [11] ThreadProcessConnection: 75 74 3E 0D 0A 3C 72 65 67 69 6F 6E 20 69 64 3D ut> <region id=
11:59:29:593 [11] ThreadProcessConnection: 22 49 6D 61 67 65 22 20 68 65 69 67 68 74 3D 22 "Image" height="
11:59:29:593 [11] ThreadProcessConnection: 31 30 30 25 22 20 77 69 64 74 68 3D 22 31 30 30 100%" width="100
11:59:29:593 [11] ThreadProcessConnection: 25 22 20 66 69 74 3D 22 6D 65 65 74 22 2F 3E 0D %" fit="meet"/>
11:59:29:593 [11] ThreadProcessConnection: 0A 3C 72 65 67 69 6F 6E 20 69 64 3D 22 54 65 78 <region id="Tex
11:59:29:593 [11] ThreadProcessConnection: 74 22 20 68 65 69 67 68 74 3D 22 31 30 30 25 22 t" height="100%"
11:59:29:593 [11] ThreadProcessConnection: 20 77 69 64 74 68 3D 22 31 30 30 25 22 20 66 69 width="100%" fi
11:59:29:593 [11] ThreadProcessConnection: 74 3D 22 73 63 72 6F 6C 6C 22 2F 3E 0D 0A 3C 2F t="scroll"/> </
11:59:29:593 [11] ThreadProcessConnection: 6C 61 79 6F 75 74 3E 0D 0A 3C 2F 68 65 61 64 3E layout> </head>
11:59:29:593 [11] ThreadProcessConnection: 0D 0A 3C 62 6F 64 79 3E 0D 0A 3C 70 61 72 20 64 <body> <par d
11:59:29:593 [11] ThreadProcessConnection: 75 72 3D 22 33 73 22 3E 0D 0A 3C 74 65 78 74 20 ur="3s"> <text
11:59:29:593 [11] ThreadProcessConnection: 73 72 63 3D 22 34 41 35 41 45 39 37 33 2E 74 78 src="4A5AE973.tx
11:59:29:593 [11] ThreadProcessConnection: 74 22 20 72 65 67 69 6F 6E 3D 22 54 65 78 74 22 t" region="Text"
11:59:29:593 [11] ThreadProcessConnection: 2F 3E 0D 0A 3C 2F 70 61 72 3E 0D 0A 3C 2F 62 6F /> </par> </bo
11:59:29:593 [11] ThreadProcessConnection: 64 79 3E 0D 0A 3C 2F 73 6D 69 6C 3E 0D 0A 20 04 dy> </smil>
11:59:29:593 [11] ThreadProcessConnection: 83 C0 22 3C 34 41 35 41 45 39 37 33 2E 74 78 74 "<4A5AE973.txt
11:59:29:593 [11] ThreadProcessConnection: 3E 00 8E 34 41 35 41 45 39 37 33 2E 74 78 74 00 > 4A5AE973.txt
11:59:29:593 [11] ThreadProcessConnection: 54 65 73 74 Test
11:59:29:593 [11] ThreadProcessConnection: Got application/vnd.wap.mms-message
11:59:29:593 [11] ThreadProcessConnection: Got m-send-req
11:59:29:593 [11] ThreadProcessConnection: TO: +27728202031/TYPE=PLMN
11:59:29:593 [11] MMSRoutingCallback: +27728202031/TYPE=PLMN
11:59:29:593 [11] MMSRoutingCallback: +27728202031/TYPE=VASP:Vodacom
11:59:29:593 [11] CheckMMSBlockedContent: body part #1 Content-Type = application/smil
11:59:29:593 [11] CheckMMSBlockedContent: body part #2 Content-Type = text/plain
11:59:29:593 [11] DeliverMMSMessage: TO: +27728202031/TYPE=VASP:Vodacom
11:59:29:593 [11] DeliverMMSMessage: Found VASP Recip - Vodacom
11:59:29:593 [11] DeliverMMSMessage-VASP: +27728202031
11:59:29:593 [11] ThreadProcessConnection: Packet Length is 153 bytes
11:59:29:593 [11] ThreadProcessConnection: 48 54 54 50 2F 31 2E 30 20 32 30 30 20 4F 4B 0D HTTP/1.0 200 OK
11:59:29:593 [11] ThreadProcessConnection: 0A 43 6F 6E 6E 65 63 74 69 6F 6E 3A 20 63 6C 6F Connection: clo
11:59:29:593 [11] ThreadProcessConnection: 73 65 0D 0A 43 6F 6E 74 65 6E 74 2D 54 79 70 65 se Content-Type
11:59:29:625 [11] ThreadProcessConnection: 3A 20 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E : application/vn
11:59:29:625 [11] ThreadProcessConnection: 64 2E 77 61 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 d.wap.mms-messag
11:59:29:625 [11] ThreadProcessConnection: 65 0D 0A 43 6F 6E 74 65 6E 74 2D 4C 65 6E 67 74 e Content-Lengt
11:59:29:625 [11] ThreadProcessConnection: 68 3A 20 34 38 0D 0A 0D 0A 8C 81 98 34 41 35 41 h: 48 4A5A
11:59:29:625 [11] ThreadProcessConnection: 45 39 37 34 00 8D 90 92 80 8B 32 30 30 39 30 37 E974 200907
11:59:29:625 [11] ThreadProcessConnection: 32 30 2F 31 31 2F 46 35 36 33 36 42 41 38 40 6C 20/11/F5636BA8@l
11:59:29:625 [11] ThreadProcessConnection: 6F 63 61 6C 68 6F 73 74 00 ocalhost
11:59:29:625 [11] ThreadProcessConnection: Processing Complete
11:59:29:625 [11] InternalProcessConnection: Thread ended
11:59:31:281 [10] ThreadProcessVASPQ: recipArray count = 1
11:59:31:453 [10] InetServerConnect: Connected to mms.vodacom4me.co.za (196.207.45.50:8082)
11:59:31:453 [10] ThreadProcessVASPQ: POST /mm7 HTTP/1.1
Authorization: Digest username="27829899991", realm="openwavemm7", nonce="SlrpqQ==57572ea1391235254943a99fa701e2d7e10818cc", uri="/mm7", qop="auth", nc="00000010", cnonce="30751a50799b85603d2e5077fc26919926", response="c51fa7dd816b895eead2a77d414eadd5", opaque="Ѓ‚"
Host: mms.vodacom4me.co.za:8082
SOAPAction: ""
Content-Length: 1736
Content-Type: multipart/related; boundary="---mime-boundary-EA99EEA5.E8F402E6"; type="text/xml"; start="<mm7_msg>"


11:59:31:453 [10] ThreadProcessVASPQ: -----mime-boundary-EA99EEA5.E8F402E6
Content-Type: text/xml; charset=utf-8
Content-ID: <mm7_msg>

<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
<TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0" env:mustUnderstand="1">20090720115931-D35B7262-x40x-localhost</TransactionID>
</env:Header>
<env:Body>
<SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0">
<MM7Version>5.3.0</MM7Version>
<SenderIdentification>
<SenderAddress>+27829899991</SenderAddress>
</SenderIdentification>
<Recipients>
<To>
<Number>27728202031</Number>
</To>
</Recipients>
<MessageClass>Personal</MessageClass>
<Priority>Normal</Priority>
<Subject>Test</Subject>
<Content href="cid:mms_cid" />
</SubmitReq>
</env:Body>
</env:Envelope>

-----mime-boundary-EA99EEA5.E8F402E6
Content-Type: multipart/related; start="<4A5AE973.smil>"; type="application/smil"; boundary="---mime-boundary-14E73663.93558524"
Content-ID: <mms_cid>

-----mime-boundary-14E73663.93558524
Content-Type: application/smil; name="4A5AE973.smil"; charset=utf-8
Content-ID: <4A5AE973.smil>
Content-location: 4A5AE973.smil

<smil>
<head>
<layout>
<region id="Image" height="100%" width="100%" fit="meet"/>
<region id="Text" height="100%" width="100%" fit="scroll"/>
</layout>
</head>
<body>
<par dur="3s">
<text src="4A5AE973.txt" region="Text"/>
</par>
</body>
</smil>

-----mime-boundary-14E73663.93558524
Content-Type: text/plain
Content-ID: <4A5AE973.txt>
Content-location: 4A5AE973.txt

Test
-----mime-boundary-14E73663.93558524--

-----mime-boundary-EA99EEA5.E8F402E6--

11:59:32:000 [10] HttpResponseWait: Chunked response Ok
11:59:32:000 [10] HttpChunkStrip: Enter
11:59:32:000 [10] HttpChunkStrip: Decoding chunk size 645
11:59:32:000 [10] HttpChunkStrip: Decoding chunk size 0
11:59:32:000 [10] HttpChunkStrip: Exit
11:59:32:000 [10] ThreadProcessVASPQ: MM7 - got http ok response
11:59:32:000 [10] ThreadProcessVASPQ: HTTP/1.1 200 OK
Content-type: text/xml
Connection: Keep-Alive
Keep-Alive: timeout=30, max=150
Transfer-Encoding: chunked

<?xml version="1.0" encoding="UTF-8"?><E:Envelope xmlns:E="http://schemas.xmlsoap.org/soap/envelope/" xmlns:s="http://www.w3.org/2001/XMLSchema-instance" xmlns:y="http://www.w3.org/2001/XMLSchema"><E:Header><ns1:TransactionID xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0">20090720115931-D35B7262-x40x-localhost</ns1:TransactionID></E:Header><E:Body>< m:SubmitRsp xmlns:m="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0"><MM7Version>5.3.0</MM7Version><Status><StatusCode>1000</StatusCode></Status><M essageID>RkpkThUAC0pEAaLAqAx2</MessageID></m:SubmitRsp></E:Body></E:Envelope>
11:59:32:000 [10] ThreadProcessVASPQ: MM7 - got MessageID
12:00:00:781 [0] main: 53 Days remaining in trial version
12:00:03:000 [10] ThreadProcessVASPQ: closing keep-alive connection


---

Regards

Dagga
Kerry Reid
New member
Username: Dagga

Post Number: 2
Registered: 04-2009
Posted on Monday, July 20, 2009 - 12:44 pm:   

Actually, scratch this, it would seem I was trying to submit to a phone a on a different network which is apparently not allowed.

So, my next question is:

If the provider I am submitting to does not allowing sending to the TO number, can NowSMS report this and switch to another route?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1058
Registered: 08-2008
Posted on Tuesday, July 21, 2009 - 06:57 pm:   

Hi Dagga,

The problem is ... there's no error.

The response that is coming back actually indicates success. Even a "MessageID" value is being returned, which normally indicates that the MMSC has accepted the message.

It's very possible that the provider is throwing away any messages destined for recipients outside of their network ... but the open question is ... if they do this ... how are you supposed to know?

If you do have a way of performing a carrier lookup, NowSMS has an MMS routing callback interface. With this interface, every time NowSMS routes an MMS message, it performs an HTTP callback to ask what route should be used for the recipient phone number. If you had a way to implement such a lookup, then you could decide which route to use.

The routing callback is described here:

http://blog.nowsms.com/2008/04/mobile-number-portability-mnp-and.html

I wish I had a better answer for you ... but in a situation where an error isn't even returned, it's difficult to figure out anyway to handle the situation.

--
Des
NowSMS Support
Kerry Reid
New member
Username: Dagga

Post Number: 3
Registered: 04-2009
Posted on Wednesday, July 22, 2009 - 07:13 am:   

Thanks Des, I'll make some enquiries, for the record it is working when I send to a phone on the same network...
Trojan USC
New member
Username: Trojansc

Post Number: 1
Registered: 04-2010
Posted on Friday, April 23, 2010 - 08:08 am:   

Hi,
Need help,
Our customer is trying to submit a MM7 and he is getting a error response which is
<?xml version="1.0"?>
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.0//EN"
"http://www.wapforum.org/DTD/pap_2.0.dtd">
<pap>
<push-response push-id="unknown">
<response-result code="2001" desc="4811:Invalid interface" message-id="unknown"/>
</push-response>
</pap>
Please let me know what this error is and why he is not able to submit.
Thanks in advance
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2042
Registered: 08-2008
Posted on Friday, April 23, 2010 - 01:54 pm:   

Hi,

Where is he trying to submit an MM7 message to?

Is he using NowSMS? (You've posted this question in our support forum, so I assume it is somehow related.)

This response looks like it is formatted according to the WAP Push Access Protocol (PAP).

It could be a response from a Logica CMG MMSC. Their so-called MM7 interface doesn't use standard MM7 ... instead it uses an MM7-like interface build around the WAP Push Access Protocol (PAP). (I would expect that newer versions of Logica's MMSC would support the actual MM7 protocol, but I've never seen confirmation of this.)

Assuming this is a LogicaCMG MMSC, NowSMS does support this interface. When configuring the MM7 connection, you need to select the "Non-Standard MM7 Variation" of "LogicaCMG - PAP".

--
Des
NowSMS Support
Trojan USC
New member
Username: Trojansc

Post Number: 2
Registered: 04-2010
Posted on Saturday, April 24, 2010 - 08:36 am:   

Hi Des,
Thanks for your response,
I'm very new to NowSMS and very new to MMSC and SMSc, I think I posted it in wrong thread as it is Logica CMG's MMSC.
The problem occurs when the customer tryies to submit the MM7 to Logica CMG's MMSC... he is getting this response, so should I have to make any changes from our side while configuring the MM7? Since while provisioning the MM7 i used SOAP but i dont know why he is getting a response as PAP.
Thanks for your support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2047
Registered: 08-2008
Posted on Saturday, April 24, 2010 - 10:06 pm:   

Hi,

When configuring the MM7 connection in NowSMS, you need to select the "Non-Standard MM7 Variation" of "LogicaCMG - PAP".

LogicaCMG calls this protocol MM7, but it is not truly MM7. It does not use SOAP, it uses PAP.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3459
Registered: 08-2008
Posted on Thursday, September 08, 2011 - 07:55 pm:   

The most recent post on this thread is unrelated to earlier discussion and has been moved to:

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