Email to MMS decode failure...

Email to MMS decode failure... SearchSearch
Author Message
abhishek gupta
New member
Username: Abhigup40

Post Number: 5
Registered: 11-2008
Posted on Thursday, November 20, 2008 - 04:49 am:   

If i send email to "mms email address" of my cell number, nowMMS recieves it and sends it to my VASP application over mm7 interface.

This VASP application is not accepting this message saying that nowMMS sent wrong xml data. I suspect that nowMMS is adding "bcc" field, which is having wrong information. Is it possible to disable "bbc" field in mm7 message or is there something else which is wrong.
====================================================
Logs of mm7 message from nowMMS to my VASP Application:



<?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-6-MM7-1-4" env:mustUnderstand="1">20081119204753-9AF9D613@10.7.5.153</TransactionID>
</env:Header>
<env:Body>
<DeliverReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4">
<MM7Version>6.8.0</MM7Version>
<Sender>
<RFC2822Address>guptaa@qualcomm.com</RFC2822Address>
</Sender>
<Recipients>
<To>
<Number displayOnly="true">+18582326439/TYPE=PLMN</Number>
</To>
<Bcc>
<Number>ê+18582326439</Number>
</Bcc>
</Recipients>
<Subject>RE: test mms with text</Subject>
<Content href="cid:mms_cid" />
</DeliverReq>
</env:Body>
</env:Envelope>

-----mime-boundary-34858E96.E1C68197---
Content-Type: multipart/mixed; boundary="---mime-boundary-F144C8D4.F248D655---"
Content-ID: <mms_cid>

-----mime-boundary-F144C8D4.F248D655---
Content-Type: text/plain; charset=utf-8

Text only...

-----mime-boundary-F144C8D4.F248D655-----

-----mime-boundary-34858E96.E1C68197-----

=====================================================
Error response from VASP application to nowMMS




Debug: 2008 Nov 19, 20:47:53 Nr=0 cmm7_servlet.cpp:1093
MM7 Servlet responding with body:<?xml version="1.0" encoding="UTF-8"?>
<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-0" env:mustUnderstand="1"/>
</env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Client</faultcode>
<faultstring>Validation error</faultstring>
<detail><VASPErrorRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0">
<MM7Version>5.3.0</MM7Version>
<Status>
<StatusCode>4004</StatusCode>
<StatusText>Validation error</StatusText>
<Details>XML Parse error: not well-formed (invalid token) at line 17.
</Details>
</Status>
</VASPErrorRsp>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
abhishek gupta
New member
Username: Abhigup40

Post Number: 6
Registered: 11-2008
Posted on Thursday, November 20, 2008 - 08:33 am:   

After following more thread on discussion forum, seems like problem is "+" sign in recipient list...is it possible to remove them?

Thanks
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7697
Registered: 10-2002
Posted on Thursday, November 20, 2008 - 07:18 pm:   

Hi,

I'm suspicious about that "ê" character before the "+".

I suspect there is some unexpected UTF-8 encoding happening somewhere along the route.

That's the character that would be causing a problem for the XML parsing.

(The "+" character is a problem in that it is not allowed in phone numbers for some of the earlier versions of the MM7 XML schema, but it gets automatically removed if NowSMS is configured to use one of the earlier version schemas.)

There might be an easy solution to this problem.

On the "SMSC" list, go into "Properties" for the modem. Set the "Phone Number" to be your phone number. I think you're fine to include a "+", but you can try with and without.

That number is what should show up as the "To:" field.

If problems persist, enable both the SMSDEBUG.LOG and MMSCDEBUG.LOG. Repeat the sequence, and e-mail those two files to nowsms@nowsms.com with "Attention: Bryce" in the subject line, and I'll take a closer look to see what is happening.

-bn