Sponsored Content
Operating Systems Solaris Carrier Detection in Solaris 8 for Dial in and Null Modem Connections Post 302820883 by rstor on Thursday 13th of June 2013 03:09:33 PM
Old 06-13-2013
Carrier Detection in Solaris 8 for Dial in and Null Modem Connections

I am having troubles with carrier detection for dialing in via a modem or direct connection via a null modem connection under Solaris 8 (i.e. login session remains active after the modem disconnects). I tried two different dumb modems (which do not respond to AT commands) on the machine that I am dialling into . I tested the CD output on one of the modems and found the appropriate voltage on the CD line when a carrier is detected/not detected (I have confirmed this using a volt meter and applying the appropriate carrier tone via a function generator). If you dial in, login, then hang up, and call back the previous session continues without prompting to login.

I then decided to try a null modem connection. When accessing the serial console on the Solaris 8 system using a null modem cable, the login session remains active when disconnecting the cable and plugging it back in. To my understanding this should not happen, in the first case with the modem, or with the null modem cable as I disabled software carrier detection:

Code:
eeprom ttya-ignore-cd=true  
eeprom ttya-rts-dtr-off=true

Also I've specified the -S n parameter to disable software carrier detection:

Code:
/usr/sbin/pmadm -a -p zsmon -s ttya -i root \
-v `/usr/sbin/ttyadm -V` -fu -m "`/usr/sbin/ttyadm \
-p "login:" -d /dev/term/a -s /usr/bin/login -l contty2H from  -b \
-S n -m ldterm,ttcompat`" -y "dial in/out on serial port"


The instructions that I followed to setup the dial in connection was from Celeste Stokely’s Tutorial on Solaris 2.x Modems and Terminals.

I decided to test out carrier detection on FreeBSD 9.1 on a different machine running within virtual box. I used a usb-serial dongle which shows up as ttyu0 on the BSD machine. Carrier detection appears to work. When I establish a null modem connection (using the same null modem cable that I tried on the Solaris machine) I receive a login prompt. If I login, and then unplug and plug back the null modem cable, I get the login prompt again and the old session does not continue.

I have read a post on-line about carrier detection in Solaris not working and being "broken".

It this correct? Is carrier detection a known bug/issue in Solaris 8?

Last edited by Scott; 06-13-2013 at 06:52 PM.. Reason: Please use code tags
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Got connected with Modem but cannot dial Telephone no. to connect to host

Hello There, I configure my Modem as follow. Step1. # admintool & Then from Browse --> Serial Port i select tta port and Edit --> Modify From that i select Template : Modem:Dial Out Baud Rate: 9600 Ok Step 2 # tip /dev/cua/a connected (1 Reply)
Discussion started by: abidmalik
1 Replies

2. UNIX for Dummies Questions & Answers

Hyperterminal null modem connection to Solaris

I am new to Unix. I just got my SUN box from ebay with Solaris supposedly preloaded. The problem is I am unable to connect via Hyperterminal to Solaris, or more to the point, cannot tell if I have a successful connection and that solaris is the one not properly booted up. I hooked up a null... (3 Replies)
Discussion started by: seethams
3 Replies

3. UNIX for Dummies Questions & Answers

Dial-Up Modem

Im using Kinternet with a Lucent modem on Suse 9.0 Ive installed the ltmodem driver and suse says the device is ready and configured. Ive configured it at /dev/ttyS0 This is the log that Kinternet gives after trying to connect: SuSE Meta pppd (smpppd-ifcfg), Version 1.06 on linux. Status... (0 Replies)
Discussion started by: Synbios
0 Replies

4. SCO

Dial-Out & Dial-In Connections in OpenServer 5.0.6.

Friends, I am facing a problem in connecting two SCO Openserver 5.0.6 servers through Dial-Up connectivity as is done in the case of two Windows PCs. Please help me out with the following problems: (a) How to configure the modem? (b) How to setup a Dial-In connection? (c) How to... (1 Reply)
Discussion started by: thecobolguy
1 Replies

5. Solaris

null modem for testing

hi all.. sorry for repeating the same question many times, i just set up a null modem, i am using this as reference : DB25 DB9 -- - 2 TD ---- 2 RD 3 RD ---- 3 TD 4 RTS ---- 8 CTS 5 CTS ---- 7 RTS 7 GND ---- 5 GND 6 DSR -+ +--- 4 DTR 8... (0 Replies)
Discussion started by: waterbear
0 Replies

6. Solaris

help me!!!! how configure modem dial up with smc in solaris 10

Dear All, i have problem during install modem dial up with smc in solaris 10. i can't find "login" because it's stop in _receive started transmit started. thanks for your attention. this is the list during i dial to this number : altconn called Device Type ACU wanted... (0 Replies)
Discussion started by: mr.ridho
0 Replies

7. IP Networking

modem detection

How to get information that where is my modem configured in /dev. I have two modems configured in my device .. one is USB and other is PCI modem.. USB is detected as /dev/USB0. but how to see about PCI modem? (0 Replies)
Discussion started by: s123.radha
0 Replies

