TSAPI extended logs
-
cavagnaro
TSAPI extended logs
Hi guys,
One question here. I'm facing an issue on a customer with TSAPI, IP DRLink does work fine but from time to time the CSTA link between the Recorder and TSAPI gets LINK DOWN and all records begin to fail having to restart services...so until recorder guys fix the issue on their side I'm trying to figure out why the LINK DOWN happens...
Looking at TSAPI logs well...no much info to see...on the config file I see a line about how many files we want to keep for historical but as they don't store many information it becomes useless. So how can I increase the verbosity so I could see clients connection/disconnection and possible issues with PBX or something like that?
BTW: I know I can use tsa_maintenance but the idea is to leave it unattended
Thanks in advance
One question here. I'm facing an issue on a customer with TSAPI, IP DRLink does work fine but from time to time the CSTA link between the Recorder and TSAPI gets LINK DOWN and all records begin to fail having to restart services...so until recorder guys fix the issue on their side I'm trying to figure out why the LINK DOWN happens...
Looking at TSAPI logs well...no much info to see...on the config file I see a line about how many files we want to keep for historical but as they don't store many information it becomes useless. So how can I increase the verbosity so I could see clients connection/disconnection and possible issues with PBX or something like that?
BTW: I know I can use tsa_maintenance but the idea is to leave it unattended
Thanks in advance
-
cavagnaro
Re: TSAPI extended logs
Hey Krzysio
Well I see no CSTA link down on PBX. That is the funny part.
Customer has done something even he swears he didn't
Now since I let him know the issue what happened more than 10 times a day is no longer happening....or the gizmo got bored...hehe
Still wondering how to get logs...
Well I see no CSTA link down on PBX. That is the funny part.
Customer has done something even he swears he didn't
Still wondering how to get logs...
Re: TSAPI extended logs
Hi,
You can take on OXE a rotational tcpdump capture, filtering for the ip of the tsapi server and for the tcp protocolo and port 2555. Then send me the capture that convers the issue.
Br.
Sadim
You can take on OXE a rotational tcpdump capture, filtering for the ip of the tsapi server and for the tcp protocolo and port 2555. Then send me the capture that convers the issue.
Br.
Sadim
-
cavagnaro
Re: TSAPI extended logs
Thanks guys for the help
Lets see how this baby behaves these days, if continues bothering will accept your offer
Thanks!
Lets see how this baby behaves these days, if continues bothering will accept your offer
Thanks!
Re: TSAPI extended logs
Hi,
Do not forget to put the option "-s 0" in the tcpdump, if not packets will be cut
BR.
Sadim
Do not forget to put the option "-s 0" in the tcpdump, if not packets will be cut
BR.
Sadim
-
krzysioD
Re: TSAPI extended logs
As for csta, there is TG - telnet to pbx tcp:2555, then type D, then ls? IIRC
But you've asked for tsapi logs, should there be a 'dyn' directory and 'log' under tsapi server?
Will check it on Monday.
But you've asked for tsapi logs, should there be a 'dyn' directory and 'log' under tsapi server?
Will check it on Monday.
-
cavagnaro
Re: TSAPI extended logs
Yes there is the log folder but the files it generates are just garbage...nothing that you can analyze. That is why I asked how to do a full verbose on those...
Re: TSAPI extended logs
Wasn't OXE upgrade ?

