Sponsored Content
Full Discussion: Building a 43p using BOOTP
Operating Systems AIX Building a 43p using BOOTP Post 302156063 by johnf on Monday 7th of January 2008 05:06:38 AM
Old 01-07-2008
Further the CDROM does not even appear in the SMS boot list.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

bootp/tftp

Hi, Setting up print queue, using SMIT on AIX And I have an option saying do I wish to make this a BOOTP/TFTP server. What exactly does this do? Thanks (3 Replies)
Discussion started by: maverick
3 Replies

2. UNIX for Dummies Questions & Answers

Network Install PXE/BootP/TFTP

Im trying to help my professor at school, were trying to setup a linux server, that is configured with bootp/tftp/PXE. the client computer NICs have support to boot off PXE. What we would like to do is if a client computer does not have an OS, it would boot off the server, and display a menu to the... (1 Reply)
Discussion started by: kwalick
1 Replies

3. UNIX for Dummies Questions & Answers

Save 43p bios?

Is there any way to backup the bios on a 43P-140 7043? (0 Replies)
Discussion started by: freestyle10269
0 Replies

4. Linux

BOOTP on HP Thin clients

Please m new around here! Can anyone take me thru implementing bootp on my thin clients via my central server? Preciate ur assistance. Thanks folks! (2 Replies)
Discussion started by: chuk_uka
2 Replies

5. AIX

43p 120

I have acquired a 43p 120 (7248-120) and I have two questions: Can anyone remember what is the highest version of AIX which I can install (5.1 I believe) and Can anyone remember how to boot this from the CDROM (boot floppy?) (1 Reply)
Discussion started by: johnf
1 Replies

6. SCO

Need help in BOOTP Server and Client configuration

Dear All; I need help in configuring the BOOTP server, I have found something on internet forums regarding the file: bootptab and editing some lines but Im not if they are all correct. Also, I need help to configure my clients (UNIX) to boot up with this bootp server(UNIX). I will be... (1 Reply)
Discussion started by: amirzandi
1 Replies

7. AIX

model 43P 7248 Recovery!

HI all! this is my problem: my boss got a Model 43P 7248-100 PowerPC server with the AIX 4.2 os, but some days ago it crashed and now it doesn't want to boot up again, it stops after the initial diagnostic phase with the "PowerPC" screen! I must recover some important data from the hard disk, so... (6 Replies)
Discussion started by: AKO
6 Replies

8. AIX

brisque impose 43P 150 aix version 4 HELP!!!!!!!!

hi to everybody I have a problem with the AIX version 4: I can not get into failsafe session kindly someone knows how to enter this mode? thanks in advance (5 Replies)
Discussion started by: elektrospeed
5 Replies

9. AIX

EXP400 with 43P machine not booting

Hello I connected the exp400 & turned on the aix machine which is 7043-150 but now I guess probably ODM is corrupted as it does not boot. Its stuck at 0518 code. Also, on the console it shows stuck on the kernel, which then it does not want to boot. Is it possible to fix from maintenance... (1 Reply)
Discussion started by: pdhawan
1 Replies

10. Solaris

Bootp/tftp issue neeeeeed help plz

i find a solution (2 Replies)
Discussion started by: shady_2005
2 Replies
GSMSMSD(8)						      System Manager's Manual							GSMSMSD(8)

