octel server issues affecting my aspect script

[frumpus]

seems like a lot of you are telecom pros in here so maybe you can explain something to me.

Ok, so I’m a computer guy, not so much a telecom person. In my world, machines are programmed to act in certain ways and they follow the programming consistently and the same actions always lead to the same responses and results. This doesn’t seem to be the way of Octel. I swear that thing has a mind of its own. It is difficult to write an aspect script to wait for a prompt when you don’t know which prompt it feels like using at any given moment.

Can you tell me why, for example, about half the time I connect with telnet I get the correct prompt:

ROCKHR@PASSWORD:

And the other half of the time I start with only:

ROCKHR@

Where I have to hit enter to get to:

PASSWORD:

Before I can log in?

It’s enough of a nuisance when I am logging on manually but for the script it is a real problem. Any thoughts on why this is happening or what can be done about it?

 

[frumpus]

By the way, I have worked around this problem using 'if waitfor' as mentioned in phonejack99's 'newbie script' thread. I'm just really curious as to what causes this inconsistency. any octel admins out there?

 

[teletubby5e]

been a while since i have been in one, but i remember the 250 logon process being a little flaky. i remember trying something in raw mode, and even adjusted the transmit pacing, and never was able to achieve the consistency you are looking for, but finally just made a kludge solution and started off the script with a few ^M entries to get to the right prompt. once logged in though, it was fine, i ran scripts that created a ton of mailboxes. if you find you are doing a lot of work in the octel, you need to investigate their cli command line interface, which is not documented very well.....

 

[teletubby5e]

I looked at my old scripts and see where I was using a ^C to wake it up for some reason, is that what you are using?