Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How do I set up call tracing? 1

Status
Not open for further replies.

perelo

Technical User
Sep 14, 2005
24
SE
Wé´re having trouble with an ACD-queue and I would like to monitor incoming calls on DN 5972 and see how/where it´s routed, how do I do that?
 
What am I supposed to get out of that command? Is there a polling interval involved?
I´m reading in my maintenace book from Meridian and it says something about "enhanced trace command", do I have to enable that for the specific DN/TN?

I typed this: "trac 0 5972" and got this in reply: "tra122".
 
Is it possible to trace an external call with this program? The 5972 extension is a CDN, does that cause a problem when tracing?
 
ld 50
entc 0 xxxx 1
gotr

that traces xxxx dynamic for one hour.. for acd i was use acd reports, set up a scb in ld 23 build a tty with acd as user and point the acd group to it.. another way is for a digital trunk

trad x x.. if your using procomm

proc main

loop:
transmit "trad x x^M" ;change xx to your tn
pauses 5
goto loop
endproc

that script will trace a call on a single trunk as it travels through the switch.. you will see acd que's and transfers

john poole
bellsouth business
columbia,sc
 
I haven´t got admin right for LD 50.

Isn´t ENTC a function for the LD 80?

However I can´t get the script to work, it looks like this:

proc main

loop:
transmit "trad 8 0^M" ;change xx to your tn
pause 3
goto loop
endproc

I´ve tried this on my own TN (8 0 2 7) but I can´t see anything happening on that TN, I used my cellphone to make a incoming call but nothing is registerd in the switch, LD 80 only replies with "TRA0101 Illegal input parameters"
 
my type-O all trace commands are ld 80.. to run a script, go to script edit, new (alt f3) paste the script in a blank page, so a save as, close that, still in from the open screen (alt f3) pick the new script, then click complile and run... you need to be in ld 80 before it starts.. after you start it], alt period will stop or start the active script.. you can add any script to the meta keys, using alt f8 and using the drop down to pick run script, then enter the script name with the .was extension...sorry i didn't make myself clear

john poole
bellsouth business
columbia,sc
 
This is my procom plus script file that I use to stat, monitor etc DN's Cards etc in LD 32 & 80 etc. If you forget to log into the correct overlay, it should recover & continue running the log file.
Copy & paste the details below into a aspect file called e.g. "Trac_IDU.was".



; TRAC_IDU.WAS HOW TO RUN A CONTINUOUS 'TRAC' COMMAND
; 20th July 2005
; NOTE!
; This program will only work with a WINDOWS version of Procomm Plus.
; The " ; " denotes that the data on the program file line is ignored,
; when the script is run.

integer event
STRING C_FILE="C:\PROGRA~1\SYMANTEC\PROCOM~1\ASPECT\COM_FILE" ; Check that this path line is correct for the aspect folder!.
STRING COMMAND

PROC MAIN

When Target 0 "OVL013 " CALL OVL013
When Target 1 "OVL428 " CALL OVL428
When Target 2 "OVL111 " CALL OVL111
When Target 3 "SCH0101 " CALL SCH0101
When Target 4 "SCH0510 " CALL OVL013
When Target 5 "SCH101" CALL SCH0101
When Target 6 "SCH0099 " CALL OVL013
When Target 7 "TFC000 " CALL OVL013
When Target 8 "NPR003 " CALL NPR003
When Target 9 "TRA100 " CALL TRA100


fopen 0 C_FILE readwrite text
fgets 0 COMMAND

dialogbox 0 66 20 250 233 2 "Use TRAC in LD 80 or STAT, IDU etc in LD 32"
editbox 1 28 25 138 11 COMMAND
pushbutton 2 181 24 40 13 "OK" OK DEFAULT
text 3 34 2 180 12 "Enter 'TRAC' Command in LD 80 for Call Traces" center
text 5 24 57 140 11 "TRACE DN = TRAC <CUST DN>" left
text 6 24 69 150 11 "TRACE TRUNK = TRAC <ROUTE MEMBER>" left
text 7 24 82 180 11 "TRACE DIGITAL TRUNK = TRAD <LOOP CHANNEL>" left
text 8 24 106 178 11 "TRACE KEY (BIG SW) = TRAC <L S C U KEY>" left
text 9 24 94 170 11 "TRACE KEY (OPT 11) = TRAK <CARD UNIT KEY>" left
text 10 24 119 176 11 "TRACE UNIT (OPT 11) = TRAK <CARD UNIT>" left
text 11 24 131 140 11 "TRACE UNIT (BIG SW) = TRAC <L S C U>" center
groupbox 12 16 46 221 130 "All of the commands listed are in LD 80"
enddialog

