asterisk users - Jul 2004 - How to track (log file) Dial Plan events to fix unsteadily states like opened FXO port

On Thu, 2004-07-01 at 11:00, Miroslav Nachev wrote:
>    Hi,
> 
>    We have our own algorithm handling (dial plan) the calls and
> different events. When we receive an external call (from FXO),
> probably in consequence of our algorithm, some times the FXO port
> remains open and we could not establish the reason why the port is not
> closing. We were thinking a lot what might be the problem - for
> example we might forget to call the "hang-up method" somewhere in
the
> script. Unfortunately we were not able to fix the problem. We came to
> the conclusion that the only way to establish where the mistake is, is
> to ask you for information about is there any log files, which could
> help us tracing the actions and seeing which action is completed and
> which not. 
>    Seeing the actions sequence will help us to establish and solve the
> problem we have. We count on your help for the solution of this
> problem. 
You speak of FXO, this makes me assume you are speaking of an analog
POTS line. 
If so, then your next question is which side of the call did the actual
hangup. If the non asterisk side did the hangup, does it provide
disconnect supervision? If no disconnect supervision, can you get a tone
pattern for busydetect or callprogress to detect those events.

Maybe searching around for those few new terms I just used above will
get you hooked up with previous threads to understand anything else you
need.
-- 
Steven Critchfield  <critch@basesys.com>

Hi,

   We have our own algorithm handling (dial plan) the calls and
different events. When we receive an external call (from FXO),
probably in consequence of our algorithm, some times the FXO port
remains open and we could not establish the reason why the port is not
closing. We were thinking a lot what might be the problem - for
example we might forget to call the "hang-up method" somewhere in the
script. Unfortunately we were not able to fix the problem. We came to
the conclusion that the only way to establish where the mistake is, is
to ask you for information about is there any log files, which could
help us tracing the actions and seeing which action is completed and
which not. 
   Seeing the actions sequence will help us to establish and solve the
problem we have. We count on your help for the solution of this
problem. 


   Best Regards,
   Miroslav Nachev

   COSMOS Software Enterprises, Ltd.
   Tel:    (+359-2)   983-32-62
   Mobile: (+359-88)  897-31-95
   E-Mail: m_natchev@yahoo.com
           miro@space-comm.com
   http://www.space-comm.com

   Post address:
      P. O. Box 941,
      1000 Sofia,
      Bulgaria

   Office address:
      ap. 9, fl. 4,
      "11 August" str., No. 43,
      1202 Sofia,
      Bulgaria