Hi,
How we can get the running active sessions with terminal ID in ptx controller 9500, curently we are using the below mentioned command to get the list of established connection -
CMD Console:> netstat -a
is there any other way to check the running session information.
Regards
Shobhit Ke
Hello Shobhit
This is Arthur with the Psion Teklogix helpdesk
b>TERM (00A913F8) psts 00, iflag 00, msgq 00000000, rmsg 00000000b>CLINK (00A913C0) addr 1005d, ists 80, channel #52 (01666D50)b> fhno 00, ahno 00, frno 00, arno 00b> Amsg 00000000b> amsg 00000000b> on DTCP52 10.1.43.5b>SESSION(00A1D960) tnum 93., taddr 1005d, HAS_SRV ON_LINE (30)b> sess type TRANSPARENT params 135 15 15 0 40 12 4 0 hcnt 0b> host type ANSI name MARC_-, #1, pass 0, current server
A terminal with IP address 10.1.43.5 is connected to the controller using a 'direct TCP' connection (not 802.IQ). 802.IQ or other cellular devices will report the configured radio address and the base station on which they are most recently associated. If you look for this terminal in the output of your bcm !T, you should find that it has the terminal address (hex taddr=1005d) 65629.
This terminal is configued with terminal number 93 and currently has an ANSI open session [edit: the open session is with the controller, not the host] titled MARC. More information is required from the controller configuration to identify the IP address of the server.
Cellular terminals also include information about session tnum 0 with a type of 'control'. The ONLINE/OFFLINE status of this session indicates the state of the terminal.
Hi Shobhit,
You could run this command when you telnet into 9500 on the port 9523
telnet IPaddress of 9500 9523
> bcm tsts
You are going to see something like this:
b>TERM (0084A0F8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (0084A0C0) addr 10005, ists 80, channel #1 (0084A1A0)
b> fhno 00, ahno 00, frno 00, arno 00
b> Amsg 00000000
b> amsg 00000000
b> on DTCP1 10.65.3.69
b>SESSION(007EE890) tnum 5., taddr 10005, HAS_SRV ON_LINE (30)
b> sess type TRANSPARENT params 135 66 63 47 40 188 16 0 hcnt 0
b> host type TESS name 5250_t, #1, pass 0, current server
If you are using 9010t connection from the terminal you will see the IP address , terminal number and connection status of the terminal highlited above.
Kind regards,
Lana
Help Desk
Thanks for your reply.
We are using the 9010T and 802.IQV1 to emulate the application screen on Handheld, Now we need to retrieve the list of IP of Handheld connected to Ptx Controller and Host Application.
Also let me know if there is any documents relate to telnet debug command?
Shobhit Kr
is there any way or specific command to get the simple list of the activated sessions on ptx controller?
Hi Shobhit ,
For 802.IQ you can use:
>C print terse
-to see if there is 802.Iq beakoning :
C d 9
C d 0 to turn if off
C>Beacon timer expired.
C>Beacon bn1=39 bn0=b1
C>Tx( 10).62 0000 dst:ff:ff:ff:ff:ff:ff src:00:c0:af:00:42:b2
(mac address destination - broadcast )
WHERE TERMINAL NUMBER IS CONVERTED FROM DECIMAL TO HEX :
www.statman.info/.../hexadecimal.html
Sample of the output :
C>802.IQ v1 OFFLINE Taddr : 0x0077 MAC: 00:10:c6:80:21:68 RTT: 177 ms
C>802.IQ v1 OFFLINE Taddr : 0x0045 MAC: 00:16:41:02:f9:bb RTT: 186 ms
C>802.IQ v1 OFFLINE Taddr : 0x0008 MAC: 00:16:41:02:f8:39 RTT: 135 ms
C>802.IQ v1 OFFLINE Taddr : 0x0021 MAC: 00:16:41:02:f5:3c RTT: 192 ms
C>802.IQ v1 OFFLINE Taddr : 0x0035 MAC: 00:16:41:02:f8:7b RTT: 167 ms
Hi Shobit
Lana has pointed you in the right direction as regards the connections on the terminal side.
What is the emulation you are running on the host side? The commands available to list sessions open with the host depend on the emulation type.
Cheers
Nick, ANSCII - 9010T we are running at Host Type?
Hi Lana,
As advised by you we connected the Ptx Controller to telnet and getting the below mentioned information, as per the details below the telnet console was showing no's of terminal as ONLINE which are basically switch off. and its not associated with the RF Network? Can you pls explain me why its showing the devices as online on statement-
b> host type ANSI name MARC_-, #1, pass 0, current server
b>TERM (00A913F8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A913C0) addr 1005d, ists 80, channel #52 (01666D50)
b> on DTCP52 10.1.43.5
b>SESSION(00A1D960) tnum 93., taddr 1005d, HAS_SRV ON_LINE (30)
b> sess type TRANSPARENT params 135 15 15 0 40 12 4 0 hcnt 0
b>TERM (00A93A78) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A93A40) addr 10099, ists 80, channel #7 (0166B550)
b> on DTCP7 10.1.43.61
b>SESSION(00A38070) tnum 153., taddr 10099, HAS_SRV ON_LINE (30)
b> host type ANSI name WMS-MU, #2, pass 0, current server
b>TERM (01590E68) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (01590E30) addr 1009a, ists 80, channel #76 (016B2170)
b> on DTCP76 10.1.42.107
b>SESSION(00A39FC0) tnum 154., taddr 1009a, HAS_SRV ON_LINE (30)
b>TERM (00A198F8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A198C0) addr 1009d, ists 80, channel #53 (0166F330)
b> on DTCP53 10.1.42.110
b>SESSION(00A18080) tnum 157., taddr 1009d, HAS_SRV ON_LINE (30)
b>TERM (00A1B7F8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A1B7C0) addr 100ab, ists 80, channel #212 (016B6120)
b> on DTCP212 10.1.43.87
b>SESSION(00A1B760) tnum 171., taddr 100ab, HAS_SRV ON_LINE (30)
b>TERM (00A9E2D8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A9E2A0) addr 100ac, ists 80, channel #69 (016B5DD0)
b> on DTCP69 10.15.2.164
b>SESSION(00A399C0) tnum 172., taddr 100ac, HAS_SRV ON_LINE (30)
b>TERM (00A18138) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A18100) addr 100b4, ists 80, channel #85 (00AEE060)
b> on DTCP85 10.15.130.112
b>SESSION(00A396C0) tnum 180., taddr 100b4, HAS_SRV ON_LINE (30)
b>TERM (00A0DDB8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A0DD80) addr 100bf, ists 80, channel #82 (00AEB3C0)
b> on DTCP82 10.1.42.121
b>SESSION(00A0C0A0) tnum 191., taddr 100bf, HAS_SRV ON_LINE (30)
b>TERM (00A09AD8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A09AA0) addr 100cc, ists 80, channel #59 (0166D990)
b> on DTCP59 10.1.3.190
b>SESSION(00A09A40) tnum 204., taddr 100cc, HAS_SRV ON_LINE (30)
b>TERM (00A20C38) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A20C00) addr 100cd, ists 80, channel #42 (016B5CD0)
b> on DTCP42 10.1.42.135
b>SESSION(00A20BA0) tnum 205., taddr 100cd, HAS_SRV ON_LINE (30)
b>TERM (00A1B278) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A1B240) addr 100d0, ists 80, channel #10 (016908F0)
b> on DTCP10 10.1.42.138
b>SESSION(00A1B1E0) tnum 208., taddr 100d0, HAS_SRV ON_LINE (30)
b>TERM (00A1E9E8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A1E9B0) addr 100e2, ists 80, channel #217 (01663EA0)
b> on DTCP217 10.1.42.156
b>SESSION(00A3A7E0) tnum 226., taddr 100e2, HAS_SRV ON_LINE (30)
b>TERM (00A8B138) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A8B100) addr 100ee, ists 80, channel #236 (016875F0)
b> on DTCP236 10.1.42.168
b>SESSION(00A3A360) tnum 238., taddr 100ee, HAS_SRV ON_LINE (30)
b>TERM (015ED2B8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (015ED280) addr 100ef, ists 80, channel #74 (016B4960)
b> on DTCP74 10.1.42.169
b>SESSION(00A3A300) tnum 239., taddr 100ef, HAS_SRV ON_LINE (30)
b>TERM (01571B78) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (01571B40) addr 100f1, ists 80, channel #72 (0168B550)
b> on DTCP72 10.1.42.171
b>SESSION(00A3A240) tnum 241., taddr 100f1, HAS_SRV ON_LINE (30)
b>TERM (00A97F78) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A97F40) addr 100ff, ists 80, channel #84 (00AEE160)
b> on DTCP84 10.1.42.185
b>SESSION(00A3BCC0) tnum 255., taddr 100ff, HAS_SRV ON_LINE (30)
b>TERM (00A09418) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A093E0) addr 10108, ists 80, channel #255 (016B11B0)
b> on DTCP255 10.1.4.194
b>SESSION(00A09380) tnum 264., taddr 10108, HAS_SRV ON_LINE (30)
b>TERM (00A9EC38) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A9EC00) addr 1010b, ists 80, channel #11 (0166D050)
b> on DTCP11 10.1.42.197
b>SESSION(00A3B900) tnum 267., taddr 1010b, HAS_SRV ON_LINE (30)
b>TERM (00A12D98) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A12D60) addr 10113, ists 80, channel #75 (016B4F20)
b> on DTCP75 10.1.42.205
b>SESSION(00A14610) tnum 275., taddr 10113, HAS_SRV ON_LINE (30)
b>TERM (00A1A7F8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A1A7C0) addr 1011a, ists 80, channel #80 (00AEFEA0)
b> on DTCP80 10.1.42.212
b>SESSION(00A190A0) tnum 282., taddr 1011a, HAS_SRV ON_LINE (30)
b>TERM (00A916F8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A916C0) addr 10121, ists 80, channel #60 (01669A50)
b> on DTCP60 10.1.42.219
b>SESSION(00A3B1E0) tnum 289., taddr 10121, HAS_SRV ON_LINE (30)
b>TERM (00A232C8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A23290) addr 10129, ists 80, channel #36 (016679C0)
b> on DTCP36 10.1.42.227
b>SESSION(00A3CF00) tnum 297., taddr 10129, HAS_SRV ON_LINE (30)
b>TERM (00A383D8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A383A0) addr 1012a, ists 80, channel #197 (01672DB0)
b> on DTCP197 10.1.42.228
b>SESSION(00A3CEA0) tnum 298., taddr 1012a, HAS_SRV ON_LINE (30)
b>TERM (00A99778) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A99740) addr 10136, ists 80, channel #246 (01663470)
b> on DTCP246 10.15.130.86
b>SESSION(00A3CA20) tnum 310., taddr 10136, HAS_SRV ON_LINE (30)
b>TERM (0159E918) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (0159E8E0) addr 10137, ists 80, channel #61 (0166DB00)
b> on DTCP61 10.15.130.68
b>SESSION(00A3C9C0) tnum 311., taddr 10137, HAS_SRV ON_LINE (30)
b>TERM (0168FB88) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (0168FB50) addr 10138, ists 80, channel #134 (0166C180)
b> on DTCP134 10.15.130.69
b>SESSION(00A3C960) tnum 312., taddr 10138, HAS_SRV ON_LINE (30)
b>TERM (00A14EC8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A14E90) addr 1013a, ists 80, channel #71 (0169B230)
b> on DTCP71 10.15.130.71
b>SESSION(00A13780) tnum 314., taddr 1013a, HAS_SRV ON_LINE (30)
b>TERM (00A12798) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A12760) addr 1013b, ists 80, channel #194 (016827A0)
b> on DTCP194 10.15.130.72
b>SESSION(00A12060) tnum 315., taddr 1013b, HAS_SRV ON_LINE (30)
b>TERM (0159C818) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (0159C7E0) addr 1013c, ists 80, channel #250 (016770F0)
b> on DTCP250 10.15.130.73
b>SESSION(00A3C8A0) tnum 316., taddr 1013c, HAS_SRV ON_LINE (30)
b>TERM (00A0D818) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A0D7E0) addr 10143, ists 80, channel #78 (016812F0)
b> on DTCP78 10.15.130.80
b>SESSION(00A0D780) tnum 323., taddr 10143, HAS_SRV ON_LINE (30)
b>TERM (00A1E138) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A1E100) addr 10145, ists 80, channel #73 (016B74A0)
b> on DTCP73 10.15.130.82
b>SESSION(00A1E0A0) tnum 325., taddr 10145, HAS_SRV ON_LINE (30)
b>TERM (00AA8508) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00AA84D0) addr 10147, ists 80, channel #159 (016A8160)
b> on DTCP159 10.15.130.84
b>SESSION(00A3C5A0) tnum 327., taddr 10147, HAS_SRV ON_LINE (30)
b>TERM (00A09558) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A09520) addr 1014d, ists 80, channel #182 (0166BBE0)
b> on DTCP182 10.15.130.90
b>SESSION(00A094C0) tnum 333., taddr 1014d, HAS_SRV ON_LINE (30)
b>TERM (00A96138) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A96100) addr 1014e, ists 80, channel #249 (01672540)
b> on DTCP249 10.15.130.91
b>SESSION(00A3C3C0) tnum 334., taddr 1014e, HAS_SRV ON_LINE (30)
b>TERM (00A20578) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A20540) addr 10154, ists 80, channel #26 (01672980)
b> on DTCP26 10.15.130.97
b>SESSION(00A3C180) tnum 340., taddr 10154, HAS_SRV ON_LINE (30)
b>TERM (00A11528) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A114F0) addr 1015a, ists 80, channel #65 (016A3140)
b> on DTCP65 10.15.130.103
b>SESSION(00A14590) tnum 346., taddr 1015a, HAS_SRV ON_LINE (30)
b>TERM (00A1AF78) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A1AF40) addr 1015f, ists 80, channel #47 (01692B80)
b> on DTCP47 10.15.2.88
b>SESSION(00A3D6A0) tnum 351., taddr 1015f, HAS_SRV ON_LINE (30)
b>TERM (00AA0B18) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00AA0AE0) addr 10168, ists 80, channel #223 (01673C60)
b> on DTCP223 10.1.43.88
b>SESSION(00A3D3A0) tnum 360., taddr 10168, HAS_SRV ON_LINE (30)
b>TERM (00A92758) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A92720) addr 10185, ists 80, channel #87 (00AE9180)
b> on DTCP87 10.1.43.63
b>SESSION(00A3EDE0) tnum 389., taddr 10185, HAS_SRV ON_LINE (30)
b>TERM (00AA4D38) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00AA4D00) addr 10187, ists 80, channel #183 (01685270)
b> on DTCP183 10.1.43.65
b>SESSION(00A3ED20) tnum 391., taddr 10187, HAS_SRV ON_LINE (30)
b>TERM (00A89698) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A89660) addr 10188, ists 80, channel #86 (00AEF850)
b> on DTCP86 10.1.43.66
b>SESSION(00A3ECC0) tnum 392., taddr 10188, HAS_SRV ON_LINE (30)
b>TERM (00A19198) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A19160) addr 1018a, ists 80, channel #35 (01686220)
b> on DTCP35 10.1.43.68
b>SESSION(00A19100) tnum 394., taddr 1018a, HAS_SRV ON_LINE (30)
b>TERM (00A233A8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A23370) addr 1018c, ists 80, channel #83 (00AEEB20)
b> on DTCP83 10.1.43.70
b>SESSION(00A3EBA0) tnum 396., taddr 1018c, HAS_SRV ON_LINE (30)
b>TERM (00A142B8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A14280) addr 10190, ists 80, channel #35 (016945D0)
b> on DTCP35 10.1.43.74
b>SESSION(00A14220) tnum 400., taddr 10190, HAS_SRV ON_LINE (30)
b>TERM (00A18C38) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A18C00) addr 1019b, ists 80, channel #230 (016AA840)
b> on DTCP230 10.1.42.233
b>SESSION(00A18BA0) tnum 411., taddr 1019b, HAS_SRV ON_LINE (30)
b>TERM (00A1F7F8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A1F7C0) addr 101a5, ists 80, channel #97 (01663B80)
b> on DTCP97 10.1.42.243
b>SESSION(00A1E040) tnum 421., taddr 101a5, HAS_SRV ON_LINE (30)
b>TERM (00A1A0F8) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A1A0C0) addr 101a7, ists 80, channel #54 (0166C280)
b> on DTCP54 10.1.42.245
b>SESSION(00A1A060) tnum 423., taddr 101a7, HAS_SRV ON_LINE (30)
b>TERM (00AA4E78) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00AA4E40) addr 101a9, ists 80, channel #32 (016673B0)
b> on DTCP32 10.1.42.247
b>SESSION(00A3E2A0) tnum 425., taddr 101a9, HAS_SRV ON_LINE (30)
b>TERM (00A9A218) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00A9A1E0) addr 101b2, ists 80, channel #33 (0167C640)
b> on DTCP33 10.1.43.191
b>SESSION(00A3FF00) tnum 434., taddr 101b2, HAS_SRV ON_LINE (30)
b>TERM (00AA5188) psts 00, iflag 00, msgq 00000000, rmsg 00000000
b>CLINK (00AA5150) addr 101c5, ists 80, channel #81 (00AEAAA0)
b> on DTCP81 10.15.5.212
b>SESSION(00A3F8A0) tnum 453., taddr 101c5, HAS_SRV ON_LINE (30)
b>Link to 9150FF_C7 [10.1.15.102] (ch 1; id 988) closed (OpenTmOut)
b>Link to 9150FF_D11 [10.1.15.105] (ch 4; id 1552) closed (OpenTmOut)
b>Link to 9150AP_STAND-BY2 (ch 22; id 1812) closed (OpenTmOut)
b>Link to 9160_JV Gate [10.10.56.48] (ch 23; id 1352) closed (OpenTmOut)
b>Link to 9160_Material Gat (ch 24; id 984) closed (OpenTmOut)
b>Link to 9160_FF_C11 [10.1.15.228] (ch 25; id 1684) closed (OpenTmOut)
b>Link to 9160_FF_C07 [10.1.15.229] (ch 26; id 1212) closed (OpenTmOut)
b>Link to 9160_FF_C03 [10.1.15.230] (ch 27; id 1260) closed (OpenTmOut)
b>Link to 9160_SF_C04 [10.1.15.231] (ch 28; id 1652) closed (OpenTmOut)
b>Link to 9160_SF_A16 [10.1.15.233] (ch 30; id 892) closed (OpenTmOut)
b>Link to 9160_GF_S18 [10.1.15.234] (ch 31; id 1644) closed (OpenTmOut)
b>Link to 9160_GF_S08 [10.1.15.235] (ch 32; id 928) closed (OpenTmOut)
b>Link to 9150FF_C7 [10.1.15.102] (ch 1; id 928) closed (OpenTmOut)
b>Link to 9150FF_D11 [10.1.15.105] (ch 4; id 1644) closed (OpenTmOut)
b>Link to 9150AP_STAND-BY2 (ch 22; id 892) closed (OpenTmOut)
b>Link to 9160_JV Gate [10.10.56.48] (ch 23; id 1652) closed (OpenTmOut)
b>Link to 9160_Material Gat (ch 24; id 1260) closed (OpenTmOut)
b>Link to 9160_FF_C11 [10.1.15.228] (ch 25; id 1212) closed (OpenTmOut)
b>Link to 9160_FF_C07 [10.1.15.229] (ch 26; id 1684) closed (OpenTmOut)
b>Link to 9160_FF_C03 [10.1.15.230] (ch 27; id 984) closed (OpenTmOut)
b>Link to 9160_SF_C04 [10.1.15.231] (ch 28; id 1352) closed (OpenTmOut)
b>Link to 9160_SF_A16 [10.1.15.233] (ch 30; id 1812) closed (OpenTmOut)
b>Link to 9160_GF_S18 [10.1.15.234] (ch 31; id 1552) closed (OpenTmOut)
b>Link to 9160_GF_S08 [10.1.15.235] (ch 32; id 988) closed (OpenTmOut)
>Link to 9160_FF_C03 [10.1.15.230] (ch 27; id 984) closed (OpenTmOut)
>
Hi Everyone,
Any Update on My Below Quest?
Hi Shobhit
I believe that the ONLINE status you see here refers to the status of the termina vis-a-vis the controller, and does not refer to a host session. Terminals will stay online as far as the controller is concerned for some time if they go out of range, or are switched off - this way they can pick up quickly where they left off when they come back.
Since your controller appears to be running an ANSI host emulation, you can use the ansi CS command to look at the sessions each terminal has with the host (there can be more than one per terminal id, limited by the "sessions per terminal" parameter).
The command is "ansi CSn", where n is the terminal number. It will list the sessions for that terminal, and the session status.
Nick
Hi Nick,
Thx for your reply, To test the running status we configured device WAP 7535 on RF Network and started the Application via OTT Application. The device was pinging and working fine on the network
After that we checked the status of the device on Ptx Controller using "ansi CSn", it was showing that the device is ON.
After that we switched OFF the device and again checked the status of the same terminal but i am surprised that again telnet result was showing that device is ON/Active
>ANSI01 CS8
a>Terminal:8 Sess [IP Address/Name] Port
a> 0 Last=0 Estab
a> 1 10.1.1.26: 23 [SOCKET:372] Active
Is there any command for displaying the current list of devices which are connected to Ptx Controller ?
Hello Shobhit,
In this configuration, the ANSI task is responsible for managing the session between the controller and the host. The BCM task manages the sessions between the controller and the terminal.
"bcm !T" will give you a good idea of the terminals that have connected since the last reboot
"bcm tsts" will indicate the current status of each terminal.
Arthur
helpdesk
This is a little late, but you can try:
btsts