Incorrect Telnet result.

wcks · Post by **wcks** » Fri Oct 09, 2009 9:39 pm

Hello,

I'd like to test the following telnet session before I purchase the pro version. However I don't get the correct result.

Can anybody help please?

Thanks,

Below is the correct result using telnet:

Code: Select all

xGate version 2 (build 67.9 at Jun 08, 2009 10:19:27 at host acer-401d326411)
Copyright (c) 1999-2008 Switchlab Limited
All rights reserved
------------------------------------------------------------------------------
login: admin
password:
Login success as admin
BM4_Xpro3# show call-stat
  Current counters:
    Nb of concurrent incoming calls: 78
    Nb of concurrent outgoing calls: 75
    Total nb of concurrent calls: 153
    Incoming calls/sec: 0
    Outgoing calls/sec: 0
    Total calls/sec: 0
  Maximum counters:
    Nb of concurrent incoming calls: 214
    Nb of concurrent outgoing calls: 212
    Total nb of concurrent calls: 426
    Incoming calls/sec: 12
    Outgoing calls/sec: 19
    Total calls/sec: 30
BM4_Xpro3#

Below are the script:

Code: Select all

TelnetConnect>10.20.3.32,23,hTN
TelnetWaitFor>hTN,login:,5,r1
TelnetSend>hTN,admin%CR%
TelnetWaitFor>hTN,password:,5,r1
TelnetSend>hTN,bigben%CR%
TelnetWaitFor>hTN,pro3#,5,r1
TelnetSend>hTN,show call-stat%CR%
TelnetWaitFor>hTN,pro3#,5,r2
TelnetClose>hTN
MessageModal>TELNET_SESSIONLOG

Below is the incorrect value of R2 in the watch list:

Code: Select all

TELNET_SESSIONLOG= xGate version 2 (build 67.9 at Jun 08, 2009 10:19:27 at host acer-401d326411)
Copyright (c) 1999-2008 Switchlab Limited
All rights reserved
------------------------------------------------------------------------------
login: [1@a[1@d[1@m[1@i[1@n
R2=[1@s[1@h[1@o[1@w[1@ [1@c[1@a[1@l[1@l[1@-[1@s[1@t[1@a[1@t
R1=
Login success as admin
BM4_Xpro3#

Post by **Marcus Tettmar** » Thu Oct 22, 2009 10:16 am

Just as a follow up for anyone who might be interested we worked with wcks on this who gave us a login to their telnet server and we found that Macro Scheduler was not removing escape sequences. We have now fixed this in the next maintenance release so that the telnet commands now strip out all escape sequences leaving only ANSI text.