Modem mc35 error 619

modem mc35 error 619

Works for Windows 7/8/10/Vista/ XP. Follow These Simple Instructions. failure to report an accident; operating government vehicle. Complaint substantiated; appropriate disciplinary action. major public health problem in the United States today, A64 (II), Mc35, 1321 (I) EDITORIAL, Towards a rotavirus vaccine, Lancet 2:619-620. (1981).

Modem mc35 error 619 - Exaggerate

1989_SGS_Modem_Databook_and_Applications 1989 SGS Modem Databook And Applications

User Manual: 1989_SGS_Modem_Databook_and_Applications

Open the PDF directly: View PDF PDF.
Page Count: 802

11 ~ INTEGRATED TECHNICAL SALES I 2620 Augustine Drive, Suite 210 Santa Clara, CA 95054 (408) 727 -3406 Fax: (408) 727-5717 MODEM DATABOOK & APPLICATIONS 1st EDITION MAY 1989 USE IN LIFE SUPPORT MUST BE EXPRESSLY AUTHORIZED SGS-THOMSON' PRODUCTS ARE NOT AUTHORIZED FOR USE AS CRITICAL COMPONENTS IN LIFE SUPPORT DEVICES OR SYSTEMS WITHOUT THE EXPRESS WRITTEN APPROVAL OF THE PRESIDENT OF SGS-THOMSON Microelectronics. As used herein: 1. Life support devices to systems are devices or systems which, are intended for surgical implant into the body to support or sustain life, and whose failure to perform, when properly used in accordance with instructions for use provided in the labeling, can be reasonably expected to result in a significant injury to the user. 2. A critical component is any component of a life support device or system whose failure to perform can be reasonably expected to cause the failure of the life support device or system, or to affect its safety or effectiveness. TABLE OF CONTENTS INTRODUCTION Page 4 ALPHANUMERICAL INDEX 6 PRODUCT SELECTOR 8 MODEM DATASHEETS 11 MODEM APPLICATION SUPPORT 379 POWER SUPPLY MODULE 545 DSP DATASHEETS 551 DSP APPLICATION SUPPORT 723 3 INTRODUCTION SGS-THOMSON MODEM ICs: A COMMITMENT TO EXCELLENCE SGS-THOMSON Microelectronics has been a key player in the modem IC market for a long time, accumulating expertise in developing public telephone network modems - V.23, V.22bis, V.32 and others - and exploiting strong manufacturing resources to produce them in quantity. For this market the company employs technologies that are ideally suited to mixed analog/digital circuits, from a 3 micron double poly to 1.2 micron double metal CMOS processes allowing switched capacitor filtering and high density logic. Active in a broad spectrum of telecom applications, SGS-THOMSON's design and manufacturing engineers have experience in leading-edge circuits such as the ISDN echo canceller and S Interface transceivers. Moreover, the company is unique in combining expertise in analog conversion and filtering circuits exemplified by the Analog Front Ends and in digital signal processing techniques such as automatic adaptive equalization, digital filter carrier recovery and echo cancellation. In addition to Modem ICs, this databook includes a family of general purpose DSPs that are used in modem datapump design and other telecom applications. 4 v. 32 - With the SGS-THOMSON TS7532 kit you can build a V. 32 datapump with less than 10 chips. The Kit consist of three DSPs and three Analog Front End ICs. To simplify application software development the DSP family is supported by powerful development tools, including emulators, EPROM modules, cross assemblers simulators, and even a C compiler. Thanks to this set of tools, the users may adapt the SGS-THOMSON application software to suit their own specific needs. INTRODUCTION YOUR PARTNER FOR CUSTOMIZED MODEM ICs SGS-THOMSON Microelectronics has a long history of close cooperation with major customers in the development of modem les, putting the company in an enviable situation for the definition of new dedicated or custom products for this market. This capability is further enhanced by the combination of analog and digital functions on the same chip that is permitted by new generation technologies. This databook may contains the solution you are looking for, but if you have new ideas or a highly specific application contact SGS-THOMSON to discuss customized solutions. Development support - SGS-THOMSON's: Digital Signal Processor (DSP) family is supported by a com• prehensive range of hardware and software development tools. 5 ALPHANUMERICAL INDEX Function Page Number EF791 0 V.21N.23 FSK Modem .............................. . 13 EFRMAFE TS6895C/51/52 Evaluation Board ..................... . 381 GS-MS1212 Modem Board Power Supply ......................... . 547 ST18930EMU Emulation Development Board ........................ . 725 ST18930EPR EPROM Emulator .................................. . 729 ST18930HDS Hardware Development System ....................... . 731 ST18930LlB Software Routine Library ............................ . 735 ST18930SP Software Package .................................. . 737 ST18930SPC C Compilar Package ................................ . 743 ST18930/31 Digital Signal Processor ............................. . 553 ST18940/41 Digital Signal Processor ............................. . 619 TS7513 Single Chip Asynchronous FSK Modem ................ . 45 TS7514 Programmable V.23 Modem with DTMF ................ . 61 TS7514EVA TS7514 Evaluation Board ............................ . 385 TS7515 Single Chip DPSK and FSK Modem ................... . 83 TS7515EVA TS7515 Evaluation Board ............................ . 387 TS7524 V.22bis, V.22, Bell 212, V.21, V.22, Bell 103 Modem Chipset 101 TS7524EVA V.22bis Evaluation Board ............................ . 389 . V.32 Modem Chipset ............................... . 137 TS7532DEMO V.32 Demo Board .................................. . 391 TS7532DPUMP V.32 Data Pump ................................... . 393 TS7542 Multimode Modem Analog Front End .................. . 181 TS7542EVA Modem Analog Front and Evaluation Board ............. . 395 TS75C25 V.22bis, V.22, Bell 212, V.21, V.22, Bell 103 Modem Chipset 217 TS75C32 V.32,V.22bis,V.22,V.23,V.21 ,Bell 212,Bell 103 Modem Chipset 255 TS68930EMU Emulation Development Board ........................ . 745 TS68930EPR EPROM Emulator .................................. . 749 Type Number TS7532 6 ALPHANUMERICAL INDEX Function Page Number TS68930HDS Hardware Development System ........................ 753 TS68930LlB Software Routine Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757 TS68930SP Software Package ................................... 759 TS68930SPC C Compiler Package ................................. 765 TS68930/31 Digital Signal Processor .............................. 669 TS68950 Modem Transmit Analog Interface ...................... 301 TS68951 Modem Receive Analog Interface ...................... 319 TS68952 Modem Transmit/Receive Clock Generator ............... 349 TS75320 Digital Echo Canceller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Type Number 7 PRODUCT SELECTOR HIGH SPEED MODEMS Type Number TS75C32 TS7532 TS75320 TS75C25 TS7524 Description Page V.32, V.22bis, V.22, V.23, V.21, Bell 212, Bell 103 Modem chipset V.32 Modem Chipset ........................................ 255 137 Digital Echo Canceller ....................................... V.22bis, V.22, Bell 212, V.21, V.22, Bell 103 Modem Chipset ....... V.22bis, V.22, Bell 212, V.21, V.22, Bell 103 Modem Chipset ....... 367 217 101 ANALOG FRONT ENDS Type Number TS7542 TS68950 TS68951 TS68952 Description Page Multimode Modem Analog Front End ........................... Modem Transmit Analog Interface ............................. Modem Receive Analog Interface ............................... Modem Transmit/Receive Clock Generator ...................... 181 301 319 349 SINGLE CHIP MODEMS Type Number TS7515 TS7514 TS7513 EF7910 Description Page Single Chip DPSK and FSK Modem ............................ Programmable V.23 Modem with DTMF ......................... Single Chip Asynchronous FSK Modem ......................... V.21IV.23 FSK Modem ....................................... 83 61 45 13 MODEM APPLICATIONS SUPPORT Type Number Description Page TS7532DEMO TS7532DPUMP TS7524EVA TS7542EVA TS7515EVA TS7514EVA EFRMAFE V.32 Demo Board ............................................ V.32 Data Pump ............................................ V.22bis Evaluation Board ..................................... Modem Analog Front and Evaluation Board ...................... TS7515 Evaluation Board ..................................... TS7514 Evaluation Board ..................................... TS68950/51/52 Evaluation Board .............................. 391 393 389 395 387 385 381 Using the TS75320 Echo Canceller in V.32 Modems (AN341) Interfacing the TS7524 Modem Chipset to a Communication Control Processor (AN342) Using TS7515 Single Chip V.22/BeIl212A Modem Around 80C51 Microcontroller (AN343) How to Establish a Connection with an Unknown Modem Using CCITT V.22 Modem (AN344) Application Guide to the Use of the TS7515 Single Chip FSK and DPSK Modem (AN345) TS7513 V.23 Modem Principle and Applications (AN346) A very low cost and powerful solution for V.23 application: TS7514 (AN349) 8 397 427 443 447 451 515 533 PRODUCT SELECTOR POWER SUPPLY MODULE Type Number GS-M51212 Description Page 13W Triple Output DC-DC Converter Module ..................... 547 DIGITAL SIGNAL PROCESSORS Type Number ST18940/41 ST18930/31 TS68930/31 Description Page Digital Signal Processor ...................................... Digital Signal Processor ...................................... Digital Signal Processor ...................................... 553 669 619 DSP APPLICATIONS SUPPORT Type Number ST18930HDS ST18930EMU ST18930EPR ST18930SPC ST18930SP ST18930LlB TS68930HDS TS68930EMU TS68930EPR TS68930SPC TS68930SP TS68930LlB Description Page Hardware Development System ............................... Emulation Development Board ................................ EPROM Emulator ........................................... C Compiler Package ......................................... Software Package ........................................... Software Routine Library ..................................... Hardware Development System ............................... Emulation Development Board ................................ EPROM Emulator ........................................... C Compiler Package ......................................... Software Package ........................................... Software Routine Library ..................................... 731 725 729 743 737 735 753 745 749 765 759 757 Interfacing SGS-THOMSON DSP with Analog Front Ends (AN347) Application Notes Summary (AN348) 767 797 9 MODEM DAT ASHEETS 11 EF7910 V.21 / V.23 FSK MODEM • COMPLETE FSK MODEM - JUST ADD LINE INTERFACE • COMPATIBLE WITH BELL 103/113/108, BELL 202, CCITI V.21 , CCITI V.23 SPECIFICATIONS • NO EXTERNAL FILTERING REQUIRED • ALL DIGITAL SIGNAL PROCESSING, DIGITAL FILTERS AND ADCIDAC INCLUDED ON-CHIP • INCLUDES ESSENTIAL RS-232/CCITI V.24 HANDSHAKE SIGNALS • AUTO-ANSWER CAPABILITY • LOCAL COPYITEST MODES • 1200 BPS FULL DUPLEX ON 4-WIRE LINE • PIN-PROGRAMMABLE MODE SECTION P DIP28 (Plastic Package) J DESCRIPTION The EF7910 is a single-chip asynchronous Frequency Shift Keying (FSK) voiceband modem. It is pin selectable for baud rates of 300, 600, or 1200 bits per second and is compatible with the applicable Bell and CCITI recommended standards for 103/113/108,202, V.21 and V.23 type modems. Five mode control lines select a desired modem configuration. Digital signal processing techniques are employed in the EF791 0 to perform all major functions such as modulation, demodulation and filtering. The EF791 0 contains on-chip analog-to-digital and dig ital-to-analog converter circuits to minimize the external components in a system. This device includes the essential RS-232/CCITI V.24 terminal control signals with TIL levels. CERDIP28 (Cerdip Package) (Ordering Information at the end of the data-sheet) PIN CONNECTIONS DIP/CERDIP28 Clocking can be generated by attaching a crystal to drive the internal crystal oscillator or by applying an external clock signal. A data access arrangement (DAA) or acoustic coupler must provide the phone line interface externally. The EF791 0 is fabricated using HMOS technology. All the digital input and output signals (except the external clock signal) are TIL compatible. Power supply requirements are ± 5 volts. January 1989 M88EF7910-01 1/31 13 ~ .j>. ~ ID m o(') ...... r ~ n n TRANSMITTED 18 .-J L.J L-. DATA <>sAC; '" TRANSMITTED 8 TRANSMmER CARRIER JVVL "c :; G) ::0 » s: CAP, JVVL ~6 7 CAP 2 RECEIVER 5 RECEIVED CARRIER ~ I~ ~o i!il: .. en 13~ REQUEST TO SEND } MCz 02!-. 25 MC4 DATA TERMINAL READY ~ CLEAR TO SEND 11 ... ~ 14~ INTERFACE CONTROL 21 ~ CARRIER DETECT 1", ~ o 2 0 24 XTAL,/CLK 23 XTAL2 ~ MAIN REQUEST TO SEND CLEAR TO SEND 27 0-::- m "T1 L-- CARRIER DETECT 3~ s: n MCO MC3 IJlIi ~ n .-J L.J 12", 02?MC, ~ ""en @. ~i! 26 ,MAINO 5 RECEIVED DATA TIMING CONTROL 0 0 0 RING RESET 20 +5V Vee 4 9 22 0 -5V Vee 0 AGND 0 DGND } BACK "T1 ...oco EF7910 INTERFACE SIGNAL DESCRIPTION MCo - MC4 (control inputs) CARRIER DETECT (CD) These five inputs select one of thirty-two modem configurations according to the Bell or CCITT specifications listed in table 1. Only 19 of these 32 modes are actually available to the user. A LOW on this output indicates that a valid carrier signal is present at the receiver and has been present for at least a time, tCDON, where tCDON depends upon the selected modem configuration (Table 3b). A HIGH on this output signifies that no valid carrier is being received and has not been received for a time, .!cooFF. CARRIER DETECT remains HIGH when DTR is HIGH. Values fortcDoN and tcDOFF are configuration dependent and are listed in table 3b. Modes 0-8 are the normal operation modes. The 1200 Baud modes can be selected with or without a compromise equalizer. Modes 16-25 permit loop back of the EF791 0 transmitter and receiver. No internal connection is made. The user must externally connect the TRANSMITTED CARRIER pin (figure 1) to the RECEIVED CARRIER pin if analog loopback is required. For digital loopback, external connection of RECEIVED DATA and TRANSMITTED DATA is required. Whenever a mode in this group is selected, the effect is to set all transmit and receive filters to the same channel frequency band so that loopback can be performed. Modes 9-15 and 26-31 are reserved and should not be used. DATA TERMINAL READY (DTR) A LOW level on this input indicates the data terminal desires to send and/or receive data via the modem. This signal is gated with all other TTL inputs and outputs so that a low level enables all these signals as well as the internal control. logic to fun?tion. A HIGH level disables all TTL I/O pinS and the Internallogic. REQUEST TO SEND (RTS) A LOW level on this input instructs the modem to enter transmit mode. This input must remain LOW for the duration of data transmission. The signal has no effect if DATA TERMINAL READY is HIGH (disabled). A HIGH level on this input turns off the trans mitter. CLEAR TO SEND (CTS) This output goes LOW at the end of a delay initiated when REQUEST TO SEND goes LOW. Actual data to be transmitted should not be presented to the TRANSMITTED DATA input until a LOW is indicated on the CLEAR TO SEND output. Normally the user should force the TD input HIGH whenever CTS is off (HIGH). This signal never goes LOW as long as DTR is HIGH (disabled). CLEAR TO SEND goes HIGH at the end of a delay initiated when REQUEST TO SEND goes HIGH. TRANSMITTED DATA (TD) Data bits to be transmitted are presented on this input serially; HIGH (mark) corresponds to logic 1 and LOW (space) corresponds to logic O. This data determines which frequency appears at any instant at the TRANSMITTED CARRIER output pin (table 3a). No signal appears at the TRANSMITTED CARRIER output unless DTR is LOW and RTS is LOW. RECEIVED DATA (RD) Data bits demodulated from the RECEIVED CARRIER input are available serially at this output. HIGH (mark) indicates logic 1 and LOW (space) indicates logic O. Under the following conditions this output is forced to logic 1 because the data may be invalid: 1. When CARRIER DETECT is HIGH 2. During the internal squelch delay at half-duplex line turn around (202N.23 modes only) 3. During soft carrier turnoff at half-duplex line turn around (202 mode only) 4. When DTR is HIGH _ _ 5. When RTS ON and BRTS OFF in V.23/202 rnodes only 6. During auto-answer sequence BACK REQUEST TO SEND (BRTS) Since the 1200 bps modem configurations, Bell 202 and CCITT V.23, permit only half duplex operation over two-wire lines, a low baud rate "backward" channel is provided for transmission from the main channel receiver to the main channel transmitter. This input signal (BRTS) is equivalent to REQUEST TO SEND for the main channel, except it belongs to the backward channel. Note that since the EF791 0 contains a single transmitter, RTS and BRTS should not be asserted simultaneously. BRTS is meaningful only when a 202 or V.23 mode is selected by MCo-MC4. In all other modes it is ignored. 3/31 15 EF7910 For V.23 mode the frequency appearing at the transmitted carrier (TC) output pin is determined-ID'-a MARK or SPACE at the back transmitted data (BTD) input (table 3a). 5. When BRTS ON and RTS OFF in V.23 modes only For 202 mode a frequency of 387 Hz appears at TC when BRTS is LOW and BTD is HIGH. No energy (0.0 Volt) appears at TC when BRTS is LOW and BTD is HIGH. No energy (0.0 volt) appears at TC when BRTS is HIGH. BTD should be fixed HIGH for 202 back channel transmission. The signal, BRTS, then is equivalentto the signal, Secondary Requestto-Send, for 202 SIT modems, or Supervisory Transmitted Data for 202 C/D modems. This analog output is the modulated carrier to be conditioned and sent over the phone line. TRANSMITTED CARRIER (TC) RECEIVED CARRIER (RC) This input is the analog signal received from the phone line. The modem extracts the information contained in this modulated carrier and converts it into a serial data stream for presentation at the RECEIVED DATA (BACK RECEIVED DATA) output. BACK CLEAR TO SEND (BCTS) RING This line is equivalent to CLEAR TO SEND for the main channel, except it belongs to the back channel. BCTS is meaningful only when a V.23 mode is selected by MCo-MC4. This signal is not used in Bell 202 back mode. This input signal permits auto-answer capability by responding to a ringing signal from a data access arrangement. If a ringing signal is detected (RING LOW) and DTR is LOW, the modem begins a sequence to generate an answer tone at the TC output. ------ BACK CARRIER DETECT (BCD) ---=~-===-= This line is equivalent to CARRIER DETECT for the main channel, except it belongs to the backward channel. BCD is meaningful only when a 202 or V.23 mode is selected by MCo-MC4. For V.23 back channel mode, BCD turns on when either the MARK or SPACE frequency appears with sufficient level at the received carrier (RC) input. For 202 back channel mode, BCD turns on in response to a 387 Hz tone of sufficient level at the RC input. In this case BCD is equivalent to the signal, Secondary Received Line Signal Detector, for 202 SIT modems, or Supervisory Received Data for 202 C/D modems. BACK TRANSMITTED DATA (BTD) This line is equivalent to TRANSMITTED DATA for the main channel, except it belongs to the back channel. BTD is meaningful only when a 202 or V.23 mode is selected by MCo-MC4. For 202 back transmission of on/off keying, BTD should be fixed at a HIGH level. BACK RECEIVED DATA (BRD) This line is equivalentto RECEIVED DATA (except clamping) for the main channel, except it belongs to the back channel. BRD is meaningful only when a V.23 mode is selected by MCo-MC4. Underthe following conditions this output is forced HIGH: 1. 2. 3. 4. BRD HIGH DTR HIGH V.21 /1 03 mode During auto-answer 4/31 16 XTAL1, XTAL2 Master timing of the modem is provided by either a crystal connected to these two inputs or an external clock inserted into XTAL1. The value of the crystal or the external clock frequency must be 2.4576 MHz ± 01 %. Vcc + 5 volt power supply (± 5 %) VBB - 5 volt power supply (± 5 %). DGND Digital signal ground pin. AGND Analog signal ground pin (for TRANSMITTED CARRIER and RECEIVED CARRIER). CAP1, CAP2 Connection points of external capacitor/resistor required for proper operation of on-chip analog-to-digital converter. Recommended values are: C = 2 nF ± 10 %, R = 100 n ± 10 %. RESET This input signal is for a reset circuit which operates in either of two modes. It automatically resets when power is applied to the device, or it can be activated by application of an external active low TTL pulse. EF7910 Table 1. MC4 MC3 MC2 MC1 MC a 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 1 1 1 0 0 0 1 1 0 0 1 1 0 0 1 0 1 0 1 0 1 0 Bell 103 Originate 300 bps Full Duplex Bell 103 Answer 300 bps Full Duplex Bell 202 1200 bps Half Duplex Bell 202 with Equalizer 1200 bps Half Duplex CCITT V.21 Orig 300 bps Full Duplex CCITT V.21 Ans 300 bps Full Duplex CCITT V.23 Mode 21200 bps Half Duplex CCITT V.23 Mode 2 with Equalizer 1200 bps Half Duplex CCITT V.23 Mode 1600 bps Half Duplex 0 0 0 0 0 0 0 1 1 1 1 1 1 1 0 0 0 1 1 1 1 0 1 1 0 0 1 1 1 0 1 0 1 0 1 Reserved 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 0 0 1 1 0 0 0 1 0 1 0 1 0 1 0 1 Bell 103 Orig Loopback Bell 103 Ans Loopback Bell 202 Main Loopback Bell 202 with Equalizer Loopback CCITT V.21 Orig Loopback CCITT V.21 Ans Loopback CCITT V.23 Mode 2 Main Loopback CCITT V.23 Mode 2 with Equalizer Loopback CCITT V.23 Mode 1 Main Loopback CCITT V.23 Back Loopback 1 1 0 1 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 1 1 1 1 1 0 1 Reserved 1 1 Figure 1 : Loopback Configurations. EF7910 [----, r-----:"" .......~ I DATA TERMINAL ~1-', LOOPBACK ~ TRANSMITTER I I[~ TC ANAL';" 0 Tx PHONE UNE ~ L:_:=_~ Rx M88EF7910·Q3 5/31 17 EF7910 THEORY OF OPERATION The EF7910 MODEM consists of three main sections, shown in the block diagram - Transmitter, Receiver, and Interface Control. TRANSMITTER (modulator) The transmitter, shown in figure 2 receives binary digital data from a source such as a UART and converts the data to an analog signal using frequency shift keying (FSK) modulation. This analog signal is applied to the phone line through a DM or acoustic coupler. FSK is a modulation technique which encodes one bit per baud. A logic one applied to the TRANSMITTED DATA (TD) input causes a sine wave at a given frequency to appear at the analog TRANSMITTED CARRIER (TC) output. A logic zero applied to input TD causes a sine wave of a different frequency to appear at the TC output. As the data at the TD input switches between logical one and zero, the TC output switches between the two frequencies. In the EF791 0 this switching between frequencies is phase continuous. The frequencies themselves are digitally synthesized sine functions. The frequencies for each modem configuration available in the EF7910 are listed in table 3a. The process of switching between two frequencies as in FSK generates energy at many more frequencies than the two used in the modulation. All the transmitted information can be recovered from a frequency band B Hz wide, where B is the bit rate or maximum rate of change of the digital data at the TD input. This band is centered about a frequency, fc, where fc = f1 + (f2 - f1)/2 (f1 = lower of two FSK frequencies) (f2 = higher of two FSK frequencies) In addition to this primary information band, there exist side bands containing redundant information. It is desirable to attenuate these bands for two reasons: 1. The phone companies have specifications on the amount of energy allowed in certain frequency bands on the line. 2. If two independent information channels are present simultaneously on the line (e.g. 300 bps full duplex or 1200 bps half duplex with back), the redundant transmitter components may fall in the frequency band of the local receiver chan nel and interfere with detection. In the EF791 0 these redundant and undesirable components are attenuated by digital bandpass filters. Following the digital bandpass filters, the filtered FSK signal is converted to an analog signal by an on-chip DAC operating at a high sample rate. This analog FSK signal is finally smoothed by a simple on-chip analog low pass filter. RECEIVER (demodulator) A simplified block diagram of the EF7910 FSK receiver is shown in Figure 3. Data transmitted from a remote site modem over the phone line is an FSKmodulated analog carrier. This carrier is applied to the RECEIVED CARRIER (RC) pin via a DM or acoustic coupler. The first stage of the demodulator is a simple on-chip analog low pass anti-alias filter. The output of this is converted into digital form and filtered by digital bandpass filters to improve the signal to noise ratio and reject other independent channel frequencies associated with the phone line in the case of full duplex configuration. The bandpass filtered output is digitally demodulated to recover the binary data. A carrier detect signal is also digitally extracted from the received line carrier to indicate valid data. Figure 2: Transmitter Block Diagram. ...J1SL FROM UART TO SINE SYN'T)tESIZER DIGITAL BANDPASS FILTERS TC I)JW' TDDAA OR ACOUSnc COUPLER M88EF791 0-04 6/31 18 EF7910 Figure 3 : Receiver Block Diagram. 'WV' RC ANALOG PREFILTER DIGITAL BANDPASS FILTERS ADC DIGITAL DEMODULATION RD TO UART FROMOAA OR ACOUSTIC COUPLER M88EF7910·05 INTERFACE CONTROL This section controls the handshaking between the modem and the local terminal. It consists primarily of delay generation counters, two state machines for controlling transmission and reception, and mode control decode logic for selecting proper transmit frequencies and transmit and receive filters according to the selected modem type. Inputs and outputs from this section are as follows: REQUEST TO SEND (Main and Back) CLEAR TO SEND (Main and Back) CARRIER DETECT (Main and Back) RING MCO-MC4 DATA TERMINAL READY Internal logic clamps protocol signals to different levels under certain conditions (e.g., initial conditions). When Bell 103/113 and V.21 modem configurations are selected, the back channel signals are non-functional. Figures 6 and 7 depict the sequencing of the two state machines. State machine 1 implements main or back channel transmission and the auto-answer sequence. State machine 2 implements reception on main or back channel. The state machine powers on to the state labelled INITIAL CONDITIONS. Handsha~e signals are set to or assumed to be the levels listed in table 2. The machine then waits for DATA TERMINAL READY (DTR) to be turned on. Whenever DTR is turned to the OFF state from an ON condition, each state machine and external signals return to the initial conditions within 25 microseconds. After DTR is turned 6..,I ~ ON the EF7910 becomes operational as a modem and the state machines proceed as depicted in the flowcharts. The definitions of the terms Full Duplex and Half Duplex used in these flowcharts are depicted below (figs. 4 and 5). "Full Duplex" applies to all 103/113, V.21 modes. "Hall Duplex" applies to 202 and V.23, both forward and backward channel. Full Duplex: Data can be transmitted and received simultaneously at a rate of 300 baud. Two independent 300 Hz channels are frequency multiplexed into the 3000 Hz bandwidth of the phone line. The EF7910 configurations for the Bell 103/113 and CCITT V.21 can be operated full duplex. Half Duplex: In half duplex with back channel, the modem may transmit at 1200/600 baud and receive at 5/75 baud. Alternatively it may transmit at 5/75 baud and receive at 1200/600 baud. Examples are Bell 202 and CCITT V.23. Table 2 : Initial Conditions Data Terminal Re~DTR) Request to SenQJBTS) Clear to Send (CTS) Transmitted Data (TO) __ Back Channel Request to Send (BRTS) Back Channel Clear to Send (BCTS) Back Channel Transmitted Data (BTD) _ Ring (RING) Carrier Detect (CD) Received Data (RD) _ Back Channel Carrier Detect (BCD) Back Channel Received Data (BRD) SGS·1HOMSON OFF OFF OFF Ignored OFF OFF Ignored OFF OFF MARK OFF MARK 7/31 [email protected] m -" ~ ~ --J MAIN LINE BACK 2 S~r-4 "c~--e sec . "ft ,uv ~A~ rvw I n~ i= hnnlc I-ar s ce mgt sr I s ce ata cs e to cs In I' 0-------; ~ tone I I S~UELCH , Markl --I space Back channel data called to calling ~~~ Back channel data calling to called ' I / / I m ." ......

Incident Response

Additional Context

Related Sandbox Artifacts

Associated URLs
hxxps://the-eye.eu/public/Books/humble_books_20180509/silenceonthewire.pdf

Indicators

Not all malicious and suspicious indicators are displayed. Get your own cloud service or the full version to view all details.

  • Exploit/Shellcode
  • Network Related
    • Sends traffic on typical HTTP outbound port, but without HTTP header
      details
      TCP traffic to 95.101.13.67 on port 80 is sent without HTTP header
      TCP traffic to 8.253.193.109 on port 80 is sent without HTTP header
      TCP traffic to 92.122.173.100 on port 80 is sent without HTTP header
      TCP traffic to 184.86.53.99 on port 80 is sent without HTTP header
      source
      Network Traffic
      relevance
      5/10
  • External Systems
  • General
    • Contacts server
      details
      "95.101.13.67:80"
      "8.253.193.109:80"
      "92.122.173.100:80"
      "184.86.53.99:80"
      source
      Network Traffic
      relevance
      1/10
    • Creates mutants
      details
      "\Sessions\1\BaseNamedObjects\Local\Acrobat Instance Mutex"
      "\Sessions\1\BaseNamedObjects\DBWinMutex"
      "\Sessions\1\BaseNamedObjects\com.adobe.acrobat.rna.RdrCefBrowserLock.DC"
      source
      Created Mutant
      relevance
      3/10
    • Process launched with changed environment
      details
      Process "RdrCEF.exe" (Show Process) was launched with new environment variables: "PATH="%PROGRAMFILES%\(x86)\Adobe\Acrobat Reader DC\Reader\plug_ins;%PROGRAMFILES%\(x86)\Adobe\Acrobat Reader DC\Reader\;%PROGRAMFILES%\(x86)\Adobe\Acrobat Reader DC\Reader\plug_ins\test_tools""
      Process "RdrCEF.exe" (Show Process) was launched with modified environment variables: "PROCESSOR_ARCHITECTURE, CommonProgramFiles, ProgramFiles"
      Process "RdrCEF.exe" (Show Process) was launched with missing environment variables: "MEOW"
      source
      Monitored Target
      relevance
      10/10
    • Scanning for window names
      details
      "AcroRd32.exe" searching for window "_AcroAppTimer"
      "AcroRd32.exe" searching for class "AdobeAcrobatSpeedLaunchCmdWnd"
      "AcroRd32.exe" searching for class "AdobeReaderSpeedLaunchCmdWnd"
      "AcroRd32.exe" searching for class "Acrobat Instance Window Class"
      "AcroRd32.exe" searching for class "ACROSEMAPHORE_R18"
      "AcroRd32.exe" searching for class "JFWUI2"
      "AcroRd32.exe" searching for class "Shell_TrayWnd"
      source
      API Call
      relevance
      10/10
    • Spawns new processes
      details
      Spawned process "RdrCEF.exe" with commandline "--backgroundcolor=16448250" (Show Process)
      Spawned process "RdrCEF.exe" with commandline "--type=renderer --primordial-pipe-token=F1DA1740676506D44F63801C ..." (Show Process)
      Spawned process "RdrCEF.exe" with commandline "--type=renderer --primordial-pipe-token=1BED508080E9F1B86849DBEF ..." (Show Process)
      source
      Monitored Target
      relevance
      3/10
    • Spawns new processes that are not known child processes
      details
      Spawned process "RdrCEF.exe" with commandline "--backgroundcolor=16448250" (Show Process)
      Spawned process "RdrCEF.exe" with commandline "--type=renderer --primordial-pipe-token=F1DA1740676506D44F63801C ..." (Show Process)
      Spawned process "RdrCEF.exe" with commandline "--type=renderer --primordial-pipe-token=1BED508080E9F1B86849DBEF ..." (Show Process)
      source
      Monitored Target
      relevance
      3/10
  • Installation/Persistance
    • Creates new processes
      details
      "AcroRd32.exe" is creating a new process (Name: "%PROGRAMFILES%\(x86)\Adobe\Acrobat Reader DC\Reader\AcroCEF\RdrCEF.exe", Handle: 1372), "RdrCEF.exe" is creating a new process (Name: "%WINDIR%\explorer.exe", Handle: 1352), "RdrCEF.exe" is creating a new process (Name: "%PROGRAMFILES%\(x86)\Adobe\Acrobat Reader DC\Reader\AcroCEF\RdrCEF.exe"
      Handle: 1432)
      source
      API Call
      relevance
      8/10
    • Dropped files
      details
      "A9R8p8t17_1gznttl_1pc.tmp" has type "data"
      "A9Rkpyrn_1gzntto_1pc.tmp" has type "data"
      "Visited Links" has type "data"
      "0FDED5CEB68C302B1CDB2BDDD9D0000E76539CB0.crl" has type "data"
      "A9Rmpw91h_1gznttm_1pc.tmp" has type "data"
      "CE338828149963DCEA4CD26BB86F0363B4CA0BA5.crl" has type "data"
      source
      Extracted File
      relevance
      3/10
    • Found a string that may be used as part of an injection method
      details
      "Shell_TrayWnd" (Taskbar window class may be used to inject into explorer with the SetWindowLong method)
      source
      String
      relevance
      4/10
    • Touches files in the Windows directory
      details
      "RdrCEF.exe" touched file "%WINDIR%\SysWOW64\oleaccrc.dll"
      "RdrCEF.exe" touched file "%WINDIR%\Globalization\Sorting\SortDefault.nls"
      "RdrCEF.exe" touched file "%WINDIR%\System32\drivers\etc\hosts"
      "RdrCEF.exe" touched file "%WINDIR%\System32\spool\drivers\color\sRGB Color Space Profile.icm"
      "RdrCEF.exe" touched file "%WINDIR%\SysWOW64\KBDUS.DLL"
      "RdrCEF.exe" touched file "%WINDIR%\Fonts\arial.ttf"
      "RdrCEF.exe" touched file "%WINDIR%\Fonts\ARIALN.TTF"
      "RdrCEF.exe" touched file "%WINDIR%\Fonts\ariali.ttf"
      "RdrCEF.exe" touched file "%WINDIR%\Fonts\ARIALNI.TTF"
      "RdrCEF.exe" touched file "%WINDIR%\Fonts\arialbd.ttf"
      "RdrCEF.exe" touched file "%WINDIR%\Fonts\ARIALNB.TTF"
      "RdrCEF.exe" touched file "%WINDIR%\Fonts\arialbi.ttf"
      "RdrCEF.exe" touched file "%WINDIR%\Fonts\ARIALNBI.TTF"
      source
      API Call
      relevance
      7/10
  • Network Related
    • Found potential URL in binary/memory
      details
      Pattern match: "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      Pattern match: "http://ns.adobe.com/illustrator/1.0/"
      Pattern match: "http://purl.org/dc/elements/1.1/"
      Pattern match: "http://ns.adobe.com/xap/1.0/mm/"
      Heuristic match: "}xC%B%B%B%B%B%B%B%.vg"
      Heuristic match: "'Aid.sd"
      Heuristic match: "r__hr_tic.st"
      source
      String
      relevance
      10/10

File Details

All Details:

silenceonthewire.pdf

Screenshots

Loading content, please wait...

Hybrid Analysis

Tip: Click an analysed process below to view more details.

Analysed 4 processes in total.

  • AcroRd32.exe "C:\silenceonthewire.pdf" (PID: 2208)
    • RdrCEF.exe --backgroundcolor=16448250 (PID: 2444) Hash Seen Before
      • RdrCEF.exe --type=renderer --primordial-pipe-token=F1DA1740676506D44F63801C87F5CAAD --lang=en-US --disable-pack-loading --lang=en-US --log-file="%PROGRAMFILES%\(x86)\Adobe\Acrobat Reader DC\Reader\AcroCEF\debug.log" --log-severity=disable --product-version="ReaderServices/18.9.20044 Chrome/59.0.3071. (PID: 3300) Hash Seen Before
      • RdrCEF.exe --type=renderer --primordial-pipe-token=1BED508080E9F1B86849DBEF3A8B929D --lang=en-US --disable-pack-loading --lang=en-US --log-file="%PROGRAMFILES%\(x86)\Adobe\Acrobat Reader DC\Reader\AcroCEF\debug.log" --log-severity=disable --product-version="ReaderServices/18.9.20044 Chrome/59.0.3071. (PID: 3268) Hash Seen Before
Logged Script Calls Logged Stdout Extracted Streams Memory Dumps
Reduced Monitoring Network Activityy Network Error Multiscan Match

Network Analysis

This report was generated with enabled TOR analysis

DNS Requests

No relevant DNS requests were made.

HTTP Traffic

No relevant HTTP requests were made.

标 题: 【分享】安卓源码+内核修改编译(修改内核调试标志绕过反调试)
作 者: koflfy
时 间: 2016-10-26,18:05:19
链 接: http://bbs.pediy.com/showthread.php?t=213481

历经两天时间,终于完整的编译完安卓操作系统源码+内核,并修改了内核的几个调试标志以达到绕过一些反调试的目的。
在此感谢同学辉哥以及群友f8的指点,如有错误或者遗露的地方,欢迎网友跟贴指正。 

编译环境:
Ubuntu 14.04.4 for 64  http://releases.ubuntu.com/14.04/ubuntu-14.04.4-desktop-amd64.iso
jdk-6u45-linux-x64     http://download.oracle.com/otn/java/jdk/6u45-b06/jdk-6u45-linux-x64.bin?AuthParam=1467420548_35233aa4ba06eb66eb56a2a30757134b


手机:nexus 5
官方指导网址:http://source.android.com/source/index.html
编译 OS : Ubuntu 14 或者 Mac

安装vim编辑器  
sudo apt-get install vim


一、环境配置
安装JDK
创建安装目录,在/usr/java下建立安装路径(主目录下,并非home目录),并将下载好的jdk文件考到该路径下:

mkdir /usr/java

jdk-6u45-linux-x64 这个是自解压的文件,在linux上安装如下:

chmod 755 jdk-6u45-linux-x64.bin

(注意,这个步骤一定要在jdk-6u45-linux-x64 .bin所在目录下)
./jdk-6u45-linux-x64.bin

配置JDK,编辑/etc/profile文件

sudo vim /etc/profile

 在里面添加如下内容

export JAVA_HOME=/usr/java/jdk1.6.0_45
export JAVA_BIN=/usr/java/jdk1.6.0_45/bin
export PATH=$PATH:$JAVA_HOME/bin
SSPATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar
export JAVA_HOME JAVA_BIN PATH CLASSPATH

让/etc/profile文件修改后立即生效 ,可以使用如下命令:
. /etc/profile
注意:  . 和 /etc/profile 有空格.

重启查看java版本
 java -version
 屏幕输出:
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)

