Meridian Telnet->RS232 login problem

Meridian Telnet->RS232 login problem

NewsGroups | Search | Tools
 comp.dcom.sys.nortel  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Meridian Telnet->RS232 login problem sjones 08-29-2007
Posted by on August 29, 2007, 5:18 am
If you were  Registered and logged in, you could reply and use other advanced thread options
We have a TCP to serial converter used to login to a Meridian Switch
at 9600 baud via a telnet session and are trying to send a file to
login and get the response OVL428, note the echoed characters are
also missing the odd character, however if we log in manually via the
same telnet session all works OK. Is there some speed issue here, or
does the Meridian have a limited RS232 input buffer size, and if so
does it toggle its handshake lines? We are sending 13 characters for
the login, wait for the response, then the password. Any thoughts?


Pure Networks
Posted by Al Gillis on August 29, 2007, 1:23 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
13 characters, huh? What are those 13? You might reconfigure your process
to send a return, then "LOGI", another carriage return and then wait for the
response "PASS?". Finally send the appropriate password. If you're sending
13 characters all at one swell foop you're probably sending to many and the
M-1 simply rejects whatever you send by claiming invalid login/password with
its' OVL message.



> We have a TCP to serial converter used to login to a Meridian Switch
> at 9600 baud via a telnet session and are trying to send a file to
> login and get the response OVL428, note the echoed characters are
> also missing the odd character, however if we log in manually via the
> same telnet session all works OK. Is there some speed issue here, or
> does the Meridian have a limited RS232 input buffer size, and if so
> does it toggle its handshake lines? We are sending 13 characters for
> the login, wait for the response, then the password. Any thoughts?
>



Posted by Telephonist on August 29, 2007, 3:52 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
On Aug 29, 3:18 am, sjo...@scannex.co.uk wrote:
> We have a TCP to serial converter used to login to a Meridian Switch
> at 9600 baud via a telnet session and are trying to send a file to
> login and get the response OVL428, note the echoed characters are
> also missing the odd character, however if we log in manually via the
> same telnet session all works OK. Is there some speed issue here, or
> does the Meridian have a limited RS232 input buffer size, and if so
> does it toggle its handshake lines? We are sending 13 characters for
> the login, wait for the response, then the password. Any thoughts?

I have two TTY ports connected to a serial (terminal) server, which
several of us access over the LAN via Hyperterminal Private Edition
(which allows mapping key macros). I have a function key configured
to send LOGI<ENTER>"User Name"<ENTER>"Password"<ENTER>ld 02<ENTER>
(for a total of 28 characters and four carriage returns) as one
continuous string at 9600 baud, with no problems. It logs me right in
and pulls up LD 2.


Similar ThreadsPosted
Problem with Nortel Meridian 61C November 26, 2007, 8:30 am
Novice Problem on Meridian changing Keys on 2008 February 24, 2005, 1:22 pm
MAT login ID and Password July 26, 2006, 6:49 pm
Nortel VPN login failure September 26, 2007, 7:17 pm
Contivity: Post login behavior August 29, 2007, 4:14 pm
Login to a Nortel BayStack 470 switch with radius March 20, 2006, 3:34 am
Meridian E1 to Meridian T1 through Cisco Router March 16, 2005, 7:44 am
Odd PRI problem on 81c April 4, 2006, 11:31 pm
problem with NAM vm box June 1, 2006, 10:52 am
Problem. December 21, 2006, 8:07 am

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map