while 1
dlgevent 0 event
switch event


case 2
exitwhile
endcase


endswitch
endwhile

fclose 0

fopen 0 C_FILE create text
fputs 0 COMMAND

start:
TRANSMIT COMMAND
TRANSMIT "^M"
WAITFOR "."

GOTO start

ENDPROC

PROC OVL013
pause 1
transmit "****^M"
pause 2
; waitfor ">"
transmit "LD 80^M"
pause 2
ENDPROC

PROC OVL111
transmit "****^M"
waitfor ">"
USERMSG "Script failed, as the TTY user is NOT logged into the system!"
exit
ENDPROC

PROC OVL428
USERMSG "Script failed. The Login name & password combination is invalid. Check the password & login name & try again.!"
exit
ENDPROC

PROC SCH0101
pause 1
transmit "****^M"
; waitfor ">"
; USERMSG "Please press Enter & wait 30 seconds as the TTY is already logged in!"
ENDPROC

PROC NPR003
pause 1
transmit "****^M"
pause 1
; waitfor ">"
transmit "LD 80^M"
pause 1
ENDPROC

PROC TRA100
pause 1
transmit "****^M"
pause 2
; waitfor ">"
transmit "LD 32^M"
pause 2
ENDPROC

All the best

Firebird Scrambler
Meridian Programmer in the UK

 
need to add a loop check box in that one, only reason i psoted the short one is becuase it comes in handy for dynamic trace without needing to look up the entc command once a month... i use the short loop for monitioring for an idle condition

john poole
bellsouth business
columbia,sc
 
Firebird Scrambler, I haven´t got the COM_FILE folder in the ASPECT folder, how should I set it up? Do I only have to create the folder? Am I missing a file?

I´m also getting an error dialog box saying: "Error 5: Invalid identifier
 
I've just updated my file again. Make sure that you alter the "Aspect file path". My script is designed to work using the path..
"C:\PROGRA~1\SYMANTEC\PROCOM~1\ASPECT"
The example listed above is using a copy of Procomm 4.8 with the programs default settings. Your own system may well be listed differently such as
"C:\PROGRA~1\PROCOM~1\ASPECT" or "C:\PROGRAM FILES\SYMANTEC\PROCOMM PLUS\ASPECT"

You must change the settings in my script to match your own path line, before you compile it!. Otherwise you will get a error message.
The COM_FILE will be generated when you script is running.




; TRAC_IDU.Was How to run a continuous 'TRAC' command
; 3rd January 2006
; NOTE!
; This program will only work with a WINDOWS version of Procomm Plus.
; The " ; " denotes that the data on the program file line is ignored,
; when the script is run.

; Follow the instructions by Ticking the box's on the screen & locating your source file.
; You might need to change the "Transmit Pacing" depending on the software version!
; A higher number is needed to slow the program down for older processors.

; This program file should remain unaltered & only copies made from it for whatever
; use is required. P.S. I suggest that you make it a "READ ONLY" file. & store it on
; your P.C's HARD DRIVE.

;#include "vkeys.inc" ; You must have this file "vkeys.inc"
; ; located within the "Aspect" folder!


PROC MAIN

integer event
STRING C_FILE="C:\PROGRA~1\SYMANTEC\PROCOM~1\ASPECT\COM_FILE"
; Change the Aspect Drive/path if it's required!. i.e. (C:\PROGRA~1\) etc.
string s_tx_list = "0,5,10,15,20,25,50,100,200,300,400,500,600,700,800,900"
string s_tx_item = "100"
STRING COMMAND

When Target 0 "OVL013 " CALL OVL013
When Target 1 "OVL428 " CALL OVL428
When Target 2 "OVL111 " CALL OVL111
When Target 3 "SCH0101 " CALL SCH0101
When Target 4 "SCH0510 " CALL OVL013
When Target 5 "SCH101" CALL SCH0101
When Target 6 "SCH0099 " CALL OVL013
When Target 7 "TFC000 " CALL OVL013
When Target 8 "NPR003 " CALL NPR003
When Target 9 "TRA100 " CALL TRA100

fopen 0 C_FILE readwrite text
fgets 0 COMMAND

