How do I host my content on a server seperate from NOWSMS

How do I host my content on a server seperate from NOWSMS SearchSearch
Author Message
jerrel
New member
Username: Jerrel

Post Number: 9
Registered: 02-2004
Posted on Thursday, January 26, 2006 - 01:07 pm:   

Dear Bryce,
I would like to know how I can make the content requested by a customer available on another server. This after nowsms formatted it according to the UAPROFS.
I want to do this, because on the server where nowsms resides, i dont have enough bandwidth to support multiple downloads, and on the server where i do have bandwidth, i cant install nowsms.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5441
Registered: 10-2002
Posted on Thursday, January 26, 2006 - 04:00 pm:   

Hi Jerrel,

Other than moving NowSMS, I don't have any good suggestions for you.

Let me explain why ...

NowSMS doesn't know what the UAProf is of the receiving device, until that device connects in to retrieve the content.

So even if the content were on another server ... the device would have to connect to NowSMS to retrieve the content, so that NowSMS could see the UAProf in the request.

-bn
jerrel
New member
Username: Jerrel

Post Number: 10
Registered: 02-2004
Posted on Friday, January 27, 2006 - 06:04 pm:   

Dear bryce,
Thanks for your quick and clear responce.
I do however still have some questions regarding the wap push feature.

To start, I want to list the steps in which I think the process works, and how content is downloaded. Please correct me if I'm wrong.

1) A wap push I send to NOWSMS through this url (e.g http://127.0.0.1:8800/?PhoneNumber=8560999&MMSSubject=Ringtone&MMSWAPPush=Yes&MM SFile=http://192.168.10.3/midi/180001.mid)


2) NowSMS fetches the 180001.mid file, and creates a folder containing this file and some other files in the MMSCDATA folder.
the files that are created have the extensions
*.HDR
*.MMS
*.WML
And a configuration file

3) After the file have been created, Nowsms sends a url to the device, containing a link to the *.WML file

4) The User can then click the link, and the device will then send a link to where Nowsms can download the UAprof for this device.


5) After the UAprof have been downloaded, NOWSMS formats the content according to the specs in the UAprof file, and the content can then be downloaded by the device.

Please tell me if I have this right.

If so, I would like to know if this procedure works for all phones that have the GPRS capability, and for all types of content (e.g Sound, pictures, screensavers, video) ?

Also I would like to know, what the purpose is of the three files mentioned in step 2 ?


And my last question is, why is the content and all other files placed in the MMSCDATA folder If Nowsms only knows how the content should be formatted after it fetches the UAProf file ?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5487
Registered: 10-2002
Posted on Monday, January 30, 2006 - 07:12 pm:   

Hi Jerrel,

The content conversion is primarily for graphics. Audio conversions are very limited.

That said, MIDI is very widely supported. I'd be surprised to find a phone that supported WAP, but did not support MIDI.

The main challenge that you run into using WAP Push to send ring tones is that the receiver needs to have WAP/internet access in their phone enabled.

(Without this, you can only do more limited types of ring tones like Nokia Smart Messaging or EMS ... which are transmitted purely over SMS.)

Anyway, there's not much that the NowSMS content conversion offers in this area. While MIDI is pretty widely supported, MIDI is a synthesised audio format. More advanced ring tones, often known as true tones, tend to use recorded audio formats (like MP3). But we don't get into the content conversion in this area because converting recorded audio to synthesised audio is a very inexact science.

So you might want to send a push with multiple links. NowSMS is going to use the last part of the filename in building the link, so you could push multiple versions to the user, and let them download multiple versions to see which one works best for their phone by including multiple MMSFILE references.

I can't really comment too much on the internal structure/layout of the files. But I can tell you that one of things that people like about using NowSMS for this type of push is a configuration setting described here: http://support.nowsms.com/discus/messages/1/11180.html