安装编译库
sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 \
lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache \
libgl1-mesa-dev libxml2-utils xsltproc unzip 

配置 USB 端口(查看后面 fastboot模式下不识别手机问题,该文件内容需要修改不能直接用于Nexus5)
下载51-android.rules文件(见附件,下载后把.doc扩展名去掉就行),放到 Ubuntu 的/etc/udev/rules.d/51-android.rules 目录下,
并根据手机的机型进行配置(把最后一个username字符串改成自己用户名) 

repo源码
使用 repo 工具进行源码下载。
下面的方法是不需要翻墙的,如果你认为自己的 VPN 够强大的话可以直接按照官网的指导来下载
设置 github 邮箱姓名使用 git 工具(不是必要的)
git config --global user.email "<你的 github 的 email 地址>"
git config --global user.name "<你的 github 的 name 名称>"


下载 repo 工具(清华的源)
git clone git://aosp.tuna.tsinghua.edu.cn/android/git-repo.git/
git clone https://aosp.tuna.tsinghua.edu.cn/android/git-repo.git

得到一个 git-repo 项目,找到里面的 repo 文件,复制到 ~/bin/repo 中
赋予执行命令
chmod a+x ~/bin/repo

修改下载 URL
双击打开 repo,修改 REPO_URL 为
REPO_URL = 'git://aosp.tuna.tsinghua.edu.cn/android/git-repo'
REPO_URL = 'https://aosp.tuna.tsinghua.edu.cn/android/git-repo'
然后使用
export PATH=~/bin:$PATH
导出 bin 执行目录

