QMessage Monitor IBM i Configuration

Check that a valid QRemote Control license code has been entered, either in the F8 Defaults screen, or against each system record.

 

QMessage Monitor PC Configuration

From the main QMessage Monitor Maintenance module, select “Authority Lists” and check that an *SMSCMD authority list has been created. The user *PUBLIC should be created with no authority and then individual users added as required.

 

QMessage Monitor Escalation Procedures

  1. Escalation Users should be created or amended to use QRC.

     

  2. Support Group *QRC (the panic list) should be created, if required. This is used to notify Support staff that QRC may be experiencing problems.

  3. Ensure that a simple Escalation Procedure has been created to page the QRC user.

  4. Create an Auto Reply record to use the escalation procedure.

 

QRemote Control PC Configuration

  1. Always define a naming convention – allows for multiple servers and units to be configured.

  2. Ensure that the IBM i user ID and password given to you is valid, else use the MM profile.

  3. Remember to export the system configuration so that you can use MESSAGE.EXE for test purposes.

  4. Ensure that you know whether the SIM requires a PIN or not. Remember, that if using a SIM from a mobile phone, all messages should be cleared out and inform everyone not to use that number during the demo period.

  5. Ensure that the Service Center Address number is known beforehand or at least that you have verified the carrier. A drop-down list is available.

  6. Use the System Details to verify the firmware version, if necessary.

  7. Use the IBM i host TX job to verify the IBM i QRemote Control version.

  8. Use the HELP > ABOUT screen to verify the QRemote Control PC build information.

 

AT command troubleshooting guide

Tx:AT+CPIN?
Rx:+CPIN: READY
Rx:OK
Is a PIN number required?
“SIM PIN” response = waiting for PIN.
“SIM PUK” response = PUK code required.
Tx:ATZ
Rx:OK
Reload manufacturer default configuration
Tx:ATE0
Tx:ATE0
Rx:OK
Echo off.
Tx:AT+CGMI
Rx:Xircom
Rx:OK
Request manufacturer’s name.
Tx:AT+CGMM
Rx:Eagle II/Redhawk II
Rx:OK
Request equipment model code.
Tx:AT+CGMR
Rx:Version E12T223d
Rx:OK
Request equipment’s firmware level.
Tx:AT+CMGF=0
Rx:OK
Set’s Short Message mode to PDU mode.
Tx:AT+CSCA="+nnn"
Rx:OK
Registering with the SMS service centre.
Tx:AT+CMEE=2
Rx:OK
Report Mobile equipment error.
(2= enable result code and use numeric values)
Tx:AT+CSMS=0
Rx:+CSMS: 1,1,1
Rx:OK
Select message service.
(0= GSM 07.05 Phase 2 version 4.7.0 supported)
Tx:AT+CNMI=1,1,0,1,0
Rx:OK
New SMS message indications.
Tx:AT+CREG=0
Rx:OK
Registering with the GSM Network.
Tx:AT+CREG?
Rx:+CREG: 0, 1
Rx:OK
What networks are available?
Tx:AT+CSQ
Rx:+CSQ: 30,99
Rx:OK
Requesting signal strength data.
Tx:AT+CMGL=4
Rx:OK
List SMS messages from preferred store.
(4= all messages [PDU mode])

 

Troubleshooting Hints

  • If using a SIM from a mobile phone, always ensure that the inbox, outbox, and message archives have been cleared down.
  • Also, warn people who are likely to phone them, not to use the mobile number for the duration of the demo. An incoming call will cause the unit to generate a communications error.
  • Never insert or remove a SIM while the unit is powered on.
  • Always ensure that phone numbers are entered in the international format, +NNnnnnnn where NN=the country code, without spaces. This applies to escalation users as well as the Service Centre Address.
  • As the Flight Recorders are encrypted, a copy of DecoderRing will be required, if you wish to review the recorder for first level support purposes.
  • AT guides are available on a CD supplied with the hardware, if required.
  • If you receive a Frame Error message when configuring the SMS Server, amend the BAUD Rate to a higher value (best advice is to amend it to the maximum value and then work backwards to find the optimum setting).

 


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: January 08, 2018