Outgoing Data Call Setup.doc

Practical Example 4.1: Outgoing Data Call Setup. This example makes use of two modules. One device initiates a data call and the other is configured to accept this call. The setup below configures the originating side. For more insight into the example, look at Practical Example 4.2: Incoming Data Call Setup.

//THIS IS THE SETUP FOR THE MOBILE DEVICE ORGINATING THE DATA CALL TO THE MC75

ati              //Display product identification information – module and revision are presented

SIEMENS

MC55

REVISION 04.00

OK

at+cpin?              //Check whether network authentication is required. Module is ready for use

+CPIN: READY

OK

at+cops?              //Query present status of module’s network registration. Module has been

+COPS: 0,0,"MTN-SA"              //authenticated on the MTN Network

OK

at+csq              //Query quality of received signal strength and channel bit error rate

+CSQ: 31,99

OK

at+cmee=2              //Set mobile equipment error message format to verbose mode (strings)

OK

at+cbst=0,0,1                                                                                                                 //Set autobauding on both modules . If not set , then problems can occur across different Network Operators

OK

at\q3              //Set hardware flow control. This is necessary because there might be cases where the sending device  NB! Tell you when the buffer is full.

OK              //transmits data faster than the receiving device can accept. The module would then need to indicate to the

              //sending device to stop sending data to prevent data loss or corruption.

at&w              //Store the currently set parameters to a user defined profile in non-volatile memory

OK

atd0824114034              //Initiate a data call. NOTE: For data calls, the ‘;’ is left out. Also, the settings for AT^SM20 do not apply.

CONNECT 9600/RLP                                                                                    //The data call has been established correctly. A link with 9600 bps using Radio Link Protocol has been set up.

This is data sent back to the MC55+++This is more data sent to the MC55 after sw              //Here data is sent from the MC55 to the MC75 – you will see this output on Incoming Data Call script

itching the MC75 from data mode to command mode using +'s and then back to data              //The data presented here, is data which is sent from the MC75 to the MC55 ie. data sent to this module.

mode using ATO+++                                                                                                 

NO CARRIER                                                                                                                //Here the other party terminated the call hence the URC – NO CARRIER

atd0824114034;              //Setup up a voice call to the MC75 to see the difference in behaviour of an incoming voice call. NOTE: the ‘;’

OK              //Here the OK indicates that the connection has been setup. Refer to the Practical Example 4.2: Incoming Data Call

                                                                                                                              //Setup.

NO CARRIER              //URC indicating that the call was ended 

at^smso                                                                                                                //Shutdown module gracefully

^SMSO: MS OFF                                                                                                  //Response indicating that the terminal is powering down

OK

^SHUTDOWN                                                                                                  //URC indicating that the terminal can be powered down in less than 1 second