| M7 Configuration/ Error |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 07, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Walhan New member Username: Walhan Post Number: 11 Registered: 11-2008 |
Hi, We want to make test with MMS functionality for nowsms. Our aim is to make MMS sent successfully through operator using MM7. Ofcourse I configured MMSC Routing and set it as default route  Now, the results of sneing MMS is mystry for me: When I send MMS having text only from Web Menue the web will give this messege: MMSMessageID=20090227/13/8AD34E5B and at service page, the "MMS Process (User)" is incremented by one and no other counter adds. and when refering to the log MMSC20090227.LOG, it shows: 2009-02-27 13:19:22,MMSOUT,VASP:MMS Test,,xxxxxnumber,Retry Pending - Unable to deliver message,E0462D7F.MMS 2009-02-27 13:19:27,MMSOUT,VASP:MMS Test,,xxxxnumber,Retry Pending - MM7 - got unknown response - HTTP status - 500 Internal Server Error,E0462D7F.MMS ------------------------ -----mime-boundary-BD5A8781.9F11D8C2-- 13:22:29:843 [12] HttpResponseWait: Ok 13:22:29:843 [12] ThreadProcessVASPQ: MM7 - got unknown response - HTTP status - 500 Internal Server Error 13:22:29:843 [12] ThreadProcessVASPQ: HTTP/1.1 500 Internal Server Error content-type: text/xml; charset="utf-8" Content-Length: 280 <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <faultcode>soap:Client</faultcode> <faultstring>Client error</faultstring> </soap:Fault> </soap:Body> </soap:Envelope> 13:22:29:843 [12] ThreadProcessVASPQ: Outbound route HerHis: setting retry for E0462D7F.MMS 13:23:04:859 [12] ThreadProcessVASPQ: recipArray count = 1 13:23:04:890 [12] InetServerConnect: Connected to xxx.xxx.xxx.xxx:port (xxx.xxx.xxx.xxx:Port) 13:23:04:890 [12] ThreadProcessVASPQ: POST /mmsc/mm7/MMSServiceSOAPPort630 HTTP/1.1 Host: xxx.xxx.xxx.xxx:Port SOAPAction: "" Content-Length: 1835 Content-Type: multipart/related; boundary="---mime-boundary-29C3F27C.D933CDFD"; type="text/xml"; start="<mm7_msg>" 13:23:04:890 [12] ThreadProcessVASPQ: -----mime-boundary-29C3F27C.D933CDFD 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-6-MM7-1-3" env:mustUnderstand="1">20090227132304-A8EFC079@78.93.29.170</TransactionID></env:Header><env:Body><SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-3"><MM7Version>6.3.0</MM7Version><SenderIdentification><VASPID>STC</VASPID><VASID>Betterlife</VASID><SenderAddress><Number>804611</Number></SenderAddress></SenderIdentification><Recipients><To><Number>0555425809</Number></To></Recipients><ServiceCode>8041</ServiceCode><MessageClass>Personal</MessageClass><DeliveryReport>false</DeliveryReport><ReadReply>false</ReadReply><Priority>Normal</Priority><Subject>f</Subject><Content href="cid:mms_cid" /></SubmitReq></env:Body></env:Envelope> -------------------------- Any direction please? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 524 Registered: 08-2008 |
Hi Walhan, Try changing the MM7 Schema version to REL-6-MM7-1-0. For the MMSC that you are talking to (looks like a Nokia), that is required. -- Des NowSMS Support | |||
| Walhan New member Username: Walhan Post Number: 12 Registered: 11-2008 |
Thank you it is working | |||
| tekken New member Username: Tekkenmaster2008 Post Number: 1 Registered: 03-2009 |
Hello, I had experience the same situation with Huawei MMSC, any specific issues with this MMSC platform? I tried using: • 3GPP MMS Version : 6.3.0 • MM7 Schema : REL-6-MM7-1-0 • MMSC Platform : Huawei Appreciating your feedback. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 662 Registered: 08-2008 |
Hi, Can I see the MMSCDEBUG.LOG to see what information you're getting back? I would go with REL-5-MM7-1-2 and 3GPP MMS Version 5.3.0 (it's actually 5.5.0 but the schema requires the wrong version number to be specified). This is a good baseline version for most MMSCs (except Comverse which likes REL-5-MM7-1-0 and version 5.3.0). Actually, the version information might not be an issue. I've looked through some past support incidents, and it appears that people had the most success with REL-6-MM7-1-0 and version 6.3.0. So, I'd be curious to see what the MMSC is reporting back in the MMSCDEBUG.LOG. Chances are that it is either a wrong URL that you have been given ... or the operator firewall is not opened to your IP address ... or the account on the MMSC is not authorized for your IP address ... or there is some other authentication problem. From past experiences interfacing with a Huawei MMSC over MM7, we've noted that the "VASPID", "VASID" and "Service Code" parameters are all usually required (although it is up to the operator which parameters might be required). Also make sure that your "Default Sender Address" is configured with a value that is acceptable to the provider. -- Des NowSMS Support | |||