下载源码
新建一个目标文件夹用于存放源码文件,命令行中用 cd 指令进入。执行下面指令
repo init -u https://aosp.tuna.tsinghua.edu.cn/android/platform/manifest -b android-4.4.4_r1
-b 后面的参数是刚才查到的 branch 号

repo 更新使用 repo sync 指令即可完成下载,也可以使用下面的脚本

export PATH=~/bin:$PATH
repo sync -j4
while [ "$?" != "0" ]; do
  sleep 30
  repo sync -j4
done

接下来在官网下载手机对应的驱动(如下):
https://developers.google.com/android/nexus/drivers#hammerhead
找到Nexus 5 (GSM/LTE) binaries for Android 4.4.4 (KTU84P)
下面三个文件都要下载,解压后是三个.sh文件,放到安卓源码目录下,分别对三个文件chmod a+x 文件名赋权限,然后分别执行三个文件,此时会生成 vendor文件夹。

编译代码如果前面的步骤没出问题,那么用下面的指令就可以直接进行编译(aosp_arm-eng为模拟器,nexus5为aosp_hammerhead-userdebug),编译完后操作系统路径为out/target/product/hammerhead下。

source build/envsetup.sh #设置编译环境
lunch aosp_hammerhead-userdebug #设置编译选项
export USE_CCACHE=1 #使用缓存,可以加快以后的编译速度
prebuilts/misc/linux-x86/ccache/ccache -M 100G #使用 100GB 来作为缓存的空间
export CCACHE_DIR=/<path_of_yourt_choice>/.ccache #设置缓存地址,可以不要这个命令而使用默认缓存路径
make -j4


