USB Modem on Media Server dropping line 1

What are you connecting to? Hardware platform? Definity/CM software version?
What type login are you using?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

dadmin login

Operating system: Linux 2.6.18-128.AV7gPAE i686 i686
Built: May 10 21:38 2011

Contains: 02.1.016.4
CM Reports as: R015x.02.1.016.4
CM Release String: HP_DL360_G7-015-02.1.016.4

If you are dialing in remotely, you cannot do that from ASA. You will need a remote connection setup, then once you are connected, you will use a ASA profile setup with the IP address of the PBX to connect to.

So to setup the remote access username and password, you will need to access the pbx locally and set that up through the web maint page.

The S8XXX series servers are a little different then the old Definity pbx's.

A login with type "remote" must be used for the initial connection.

As far as programming logins and passwords, you do this only in the Main server.
The filesync to the LSP(s)/ESS(s) will take care of the synchronization of the
server login names, passwords and attributes to the other servers.

If you set a password in the LSP for a login, the next file sync from the Main
server will overwrite it(them) with the Main server login(s) and password(s).

If remlogin is login type "remote" you can test the login and password
authentication from linux command line to see if it starts PPP

ssh remlogin@$HOSTNAME

For testing using s8400 or s8500 which have modem connection via MPC / SAMP
ssh -p 10022 remlogin@$my-samp
--------------------------------------------------------------------------------
Are you configured for PPP access from your PC? In order to access the PBX using
the modem you need to use PPP to establish the connection and then use ASA or
telnet to access the server. You must have a remote login account created on the
PBX already. It is usually "dremote" for Dadmin logins, and "cremote" for
customer logins.

Excerpt from Admin Guide

To use Windows for PPP modem connection:
1. Navigate to the Network and Dial-up Connections screen and right-click the
dial up connection you want to use.
2. Select Connect.
3. Leave the User Name, Password, and Domain fields blank. If the Dial field is
blank, enter the appropriate telephone number.
4. Click the Dial button. When the media server's modem answers, the system
displays the After Dial Terminal screen.
5. Log on to the LAN.
A. Enter your remote access login name and password.
B. When the Start PPP Now! message appears, click Done.
C. The system displays a small double-computer icon in the lower right
portion of your screen.
6. Double-click the double-computer icon.
7. The system displays the connection?s Dialup Status box.
8. Click on the Details tab.
9. Note the Server IP address.
10. Open a telnet session to the Media Server:
Type telnet <ip-address>, where <ip-address> is the Server IP address as
noted in the Dialup Status box from Step 9.
11. Access SAT or use the CLI commands as needed.
--------------------------------------------------------------------------------

Windows 7 setup
1. Network and Sharing Center
2. Set up a new connection or network
3. Set up a dial-up connection
Create a Dial-up Connection
Dial-up phone number field: xxxyyyzzzz

You will do this in the terminal window after receiving login: prompt
User name: don't fill in
Password: dont fill in

I use DUN PPP, but you can have several for different PBX's, or you can change
the phone number each time you use this one RAS connection.
Connection name: DUN PPP or s87xx RAS

When you bring up the connection, you can modify attributes with the Properties
window.

General Tab is for configure modem, dialing rules, alternate numbers.

Options Tab is for personal preferences. (Below is what I use)
Display progress while connecting - check
Prompt for name and password, certificate, etc. - check
Include Windows logon domain - No check
Prompt for phone number - check

Idle time before hangup - never

PPP Settings
Enable LCP extensions - check
Enable software compression - check
Negotiate multi-link for single-link connections - No check

Security tab

Data encryption:
Optional encryption (connect even if no encryption)

Bullet in Allow these protocols
Unencrypt password (PAP) - check
Challenge Handshake Authentication Protocol (CHAP) - check
Microsoft CHAP Version 2 *MS-CHAP v2) - check
Automatically use my Windows login name - No check

Interactive logon and scripting
Show terminal windown - check

Networking tab
Internet Protocol Version 6 (TCP/IPv6) - check
Internet Protocol Version 4 (TCP/IPv4) - check

Set properties on each of the above
and on the General Tab, click Advanced

Use default gateway on remote network - No check
Automatic metric - check
PPP link
Use IP header compression - check
--------------------------------------------------------------------------------
Start RAS connection, Dial: change inads modem number for access or use a
different RAS connection for each connection. You can also change properties
for each session just before you use it.

Click Dial, wait for terminal window to return login: prompt
manually type your user logname, then the logname's password, wait for curly
braces and what looks like garbage to go across the window, click done.

Status the RAS connection and verify the IP address used when successfully
logged in. This will be the RAS access IP address for your server. Use it for
your IE browser, ASA, putty, etc. for access.

Disconnect the RAS connection when done.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting