| Sierra Aircard 860 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Pradeep Mysore New member Username: Pmysore Post Number: 3 Registered: 01-2006 |
I am trying to use a Sierra 860 AirCard (Cingular) with NowSMS. For some reason, I keep getting a CMS Error: 330 (as indicated in the log files). After 2-3 hours, it suddenly starts working (absolutely no changes in any way whatsoever). I tried the stuff indicated in some of the old threads, like changing SMSC configuration from Default to GSM etc but to no avail. Any help would be highly appreciated. | |||
| Pradeep Mysore New member Username: Pmysore Post Number: 4 Registered: 01-2006 |
Also, when it does work, for some reason I am not able to send an SMS to the card through my MIDlet. If I send an SMS using Text messaging, everything works great and NowSMS is able to forward my SMS to a servlet (2 way SMS). In my midlet, I tried sms://1-Ph-No as well as sms://Ph-No with no success. This (sms://Ph-No) used to work great when I used a Cingular cell phone connected to NowSMS. How is the Aircard different from a cell phone in terms of receiving an SMS from a midlet? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6364 Registered: 10-2002 |
Hi Pradeep, I'm assuming that the "CMS ERROR: 330" occurs when you are sending, correct? According to the CMS error code list (http://support.nowsms.com/discus/messages/1/829.html) ... 330 means that the SMSC address is unknown. It is very bizarre that this error would occur sporadically. Let me explain what it means. When you send an SMS message with a GSM modem, the modem connects to an SMSC and asks the SMSC to deliver the message. By default, NowSMS will always tell the modem to use its default SMSC. The SMSC is identified as a special phone number that is preloaded on the SIM card. My understanding of the 330 error is that it would occur when the default SMSC is not known. I've seen a few instances, generally with very old GSM modems (most memorably an infrared modem that was an add-on for some old Ericsson phones, before it was SonyEricsson) ... where the modem did not support reading the SMSC from the SIM card. But more recently, we have also seen reports that the SMSC address must be manually defined for some Samsung 3G phones to be used as a modem. (See http://support.nowsms.com/discus/messages/1/14836.html) In those cases, the error was consistent, not sporadic. Nonetheless, the first thing I would suggest would be to determine the SMSC address that you should be using, and try setting it in your NowSMS configuration to see if this fixes the sporadic problem. I'm not sure that I fully understand your follow-up statement/question. I think you are saying that when the modem seems stuck in this "CMS ERROR 330" when sending situation ... that you are also having trouble sending messages into the modem. I'm assuming that in your tests, you use the built-in SMS client in a mobile phone and it can send a text message ok ... but then you try sending from your MIDlet on the same phone, and the text message does not go through. When the text message does not go through ... what happens? Do you get an immediate error? Does the message arrive hours later or never? That is too weird to be a coincidence. I'm just not sure what this would mean ... or what the relationship is ... My best guess is that maybe you're having a signal strength related issue. My guess is that sometimes you are connected to Cingular's 3G/UMTS network, and sometimes you are connected to EDGE/GPRS. And the behaviour is different depending on which network you are connected to. So what can we do? I'm not sure what commands are available that would tell us whether the modem is registered to 3G/UMTS or GPRS/EDGE. I'd be curious ... if you connect to the modem using HyperTerminal ... and issue the command AT+COPS=? (this command may take about a minute or so to complete, so be patient) ... are multiple entries listed for Cingular? Or is there just a single entry? If there are multiple entries, we could configure NowSMS to periodically issue the AT+COPS? command to see which we are currently connected to ... and check that in the log. Unfortunately, I suspect you're going to see only a single entry. Unless the AT+COPS? command returns a number after the operator name ... for example, if AT+COPS? returns: +COPS: 0,0,"Cingular",# Then the "#" should be "2" if you are connected to UMTS. Unfortunately, it is optional for this parameter to be returned. So you might not see any value returned after the operator name. Another command that might be interesting is AT+WS46? ... if you issue that command from HyperTerminal what response do you see? What about AT+WS46=? ... I suspect you're going to see a value of 25 returned for AT+WS46? ... and AT+WS46=? should return 11,22,25. But I'd like to hear directly what you see when issuing these commands. We could use AT+WS46 to force the modem into using GSM/GPRS/EDGE only (AT+WS46=12) ... or UMTS/WCDMA/3G only (AT+WS46=22). But I'd like to try to understand the problem better first. Here's an idea ... If we are switching between GPRS/EDGE and UMTS ... maybe the modem is not auto-attaching properly for one of the technologies. Try editing SMSGW.INI, and under the [Modem - Sierra ...] header, add CommandPreSend1=AT+CGATT=1 ... this will cause NowSMS to send this command to the modem before each attempt to send a message. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6368 Registered: 10-2002 |
Follow-up ... As I work through other tech support issues today, it seems like "CMS ERROR 330" is coming up quite frequently on 3G modems. I'm guessing that your modem is indeed sometimes connecting with GPRS/EDGE, and sometimes with UMTS/WCDMA/3G. And I'm further guessing that when the modem is connected with GPRS/EDGE, everything is working ok. But when the modem is connected with 3G/UMTS/WCDMA ... this is when you are seeing the "CMS ERROR 330". I'm further guessing that some chipset that is being used by a variety of 3G modem manufacturers does not support the "default SMSC" setting from the SIM card. So when you are in 3G mode, this error is being returned about the unknown SMSC. Inserting the appropriate SMSC number (SMSC=+number) for your mobile operator into your SMSGW.INI file (under the [Modem - Sierra ...] section header) should hopefully resolve this problem. The best way to determine this SMSC number is to put the SIM into a mobile phone, and check the SMS messaging settings in the phone ... usually the UI on the phone will present an option to read/set the SMSC address. -bn | |||
| Pradeep Mysore New member Username: Pmysore Post Number: 8 Registered: 01-2006 |
Thanks for the info. I am trying to use hyperterminal but for some reason it doesn't give me the Direct to COM option at all. All I can see is the Sierra Modem, Internal Modem and the COM ports. The Control Panel/Modem tells me that Sierra is on COM6, so there should be Direct to COM6 option right? FYI, I am using Windows XP. Thanks a bunch. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6371 Registered: 10-2002 |
In HyperTerminal, the "Connect Using" box should have an option for COM6. (Unless some other program might be already using it ... so stop the NowSMS services.) After you select the port, another screen will be displayed with connection parameters. You shouldn't need to change anything ... although I usually change "Bits per second" to 115200 (as most modems do autobaud, but they might not autobaud down to the default for HyperTerminal of 2400). -bn | |||
| Pradeep Mysore New member Username: Pmysore Post Number: 9 Registered: 01-2006 |
AT+COPS? gave me +COPS: 0,0, "Cingular", 0 AT+WS46? gave me +WS46: 25 AT+WS46=? gave me +WS46: (12,22,25) FYI, NowSMS is working now. So that means like you said that it is on GPRS/EDGE. I will let you know if and when it switches over to the 3G network. About my other question about SMS Receive, I do not get the message sent by the midlet at all (no mention in the log files). But if I use the ordinary text message UI on the phone, there is no problem at all. Previously, I was able to use the same midlet to send SMS to a Cingular cell phone with a infrared connection to a laptop running NowSMS with no problems. Thanks a lot for helping me out. | |||
| Pradeep Mysore New member Username: Pmysore Post Number: 10 Registered: 01-2006 |
Bryce, Any clue as to why NowSMS (on the Sierra 860 card) is able to receive SMS messages from the text messaging UI of a cell phone and not from a midlet residing on the cell phone? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6384 Registered: 10-2002 |
Hi Pradeep, To force the modem to stay on GPRS/EDGE, you could add the following initialisation command: AT+WS46=12 Probably the easiest place to put this would be in SMSGW.INI, under the [Modem - Sierra ...] header: CommandPostInit1=AT+WS46=12 That way, NowSMS will send that command as part of the initialisation process each time it re-initialises the modem. A value of 22 would indicate 3G only. A value of 25 indicates either. I would be inclined to try inserting the SMSC address/phone# into the SMSGW.INI file, and continue to let the modem connect 3G if it has a signal. I have no idea why the modem would be able to receive an SMS message from the text messaging UI of the phone, but not from a midlet running on that same phone. (Unless an error code is being returned to the midlet.) I say this especially considering the unusual behaviour that you have observed (where there was no such problem when a phone was used as a modem instead, and where the receiving problem seems to be sporadic). In both cases, the SMS message should be getting submitted to the operator SMSC for it to handle delivery. I assume that all is ok as long as the modem is on the GPRS/EDGE network? If you put the above setting in place to keep the modem on GPRS/EDGE, are things stable? I'm wondering if maybe Cingular's 3G network might not be quite stable. That said, I do have one other setting in NowSMS that I would suggest you setting. Set "SMS Message Storage" to be "Direct to modem", as this setting generally provides the best receive SMS message behaviour on Sierra Aircards. -bn | |||
| purnima New member Username: Info_genex Post Number: 1 Registered: 09-2006 |
Hi, We are working with XP60 GSM unit in SMS mode. The GSM modem we are using Wavecom MultiBrand Modem. Model is -MTCBA-G-F1. When ever i try to dial a number through hyper terminal using ATDT command it is returning NO CARRIER. The modem LS red light is not blinking. It is fixed. It is returning the wireless modem is not registered on the network. So please help me about how to register modem on a network? > We are using a valid SIM card with credit on it. >It is not asking for any PIN >Modem have enough power supply. >The problem is we already worked with the modem it worked correctly. We are able to send and receive messages,Dial a number from modem. > We are also able to receive signals from other modem to the modem connected to the PC for every two minutes. > But our requirement is to receive signals for every 30 seconds so we started trying to change the modem settings to set the time interval for 30 seconds.Suddenly our modem got the problem of network registration failed. We thought some modem settings have been changed. >Whenever i try to verify the signal strength with AT+CSQ command it is returning insufficient signal. AT+CSQ +CSQ: 99,99 OK Why it worked properly previously with same equipment and now it is not? Regards Purnima. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6600 Registered: 10-2002 |
Sorry, I can help you with NowSMS questions, but I am not an expert with that modem enough to provide general modem support. It sounds to me like something may be wrong with the mobile operator network subscription. Maybe the AT+COPS command will help you see what operators the modem can see. | |||
