| GSM modem and Service PRovider that works in US |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through June 02, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Chris Sammy New member Username: Csammy Post Number: 1 Registered: 11-2010 |
Hi, I am from the US and looking for a GSM modem that works on Windows 7 and a Cell phone plan that will work with it as well. I will be setting up NowSMS but I am unable to get my configuration working with Tmobile. I am unsure if it is because of the gsm modem I purchased or if I don't have Tmboile's settings right, but I would like to know if anyone in the US has gotten NowSMS to work and which (1) service provider you're using and (2) which GSM modem you are using. Thanks! | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2633 Registered: 08-2008 |
Hi Chris, From what I've seen in customer reports, T-Mobile is usually a little easier to get working than AT&T. What modem are you trying? Did the SIM come with the modem? (Sometimes a SIM that comes with a modem is activated with a plan that assumes you will be using the modem for internet access ... it usually works better to activate a SIM for a phone, then move it to the modem.) What type of problem are you experiencing? If the problem is that you can't send any SMS messages, try going into the "Properties" for the modem in the "SMSC" list, and change "SMS Access" to "GSM". -- Des NowSMS Support | |||
| Chris Sammy New member Username: Csammy Post Number: 2 Registered: 11-2010 |
Hi Des, Thanks for responding, I bought a generic EDGE GSM Modem from eBay from China and it's not working. I have Tmobile with a data plan. I think the issue is that the modem isn't a working device on 64bit so I need to find another modem. Do you know of a modem that works with Tmobile and NowSMS on Windows 7? Thanks for your help. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2635 Registered: 08-2008 |
Hi Chris, Before you give up on that modem, go into the Windows Control Panel, System, and look for the Device Manager. See if any ports show up for the modem under "Ports (COM & LPT)". If they do, you can try configuring NowSMS to talk to the COM port directly. (NowSMS Lite doesn't support this, it requires a Windows modem driver. Under Phone & Modem Options in the Windows Control Panel, you can manually add a modem driver to a COM port. It is best to use the Windows Standard 33600 bps Modem driver instead of letting Windows pick one for you. Note that you also need this driver in full NowSMS if you want to send or receive MMS, the COM port only configuration only supports SMS.) If there's no COM or LPT port, then you need a 64-bit USB driver from the manufacturer. There might be a clue as to who made the chipset for the modem under the Device Manager. You might be able to use that information to search out a 64-bit driver. I've used a variety of modems from Option and Huawei on 64-bit machines ... also the SonyEricsson MD300. I would suggest checking the manufacturer site to confirm a 64-bit driver for any other modems you look at. Also ... for T-Mobile, I would avoid any 3G modems that support their AWS (1700Mhz) 3G band, as there have been some unconfirmed reports that T-Mobile is blocking MMS access from these modems, assuming that the modems are being used for internet access only. T-Mobile uses a different 3G frequency band from all other operators, so there are relatively few modems that support their frequency. -- Des NowSMS Support | |||
| Chris Sammy New member Username: Csammy Post Number: 3 Registered: 11-2010 |
Hi Des, I keep getting this error message, 304: [SMS] SubmittedBy=127.0.0.1 Data=test tes test PhoneNumber=91**156831 [ErrorDetail] RetryCount=5 LastRetryTime=20101110100815 LastErrorInfo=ERROR - Modem Response (1): +CMS ERROR: 304 -- EDGE MODEMU I've also tried putting a 1 before the phone number and still nothing was sent. Also, I can't receive SMS messages either -is this a modem probelm? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2637 Registered: 08-2008 |
Hi Chris, Hmm ... I had to do some thinking on this one. CMS ERROR 304 means "Invalid PDU Mode Parameter", which is a very odd error to be happening. We've seen it on some Motorola phone modems that have a bug that prevent them from being able to send any messages that include user data header (long SMS or WAP push/port addressed SMS). I assume that this does not apply in your situation, as you are sending a simple short text message. My best guess would be that the modem does not read the SMSC address from the SIM card. Normally this does not result in a 304 error. The SMSC number can be manually provisioned in NowSMS by editing SMSGW.INI, and under the [Modem - driver name] section header, adding: SMSC=+xxxxxxxxx Figuring out the number to use can be a bit of a challenge. The easiest thing to do is put the SIM into a phone and navigate through the phone settings to find the SMSC number. I also did some searching, and found the following thread which might be applicable: http://support.nowsms.com/discus/messages/1/24431.html This other thread had someone experiencing CMS ERROR 304 when trying to send via a Sierra Wireless modem. In that case, the issue was that the modem driver established more than one COM port. The COM port with a modem driver installed only supported using the modem for internet access. A different COM port (for which a modem driver was not automatically installed) was able to provide SMS access. The following link describes where to look for the other COM port if this is what you are experiencing: http://www.nowsms.com/sierra-wireless-881-usb-modem-881u-and-nowsms Hopefully it's one of these two issues. -- Des NowSMS Support | |||
| Chris Sammy New member Username: Csammy Post Number: 4 Registered: 11-2010 |
Thanks Des, can you tell me what the SMSC number is? Is it something I would call Tmobile and figure out? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2639 Registered: 08-2008 |
I believe it is +12063130004 (At least that is the main number.) | |||
| Chris Sammy New member Username: Csammy Post Number: 5 Registered: 11-2010 |
I found something that said Tmobile's SMSC is 12063130004. I added that into the INI file, but now my messages are just showing as "Queued". Any ideas? | |||
| Chris Sammy New member Username: Csammy Post Number: 6 Registered: 11-2010 |
Sorry, realized you posted your response just before mine. Any clue as to why it would have them queued up now? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2640 Registered: 08-2008 |
Hi Chris, The only thing I can figure is that by default there is an increased retry period after each failed attempt. But that retry period would be minutes, not hours. Are newly posted messages also just sitting there with no attempts at sending? Enable the SMSDEBUG.LOG, restart the service, and try sending another message. Post the SMSDEBUG.LOG content in reply. -- Des NowSMS Support | |||
| Chris Sammy New member Username: Csammy Post Number: 7 Registered: 11-2010 |
Hi Des, ----11:00:09:206 [0] main: Now SMS/MMS Gateway v2010.02.09 Web server started on port number 8800 11:00:11:206 [0] main: preferred sender = 16512***761,EDGE MODEMU 11:00:11:206 [2] ThreadProcessModem: EDGE MODEMU 11:00:11:222 [2] ThreadProcessModem: Before ModemAllocate - EDGE MODEMU 11:00:11:222 [2] ThreadProcessModem: After ModemAllocate - EDGE MODEMU - OK 11:00:11:222 [2] ThreadProcessModem: Re-initializing modem: EDGE MODEMU ... 11:00:11:222 [0] main: 48 Days remaining in trial version 11:00:11:472 [2] ThreadProcessModem: ATI0 11:00:11:472 [2] ThreadProcessModem: OK 11:00:11:550 [2] ModemTest: EDGE MODEMU 11:00:11:613 [2] ModemTest: OK 11:00:11:613 [2] ThreadProcessModem: AT+CPMS? 11:00:11:628 [2] ThreadProcessModem: +CPMS: "SM",0,35,"SM",0,35 OK 11:00:11:628 [2] ThreadProcessModem: AT+CNMI=2,0 11:00:11:644 [2] ThreadProcessModem: OK 11:00:11:644 [2] ThreadProcessModem: AT+CNMI? 11:00:11:660 [2] ThreadProcessModem: +CNMI: 2,0,0,0,0 OK 11:00:11:660 [2] ThreadProcessModem: AT+CNMI=2,1 11:00:11:675 [2] ThreadProcessModem: OK 11:00:11:675 [2] ThreadProcessModem: AT+CNMI? 11:00:11:691 [2] ThreadProcessModem: +CNMI: 2,1,0,0,0 OK 11:00:11:691 [2] ThreadProcessModem: AT+CNMI=2,1,0,1 11:00:11:706 [2] ThreadProcessModem: OK 11:00:11:706 [2] ThreadProcessModem: AT+CPMS=? 11:00:11:722 [2] ThreadProcessModem: +CPMS: ("SM") OK 11:00:11:722 [2] ThreadProcessModem: AT+CPMS="SM","SM","SM" 11:00:11:738 [2] ThreadProcessModem: +CPMS: 0,35,0,35 OK 11:00:11:738 [2] ThreadProcessModem: AT+CPMS? 11:00:11:753 [2] ThreadProcessModem: +CPMS: "SM",0,35,"SM",0,35 OK 11:00:11:753 [2] ThreadProcessModem: AT+CGSMS=3 11:00:11:769 [2] ThreadProcessModem: ERROR 11:00:11:785 [2] ThreadProcessModem: AT+CNMI? 11:00:11:800 [2] ThreadProcessModem: +CNMI: 2,1,0,1,0 OK 11:00:11:800 [2] ThreadProcessModem: AT+CNMI=? 11:00:11:816 [2] ThreadProcessModem: +CNMI: (0-3),(0-3),(0-3),(0-1),(0,1) OK 11:00:11:816 [2] ThreadProcessModem: AT+COPS? 11:00:11:831 [2] ThreadProcessModem: +COPS: 0,2,00000 OK 11:00:11:831 [2] ThreadProcessModem: AT+CSQ 11:00:11:847 [2] ThreadProcessModem: +CSQ: 99,99 OK 11:00:11:847 [2] ThreadProcessModem: AT+CNUM 11:00:11:863 [2] ThreadProcessModem: +CNUM: "4D736973646E31","16512***761",129 OK 11:00:11:863 [2] ThreadProcessModem: +16512***761 11:00:11:863 [2] ThreadProcessModem: Modem initialization complete: EDGE MODEMU 11:00:11:894 [2] ThreadProcessModem: Processing 4CD9EDA9.req... 11:00:11:910 [2] ThreadProcessModem: OUT: AT+CMGS="191471***31" 11:00:11:925 [2] ThreadProcessModem: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:11:925 [2] ThreadProcessModem: OUT: 11:00:12:019 [2] ThreadProcessModem: OUT: \r 11:00:12:019 [2] ThreadProcessModem: OUT: AT 11:00:12:035 [2] ThreadProcessModem: IN: OK 11:00:13:035 [2] ThreadProcessModem: Error: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:14:035 [2] ModemTest: EDGE MODEMU 11:00:14:097 [2] ModemTest: OK 11:00:14:113 [2] ThreadProcessModem: Processing 4CD9EDAA.req... 11:00:14:128 [2] ThreadProcessModem: OUT: AT+CMGS="191471***31" 11:00:14:144 [2] ThreadProcessModem: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:14:144 [2] ThreadProcessModem: OUT: 11:00:14:238 [2] ThreadProcessModem: OUT: \r 11:00:14:238 [2] ThreadProcessModem: OUT: AT 11:00:14:253 [2] ThreadProcessModem: IN: OK 11:00:15:003 [2] ThreadProcessModem: Error: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:16:003 [2] ModemTest: EDGE MODEMU 11:00:16:066 [2] ModemTest: OK 11:00:32:081 [2] ThreadProcessModem: Processing 4CD9F194.req... 11:00:32:097 [2] ThreadProcessModem: OUT: AT+CMGS="91471***31" 11:00:32:113 [2] ThreadProcessModem: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:32:113 [2] ThreadProcessModem: OUT: 11:00:32:206 [2] ThreadProcessModem: OUT: \r 11:00:32:206 [2] ThreadProcessModem: OUT: AT 11:00:32:222 [2] ThreadProcessModem: IN: OK 11:00:33:222 [2] ThreadProcessModem: Error: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:34:128 [12] ThreadProcessConnection: Processing connection from 127.0.0.1... 11:00:34:128 [12] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=91471***31&Text=joe+call+office+line+if+y ou+receive+this&InfoCharCounter=&PID=&DCS=&DestPort=&DelayUntil=&Submit=Submit 11:00:34:128 [12] Debug: 1 recipient entries 11:00:34:191 [12] ThreadProcessConnection: Before message loop 11:00:34:191 [12] ThreadProcessConnection: Before message loop 11:00:34:191 [12] ThreadProcessConnection: Begin message loop 11:00:34:206 [12] ThreadProcessConnection: End message loop 11:00:34:222 [2] ModemTest: EDGE MODEMU 11:00:34:285 [2] ModemTest: OK 11:00:34:285 [12] WaitForSocketClose: WinSock reported ioctlsocket complete 11:00:34:285 [12] ThreadProcessConnection: Request processing complete 11:00:34:300 [2] ThreadProcessModem: Processing 4CD9F57C.req... 11:00:34:316 [2] ThreadProcessModem: OUT: AT+CMGS="6512***761" 11:00:34:331 [2] ThreadProcessModem: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:34:331 [2] ThreadProcessModem: OUT: 11:00:34:425 [2] ThreadProcessModem: OUT: \r 11:00:34:425 [2] ThreadProcessModem: OUT: AT 11:00:34:441 [2] ThreadProcessModem: IN: OK 11:00:35:191 [2] ThreadProcessModem: Error: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:36:191 [2] ModemTest: EDGE MODEMU 11:00:36:253 [2] ModemTest: OK 11:00:36:253 [2] ThreadProcessModem: Processing 4CD9F57D.req... 11:00:36:331 [2] ThreadProcessModem: OUT: AT+CMGS="91471***31" 11:00:36:347 [2] ThreadProcessModem: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:36:347 [2] ThreadProcessModem: OUT: 11:00:36:441 [2] ThreadProcessModem: OUT: \r 11:00:36:441 [2] ThreadProcessModem: OUT: AT 11:00:36:456 [2] ThreadProcessModem: IN: OK 11:00:37:206 [2] ThreadProcessModem: Error: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:38:206 [2] ModemTest: EDGE MODEMU 11:00:38:269 [2] ModemTest: OK 11:00:38:285 [2] ThreadProcessModem: Processing 4CD9F57E.req... 11:00:38:300 [2] ThreadProcessModem: OUT: AT+CMGS="191471***31" 11:00:38:316 [2] ThreadProcessModem: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:38:316 [2] ThreadProcessModem: OUT: 11:00:38:410 [2] ThreadProcessModem: OUT: \r 11:00:38:410 [2] ThreadProcessModem: OUT: AT 11:00:38:425 [2] ThreadProcessModem: IN: OK 11:00:39:175 [2] ThreadProcessModem: Error: ERROR - Modem Response (1): +CMS ERROR: 304 11:00:40:175 [2] ModemTest: EDGE MODEMU 11:00:40:238 [2] ModemTest: OK --- Do you think it's a problem with the modem? My bet is that it is and that I will probably need to get a new one. I'm using Tmobile and have found the Option, Huawei, and Sony Ericsson models you described on eBay. I could only find the Option in 3G (you said to avoid that) but couldn't find an unlocked Huawei/Sony Ericsson. Do I need to have these unlocked and/or do you know of any other places that sell these besides ebay? Thanks for all your help. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7940 Registered: 10-2002 |
Hi Chris, That is very odd. Do you have ModemTextMode=Yes in the SMSGW.INI file? I notice that NowSMS is trying to send messages using the text mode interface, which is unusual. NowSMS only uses that mode if that configuration parameter under the [Modem - Driver Name] header, or if we test the modem and it returns an error attempting to init PDU modem (AT+CMGF=0). It's very odd that it is then returning an error code of +CMS ERROR: 304, because that error indicates an invalid PDU mode parameter. Yet, from your log, it is clear that NowSMS is not even using PDU mode. If by some chance, you have ModemTextMode=Yes in the SMSGW.INI file, remove it and try it again. The SMSC= setting is ignored when ModemTextMode=Yes. The only other thing I could suggest trying is this ... under the [Modem - driver name] header, add: CommandPostInit1=AT+CSCA="+12063130004",145 This setting will explicitly set the SMSC address in text mode. I don't have any ideas about retailers ... I usually use Expansys or Amazon Marketplace when ordering in the US. Maybe Des will have some ideas on Monday. -bn | |||
| Chris Sammy New member Username: Csammy Post Number: 8 Registered: 11-2010 |
Bryce, Thanks for your help but still no success. I am also unable to receive text messages. At this point I am somewhat convinced it is a modem issue at this is an off-brand one produced in China. Has anyone setup a T-mobile/Gsm/64-bit configuration that is working? I want to replicate the same settings and purchase the same modem to ensure it works this time and I don't waste time/resources on another bad modem. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7941 Registered: 10-2002 |
Chris, Our webmaster has a system using an Option ICON 322 on Win7 64-bit with a T-Mobile US SIM. I've confirmed with him that it is not having any problems with SMS or MMS. It is a 3G modem, but it only supports the ATT or Europe/Asia 3G bands. -bn | |||
| Chris Sammy New member Username: Csammy Post Number: 9 Registered: 11-2010 |
Bryce, Thanks for the response - was it necessary to have the Option ICON 322 unlocked? Not quite sure what this means... "It is a 3G modem, but it only supports the ATT or Europe/Asia 3G bands." Are you saying that the Option ICON 322 is fine for Tmobile although it is 3G? Lastly, would your Webmaster be willing to let me see his NowSMS configuration settings? Thanks guys! | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2658 Registered: 08-2008 |
Hi Chris, He bought his Option ICON 322 unlocked from Tiger Direct. No special settings were required. This modem supports 3G on the 2100Mhz frequency (used in most of Europe & Asia), and the 850Mhz and 1900Mhz frequencies used by AT&T. T-Mobile uses a frequency referred to as AWS ... it uses 1700Mhz for uplink and 2100Mhz for downlink. This modem only supports T-Mobile for EDGE and GRPS data connectivity. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2668 Registered: 08-2008 |
A follow-up note. Another thread had me asking our web guy questions about his system again, and he did note that he is using one non-default setting in his setup. For WAP Gateway IP Address, he has specified http://216.155.165.50:8080 which uses the WAP2/HTTP proxy instead of the WAP/WSP proxy at T-Mobile US. This resolved sporadic "Unable to connect to WAP Gateway" errors. -- Des NowSMS Support | |||