以上可用初始化脚本如下:(init)
export JAVA_HOME=/usr/local/java/jdk1.6.0_45
export JRE_HOME=$JAVA_HOME/jre
export CLASSPATH=$CLASSPATH:$JAVA_HOME/lib:$JAVA_HOME/jre/lib
export PATH=$JAVA_HOME/bin:$JRE_HOME/bin:$PATH
. build/envsetup.sh
lunch aosp_hammerhead-userdebug
make -j4 

此时编译的操作系统自带默认的内核,要修改内核的话,得重新下载内核源码并修改编译。在Android源码文件夹下创建kernel文件夹,并下载内核源码:(参考http://source.android.com/source/building-kernels.html)
1、git clone https://android.googlesource.com/kernel/msm.git
(由于实验手机设备为Nexus 5,因此我们选择内核代码为msm.git)

2、checkout所选内核版本
cd ~/source/kernel/msn
git branch –a
git checkout remotes/origin/android-msm-hammerhead-3.4-kitkat-rm1

3、修改内核调试标志,绕过反调试(Kernel proc)


要修改的文件:
kernel/msm/fs/proc/base.c 
kernel/msm/fs/proc/array.c 


要修改对以下文件的写入
Status,stat, 


修改点:
base.c 第285行改成如下:
else { 
           if (strstr(symname, "trace")) { 
                return sprintf(buffer, "%s", "sys_epoll_wait"); 
           } 
           return sprintf(buffer, "%s", symname); 
      } 

array.c第134行改成如下:
      static const char * const task_state_array[] = { 
           "R (running)",        /*    0 */ 
           "S (sleeping)",       /*    1 */ 
           "D (disk sleep)",     /*    2 */ 
           "S (sleeping)",       /*    4 */ 
           "S (sleeping)", /*     8 */ 
           "Z (zombie)",         /*  16 */ 
           "X (dead)",           /*  32 */ 
           "x (dead)",           /*  64 */ 
           "K (wakekill)",       /* 128 */ 
           "W (waking)",         /* 256 */ 
      };  


array.c第187行改成如下:
      "Gid:\t%d\t%d\t%d\t%d\n", 
                get_task_state(p), 
                task_tgid_nr_ns(p, ns), 
                pid_nr_ns(pid, ns), 
                ppid, /*tpid*/0, 
                cred->uid, cred->euid, cred->suid, cred->fsuid, 
                cred->gid, cred->egid, cred->sgid, cred->fsgid); 
