A quick scan suggests that this is a non-standard MM7 implementation,
which Mbuni does not speak. Do they document the protocol fully for
starters?
On Jul 15, 2008, at 09:22, Marco Lopes wrote:
I was having some trouble compiling the latest CSV but I finally
managed
to do it, the problem is solved. The only remaining problem is to
connect to the Vodafone PT MMSC. The claim to be using some sort of
ericsson version of the MM7 protocol. I spoke with some people from
ericsson and the specification they gave me is nothing like the
vodafone
PT format.
Ericsson says their mm7 protocol is an extension to MM7 5.2.0, the
schema is supposed to be the an extension to this
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-1
but the vodafone PT XML doesn't look much like it. Is it possible
to generate such a XML from mbuni?
The vodafone example XML is the following:
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/1999/XMLSchema";>
<SOAP-ENV:Header>
<MM7Header xmlns:ns1="urn:xml-MM7Header"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/
encoding/"><Transaction-ID xsi:type="xsd:string">Mbuni-g-
qf8133.7.x756.33</Transaction-ID></MM7Header>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<MM7SubmitReq xmlns="urn:MM7Submit.Req"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
<Version>5.2.0</Version>
<Message-Type xsi:type="xsd:string">MM7Submit.Req</Message-Type>
<VASP-ID>HL</VASP-ID>
<VAS-ID>3006</VAS-ID>
<From xsi:type="xsd:string">3006
</From>
<Recipient Recipient-Type="TO"
xsi:type="xsd:string">+35191xxxxx</Recipient>
<Expiry-Date xsi:type="xsd:dateTime">2008-05-21T17:02:12Z</Expiry-
Date>
<Delivery-Report xsi:type="xsd:boolean">true</Delivery-Report>
<Subject xsi:type="xsd:string">MMS piacaba</Subject>
<Content href="cid:c1210853769.1954278474.Kv.msg"/>
</MM7SubmitReq>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
On Tue, 2008-07-15 at 07:27 -0700, Paul Bagyenda wrote:
Can you ask the MMSC provider to give you sample MM7 packets. I'll
then be able to advise you on what flags to use.
On Tue, Jul 15, 2008 at 3:10 AM, Marco Lopes <[EMAIL PROTECTED]
> wrote:
I read the cvs-20080530 documentation, and tried the flag to
remove the
mm7: prefix. Still the MMSCs returned a validation error. The
strangest
thing is that I get a validation error from 2 different MMSCs from
different mobile companies, both using version 5.3.0 with the
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2
schema.
I could not find any other flag or directive to change the XML.
Thanks.
On Wed, 2008-07-09 at 08:23 +0300, P. A. Bagyenda wrote:
The mm7: prefix should not matter. However if you read the
documentation (CVS) there is a way to control whether it appears or
not (use-mm7-soap-namespace-prefix) and also to control the name
space
URL.
P.
On Jul 08, 2008, at 18:57, Marco Lopes wrote:
I've been comparing the XML sent and the working example that
the MMSC
admin sent-me and the difference seems to be on the XML
Envelope. The
XML my mbuni instalations is sending uses the mm7: prefix on the
tags
and the example don't. I found some examples on the mailling
list that
seem to be laking this mm7: prefix, how can I configure mbuni to
use
this XML format?
Here is the working example sent by the MMSC admin:
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns: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_series/23.140/schema/REL-5-MM7-1-2
">af20dc7d33db4957</mm7:TransactionID>
</SOAP-ENV:Header>
<SOAP-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>3700</VASPID>
<VASID>3700</VASID>
<SenderAddress>
<Number>3700</Number>
</SenderAddress>
</SenderIdentification>
<Recipients>
<To>
<Number>931084004</Number>
</To>
</Recipients>
<MessageClass>Personal</MessageClass>
<DeliveryReport>false</DeliveryReport>
<Priority>Normal</Priority>
<Content allowAdaptations="true" href="cid:%3Csmil.smil%3E"/>
</SubmitReq>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
On Mon, 2008-07-07 at 16:26 +0100, Marco Lopes wrote:
The response XML is the following:
<?xml version="1.0"?><SOAP-ENV:Envelope
xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2
" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/
envelope/"><SOAP-
ENV:Body><SOAP-ENV:Fault><SOAP-ENV:faultcode>SOAP-ENV:Client</
SOAP-
ENV:faultcode><SOAP-ENV:faultstring>4817:Validation error</SOAP-
ENV:faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-
ENV:Envelope>!
On Mon, 2008-07-07 at 17:58 +0300, P. A. Bagyenda wrote:
The first XML definitely wasn't sent by Mbuni (transaction ID
format
is different). Could you show us the error you are getting?
On Jul 07, 2008, at 16:38, Marco Lopes wrote:
Hi,
I've been trying to send MMS using the cvs-20080530 version of
Mbuni.
Previously I've sent MMS using a version from May 2007 and was
able to
send, now the MMSC i'm trying to connect to reply with a
Validation
Error. It seems that the problem is a difference in the XML
format.
I'm
specifying the version on the configuration.
The configuration:
group = mmsc
id = 3006
mmsc-url = http://3006:[EMAIL PROTECTED]:10021/vas_soap
incoming-port = 9393
mm7-version = 5.3.0
mm7-soap-xmlns =
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2
type = soap
allowed-prefix = 93;+35193;35193;0035193
The old XML was:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/
envelope/">^M
<env:Header>^M
<mm7:TransactionID
xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2
" env:mustUnderstand="1">ADzy94Qs4uUZWtE0D</
mm7:TransactionID>^M
</env:Header>^M
<env:Body>^M
<DeliveryReportReq
xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2
">^M
<MM7Version>5.3.0</MM7Version>^M
<MMSRelayServerID>MMH1</MMSRelayServerID>^M
<MessageID>FE53FDBA-1DD1-71B2-B864-832D59240000</MessageID>^M
<Recipient><RFC2822Address>351931084662/TYPE=PLMN</
RFC2822Address></
Recipient>^M
<Sender><RFC2822Address>+3006/[EMAIL PROTECTED]</
RFC2822Address></Sender>^M
<Date>2008-04-16T16:42:42Z</Date>^M
<MMStatus>Expired</MMStatus>^M
</DeliveryReportReq>^M
</env:Body>^M
</env:Envelope>^M
The new XML is:
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
<SOAP-ENV:Header>
<mm7:TransactionID
xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2
" SOAP-ENV:mustUnderstand="1">Mbuni-v-jo-qf7891.1.x243.72</
mm7:TransactionID>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<mm7:SubmitReq
xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2
">
<mm7:MM7Version>5.3.0</mm7:MM7Version>
<mm7:SenderIdentification>
<mm7:VASPID>3006</mm7:VASPID>
<mm7:VASID>3006</mm7:VASID>
<mm7:SenderAddress>3006</mm7:SenderAddress>
</mm7:SenderIdentification>
<mm7:Recipients>
<mm7:To>
<mm7:Number>+351936390553</mm7:Number>
</mm7:To>
</mm7:Recipients>
<mm7:TimeStamp>2008-07-02T14:11:31Z</mm7:TimeStamp>
<mm7:ExpiryDate>2008-07-09T13:11:31Z</mm7:ExpiryDate>
<mm7:DeliveryReport>true</mm7:DeliveryReport>
<mm7:Subject>MMS piacaba</mm7:Subject>
<mm7:Content href="cid:c1215436162.831068742.Bm.msg"/>
</mm7:SubmitReq>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.mbuni.org/mailman/listinfo/users
