| MMSC Configuration Details |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hi, I have downloaded & installed the NowSMS.exe. I am very much struggling while configure with MMSC & MMSC Users Setup. Please advise me the details about MMSC Configuration. I have already seen the User Guide & Online website documnets. Looking forward to your informations. Rajinikanth | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi. Have you looked at the "Quick Start Guide" here on the web site? I think that's a good place to get started, as it walks you through the different steps of the process. How about taking a look at that document, trying to work through the steps in that document, and let us know at what stage in the configuration you need more clarification ... and we'll try to help you out. -bn | |||
| zameerzameer |
hi, i have downloaded and installed nowsms.exe, i am having trouble to configure the SMSC settings......i would aslo like to know whether i need to have credits before i use this software........or is it free and whether i have to signup somewhere( ia m asking this because the smsc settings when configured asks for a username and password.) furthermore i also wanted to know whether i could use this software without haveing a gsm phone modem, i amm connected to the net using TCP/Ip . Can i send sms annd mms using this software to gsm phones in INDIA | |||
| Bryce Norwood - NowSMS Support |
You need to have some type of connection into an SMS network. We are not an SMS service provider, only a software developer. An SMSC connection could be a GSM modem (or GSM phone with GSM modem capabilities connected to the PC with a serial or USB cable, or infrared or bluetooth connection) ... or it can be an IP-based connection to a service provider. There may be some recommendations on other discussion threads here for SMS service providers. I have, in the past, recommended Clickatell as an ok service provider to get started with. -bn | |||
| Anonymous |
my SMSC is working but have not been able to configure the MMSC as the MMS could not be sent through the gateway. I am currently using the web interface to send the message but still it is not working even though i have followed the quick start guide properly. Are there any changes that have to be done in the mobile settings for the mesage to reach or is there a problem in the configuration. The error is following: NowSMS Error Report. SMS message could not be sent to 9811480810, ERROR - Modem Response (2): +CMS ERROR: 38 | |||
| Bryce Norwood - NowSMS Support |
So text messages are sent fine, but this error only occurs when you attempt to send an MMS message? | |||
| Bryce Norwood - NowSMS Support |
CMS ERROR 38 is usually generated when the operator SMSC does not like something about the format of the SMS message. Most of the times when I've seen this in the past has been when someone is trying to send an EMS message, and the User Data Header is not encoded properly. But I would not think this should happen if you are sending an MMS message through NowSMS directly. How about sending a WAP push? Are you able to send a simple WAP Push using the NowSMS gateway? (Just enter any URL and a very short text message ... the test is to see if the push message gets delivered to the phone, but the phone doesn't have to visit the actual URL.) -bn | |||
| ankushmahajan |
i have sent the WAP push message using the web interface and it works fine but still the MMS is not been able to work. Can u suggest a way to get out of this problem. [SMSGW] Debug=Yes WebAuth=No WebMenu=Yes WebPort=8800 IPAddress=203.197.217.248 ReceiveSMS=No ReceiveMMS=No Modem1=Nokia GSM Data 3.0 SMPPPort=7777 [Modem - Nokia GSM Data 3.0] PhoneNumber=+919837098300 [Inbound SMS Routing] disha=+919837098300 [MMSC] WebPort=80 SMTPPort=25 RelayHost= HostName=203.197.217.248 DomainName= AdminUser= AdminPassword= SMTPRequireAuth=No EnableDeliveryNotification=Yes ConvertImages=Yes ConvertEMailWAVAMR=No ConvertEMailBMPJPG=No ConvertScaleToScreen=Yes SMSEMail=No SMSDomainName= SMSPerEMail=1 MSISDNHeaderNokiaFormat=Yes [MMS Content Types] image/jpeg=.jpg image/gif=.gif image/vnd.wap.wbmp=.wbmp image/png=.png image/bmp=.bmp text/plain=.txt text/x-imelody=.imy text/x-emelody=.emy text/x-vcard=.vcf text/x-vcalendar=.vcs text/calendar=.ics text/vnd.sun.j2me.app-descriptor=.jad application/smil=.smil application/java-archive=.jar application/x-java-archive=.jar application/vnd.symbian.install=.sis application/vnd.wap.wmlc=.wmlc application/vnd.nokia.ringing-tone=.rng audio/wav=.wav audio/x-wav=.wav audio/amr=.amr audio/x-amr=.amr audio/midi=.midi audio/x-midi=.midi audio/sp-midi=.midi audio/rmf=.rmf audio/x-rmf=.rmf audio/x-beatnik-rmf=.rmf application/vnd.wap.mms-message=.mms application/vnd.smaf=.mmf video/3gpp=.mp4 [Extensions] .jpg=image/jpeg .jpeg=image/jpeg .gif=image/gif .wbmp=image/vnd.wap.wbmp .png=image/png .bmp=image/bmp .txt=text/plain .imy=text/x-imelody .emy=text/x-emelody .vcf=text/x-vcard .vcs=text/x-vcalendar .jad=text/vnd.sun.j2me.app-descriptor .smil=application/smil .smi=application/smil .jar=application/java-archive .sis=application/vnd.symbian.install .wmlc=application/vnd.wap.wmlc .rng=application/nokia.ringing-tone .wav=audio/wav .amr=audio/amr .midi=audio/midi .mid=audio/midi .rmf=audio/rmf .mms=application/vnd.wap.mms-message .mmf=application/vnd.smaf .ics=text/calendar .mp4=video/3gpp .3gp=video/3gpp above are the config files. is there any problem in the above? | |||
| ankushmahajan |
does the phone configuration needs a chang for sending the message to it from the web interface | |||
| Bryce Norwood - NowSMS Support |
The phone configuration would not affect a "CMS ERROR 38" being generated. I'm puzzled that WAP push would work, but an MMS notification would not ... as essentially an MMS notification message is encapsulated inside of a WAP push. The primary difference is that an MMS notification usually spans 2 SMS messages, so I'm suspecting that the problem that you are experiencing is related to message concatenation. Try a WAP push again, but this time, in the text field, enter 150 characters of text. Does this work? I'm expecting that it would fail. Could you enable the Debug mode on the gateway? Do this by manually editing SMSGW.INI and add Debug=Yes under the [SMSGW] section header. Then restart the gateway service. Then repeat your tests ... send a text message. Send a simple WAP push message. Send an MMS message. Then e-mail the SMSDEBUG.LOG to me at nowsms@now.co.uk, so I can take a look to see if I see anything unusual. One other idea ... before trying this ... try downloading and installing the NowSMS version at the following link: http://www.nowsms.com/download/nowsms420a.exe That version encodes the SMS header slightly different from the original v4.20 release. I don't think it will make a difference for your situation, but it is worth trying. -bn | |||
| ankushmahajan |
the problem is that when sending MMS notification through web interface, the phone does not get any notigication. When I saw in the directory content, it shows the MMS file in MMSCDATA/20030724/15/ directory & I M giving the URL in notification interface as http://IPAddress/MMSCDATA/20030724/15/a.mms. if this file is copied to \MMSCDATA\ directory it works on giving URL as http://IPAddress/a.mms. Please let me know any solution related to this prob. | |||
| Bryce Norwood - NowSMS Support |
http://IPAddress/20030724/15/a.mms would retrieve MMSCDATA/20030724/15/a.mms (the MMSCDATA reference is assumed). I'm not sure how this is related to the CMS Error 38, however? Or have you gotten past that problem? | |||
| ankushmahajan |
there are two problems that i am facing currently: the first is that the MMS notification can be sent but still the mms message cannot be send from the web interface. the second is relating sending the MMS notification. In this if the MMS URL is given as the default where the MMS file is generated by the software,i.e., http://Ipaddress/20030715/14/a.MMS the CMS error: 38 occurs and the Software retries finally giving the error failed sending. But on the other hand if the file is copied from the asbove location to the MMSCDATA folder directly and now if the MMS URL is given as http://ipaddress/a.mms it sends it in one go. It is a very puzzling problem and please suggest a solution to it quickly. | |||
| Bryce Norwood - NowSMS Support |
I'd like to see an SMSDEBUG.LOG file for when it works, and when it does not work. If you could e-mail this to me at my nowsms@now.co.uk e-mail address, then I would appreciate it. My suspicion at the moment is that for some reason, your operator's SMSC does not like concatenated messages. When we generate an MMS notification automatically ("Send MMS Message" in the web interface), the notification message is most likely longer than the other notification. I'd be curious if you send a WAP push message with over 150 characters in the text of the message ... does this also result in the CMS ERROR 38? -bn | |||
| ankushmahajan |
when i try to send a WAP push message with more than 150 characters, the message is sent and i can receive 160 characters. so I think that the problem which you were considering is not there. Please if u can tell me exactly the next step that i should take to make it working. | |||
| ankushmahajan |
i have got over with the problem that i posted earlier.the mms is being sent from the path created by the software,ie, MMSCDATA/.. . Now I want to try this using two mobile handsets and use the gateway. Can you please guide me through the changes that has to be made to handset's configuration. | |||
| Bryce Norwood - NowSMS Support |
Hi Ankush, I think I would still like to see a log file as I described above. As the file may be a bit large, you can e-mail it to nowsms@now.co.uk instead of posting here. I'd like to see a log file that shows the long WAP push being sent successfully, and the MMS notification failing. -bn | |||
| ankushmahajan |
it no longer gives that problem and hence i don't think there is a problem in sending the message any more. Regarding the WAP push message, it went in the first go and hence there was absolutely no problem with it and then on trying the MMS message it also went. But still if you want to have a look at the file i will send it in a day or 2. | |||
| Bryce Norwood - NowSMS Support |
Unless the problem resurfaces, I would say all is well that ends well ... although it still puzzles me. Perhaps there was a temporary network problem at the time of the first attempts. | |||
| Anonymous |
"The primary difference is that an MMS notification usually spans 2 SMS messages, so I'm suspecting that the problem that you are experiencing is related to message concatenation. " can you give some advice on concatenation? I do receive two sms, it's one mms notification. | |||
| Bryce Norwood - NowSMS Support |
Well, assuming that you are not using NowSMS (which would reassemble the message and parse the notification), you'll want to look at the specifications for concatenated SMS. There's some good info in the WAP WDP specification ... where it talks about WAP over GSM SMS, and how UDH is used. The specification that documents concatenated SMS for GSM is the ETSI GSM 03.40 specification. -bn | |||