修改完成后,按下面步骤编译内核,刷入系统


4、修改Makefile文件支持交叉编译器,编译内核。可用内核初始化脚本如下:
#How to build
export PATH='/home/coffee/source/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin':$PATH
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
make hammerhead_defconfig
make -j4

编译成功后可以看到下面的输出:
OBJCOPY  arch/arm/boot/zImage
Kernel:     arch/arm/boot/zImage is ready
CAT           arch/arm/boot/zImage-dtb
Kernel:     arch/arm/boot/zImage-dtb is ready
编译完内核后,内核生成的路径为:kernel/msm/arch/arm/boot目录下的zImage-dtb文件(nexus 5是这个文件,nexus 4是zImage文件,请注意别弄错了),把该文件复制到源码下的device/lge/hammerhead-kernel夹下(注意:nexus 4则为mako-kernel文件夹),覆盖掉同名文件,然后重新按上面步骤编译一次安卓源码(这时候编译很快完成)即可。

刷机
插上手机连接上电脑,确认正常连接上电脑后,进行刷机
转到源码img生成路径
cd source/out/target/product/hammerhead/
Adb reboot bootloader
Fastboot -w flashall

大概两分钟后,系统即刷成功。



在 bootloader 下连不上手机的参考前两面的配置 USB 端口一节
编译指令
部分编译的
m:编译所有的模块
mm:编译当前目录下的模块,当前目录下要有 Android.mk 文件
mmm:编译指定路径下的模块,指定路径下要有 Android.mk 文件
部分编译完以后,需要使用
Make snod 来把编译的东东整合到镜像中