dialogbox 0 69 20 247 328 2 "Use either TRAC, TRAD etc in LD 80 or STAT, IDU etc in LD 32"
editbox 1 83 23 104 11 COMMAND
pushbutton 2 194 21 40 13 "Accept" OK DEFAULT
combobox 3 200 50 34 96 DROPDOWNLIST s_tx_list s_tx_item
text 4 2 2 237 12 "Enter 'TRAC' Command in LD 80 for Call Traces" center
text 5 16 90 200 11 "Trace a DN = TRAC (Customer, Directory Number)" left
text 6 16 100 200 11 "Trace a Trunk = TRAC (Route, Member)" left
text 7 16 110 200 11 "Trace a Digital Trunk = TRAD (Loop, Channel Number)" left
text 8 16 120 200 11 "Trace a Key (Opt 11) = TRAK (Card, Unit, Key)" left
text 9 16 130 200 11 "Trace a Key (Opt 21-81) = TRAC (L,S,C,U, Key)" left
text 10 16 140 200 11 "Trace a Unit (Opt 11) = TRAK (Card, Unit)" left
text 11 16 150 200 11 "Trace a Unit (Opt 21-81) = TRAC (L,S,C,U)" left
text 12 16 160 200 11 "Trace Attendant Loops (Opt 11) = TRAO (Card, Unit)" left
text 13 16 170 200 11 "Trace Attendant Loops (Opt 51-81) = TRAO (L,S,C,U)" left
groupbox 14 13 75 221 105 " All of the commands listed below are found in LD 80 "
groupbox 15 13 182 221 110 " All of the commands listed below are found in LD 32 "
text 16 16 200 200 11 "Stat a Card (Opt 11) = STAT (Card or Slot Number)" left
text 17 16 210 200 11 "Stat a Card (Opt 21-81) = STAT (L,S,C)" left
text 18 16 220 200 11 "Stat a TN (Opt 11) = STAT (Card, Unit)" left
text 19 16 230 200 11 "Stat a TN (Opt 21-81) = STAT (L,S,C,U)" left
text 20 16 240 200 11 "Identify a Digital TN (Opt 11) = IDU (Card, Unit)" left
text 21 16 250 200 11 "Identify a Digital TN (Opt 21-81) = IDU (L,S,C,U)" left
text 22 16 260 200 11 "Identify a IPE Card (Opt 11) = IDC (Card or Slot Number)" left
text 23 16 270 200 11 "Identify a IPE Card (Opt 21-81) = IDC (L,S,C)" left
text 24 16 280 200 11 "Identify Firmware on Taurus sets = FSUM ALL" left
text 25 76 47 120 11 "Select the systems Transmit Pacing. " right
text 26 67 59 130 11 "User a higher number on older software!." right
groupbox 27 15 296 220 28 "Notes"
text 28 23 310 206 11 "(L,S,C,U) = (Opt 21-81) Loop, Shelf, Card and Unit Number" left
enddialog

while 1
dlgevent 0 event
switch event


case 2
exitwhile
endcase


endswitch
endwhile

fclose 0

fopen 0 C_FILE create text
fputs 0 COMMAND

start:
TRANSMIT COMMAND
TRANSMIT "^M"
WAITFOR "."

GOTO start

ENDPROC

PROC OVL013
pause 1
transmit "****^M"
pause 2
; waitfor ">"
transmit "LD 80^M"
pause 2
ENDPROC

PROC OVL111
transmit "****^M"
waitfor ">"
USERMSG "Script failed, as the TTY user is NOT logged into the system!"
exit
ENDPROC

PROC OVL428
USERMSG "Script failed. The Login name & password combination is invalid. Check the password & login name & try again.!"
exit
ENDPROC

PROC SCH0101
pause 1
transmit "****^M"
; waitfor ">"
; USERMSG "Please press Enter & wait 30 seconds as the TTY is already logged in!"
ENDPROC

PROC NPR003
pause 1
transmit "****^M"
pause 1
; waitfor ">"
transmit "LD 80^M"
pause 1
ENDPROC

PROC TRA100
pause 1
transmit "****^M"
pause 2
; waitfor ">"
transmit "LD 32^M"
pause 2
ENDPROC



All the best

Firebird Scrambler
Meridian Programmer in the UK

 
You can't trace a CDN or an ACD DN in LD 80. You can trace an agent assuming the call is getting this far.

Can you explain your environment (Symposium, CCR) and the problem you are experiencing? Posting the CDN and ACD queue programming would be helpful.
 
Firebird scrambler, I´ve changed the path to STRING C_FILE="C:\PROGRAM\SYMANTEC\PROCOM~1\ASPECT\COM_FILE" and it worked! Thank you very much for all the help and the script. Is there any other script that you like to share with me to make my daily work a little bit easier?

Regards, Per Elofson, Stockholm, Sweden
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top