9 Replies Latest reply on Dec 22, 2008 8:49 PM by hangfung

    WAVECOM GSM Modem not work .

       Hello there  8-)

      I've brought a GSM modem and config everything I could find from the Doc.and once I trigger the SMS alert, the IPmonitor sent a SMS to my mobile properly .but after that, the SMS alert never worked again. 8-(

      I've checked other post on the forum, and also change the bit rate to 115200.

      my GSM MODEM is using the chipset WAVECOM Q2403A which compatible with GSM Phase2 / 2+
      I could use AT command to sent message from the GSM MODEM.so seems the GSM modem should not have any problem.

      BTW: coud you give me a more detailed configuration guide for how to connect a GSM MODEM ? or where I could got more debug message ?

      thanks in advance.


       Ricky with 8-)

       below is the log I've got when I force a test.

      ======================================

      Action Error: The outbound alert message did not reach its destination. The test failed. Call Log, started: Tuesday, July 8th, 2008 at 15:25:0





      0.001 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      0.039 secsRecv.1B
      0.528 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      0.531 secsRecv..FB F3
      1.060 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      1.063 secsRecv..FF FD
      1.219 secsRecv.FC
      1.592 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      1.597 secsRecv...FF FF FF
      2.122 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      2.133 secsRecv...FF FF FF
      2.654 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      3.107 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      3.654 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      4.107 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      4.560 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      4.563 secsRecv.1B
      5.092 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      5.094 secsRecv{s7B 73
      5.623 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      5.627 secsRecv..7F 7F
      6.154 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      6.160 secsRecv.~.7F 7E 7F
      6.686 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      6.697 secsRecv...7F 7F 7F
      7.217 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      7.670 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      8.123 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
      8.576 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D

      ===========================================

       

      and output of the config from the GSM modem

      ================

       at&v
      Q:0 V:1 S0:000 S2:043 S3:013 S4:010 S5:008
      +CR:0 +CRC:0 +CMEE:0 +CBST:0,0,1
      +SPEAKER:0 +ECHO:0,1 &C:1 &D:2 %C:0
      +IPR:115200 +ICF:3,4 +IFC:2,2

      OK

      =================

        • Re: WAVECOM GSM Modem not work .
          Peter.Cooper
          Hello Ricky,

          Wavecom should work, and it would appear that your modem is correctly configured. The list of AT commands ipMonitor is sending to the modem is to try and find a baud rate + framing + parity bits that your modem will respond on. It's looking for an "OK" but doesn't find one. This log is what we have available to debug with, and it's been a reasonably good tool thus far. It could use some improvements though, but we developers can figure out lots of stuff.

          I've seen this sort of thing a GPRS modem, where the user wasn't aware that his modem was being kicked in to provide an internet connection (removing the ability to send sms messages while doing so). I don't think this is the case.


          Before we kick this to our technical support, perhaps we can just try here on the forum a lower baud rate. Can you please try this in HyperTerminal (it will set your modem to want 38400 8N1 with hardware flow control, on power up)?

          AT&F
          AT+IPR=38400
          AT+ICF=3,4
          AT+IFC=2,2
          AT&W

          Next, close HyperTerminal and then reconfigure the Alert to use 38400 and 8N1

          Finally, try another a Force Test of your Alert and post your findings?

            • Re: WAVECOM GSM Modem not work .

               Hello Peter 8-)

                     Thanks for your reply first.Yes, I've tried the settings you've mentioned .

              =====================

              at&v
              Q:0 V:1 S0:000 S2:043 S3:013 S4:010 S5:008
              +CR:0 +CRC:0 +CMEE:0 +CBST:0,0,1
              +SPEAKER:0 +ECHO:0,1 &C:1 &D:2 %C:0
              +IPR:38400 +ICF:3,4 +IFC:2,2

              =====================

              and still the same.error log is almost the same, see below:

              ================================

              Action Error: The outbound alert message did not reach its destination. The test failed. Call Log, started: Wednesday, July 9th, 2008 at 09:43:25





              0.001 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              0.007 secsRecv.1B
              0.532 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              0.540 secsRecv..FB F3
              1.063 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              1.075 secsRecv...FF FE FF
              1.595 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              1.616 secsRecv...FF FF FF
              2.126 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              2.579 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              3.032 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              3.110 secsRecv.....7F 7F 7F 7F 7F
              3.564 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              3.567 secsRecv`..60 1C 00
              4.095 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              4.100 secsRecv.~12 7E
              4.626 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              4.633 secsRecv.1B
              5.158 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              5.165 secsRecv{s7B 73
              5.689 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              5.701 secsRecv.~.7F 7E 7F
              6.221 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              6.243 secsRecv...7F 7F 7F
              6.752 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              7.205 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              7.658 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              7.699 secsRecv.FF
              7.735 secsRecv..FF FF
              8.190 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              8.193 secsRecv...E0 1C 80
              8.721 secsSent..ATE0Q0.AT..1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
              8.726 secsRecv..12 FE

              ========================

               

              weird thing is it use to worked once (and only once,I still have the message in my mobile),but just after one weekend, it's totally not work at all.

              I've also tried 9600 but still not work.

              BTW: you've mentioned "...Alert to use 38400 and 8N1",so I could set the baud to 38400, 8 bit and none parity,but what is the "1" mean ? how could I set the "1" in the IPmonitor side ?

               

              Regards

              Ricky with 8-)

                • Re: WAVECOM GSM Modem not work .
                  Peter.Cooper

                  Hello Ricky,

                  ipMonitor assumes that people want 1 stop bit and the modem to have 1 stop bit... so something else is going on. Are you an evaluator, or do you have an active maintenance plan? Depending on which avenue, I'd like to see your case get resolved off the forums (and then post back with the findings) and appropriate settings.

                    • Re: WAVECOM GSM Modem not work .

                      Hi Peter 8-)

                          Thanks for the interpretation,so I don't need to worry about the "1". I still didn't get it work properly,but I will try to make it out.and of course, if I finally (or luckily) make it work again, I'm sure I'll post my findings here.

                          thanks anyway for your help.

                       

                      Regards

                      Ricky with 8-)

                        • Re: WAVECOM GSM Modem not work .
                          Peter.Cooper

                          Private message sent.

                            • Re: WAVECOM GSM Modem not work .
                              bfarmil

                              Was a resolution found to this problem?


                              I have exactly the same problem with an Itegno WM1080A USB GSM modem which also has a Wavecom chipset.  We are running an Evaluation copy of IPmonitor 9 on Windows 2003 Server R2 SP2 on an HP DL360G5.


                              I have tried all sorts of things and i'm fresh out of ideas.  Any assistance would be appreciated.


                              Thanks,


                               


                              Bryce.


                               Some other details:


                              Can connect to the modem on the same server using Putty with no problems and can send an SMS using AT commands.


                              Have done a at&f reset and entered the commands as suggested above.  It appears that IP Monitor has problems opening the emulated COM port that the USB modem presents as (my 2 cents worth).

                    • Re: WAVECOM GSM Modem not work .

                      Hi,Peter:

                          I have the same problem!

                      Our company bought your products ipmoniter9 before, we got some problems when we tested Alert function, when we used GSM MODEM (interface: RS-232C/USB; communication module: WAVECOM GSM 900/1800) to send SMS to mobile, there’s error happened below:

                       Action Error: The outbound alert message did not reach its destination. The test failed. 

                       Call Log, started: Thursday, December 11th, 2008 at 14:29:42     

                      0.011 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      0.454 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      0.904 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      1.355 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      1.806 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      2.256 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      2.707 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      3.158 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      3.608 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      4.059 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      4.510 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      4.960 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      5.411 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      5.862 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      6.312 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      6.763 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      7.214 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D  

                      7.664 secs    Sent    ..ATE0Q0.AT..          1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D 

                       Through debugging the parameter config many times, we found some problems below:

                       1.       We can send SMS through utilizing MS HyperTerminal (9600,8,0,1) debug successfully, and also we can send SMS through utilizing GSM MODEM software (The Sms Cat Software) successfully.

                       2.       Generally we can find four options including bps, data bits, Parity, Stop bits in SMS plating ports config options, however, here we only find three options like Baud, Data Bits, Parity in Action Parameters of ipmoniter. That means we can not find Stop bits option properly. What’s the problem?

                       Could you please advise and help us to solve above problems? Thank you very much.

                       We’re looking forward to hearing from you soon. 

                       BR,

                      lory.sun

                      • Re: WAVECOM GSM Modem not work .

                         

                         

                         

                        WAVECOM MODEM request:


                        any AT command issued by DTE must start with a capital ‘A’ and ‘T’

                        (or ‘\’). If not, DCE may send back some garbage characters and get

                        de-synchronized. Shoud it happen, DTE shall just issue once or twice

                        AT\r’ (at 2400 or 4800 baud) or just ‘AT’ (at 9600 baud) to get the

                        modem re-synchronized.

                        · the DTE shall wait for 1ms after receiving the last character of the AT

                        response (which is always ‘\n’ or 0x0A) to send a new AT command at

                        either the same rate or a new rate. Shoud this delay ignored, DCE can

                        get de-synchronised. Once again, sending once or twice ‘AT\r’ or just

                        AT’ causes the DCE to recover.

                         

                        --------------------------------------------------------------------------------
                        Action Error: The outbound alert message did not reach its destination. The test failed.
                         
                        Call Log, started: Monday, December 22nd, 2008 at 20:38:32

                         
                        0.060 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        0.083 secs Recv . 1B 

                        0.620 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        0.649 secs Recv .. FB FB 

                        1.201 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        1.282 secs Recv . FF
                         
                        1.356 secs Recv .. FF FF
                         
                        1.762 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        2.223 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        2.268 secs Recv . 7F
                         
                        2.302 secs Recv ~. 7E 7F
                         
                        2.803 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        2.814 secs Recv .. 00 00
                         
                        3.354 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        3.364 secs Recv .. 00 00
                         
                        3.935 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        3.945 secs Recv .. 00 00
                         
                        4.496 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        4.511 secs Recv ~. 7E 1E
                         
                        5.077 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        5.100 secs Recv . 1B
                         
                        5.638 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        5.666 secs Recv {{ 7B 7B
                         
                        6.219 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        6.304 secs Recv . 7F
                         
                        6.373 secs Recv .. 7F 7F
                         
                        6.769 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        7.250 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        7.293 secs Recv . FF
                         
                        7.330 secs Recv .. FE FF
                         
                        7.811 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        7.818 secs Recv .. 00 00
                         
                        8.352 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        8.361 secs Recv ... E0 00 00
                         
                        8.912 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        8.922 secs Recv . 00
                         
                        9.453 secs Sent ..ATE0Q0.AT.. 1B 0D 41 54 45 30 51 30 0D 41 54 0D 0D
                         
                        9.468 secs Recv .. FE 9E
                         
                        =======================================
                        WAVECOM MODEM
                        MULTIBAND  900E  1800
                        430a09gm.2C 1208244 110801 19:19
                        500156361171627
                        +CSCS: "GSM"
                        +CMGF: 0
                        460029866079577
                        +CCID: "89860008190743615294"
                        Q:0 V:1 S0:000 S2:043 S3:013 S4:010 S5:008
                        +CR:0 +CRC:0 +CMEE:0 +CBST:0,0,1
                        +SPEAKER:0 +ECHO:0,1 &C:1 &D:1 %C:0
                        +IPR:9600 +ICF:3,4 +IFC:2,2
                        ========================================
                        [1229991986] Connected to Reporting Services
                        [1229992471] sms error: Unable to initialize modem