| How to send ringtones to mobiles other than nokia |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through March 09, 2004 ⬆ |
◄ ► |
| Author | Message | ||||
| youssef el rayes |
i am trying to send ringtones and logos to mobiles other than nokia and it is not working at all. i send to nokia and i recieve it and it is going great but for other than nokia it don't reach at all i put 06050415811581 in the start of the body of the binary message and then i piu the binary data i get from a program that convert rttl to binary data ( that's for nokia ) for the others i use a converter that change the data into hexa and then i add the same 06050415811581 to the start of the body and i send it but i don't reach at all so what am i doing wrong can u help me plz and does 06050415811581 muct be changed for mobile type that is not nokia | ||||
| Bryce Norwood - NowSMS Support |
The User Data Header (UDH) that you mention is specific to Nokia Smart Messaging. Other mobile phones use different formats. The EMS Specification, developed by (Sony)Ericsson, Motorola, Siemens and Alcatel is one format that is used by many phones. You can find the EMS specification at the Ericsson web site, by creating an account at http://www.ericsson.com/mobilityworld. -bn | ||||
| Gary |
Hi, I am trying to send binary messages via deltica.com The messages are accepted for delivery but never actually delivered to the recipients phone. An example UDH value supplied on the Deltica web site for a Nokia Ringtone is similar but different from the UDH used by Now SMS Deltica: 010706050415810000 NowSMS: 06050415811581 Are there different standards for UDH headers, and if so how can I configure Now SMS to send in the format as required by Deltica Thanks in Advance | ||||
| Bryce Norwood - NowSMS Support |
Hi Gary, When it comes to the actual UDH header, "06050415811581" is the correct UDH for a Nokia ring tone (single part anyway, the UDH would be longer for a concatenated message that spanned multiple physical SMS messages, but NowSMS would automatically update the UDH accordingly in that case). If you wanted to get technical, only the first instance of "1581" is truly required as that is the destination port for the ring tone. The second instance of "1581" could be any hex value as the source port is not important. Could you post a more complete link to where Deltica provides this example? They might have their own requirement for their HTTP interface. Why they would require something other than the standard UDH doesn't make any sense. I could be wrong, but their UDH looks very much like the way UDH gets encoded in the UCP/EMI specification. So maybe Deltica's back end SMSC is UCP/EMI based, and they didn't understand the general UDH format. When you encode the UDH in the field that it goes into in a UCP/EMI request, "01" is the signature that indicates that UDH is in the field, and the byte has an encoding for the length of the UDH (even though the first byte of the UDH is the length!!!). I do recall that we encountered another HTTP based SMS service that required settings like this. And NowSMS actually has an undocumented setting that can be used when building an HTTP template to connect to an HTTP-based service provider where it can insert the length of the UDH into one of the URL template. I'm not sure what the URL template for Deltica would be. But if you change the URL template where the UDH is inserted to be something like this: 01@@UDHLen@@@@UDH@@ Then, I think you will get the desired results for that service. Basically, "01" looks like a prefix that they use for the UDH (similar to the UCP/EMI encoding), and we will replace @@UDHLen@@ with a hex string that specifies the number of bytes in the UDH. If you get that working, I'd be curious to know what URL templates you are using with the Deltica service, so that those settings could be shared with others. -bn | ||||
| Gary |
Thanks for the excellent explanation. Adding the UDHLen parameter and preceeding with 01 accepts binary messages no problem. As requested the template is as follows /http/gateway.url.asp?user={username}&pass={password}&TO=@@PhoneNumber@@&ORIG={o riginator}&CLASS=BINARY.SIMPLE&HEXDATA=|01@@UDHLen@@@@UDH@@|@@Data@@ The deltica (Recently changed name to Skymo) link which details the sending of binary messages can be found at http://www.skymo.com/sms/docs/Class.Binary.Simple.html This is the only documentation available on the website (that I can find). Once again, thanks for the help. | ||||
| amit bohra |
hi, this is amit bohra and i'm a software engineer working for transrim technology. right now i'm working as a trainee and i'm working on project as how to send ringtones from sms through my modem. cna you help as where to find all the inticate details about how to send ringtone from my modem which gsm/gprs enabled | ||||
| Bryce Norwood - NowSMS Support |
The second message in this thread includes a reference to the EMS specification, which was developed by (Sony)Ericsson, Motorola, Siemens and Alcatel, and is one format that is used by many phones. For Nokia phones, you should refer to the Nokia Smart Messaging Specification, which can be downloaded from http://www.forum.nokia.com. When submitting most of these messages through the Now SMS/MMS Gateway, they are submitted as binary messages with the encoding dependent on the specification that you are using. If you are trying to do this yourself, without any other software, then I refer you to the ETSI GSM 07.05 specification, which you can find at http://www.etsi.org as a starting point. That has the specification for the AT command set for sending/receiving SMS messages via a GSM modem connection. -bn | ||||
| yukeshean Unregistered guest |
Hi, If i have the following ringtone content: 06050415810000024A3A58D4E0C0C4C8C0041E5ED8F514414614614424DC10420A2B42C82CC2CC2C C2C83082C828C28C28826C2804104289D0A20A50844A248B0DA4B30A14C30C30C30C30C30B30A30B 1504080000 read from database table (provided by content provider), How can I process this content into a proper correct UCP msg string? I'm able to deliver it successfully to recipient, but the recipient do not recv the proper ringtone. It means my data encoding part has problem? Please help asao. I have no idea at all.  Thanks and Regards. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1068 Registered: 10-2002 |
I'm sorry, but I really have to direct you to the UCP/EMI specification. Unfortunately, the LogicaCMG web site seems to have been recently reorganised, and the old links no longer appear to be valid, and I cannot find the specification on their web site. I can point you to a link on the Vodafone Germany web site: http://www.vodafone.de/downloadarea/UCP-Protokoll_Emi4_1.pdf Of course, as this is the support area for the NowSMS gateway, I'll point out that you can simply configure NowSMS to connect to your UCP/EMI SMSC, and then you would send the following URL request: http://127.0.0.1:8800/?PhoneNumber=xxxxx&UDH=06050415810000&Data=024A3A58D4E0C0C 4C8C0041E5ED8F514414614614424DC10420A2B42C82CC2CC2CC2C83082C828C28C28826C2804104 289D0A20A50844A248B0DA4B30A14C30C30C30C30C30B30A30B1504080000 | ||||
| Jiten Unregistered guest |
We are developing API for sending SMS,Ringtones,wallpapers. We want to test how the ringtones comes to mobile device through email. For that we have tested RTTTL ringtones and converted to Binary Format and sent the Binary code as text SMS. But we are receiving the only text as SMS and not the ringtones. Can you please guide us how we can proceed. Is it necessary that we should get the GSM, or SMPP Gateway support for receiving the ringtones. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1352 Registered: 10-2002 |
If you are trying to send the ringtones by sending the message to SMS via an e-mail gateway (e.g., phonenumber@operatorspecific.net for many of the USA mobile operators), then I would not expect that to work. Those e-mail gateways only support text messages (and they only often add extra text to the message format as well). You need to submit it via SMS directly ... you could use a GSM modem or connect directly to an operator SMSC. At this web site, there is a free trial version of our SMS gateway software, the Now SMS/MMS Gateway. It supports GSM modems, and SMSC connections via SMPP, CIMD2, UCP/EMI and HTTP. -bn | ||||
| guruprasad New member Username: Guruprasadl Post Number: 1 Registered: 01-2004 |
Hi All, Iam fairly new to these mobileing technology, now I would want to set up a website that sends sms, ringtones, mms to mobile devices, can any one lighten me on what all I would need on the server side to set up the above features? tq in advance guru | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1691 Registered: 10-2002 |
Well, the biggest issue that you are going to face is that you need a connection to an SMS service provider in order to send messages. It doesn't work like the internet, you can't just send the messages for free over the internet. (In some situations, primarily in the US, you can send text-only messages for free via an e-mail interface.) See the following threads for discussions of "free SMS": http://support.nowsms.com/discus/messages/1/1101.html http://support.nowsms.com/discus/messages/12/1865.html http://support.nowsms.com/discus/messages/485/2171.html So you do need to pay in order to be able to send out messages. (We are not an SMS service provider, so I'm not trying to sell you on a service here.) As an alternative to using a service provider, for lower volumes you can also send/receive messages through a GSM modem. This is a specialised modem device that accepts a SIM card and operates on the mobile network. (Many mobile phones also have inbuilt modem capabilities and can be connected to the PC using a serial or USB cable, or using infrared or bluetooth links.) Here you are paying for sending messages over a subscription to the mobile operator. How you actually send messages depends somewhat on the service provider. Our product here on this web site, the Now SMS/MMS Gateway, is a middleware solution that manages connections to SMS providers. The interface to NowSMS is a simple HTTP based interface so that you can submit messages to NowSMS via HTTP, and NowSMS can forward received messages to your application over HTTP. NowSMS also helps with the formatting of some specialised SMS message types, as well as providing MMS specific functionality. MMS is more complicated than SMS. Here are some links that explain how MMS works, and the two approaches that can be used for sending MMS (which approach you use depends on whether or not your mobile operator has blocked access to external MMSCs). http://support.nowsms.com/discus/messages/1/589.html http://support.nowsms.com/discus/messages/485/1958.html As an alternative to MMS, NowSMS also supports a Multimedia WAP Push object where MMS type objects (images, ring tones, etc.) can be sent to a device over WAP push instead of MMS. (While not quite as slick as MMS, this gets around some of the MMS delivery issues discussed in the above threads.) -bn | ||||
| marco Unregistered guest |
I have created a ringtone editor where it creates an RTTL code. But how can i convert rttl code to CREATE AN MIDI FILE. thanxs | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1711 Registered: 10-2002 |
RTTTL is quite limited compared to MIDI. I've seen quite a few conversion tools for going from MIDI to RTTTL, but not so much in the other direction. You might want to investigate the following: http://www.codingworkshop.com/ringtones/index.html http://ringtonetools.mikekohn.net/ | ||||
| marco Unregistered guest |
hello bryce, Very thanxs for the very quick reply. see this: http://www.tracebit.com/te2/ToneEditor.php3 Its a very COMMON JAVA APPLET you can see on net i.e ringtone editor.This ringtone editor creates the FINAL OUTPUT in RTTL AND MIDI file. Everybody creates this in JAVA but i have created an RINGTONE EDITOR in FLASH MX. My output comes in an STRING format i.e RTTL code.so i have now rttl code in my hand, but from rttl code how can i create an midi file with say (ASP code) online like in the above link, that is my core problem. I am BIG ZERO out of FLASH MX.I have no idea with coding in asp.I need your help in creating a new experiment. thanxs marco | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1730 Registered: 10-2002 |
Marco, The http://ringtonetools.mikekohn.net/ link does have a command line utility that appears to be able to convert from RTTTL to MIDI. I haven't tried it, but based on the docs it looks like it should be possible. -bn | ||||
| marco Unregistered guest |
hello bryce, I contacted Mike he says he doesn't have any such code line that can solve my problem. please see this: http://www.mobilemoney.biz/index_en.asp?page=tools&action=rtttl2midi what the site does is calls an asp file thatz what i need an ASP code. thanxs marco | ||||
| ayo elegbe Unregistered guest |
i really what to understand how ringtone are produced from the CD to MIDI to ringtone formats to the delivery to mobile phone by sms | ||||
| Aditya Saxena New member Username: Aditya Post Number: 1 Registered: 02-2004 |
I want to write a desktop application for MIDI to HEX conversion, But I dont have any details regarding to conversion steps which are required. Can any one tell me, What kind of Steps are required OR Is there any third party COM component is available by which I can convert MIDI stream to HEX format. THANKS | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1816 Registered: 10-2002 |
Marco, I just tried the Mike Kohn tools, and it seems to convert RTTTL to MIDI just fine. I took the yngwie_trilogy.rtttl file that was included in that distribution, and converted it to MIDI as a test. I ran ringtonetools yngwie_trilogy.rtttl trilogy.midi And then I downloaded trilogy.midi through WAP to a P900, and it played just fine. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1817 Registered: 10-2002 |
From CD to MIDI to ringtones via SMS? Well, that's a tall order. Keep in mind that a CD is recorded music. MIDI is synthesised music. So if you are converting from recorded music to synthesised music, you're talking about converting the recorded music to sheet music (notes), and then putting those notes into a MIDI format ... or whatever other ringtone format is being used. (Note: Some of the higher end phones do support recorded music formats such as AMR, WAV, or even MP3 as ring tones. But most phones are using a synthesised music format which can be transmitted using much smaller sizes.) Converting from CD (or let's say MP3) to MIDI is a pretty tall order, as it is tough for software to analyse music and transcribe it into notes. (I have seen some software that claimed to be able to do this, but I haven't tried it, and I remain skeptical.) I'd suggest the following link for some starter info: http://cellphones.about.com/cs/ringtonesinfo/ | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1818 Registered: 10-2002 |
Try following some of the other links in this thread. There are quite a few different ring tone formats ... and not all are MIDI based. There are some pretty good links in this thread for additional info. I don't know that you're going to find anything COM based, but the Mike Kohn ringtonetools can do quite a bit with a simple command line tool. | ||||
| rc. shearer New member Username: Ewustudent Post Number: 1 Registered: 02-2004 |
How do I transfer a midi or .mmf file to my phone. Is it easy to pull of and if so could I get a run down -Thanks- | ||||
| Anonymous |
De la Salau si Salau Jr.
| ||||
| Sharky Unregistered guest |
De la Salau si Salau Jr.
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1892 Registered: 10-2002 |
Downloading a MIDI file is pretty simple. Put it on a web server, and make sure that file extensions on the web server are configured to know that the MIME type for the file extension is "audio/midi". Then use the browser on the phone to retrieve the URL for the file, and the phone should see the MIME type and understand that it is a MIDI file. For example, for some reason, people have posted a couple of MIDI files to our discussion board above (why people do this, and what they expect to happen is beyond my understanding, but in this case I can make use of it for an explanation). If you fetch the URL for one of these files from the browser in a phone that supports MIDI, then it should work. For example, try the link from the X-Files message above from the browser in a phone: http://support.nowsms.com/discus/messages/1/M_XFiles-2800.mid You can do the same thing with MMF files, where the MIME type is "audio/vnd.smaf". However, from what I've seen, people seem to have problems with MMF files, I think because of different encoding versions of SMAF. So this can be more difficult. While you can browse directly to one of these URLs, people usually use WAP push to send a link to one of these URLs out to a phone, so that the user does not have to navigate complicated URL links. -bn | ||||
| Anonymous |
SIEMENS - SEO Content delivery problem --------------------------------------- SMSOUT START HERE Client sent below messages as Binary from the webpage ( NowSMS ) manually, one by one & content is delivered successfully to the Siemens, no UDH is defined nor required 2004-02-19 20:38:07,403326A5.req,xxx.xxx.xxx.xxx,xxxxxxxxxxxx,OK -- SMPP - host:8006, Binary=1;DCS=F5;Data=2F2F53454F0169000400000001000300E600000003626D700A323030303 4392E626D70424DE6000000000000003E00000028000000480000000E0000000100010000000000A 80000000000000000000000020000000000000000000000FFFFFF003E184CC454466430F80000006 330E86CAA6C2E198C000000CC613238AA38990C6600000086C26710FE11CC 2004-02-19 20:38:07,403326A6.req,xxx.xxx.xxx.xxx,xxxxxxxxxxxx,OK -- SMPP - host:8006, Binary=1;DCS=F5;Data=2F2F53454F0169000400000002000300E600000003626D700A323030303 4392E626D7086C30000001384C9207C0926439100000029121C23558870912800000044292247EFC 48928440000004444C9867CC32644440000002929224638C489292800000013921C2638C87093910 0000086C4C92739C92646C3000000CC626713FF91CC8C6600000063313231 2004-02-19 20:38:07,403326A7.req,xxx.xxx.xxx.xxx,xxxxxxxxxxxx,OK -- SMPP - host:8006, Binary=1;DCS=F5;Data=2F2F53454F0169000400000003000300E600000003626D700A323030303 4392E626D70FF1899198C0000003E18E848FE242E30F800000000000000000000000000000000000 00000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000 Client is connected via SMPP Interface with NowSMS - Received as three Text Messages on the mobile not ONE 2004-02-19 20:41:54,403326AA.req,xxx.xxx.xxx.xxx,xxxxxxxxxxxx,OK -- SMPP - host:8006, DCS=F5;Text="//SEO£i@$@@@£@¥@@@@¥bmp200049.bmpBM@@@@@@@>@@@(@@@H @@@Å @@@£@£@@@@@@@@@@@@@@@@$@@@@@@@@@@@@>ΣLTFd0@@@c0ll.╬ÿ@@@a2 88├╕f@@@gΔ_" 2004-02-19 20:41:54,403326AB.req,xxx.xxx.xxx.xxx,xxxxxxxxxxxx,OK -- SMPP - host:8006, DCS=F5;Text="//SEO£i@$@@@$@¥@@@@¥bmp200049.bmp@@@Γ öÇ&C@@@)ΦÆ#Up(@@@D)"G(D@@@DD├╢&DD@@@))"F8)(@@@ΓÆ&8p @@@'9&F@@@bgΓf@@@c121" 2004-02-19 20:41:54,403326AC.req,xxx.xxx.xxx.xxx,xxxxxxxxxxxx,OK -- SMPP - host:8006, DCS=F5;Text="//SEO£i@$@@@¥@¥@@@@¥bmp200049.bmpΣΘ@@@>΅ ºH¤.0@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@" SMSOUT END HERE SMSDEBUG START HERE Client is connected via SMPP Interface with NowSMS 20:41:54:109 [13] SMPPServerReceiveMessageCallback: inbound message: sender=xxxx, recip=xxxxxxxxxxxx, pid=0, dcs=F5, udh=, msg=//SEO£i@$@@@£@¥@@@@¥bmp200049.bmpBM@@@@@@@>@@@(@@@H@@@Å @ @@£@£@@@@@@@@@@@@@@@@$@@@@@@@@@@@@>ΣLTFd0@@@c0ll.╬ÿ@@@a288├╕f @@@gΔ_ 20:41:54:156 [13] SMPPServerReceiveMessageCallback: inbound message: sender=xxxx, recip=xxxxxxxxxxxx, pid=0, dcs=F5, udh=, msg=//SEO£i@$@@@$@¥@@@@¥bmp200049.bmp@@@Γ öÇ&C@@@)ΦÆ#Up(@@@D)"G(D@@@DD├╢&DD@@@))"F8)(@@@ΓÆ&8p @@@'9&F@@@bgΓf@@@c121 20:41:54:187 [13] SMPPServerReceiveMessageCallback: inbound message: sender=xxxx, recip=xxxxxxxxxxxx, pid=0, dcs=F5, udh=, msg=//SEO£i@$@@@¥@¥@@@@¥bmp200049.bmpΣΘ@@@>ΣH¤.0 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@ SMSDEBUG END HERE Also I have tried sending the content from the client to the SMSC directly without NowSMS in between & it has been received successfully. The problem is when sending messages via SMPP Interface NowSMS is not recognizing the messages as BINARY but rather TEXT but when sent as Binary from the NowSMS webpage, runs on port 8800 by default, manually one by one received successfully Any Clues for the solution. | ||||
| Sharky Unregistered guest |
De la Sharky
| ||||
| Sharky Unregistered guest |
De la Sharky
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1918 Registered: 10-2002 |
Anonymous with the SEO problem, You're right. The DCS should tell us to parse the message as binary content. But we are not. (Usually it works for other binary types, because if the UDH is present, binary is assumed.) I can send you an update that fixes this problem. Please e-mail nowsms@now.co.uk, and reference the problem with SEO messages and SMPP relay. We're planning to post an official update in about 2 weeks, but I'd like to get this specific fix out to you sooner. And Sharky ... I don't know what you're trying to accomplish, but I don't think it is working. This is a discussion board. For some reason some people seem to think that if they post a message here, it will magically appear on their phone. But that is not the case. -bn | ||||
| Sharky Unregistered guest |
[message deleted by moderator] | ||||