NAME
gsmsmsd - SMS message reception daemon SYNOPSIS
gsmsmsd [ -a action ] [ --action action ] [ -b baudrate ] [ --baudrate baudrate ] [ -c concatenatedID ] [ --concatenate concatenatedID ] [ -C service centre address ] [ --sca service centre address ] [ -d device ] [ --device device ] [ -D ] [ --direct ] [ -f ] [ --flush ] [ -h ] [ --help ] [ -I init string ] [ --init init string ] [ -r ] [ --requeststat ] [ -s spool directory ] [ --spool spool directory ] [ -t SMS store name ] [ --store SMS store name ] [ -v ] [ --version ] [ -X ] [ --xonxoff ] { sms_type } DESCRIPTION
gsmsmsd reads new incoming SMS from the mobile phone and dispatches them to a user-defined action. Additionally it can send SMS message that it reads from a spooldir. gsmsmsd attaches itself to the device given on the command line (usually an GSM modem) using the specified baudrate and waits for incoming SMS messages. If no device is given, the device /dev/mobilephone is used. If no baudrate is given, a default baud rate of 38400 is used. If no action is given, the SMS message is printed to the standard output. If an action is specified the action is excecuted using the shell and the SMS message is written to the standard input of the action. gsmsmsd needs one empty storage slot for SMS messages in the mobile phone, otherwise SMS reception will not work. The SMS store to use for temporary storage of incoming SMS can be selected using the --store option, otherwise the ME default store is used. To terminate gsmsmsd cleanly (without losing SMS messages) one should send either SIGINT (CTRL-C on the command line) or SIGTERM to the process. Error messages are printed to the standard error output. If the program terminates on error the error code 1 is returned. sms_type may be any combination of: sms, no_sms Controls reception of normal SMS messages. cb, no_cb Controls reception of cell broadcast messages. stat, no_stat Controls reception of status reports. The default is sms, cb, and stat. OPTIONS
-a action, --action action The action to execute for each incoming SMS message. If no action is given the SMS is written to the standard output. -b baudrate, --baudrate baudrate The baud rate to use. -c concatenatedID, --concatenate concatenatedID If an ID is given, large SMSs are split into several, concatenated SMSs. All SMSs have the same ID and are numbered consecutively so that the receiving phone can assemble them in the correct order. IDs must be in the range 0..255. This number is increased by one for every outgoing concatenated SMS and wraps around after 255. Not all receiving phones will support concatenated SMSs (and dis- play them as separate SMSs), since all the numbering and ID information is carried in the user data header element at the beginning of the SMS user data. This information may show up as garbage in such phones. -C service centre address, --sca service centre address Sets the service centre address to use for all SUBMIT SMSs (may not work with some phones). -d device, --device device The device to which the GSM modem is connected. The default is /dev/mobilephone. -D, --direct Enables direct routing of incoming SMS messages to the TE. This is not supported by many mobile phone/GSM modem combinations. There- fore, the default is to store incoming SMS temporarily before processing them in the indicated store. -f, --flush This option causes gsmsmsd to flush (ie. read and erase) existing SMS messages from the SMS store selected by the --store option. The action given by the --action option is executed on each of the flushed SMS. This option should be used to ensure that enough space is available in the SMS store for temporary storage of incoming SMS, otherwise incoming SMS might be ignored silently by the ME. -h, --help Prints an option summary. -I init string, --init init string Initialization string to send to the TA (default: "E0"). Note that the sequence "ATZ" is sent first. -r, --requeststat Request status reports for sent SMS. Note: This option only makes sense if the phone supports routing of status reports to the TE. Otherwise the status reports might show on the phone's display or get lost. -s spool directory, --spool spool directory This option sets the spool directory where gsmsmsd expects SMS messages to send. The format of SMS files is very simple: The first line contains the phone number of the recipient. Everything else after the first line is interpreted as the SMS text. Please refer to gsmsendsms(1) for details on the SMS text character set and maximum length. gsmsmsd polls the spool directory every 5 seconds. Sent SMS message files are removed. -t SMS store name, --store SMS store name The name of the SMS store to read from (for the --flush option) or write to (for temporary SMS storage). This option must be must be used in conjunction with the --flush option. If this option is omitted the ME uses it's default SMS store for temporary storage of incoming SMS. A commonly available message store is "SM" (SIM card). -v, --version Prints the program version. -X, --xonxoff Uses software handshaking (XON/XOFF) for accessing the device. EXAMPLES
The following invocation of gsmsmsd sends each incoming SMS message as a mail to the user "smsadmin": gsmsmsd -d /dev/ttyS2 -b 19200 -a "mail smsadmin" This is the format of SMS deliver messages as output from gsmsmsd: ---------------------------------------------------------------- Message type: SMS-DELIVER SC address: '491710762100' More messages to send: 1 Reply path: 0 User data header indicator: 0 Status report indication: 0 Originating address: '01805000102' Protocol identifier: 0x39 Data coding scheme: default alphabet SC timestamp: 17.12.98 14:10:55(+0100) User data length: 159 User data header: 0x User data: 'Nicht vergessen! Die XtraWeihnachtsverlosung lauft noch bis zum 24.12. Nutzen Sie jetzt Ihre Gewinnchance und faxen Sie Ihren Teiln.-Gutschein an 0180/5000 056' ---------------------------------------------------------------- This is the format of SMS status report messages as output from gsmsmsd: ---------------------------------------------------------------- Message type: SMS-STATUS-REPORT SC address: '' More messages to send: 0 Status report qualifier: 0 Message reference: 0 Recipient address: '' SC timestamp: 00.00.00 00:00:00(+0000) Discharge time: 00.00.00 00:00:00(+0000) Status: 0x0 'Short message received by the SME' ---------------------------------------------------------------- The following invocation of gsmsmsd flushes all existing messages from the "SM" SMS store and looks in the "/tmp/spooldir" directory for SMS to send: gsmsmsd -d /dev/ttyS2 --spool /tmp/spooldir -f --store sm --action 'mail smsadmin' FILES
/dev/mobilephone Default mobile phone device. AUTHOR
Peter Hofmann <software@pxh.de> BUGS
Cell broadcast SMS message reception has not been tested, but it has been enabled in the gsmsmsd daemon. The mobile phone device is blocked when the gsmsmsd daemon is running, ie. it cannot be used for data transfer or from the other programs of this suite (gsmpb, gsmsms). Report bugs to software@pxh.de. Include a complete, self-contained example that will allow the bug to be reproduced, and say which version of gsmsmsd you are using. COPYRIGHT
Copyright (C) 1999 Peter Hofmann gsmsmsd is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. gsmsmsd is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details. You should have received a copy of the GNU Library General Public License along with gsmsmsd; see the file COPYING. If not, write to the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. SEE ALSO
gsminfo(7), gsmpb(1), gsmctl(1), gsmsendsms(1), gsmsmsstore(1). gsmsmsd v1.10 Sat Jun 16 22:10:00 UTC 2012 GSMSMSD(8)
All times are GMT -4. The time now is 04:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy