Unable to setup mm7 account

Unable to setup mm7 account SearchSearch
Author Message
Sajid Ahmed
New member
Username: Sajid

Post Number: 31
Registered: 10-2008
Posted on Monday, March 16, 2009 - 08:53 am:   

Hi Des,

I got my MM7 account details


http://host:port
VASID: xxxxx
VASPID: xxx

Ericsson

I configured MMSC Routing tab as describe in

http://blog.nowsms.com/2009/02/connecting-to-operator-mmsc-with-mm7.html

but i am not able to send mms.in begining i got error messages as port already in use.
Its like smsc is also on same machine so i change http port to 880 and smtp port to 225.
Now i got connected .I selected default route which i have configured.i even selected non-standard variation--> Ericsson,connection type-->to mmsc(submit format).i send messages and i am not able to recieve mms.
Please help me to figure out the problem.find attached log and debug files..
C:\Program Files\NowSMS\MMSCDATA\20090316\02

54F10980.INI

[Message]
Sender=
Subject=MMS Account Setting
DeliveryNotification=No
OriginalMessageID=20090316/02/54F10980@74.55.121.226


A2E99D0C.INI

[Message]
Sender=
Subject=MMS Account Setting
DeliveryNotification=No
OriginalMessageID=20090316/02/A2E99D0C@74.55.121.226

it will be nice of you if you can explain what all happens and where data is stored in nowsms and proceesed further .The way nowsms works technically where data is check and how to visualize the error by seeing debug log and what to do to resolve it as we may not come to you unless we give our tries...


Thanks,

Sajid
application/octet-streamAll nessary files to find mmsc conection error
MMSC ERRORS.rar (80.2 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 601
Registered: 08-2008
Posted on Tuesday, March 17, 2009 - 04:44 pm:   

Hi Sajid,

Troubleshooting the initial setup of these connections is extremely difficult.

We're trying to think of ways to make it easier. But it's difficult because there are so many possibilities of what could be wrong.

In this case, the MMSC is returning an HTTP response with error 400, simply indicating an "Invalid Request".

In most cases, this would mean that you are connecting to the wrong server.

But I do notice something interesting in the debug. The following header is present in the HTTP response:

x-nokia-mmsc-version: 4.0

Based upon this response, I don't think it's an Ericsson MMSC. I think it's a Nokia MMSC.

A Nokia MMSC would definitely not support the proprietary Ericsson format.

So set the "Non-standard MM7 Variation" setting to "None" instead of "Ericsson".

Nokia MMSCs tend to be very particular about schema versions. (See the discussion about confusion over MM7 schemas and MMS versions at http://blog.nowsms.com/2009/03/mm7-schemas-and-mms-version-number.html.)

Nokia supports 3GPP MMS version 5.5.0 and 6.3.0.

However, version 5.5.0 has a bug in the XML schema that requires itself to identify itself as 5.3.0.

So what you want to do is use one of the following settings:

MM7 Schema = REL-5-MM7-1-2
MMS Version = 5.3.0

OR

MM7 Schema = REL-6-MM7-1-0
MMS Version = 6.3.0

But wait ... there's more ...

If this is indeed a Nokia MMSC, then I don't think your provider has given you the complete URL.

It wouldn't be just http://host:port ...

With Nokia MMSCs, it is usually:

http://host:port/mmsc/mm7/MMSServiceSOAPPort if you are using the REL-5-MM7-1-2 schema.

Or, http://host:port/mmsc/mm7/MMSServiceSOAPPort630 if you are using the REL-6-MM7-1-0 schema.

You might want to verify this information with your provider. Perhaps the "x-nokia-mmsc-version: 4.0" in the response is another MMSC trying to emulate a Nokia MMSC, and it is possible that the URL without a path will work.

So my suggestion would be first to disable the Ericsson proprietary mode, and try the REL-5-MM7-1-2 schema.

If that is still failing, try changing the URL.

If both attempts fail, then I'd like to see MMSCDEBUG.LOGs of both attempts to see if that provides any other clues.

--
Des
NowSMS Support