NowSMS does not process M-Send.req msg

NowSMS does not process M-Send.req msg SearchSearch
Author Message
Eddy Kvetny
Unregistered guest
Posted on Thursday, November 11, 2004 - 01:27 pm:   

Hi,

We've purchased the NowSMS gateway for testing our MMS and WAP Push-based applications.

Now I try to send the M-Send.req messages (SMIL-formatted with only 1 text content). The message is received by MMSC (see attached MMSDEBUG.LOG) but immediately after "Got application/vnd.wap.mms-message" I see "Processing Complete" in the log and then HTTP 500 Internal Error is sent (see the attached sniffer snapshot).

What am I doing wrong ? We are using v.5.50 with the attached GSM/GPRS modem

Thanks in advance for assistance
application/x-zip-compressedMMSDEBUG_LOG and sniffer snapshot
NowSms.zip (152.7 k)
Eddy Kvetny
New member
Username: Eddyk

Post Number: 1
Registered: 11-2004
Posted on Thursday, November 11, 2004 - 03:05 pm:   

In continuation of the previous mail ...

After resetting the PC where NowSMS runs the situation got better:

1. In the log I see the following:

Got application/vnd.wap.mms-message
Got m-send-req
Processing Complete

2. Instead of HTTP Error 500 the correct M-Send.conf message (with "Sending Address unresolved" 0x84) is received. Could you please tell me why the correct phone number from CC field can't be resolved ?

Thanks in advance
Eddy Kvetny
New member
Username: Eddyk

Post Number: 2
Registered: 11-2004
Posted on Thursday, November 11, 2004 - 04:43 pm:   

Please ignore both previous messages (by the way, it might be worth allowing at least registered users to delete their messages :-)

The problem was that I forgot to configure the MMSC user at the NowSMS server and used wrong MMSC URL (without user=name). I fixed it and it started working - WAP Push SMS was sent to the recepient client.

Now, I have two other questions:

1. I configured an MMSC user with name "Admin" and some password to be able to configure the MMSC via WEB interface (http://x.x.x.x/Admin). Then I enter configured name "Admin" and password into the authentication windows opened by the WEB Browser but keep getting reject constantly. Do I miss something here ?

2. I send M-Send.req with X-Mms_Version of MMS 1.2 version but NowSms responses with M-Send.conf with MMS 1.0. Does NowSms support MMS 1.0 only ? Does it mean that NowSMS will reject the Read Report PDU (defined in MMS 1.1) ? Should my MMS client take into account the MMS version in messages from MMSC and, for example, to send Read Report as an MMS message rather than PDU ?

Thanks for your assitance
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3734
Registered: 10-2002
Posted on Thursday, November 11, 2004 - 07:54 pm:   

Hi Eddy,

If there is proprietary information that you would like to have deleted from a message, we will accomodate you. But overall, we don't like messages to be deleted because others learn from these message exchanges (even if so far, the dialog has mostly been with yourself ).

Before I get to your most recent questions, it may be worth noting in your original ZIP that the content that is being posted is not proper formatting for "application/vnd.wap.mms-message". It appears to be a text encoding of an MMS message, but the actual "application/vnd.wap.mms-message" content type is the binary MMS encapsulation format defined by the Open Mobile Alliance (OMA).

Now to the questions ...

1.) I'm not aware of any problems in this area. Are you using Internet Explorer as your browser? I just tried with both IE and Firefox, and I don't see any problems. Try changing the username and password, and see if that makes a difference.

2.) We do not support the read report PDU (although we do plan to do so in the future). You should take the version number into account when deciding whether to submit it as an read report PDU, or a standard MMS message with text information about the message having been read.

Unfortunately, determining this version is difficult (and this is one of the reasons why we have not implemented support for this PDU yet, because we will have to track versions for each client).

My advice would be to track the server's version based upon the version that you get back in the M-Send.conf, as you have suggested.

It would be nice if the GET transaction that is used to retrieve the M-Retrieve.conf identified the version number supported by the client, so that the server could adjust the version before retrieving the message ... but it does not. As such, the version in the M-Retrieve.conf may reflect the version of the sending client.

-bn
Eddy Kvetny
New member
Username: Eddyk

Post Number: 3
Registered: 11-2004
Posted on Friday, November 12, 2004 - 11:04 am:   

Bryce,

Thanks a lot for your quick response. I must admit that I learned a lot about MMS/WAP from your responses in NowSMS forums.

1. Regarding wrong MMS content type. Our MMS client shoud support both binary and textual encoding. So which content type must be used for textual encoding ? (standard MIME types with "related"/"mixed"/"alternate"). Does all MMSC support both encoding or some of them support the binary one only ?

2. Regarding administration problem: I am using the IE as an WEB explorer. An user with "Admin" as user, password and alias was added - anything else should be done ? I tried it from other PCs also but with the same result. Is it supported in v.5.50 ?(I saw in the release note of v.5.51 the mention of the WEB-based administration). Probably we should upgrade our NowSMS to v.5.51 to use the WEB-based MMSC configuration ?

3. As far as I understand NowSMS doesn't need to track the client's MMS version to receive MMS Read Report PDU from the recepient. It should be done for forwarding the Read Report to the originator. So, if NowSMS does not support version tracking, it probably can be able to receive the MMS Read Report PDU but should always convert it to the Read Report MMS message before forwarding to the originator (as it is described in the MMS transaction/encapsulation specs).
Eddy Kvetny
New member
Username: Eddyk

Post Number: 5
Registered: 11-2004
Posted on Sunday, November 14, 2004 - 07:53 am:   

Hi,

It's me again (really the dialog with myself )...

After upgrade of NowSMS to v.5.51 and checking the WEB configuration checkbox on the configuration screen everything is OK and I am able to configure MMSC/SMS users via WEB-interface