Bootloader解锁
  我们买来的Nexus4默认都是锁了bootloader的,但是为了烧自己编的系统或者其他第三方ROM就需要解锁bootloader,google提供了接口让开发者可以方便的解锁。
  先把Nexus4关机,然后同时按下两个音量键和power键,一直按住直到界面上出现bootloader的画面。
  这时用usb线连上手机,在shell里执行:
$ fastboot oem unlock

fastboot模式下不识别手机问题。但adb模式正常
coffee @ coffee -pc:~$ lsusb
Bus 001 Device 010: ID 18d1:4ee0 Google Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


修改51-android.rules内容为以下两种之一(mode必须是0666,idVendor 与 idProduct(如果有)要与实际一一对应)
http://stackoverflow.com/questions/7641939/android-fastboot-waiting-for-devices
# fastboot protocol on manta (Nexus 5)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0666", OWNER="< coffee >"
# fastboot protocol on manta (Nexus 5)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", OWNER="<coffee>"

修改完后用命令
sudo service udev restart
重启服务进程,重新拨插数据线再
fastboot devices
查看是否识别出来
上面make步骤若出现 make:nothing to be done for 'droid'
就mak clean一下。

附上手机USB识别的需要的51-android.rules文件:



今天翻了下自己的收集的资料,发现看雪上有一篇比较详细的关于Android的源码和内核源码编译的帖子。尽管已经了解了怎么折腾,但是还是记录一下,谢谢看雪的这位兄弟。不管怎样,Andorid的源码和内核源码的编译还是谷歌官方的文档为参考基准。