8. UNIX for Advanced & Expert Users

Modem (dial up) connecton to Unix machine

Hello to all, I have one problem and hope you'll be able to help me. It's about connecting Windows PC machine to Unix machine via dial up through Hyper terminal. Connection was working in the past. In the meantime, windows machine is replaced (win XP) and unix machine stayed as is. So nothing is... (1 Reply)
Discussion started by: Mick
1 Replies

9. BSD

Carrier Detection in FreeBSD

Regarding carrier detection on FreeBSD 9.1 being run within Virtual Box: I used a usb-serial dongle which shows up as ttyu0 on the BSD machine. Carrier detection appears to work. When I establish a null modem connection I receive a login prompt. If I login, and then unplug and plug back the... (2 Replies)
Discussion started by: rstor
2 Replies
acucap(4)						     Kernel Interfaces Manual							 acucap(4)

NAME
acucap - Automatic call unit capabilities file SYNOPSIS
/etc/acucap DESCRIPTION
The /etc/acucap file lists the types of autodial modems and describes their attributes. Whenever tip encounters an at field in /etc/remote file description, it searches /etc/acucap file description. If the at string there matches a name entry in /etc/acucap, the tip generic dialing routine places an outgoing call according to the attributes specified for the modem in the acucap file. Each line in the file describes how to dial a given type of modem. This description consists of strings, time delays, and flags used to control the action of any modem. Fields are separated by a colon (:). Entries that end in a backslash character () followed by a newline are continued on the next line. The first entry is the name or names of the modem. If there is more than one name for a modem, each is separated by a vertical bar (|). There cannot be any blank spaces or other characters between the first column and the modem name. The fields of the description follow the name. A field name followed by an equal sign (=) indicates that a string value follows. A field name followed by a pound sign (#) indicates that a numeric value follows. A field name followed by the separating colon (:) represents a Boolean. CAPABILITIES
The fields following the name of the modem define the capabilities of the modem. Capabilities are either strings (str), numbers (num), or Boolean flags (bool). A string capability is of the form: capability=value An example is: ss=^A^B A numeric capability is of the form: capability#value An example is: sd#1 A Boolean capability is specified simply by listing it. Strings that are not specified cause nothing to be issued. The following are available capabilities: (str) Abort string. This string is sent to the modem if tip is aborted. (num) Completion delay. This number gives the time to wait between completion string characters (in seconds, unless the ls Boolean is specified). (bool) Setting this Boolean causes the program to wait in the generic dial routine until the modem senses a carrier. (str) A modem command string which instructs the modem to change from the default speed to the speed specified by the xs field. (str) Completion string. The modem issues this string after receiving and responding to synchronization and dial strings. (num) Dial acknowledge. This number gives the time to wait before looking for a dial response (in seconds). (bool) Debug mode. Setting this Boolean causes the generic dialer to give more information as it dials. (num) Dial delay. This number gives the time between dial characters (in seconds) unless the ls Boolean is specified. (str) Dial initialization. This string is used to start a dialing sequence (placed just before the number to dial.) (str) Dial response. The modem sends this string if a dialing sequence that was just issued is successful. (str) Disconnect string. This string is sent to the modem when tip is finally disconnected. (str) Dial termination. This string is used to terminate a dialing sequence (placed just after the number to dial.) (num) Full delay. This number is the time to wait for a carrier to be detected (in seconds). If the call is not completed in this time, an error is returned. (bool) This Boolean causes the modem to hang up the phone if the line goes away. (num) This number specifies the speed at which the modem must be initialized. The conversation speed will later be set as specified by the xs field. (bool) Use an internal sleep routine rather than sleep(3) for delays. Thus, all delays are given in microseconds rather than seconds. (str) Online string. The modem sends this string after carrier has been detected. (bool) Causes a 1-second delay after toggling dtr (data terminal ready). This action will only be taken if re is also set. (bool) This Boolean causes the modem to toggle dtr (data terminal ready) before beginning synchronization. It is used to reset the present condition of the modem. (str) Replacement string. This string is a single character that will be substituted for an equal sign (=) or dash (-) in the number to be dialed; used so that delay characters can be represented uniformly, but allowing the correct delay character to be passed to a given modem. (num) Synchronization delay. This number gives the time between synchronization characters (in seconds unless the ls Boolean is specified.) (bool) This modem is attached to an interface that cannot return any characters until carrier is detected. The DMF32 interface acts in this way. (str) Synchronization response. What the modem sends in response to a synchronization string. (str) Synchronization string. The first string the modem expects to receive; a check to see if the modem is operating. (num) Specifies the speed the modem will operate at after initialization at the default speed in the is field. EXAMPLES
The following example shows an entry for a DF03 modem: df03|DF03|dec df03: :cr:hu:re:di=^A^B:dd#1:os=A:ds=^A:fd#40: RELATED INFORMATION
Commands: tip(1), sleep(3). Files: remote(4). delim off acucap(4)
All times are GMT -4. The time now is 07:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy