| Problem in MM7 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| marc bazimon New member Username: Marc_orange Post Number: 1 Registered: 01-2007 |
Hi We currently try to do cut over from a Ericsson MMSC into the Now wireless one. For a service ( blog ) we have some trouble with the soapAction. In fact we need a soap action MultimediaDeliver instead of MultimediaSubmit see a ethereal trace below. The response from blog server are 200 but it doen't work as well. Do you know how to do to have to change the soapaction in multimediaDeliver instead of MultimediaSubmit ? thanks for your help POST /mms/servlet/messagerouter HTTP/1.1 Host: orangeblog.fr:10000 SOAPAction: "MultiMediaSubmit" Content-Length: 2057 Content-Type: multipart/related; boundary="---mime-boundary-73EEF4C9.3FD90C0A---"; type="text/xml"; start="<mm7_msg>" Connection: close -----mime-boundary-73EEF4C9.3FD90C0A--- Content-Type: text/xml; charset=utf-8 Content-ID: <mm7_msg> <?xml version='1.0' ?> <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> <MM7Header SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:xml-MM7Header"> <Transaction-ID xsi:type="xsd:string"> 20070122195036-1B0AC848@mms.orange.re </Transaction-ID> </MM7Header> </SOAP-ENV:Header> <SOAP-ENV:Body> <MultiMediaSubmit SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns="urn:MM7Submit.Req"> <Version xsi:type="xsd:string">1</Version> <Message-Type xsi:type="xsd:string">MM7Submit.Req</Message-Type> <From xsi:type="xsd:string">0692080392</From> <Recipient Recipient-Type="TO" xsi:type="xsd:string">25647/TYPE=PLMN</Recipient> <Priority xsi:type="xsd:string">Normal</Priority> <Delivery-Report xsi:type="xsd:boolean">False</Delivery-Report> <Read-Reply xsi:type="xsd:boolean">False</Read-Reply> <Subject xsi:type="xsd:string">Multimedia Message</Subject> </MultiMediaSubmit> </SOAP-ENV:Body> </SOAP-ENV:Envelope> -----mime-boundary-73EEF4C9.3FD90C0A--- Content-Type: multipart/related; start="<45B4C836.smil>"; type="application/smil"; boundary="---mime-boundary-67049E0B.09F93ACC---" Content-ID: <mms_cid> -----mime-boundary-67049E0B.09F93ACC--- Content-Type: application/smil Content-ID: <45B4C836.smil> Content-location: 45B4C836.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="45B4C836.txt" region="Text"/> </par> </body> </smil> -----mime-boundary-67049E0B.09F93ACC--- Content-Type: text/plain Content-ID: <45B4C836.txt> Content-location: 45B4C836.txt TEST ORE -----mime-boundary-67049E0B.09F93ACC----- -----mime-boundary-73EEF4C9.3FD90C0A----- HTTP/1.1 200 OK Content-Length: 974 Date: Mon, 22 Jan 2007 15:51:03 GMT Connection: close Server: Resin/2.1.17 Content-Type: text/xml <?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 SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:xml-MM7Header"> <Transaction-ID xsi:type="xsd:string"> 20070122195036-1B0AC848@mms.orange.re </Transaction-ID> </MM7Header> </SOAP-ENV:Header> <SOAP-ENV:Body> <MultiMediaSubmitResponse SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns="urn:MM7Submit.Res"> <Message-ID xsi:type="xsd:string">57e39595a6af603f</Message-ID> <Message-Type xsi:type="xsd:string">MM7Submit.Res</Message-Type> <Version xsi:type="xsd:string">1</Version> <Request-Status xsi:type="xsd:string">1000</Request-Status> <Request-Status-Text xsi:type="xsd:string">OK</Request-Status-Text> </MultiMediaSubmitResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6888 Registered: 10-2002 |
Hi Marc, Currently in NowSMS, when you use the Ericsson MM7 protocol variant, there is only support for the MultiMediaSubmit format when routing MM7 messages externally. When the standard MM7 format is used, there is support for either submit or deliver format, depending on the "Connection Type" configuration setting in the "MMSC Routing" definition. I've posted an update for NowSMS 2006 which adds support for this "Connection Type" setting when the Ericsson MM7 protocol variant is used. If you set the "Connection Type" to be "To VASP (deliver format)", then NowSMS will use the "MultiMediaDeliver" action instead of the "MultiMediaSubmit" action. The update is posted at http://www.nowsms.com/download/patch2007.zip. Give this a try, and perhaps this will resolve the issue with the blogging VASP that is expecting this format. -bn | |||
| marc bazimon New member Username: Marc_orange Post Number: 2 Registered: 01-2007 |
Hi Bryce Thanks for your reply, I had patch our mmsc et test connect to the blog server but still not work. There's one more error due to a format problem in the SOAP-ENV:Body. the error are <faultcode>SOAP-ENV:Server</faultcode> <faultstring>service 'urn:MM7Deliver.Req' unknown </faultstring> <faultactor>/mms/servlet/messagerouter</faultactor> This is the SOAP-ENV:Body format from the Ericsson MMSC currently use: <SOAP-ENV:Body> <MultiMediaDeliver xmlns="urn:MM7_deliver.REQ" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <Version xsi:type="xsd:string">5.3.0</Version> <Message-Type xsi:type="xsd:string">MM7_deliver.REQ</Message-Type> <Date xsi:type="xsd:dateTime">2006-03-14T08:35:45Z</Date> <Linked-Id xsi:type="xsd:string">1038711@mms.orange.re</Linked-Id> <From xsi:type="xsd:string">+262692080398/TYPE=PLMN</From> <Priority xsi:type="xsd:string">Normal</Priority> <Subject xsi:type="xsd:string">Test Album</Subject> <Recipient Recipient-Type="TO" xsi:type="xsd:string">36672</Recipient> <Content-Type xsi:type="xsd:string">multipart/related; type="application/smil"; boundary="----=_Part_7884_1038189.1142321745723"; start="<AAAA>"</Content-Type> </MultiMediaDeliver> </SOAP-ENV:Body> And this is the SOAP-ENV:Body format from the NOW MMSC we trying to integrate: <SOAP-ENV:Body> <MultiMediaDeliver SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns="urn:MM7Deliver.Req"> <Version xsi:type="xsd:string">1</Version> <Message-Type xsi:type="xsd:string"> MM7Submit.Req</Message-Type> <Message-ID xsi:type="xsd:string">20070125/18/7A711E52@mms.orange.re </Message-ID> <From xsi:type="xsd:string">0692080392</From> <Recipient Recipient-Type="TO" xsi:type="xsd:string">25647/TYPE=PLMN</Recipient> <Priority xsi:type="xsd:string">Normal</Priority> <Delivery- Report xsi:type="xsd:boolean">False</Delivery-Report> <Read-Reply xsi:type="xsd:boolean">False</Read-Reply> <Subject xsi:type="xsd:string">test ore</Subject> </MultiMediaDeliver> </SOAP-ENV:Body> As you can see the value for xmlns in the MultiMediaDeliver mark out are urn:MM7Deliver.Req instead of urn:MM7_deliver.REQ. Is it possible to change the value from the now MMSC in order to match with the E/// one? Another error is that the field xsi:type "FROM" and "Recipient" are in the different format ( /TYPE=PLMN are missing or adding ) . In the NOW mmsc this field ( /TYPE=PLMN) is missing for the originating and ad for the recipient ( which is the short code number from the blog service ). How this information is managed with NOW MMSC and how we can change it ? Thanks for your help, it is a blocking problem for us, Regards, Marc | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6891 Registered: 10-2002 |
Hi Marc, Apologies for the delay. We do not have any specifications that define the format for Ericsson's proprietary MM7 deliver message. (The submit message format that we use simply uses a format similar to what their SDK generates.) So, the example that you have posted is helpful. We've made changes to the Ericsson MM7 deliver format similar to what you have described above. MM7Deliver.Req changed to MM7_deliver.REQ Message-Type value changed to MM7_deliver.REQ Date element added Message-ID element changed to Linked-ID element From - now includes /TYPE=PLMN Recipient - no longer includes /TYPE=PLMN (Note: interesting that From/Recipient inclusion of /TYPE=PLMN is reverse of what is expected of submit format.) Content-Type element added Hopefully this will resolve your remaining issues. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6892 Registered: 10-2002 |
P.S. - Sorry, forgot to mention ... same download URL as before http://www.nowsms.com/download/patch2007.zip | |||
| marc bazimon New member Username: Marc_orange Post Number: 3 Registered: 01-2007 |
Hi Bryce, No problem for delay we are all busy in the GSM World ;) Thanks for your reply , i will apply the patch asap and tell you if it is ok. By the way i was looking for your IMP server, it looks good, we had interest for this ( and i see that your name is in the IMP documentation , is it you the developper ;) ? ). I will maybe contact you via Volubill to have some information on it. Regards , Marc | |||
| marc bazimon New member Username: Marc_orange Post Number: 4 Registered: 01-2007 |
Hi Bryce Thank you, the patch resolve the problem and we can swap the MMSC Ericcson now. As i said , we will contact you via volubill for IMP server, do you have some marketing issue for this product? roadmap , value added service for this ? Best regards, Marc | |||