/usr/local/bin/sendsms -d $CONTACTPAGER$ -Q -f'-' localhost 2>/dev/null }

Works a treat for us. Plus we like the fact that we can also send SMSs to this software. This means that, in theory at least, our engineers could acknowledge a problem or get a status report from Nagios by texting the SMS modem. We have yet to implement this but it was a big selling point for our installation.

I hope this helps,

Gareth.

________________________________

From: nagios-users-***@lists.sourceforge.net [mailto:nagios-users-***@lists.sourceforge.net] On Behalf Of Dennis Hünseler
Sent: 17 March 2008 08:02
To: Meylikhov
Cc: nagios-***@lists.sourceforge.net
Subject: Re: [Nagios-users] Sending notifications via SMS+mobile phone


Meylikhov schrieb:

Hi!
Do you use this one - Siemens TC35i Terminal -
http://www.warburtech.com/gsm/tc35i.terminal/ ?

-----Original Message-----
From: Sander Klein [mailto:***@pictura-dp.nl]
Sent: Friday, March 14, 2008 1:38 PM
To: Meylikhov
Cc: nagios-***@lists.sourceforge.net
Subject: Re: [Nagios-users] Sending notifications via SMS+mobile phone

Hi,

I use the siemens tc35i gsm modem and think it's great. Just hook it up
to your COM port, install smstool (which is in debian) create the
configfile, make a script to send sms and go....

