Problem while sending MM7 packet from NowSMS.

Problem while sending MM7 packet from NowSMS. SearchSearch
Author Message
Ravichandra
New member
Username: Ravichandra

Post Number: 7
Registered: 05-2006
Posted on Thursday, February 22, 2007 - 03:12 pm:   

Hi,
We are not able to send MM7 packets from our server to Operator MMSC server. We are getting “500 Internal Server Error”, please find the error logs,

-----mime-boundary-06BD023F.AAECCE00---
Content-Type: text/plain
Content-ID: <45DD84AD.txt>
Content-location: 45DD84AD.txt
Text part in MMS
-----mime-boundary-06BD023F.AAECCE00-----
-----mime-boundary-6D9CBAFD.679F813E-----
17:30:11:546 [9] HttpResponseWait: Ok
17:30:11:546 [9] ThreadProcessVASPQ: mm7 - got unknown response

17:30:11:546 [9] ThreadProcessVASPQ: HTTP/1.0 500 Internal Server Error
Content-Type: text/xml; charset=utf-8
Content-Length: 521
Set-Cookie: JSESSIONID=xipoz5kep1;Path=/soap
Date: Thu, 22 Feb 2007 11:48:51 GMT
Server: Tomcat Web Server/3.3 Final ( JSP 1.1; Servlet 2.2 )
<?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:Body>

<SOAP-ENV:Fault>

<faultcode>SOAP-ENV:Server</faultcode>

<faultstring>service 'http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2' unknown</faultstring>

<faultactor>/soap/servlet/messagerouter</faultactor>

</SOAP-ENV:Fault>


</SOAP-ENV:Body>

</SOAP-ENV:Envelope>



17:30:11:546 [9] ThreadProcessVASPQ: Outbound route bsnl: setting retry for 11727481.MMS

Please help...

Regards,

Ravichandra.

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6935
Registered: 10-2002
Posted on Tuesday, March 06, 2007 - 08:36 pm:   

This is hard to say. You probably have to talk to your provider.

The server that you are connecting to is understanding that a SOAP request is being posted to it. However, it does not like the schema/service setting.

Based upon the URL that you are posting to ... I'm guessing that you might be connecting to an Ericsson MMSC, which doesn't really understand MM7. You need to select "Non-Standard MM7 Variations" = "Ericsson" in the configuration of the MM7 connection in NowSMS.

If that does not make a difference, go back to the standard setting, and try different values for the "MM7 Schema", as that seems to be what the service is rejecting. However, all you could do here is guess which schema the provider wants you to use. So you'd probably be better off asking them.

-bn
Ravichandra
New member
Username: Ravichandra

Post Number: 9
Registered: 05-2006
Posted on Friday, March 09, 2007 - 08:57 am:   

I checked with operator and found that its nokia MMSC that they are using. Does this info help in narrowing down the prorblem.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6970
Registered: 10-2002
Posted on Monday, March 12, 2007 - 07:43 pm:   

Usually Nokia uses the EAIF protocol.

I understand that they have added MM7 support in recent versions of their MMSC. But I don't recall anyone having provided any feedback on using MM7 directly with a Nokia MMSC.

I have reviewed available technical information from Nokia. And I can see that they are picky about the MM7 schema version that is used ... however, http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2 is one of the versions that they support, and it appears to be preferred.

They prefer that you set the "3GPP MMS Version" to "5.5.0" (instead of our default of "5.3.0".

However, I don't think this will resolve the problems that you are experiencing.

Nokia's documentation clearly states that the POST URI should contain "/mmsc/mm7/MMSServiceSOAPPort".

Does the "Server Address" URL that you are using include this?

The "Login Name" and "Password" fields should be blank (although Nokia suggests they will be ignored).

"VASP ID" and "VAS ID" are mandatory.

"Service Code" is probably required by your operator, so make sure you are using an appropriate value.

I'm guessing that the URL that you are using is wrong, or maybe there is an issue with one of these other parameters.

-bn