TransactionID: unknown | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
Author | Message | ||||
Anonymous |
Hello I am using the nowsms MMSC emulator and whenever i post an mm7 submit request to it, it returns a submit response with response code 1000, but the transaction id has a value of "unknown". Further to that, the content i send along in my MIME message is not captured in the MMS-IN folder as configured. Any guidance on this would be appreciated. | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5215 Registered: 10-2002 |
It would help to see exactly what you are submitting. A TransactionID of unknown in the response indicates that we did not find a valid transaction id in the request. (But the server accepts the message anyway.) And if you expect the content to go into the MMS-IN directory, you need to have the "MMSC VASP" account that you are using configured to have its messages routed into the MMS-IN directory, otherwise the MMSC will try to route the messages for outbound delivery. If this still does not answer your question, then you need to provide more details. An MMSCDEBUG.LOG from NowSMS would also be helpful, as that would show what the MMSC is actually receiving from your application. (Enable the MMSCDEBUG.LOG via the "Serial #" page of the configuration dialog.) -bn | ||||
irwin williams Unregistered guest |
ok, this is the MIME Message i am sending across: //Message starts after this line POST / HTTP/1.1 Host: 192.168.0.121:4444 Content-Length: 2632 Expect: 100-continue Connection: Keep-Alive MIME-Version: 1.0 Content-Type: multipart/related; boundary=MAINBOUNDARY4d39cbb5.8ccb.493c.ac76.f6 81f63ca43a; start="MAINBOUNDARY4d39cbb5.8ccb.493c.ac76.f681f63ca43a@telebelly.sh elly"; type="text/xml" Content-Length: 2591 soapaction:"" --MAINBOUNDARY4d39cbb5.8ccb.493c.ac76.f681f63ca43a Content-Type: text/xml; charset=utf-8 Content-ID: <MAINBOUNDARY4d39cbb5.8ccb.493c.ac76.f681f63ca43a@telebelly.shelly> <?xml version='1.0' encoding='UTF-8'?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xm lns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org /2001/XMLSchema"> <SOAP-ENV:Header> <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_s eries/23.140/schema/REL-5-MM7-1-2" SOAP-ENV:mustUnderstand="1">issomeeonegetting thebest</mm7:TransactionID> </SOAP-ENV:Header> <SOAP-ENV:Body> <mm7:SubmitReq xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_serie s/23.140/schema/REL-5-MM7-1-2"> <mm7:MM7Version>5.3.0</mm7:MM7Version> <mm7:SenderIdentification> <mm7:VASPID>VASP_TEST</mm7:VASPID> <mm7:VASID>VAS_TEST</mm7:VASID> <mm7:SenderAddress> <mm7:Number>123456</mm7:Number> </mm7:SenderAddress> </mm7:SenderIdentification> <mm7:Recipients> <mm7:To> <mm7:Number>15166771001</mm7:Number> </mm7:To> </mm7:Recipients> <mm7:MessageClass>Advertisement</mm7:MessageClass> <mm7:ExpiryDate>P1D</mm7:ExpiryDate> <mm7:DeliveryReport>false</mm7:DeliveryReport> <mm7:ReadReply>false</mm7:ReadReply> <mm7:Priority>Normal</mm7:Priority> <mm7:Subject>Check this out ---</mm7:Subject> <mm7:Content allowAdaptations="true" href="cid:mlogo_117x49.gif" /> </mm7:SubmitReq> </SOAP-ENV:Body> </SOAP-ENV:Envelope> --MAINBOUNDARY4d39cbb5.8ccb.493c.ac76.f681f63ca43a Content-Type: multipart/mixed; boundary=1f289020.9c43.4b3d.aef5.a9d02d95c5e7 Content-ID: <theactualcontent@teleios-systems.com> --1f289020.9c43.4b3d.aef5.a9d02d95c5e7 Content-Type: text/plain; charset=us-ascii this is the content --1f289020.9c43.4b3d.aef5.a9d02d95c5e7 Content-Type: image/gif Content-ID: <mlogo_117x49.gif> GIF89au 1 j?AMZw?3!♦ , u 1 ♦I8?`(dihlp,tmx|pH,→?rl:?tJZ∟!@♦Ñ♀x♦p¶►0►§☻ ☻&♠]&js+ ~☼♂‼☺c♂☼p♣pr♫♣☼ t☺↕ c♥♦‼♠♀♥lL,☻$y N^♠'‼f!|♫→<!♣♣tI ►♥5♥&4o♀p→A-`z♦K @♀{,sK1♀j☺@ai7aj▬@/X$8s‼↑♀N9`:#d %85x♂z? eb ☻4►@½.↑@D)♣♀a♦e[)Yn&→↓=E♠tPx#`↑fk"WqL=‼♀qIza<54{mYsFMv- >&,nC↨♦C ↔§-zX] ♠( ♦▬hAD ; --1f289020.9c43.4b3d.aef5.a9d02d95c5e7-- --MAINBOUNDARY4d39cbb5.8ccb.493c.ac76.f681f63ca43a-- //Message ends after the line above I have set up a VASP account, to direct the traffic into the MMS-IN folder. I have used another library to send MM7 messages to the nowsms MMSC emulator and it worked. So i suppose somethng is wrong with my MIME. Any help would be appreciated | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5226 Registered: 10-2002 |
Hi Irwin, Enable the MMSCDEBUG.LOG (easiest to do this on the Serial # page of the config), and let's take a look at what that shows when you submit this message. The forum software might have corrupted your posting above. But I'm wondering if the line breaks in the first "Content-type:" header are like shown above, or if the forum software has wrapped it. Let's see what it looks like in MMSCDEBUG.LOG, where there will be a hex dump of it. -bn | ||||
irwin williams Unregistered guest |
Hey Bryce, Thanks for your concern, I slightly modified the MIME going over the wire, by adding a boundary but there was still no change to the response. So, i've uploaded the Log.
| ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5236 Registered: 10-2002 |
Hi Irwin, I haven't had time to investigate this specifically yet. But I notice from the log file that you are running the original v5.51 release. And there have been quite a few updates with regard to MM7. Try the following patch to update your v5.51 install to v5.51k: http://www.nowsms.com/download/latestpatch.zip -bn | ||||
irwin williams Unregistered guest |
Hi Bryce, I have applied the patch according to instructions, however, the TransactionID: unknown value is still being returned. I really don't know where to look to debug the message i am sending across. I don't know if the error is in my MIME, my encoding or my XML. I appreciate your assistance, and look forward to arriving at a solution. Thank Irwin
| ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5243 Registered: 10-2002 |
Hi Irwin, Ok. I'm not sure why you're getting a success response when the message submission is not really successful. I did figure out what the problem is with the MIME encoding. There is an extra blank line between the "Content-length:" and "MIME-Version:" headers. That blank line essentially has the effect of truncating the header before you get to the "Content-type:" header. I still don't understand why a success response is being returned. But if you remove the blank line, that should resolve your problem. -bn | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5244 Registered: 10-2002 |
Follow-up ... I did some more testing, if the MMSC does not find a Content-type header in an MM7 request (which is the case in your submission, because of the blank line), then it mistakenly returns a success response, even though it doesn't actually do anything. | ||||
irwin williams Unregistered guest |
Bryce! Lo and behold, i 'removed' the new line between the HTTP Content Length and the MIME headers and it worked! Thank you very much for you patience and your efforts. I had a concern though. In my MIME documentation reading, i assumed that one could have defined all MIME related info in an HTTP transmission in a MIME object and just add that object to the stream. in doing this though, the MIME headers were separate from the HTTP headers. Is it that, MIME headers (at least in the containing MIME entity) must be a part of the HTTP headers. Is that something specific NowSMS' implementation or is it something general that I just did not note? nevertheless, thanks a lot Bryce. Irwin | ||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5290 Registered: 10-2002 |
Irwin, Sorry that I didn't respond to this earlier. It does get more than a little confusing. But "Content-type:" is both an HTTP header and a MIME header. So if you are passing a multipart MIME object in an HTTP request, you need to define its "Content-type:" in the header so that the receiver knows what type of content it is receiving. So, it's not anything unusual that we are requiring. I'm not sure exactly where to point you specification-wise, but the MM7 definition in 3GPP TS 23.140 is probably a good start (http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/). At least there you can see an MM7 example with this type of header. -bn |