It's really easy.

Greets,

Sander

Meylikhov wrote:


Hello, everybody!

Can anyone assist me in solving the following task: I need nagios to
send SMS via mobile phone connected to COM port. Are there are such
possibilities in nagios and are there any plugins that support sending
sms via mobile phone? I found only one plugin (NAGIOSMS:



http://www.nagiosexchange.org/Notifications.35.0.html?&tx_netnagext_pi1[p_vi
ew]=619


)that is currently supports sending notifications via mobile phone but
I even can't imagine how to connect mobile phone to my Linux Debian
4.0 server (2.6.18-6-686). Maybe someone already has configured
notifications send via mobile phone and can suggest me what mobile
phone to buy? I also need any help (suggestions,links, documentation,
etc) in connecting mobile phone to my Linux Debian 4.0 server.

My system:

Nagios server: Linux Debian 4.0 server 2.6.18-6-686

Nagios: nagios-3.0b5

Nagios plugins: nagios-plugins-1.4.11

NRPE: nrpe-2.10

Thank you!

------------------------------------------------------------------------

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
------------------------------------------------------------------------

_______________________________________________
Nagios-users mailing list
Nagios-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when


reporting any issue.


::: Messages without supporting info will risk being sent to /dev/null




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null



Hey, this is the right one. You can also use the Siemens MC35 Works also great with smstool. Used it in several companies...

Regards, Dennis


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null