| MMS File |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| kannan N |
Hi Currently I am involve creating MMS file. The thing is that, I am creating the .mms file using java API's from nokia. Their source code can create the headers and bodys. There is this code as show below taken from the nokia Java API: sender.setMMSCURL("http://127.0.0.1:8189"); sender.addHeader("X-NOKIA-MMSC-Charging", "1"); I changed the http to the MMSc gateway base on our IP then the .mms file is send to this URL upon running the Java program. At this point I didn't create a SMIL file cause it is for testing. The Java output test says "message send to http://IP, response 200 ok". I didn't get the message via email or even via phone. Can this work or whether "now mms gateway" work with other kinda of programs? Please advise me on this and the right way. I when through the documentation of the site "Creating the mms message" but seems to be different from my way. Thanks in advance rgds kannan | |||
| Bryce Norwood - NowSMS Support |
Kannan, Those Nokia APIs expect to submit a message to a Nokia MMSC via the EAIF protocol (a Nokia proprietary/slight variation of MM1). By contrast, the MMSC in NowSMS is expecting actual MM1, which is the protocol that is used for phone-to-MMSC connections. As EAIF is a slight variation on MM1 ... you can usually get an EAIF application to work on MM1 ... there are just a couple of issues: 1.) The error reporting is different. EAIF expects an error in the HTTP header. With MM1, the HTTP response might be "200 Ok", but an MMS-specific error is embedded in the response (this sounds like what is occurring in your situation). 2.) With EAIF, message recipients can be specified in an HTTP header "X-Nokia-MMSC-To:". With MM1, the recipients must be specified in the To/Cc headers within the MMS message itself. Back to your specific issue ... I suspect the MMSC is returning an MMS error response back indicating that it cannot identify who the user is that is submitting the message. If you look at the MMSC-yyyymmdd.LOG file in the NowSMS subdirectory, assuming the connection is making it from your application to the MMSC, there should be a log entry that says "FAILED", and "User Not Defined". You need to register a user account in the "MMSC Users" list. And then you need to modify your "MMSCURL" in the application to include the username and password (e.g., http://127.0.0.1:8189/username=password). Then, as long as you set the message recipients in the MMS message that you are submitting, as opposed to the EAIF headers, you should be fine. -bn P.S. - The upcoming v5.0 release of the Now SMS/MMS Gateway adds direct support for EAIF, so the gateway can receive EAIF connections directly (and support the Nokia proprietary headers), and it can also output EAIF to a Nokia MMSC. | |||
| kannan |
Dear Bryce, Sorry for the delay Yes I ,saw/checked the MMSC-Log file. here is the errors as shown "2003-07-14 16:32:30,MMSIN,203.94.112.254,,,User Not Defined,FAILED 2003-07-14 16:34:51,MMSIN,203.94.112.254,,,User Not Defined,FAILED" As u requested me to create a new user right. If in the MMSC user the name is there plus the phone no. How should I modify my MMSCURL if no password? http:/127.0.0.1:8189/kannan Must I really have a password. Thanks Rgds Kannan | |||
| Bryce Norwood - NowSMS Support |
Kannan, http:/127.0.0.1:8189/kannan is fine. A password is not required. If you then see log entries like this: 2003-07-14 16:34:51,MMSIN,203.94.112.254,kannan,,User Not Defined,FAILED But "kannan" is defined on the MMSC Users list, try defining a second user. I've seen a couple of tech support incidents recently where when only one user account was defined, the MMSC was not picking it up. I haven't been able to recreate the problem, but I mention it just in case you do see that problem. -bn | |||
| Bryce Norwood - NowSMS Support |
Follow-up ... Minor note, but of course there would be 2 slash (/) characters after the "http:" ... http://127.0.0.1:8189/kannan | |||
| kannan |
Hi Bruce, I really appreciate your help. Ok as you mention, I have this error log in the MMSC log file as shown. 2003-07-21 09:22:10,MMSIN,219.94.112.254,+60192360985,,User Not Defined,FAILED 2003-07-21 09:28:22,MMSIN,219.94.112.254,+60192360985,,User Not Defined,FAILED 2003-07-21 09:29:10,MMSIN,219.94.112.254,+60192360985,,User Not Defined,FAILED 2003-07-21 09:31:22,MMSIN,219.94.112.254,+60192360985,,User Not Defined,FAILED 2003-07-21 09:38:06,MMSIN,219.94.112.254,+60122137989,,User Not Defined,FAILED 2003-07-21 09:56:15,MMSIN,219.94.112.254,+60192360985,,User Not Defined,FAILED 2003-07-21 09:56:48,MMSRETRIEVE,203.82.64.225,,,20030715/09/3F135D7Aa.MMS,OK 2003-07-21 10:19:21,MMSIN,219.94.112.254,+60192360985,,User Not Defined,FAILED 2003-07-21 10:22:50,MMSRETRIEVE,203.82.64.225,,,20030715/09/3F135D76a.MMS,OK 2003-07-21 10:27:36,MMSIN,219.94.112.254,+60192360985,,User Not Defined,FAILED 2003-07-21 10:31:03,MMSIN,219.94.112.254,+60192360985,,User Not Defined,FAILED I wonder why the log file is not showing the user name, instead the phone no of the user. For example the number 0192360985 is my hp no. If I recreate, that means I have to remove my name and re-insert information again. But I tried sending via the default NOWMMS browser, it works without recreating my username. At my java program , I inserted, "sender.setMMSCURL("http://202.184.118.29/kannan");" I don't see the username appearing at all. My IP is 219.94.112.254 as shown on the log report Rgds Kannan | |||
| Bryce Norwood - NowSMS Support |
Kannan, It looks like the system is seeing that "kannan" is an alias for "+60192360985", but it doesn't find "+60192360985" in the user file. In the "MMSC Users" list, try adding a dummy entry without deleting your "kannan" entry ... for example, enter in "dummy" as the alias name, and 12345 as the phone number. Then you should have both "kannan" and "dummy" appearing in the list. Does it then work? If it does, try deleting the "dummy" account, and try again. My experience has been that it will still work after you create and then delete this second user. -bn | |||
