[asterisk-bugs] [Asterisk 0013367]: can any one help 4 this my card is TDM2400P digium
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Aug 24 08:26:45 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13367
======================================================================
Reported By: Nikhil
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13367
Category: Applications/app_zapscan
Reproducibility: have not tried
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.2.X
SVN Branch (only for SVN checkouts, not tarball releases): 1.2
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-08-23 04:39 CDT
Last Modified: 2008-08-24 08:26 CDT
======================================================================
Summary: can any one help 4 this my card is TDM2400P digium
Description:
Registered SIP '2004' at 192.168.1.174 port 57302 expires 3600
-- Executing AGI("SIP/2004-0f3f9b70", "call_log.agi|99948143943") in
new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
-- AGI Script call_log.agi completed, returning 0
-- Executing Dial("SIP/2004-0f3f9b70", "Zap/g1/9948143943||tTo") in
new stack
-- Called g1/9948143943
-- Zap/1-1 answered SIP/2004-0f3f9b70
-- Hungup 'Zap/1-1'
== Spawn extension (default, 99948143943, 2) exited non-zero on
'SIP/2004-0f3f9b70'
-- Executing NoOp("SIP/2004-0f3f9b70", "h") in new stack
======================================================================
----------------------------------------------------------------------
(0091676) Corydon76 (administrator) - 2008-08-24 08:26
http://bugs.digium.com/view.php?id=13367#c91676
----------------------------------------------------------------------
1) You have not described a problem. What you have here is a set of
output that may or may not be doing what is intended.
2) You have stated that you are using Asterisk 1.2. That version is no
longer supported on the bugtracker. You should upgrade to version 1.4.21.2
or higher if you expect to have support.
3) Since this is probably a misunderstanding of how Asterisk works and
not actually a bug, you should instead post to the Asterisk-users mailing
list with a clear description of what you are trying to do, what your
dialplan looks like, what is actually occurring, and how you think that
what is occurring conflicts with what you want to have happen. With this
information, we are more likely to be able to help you, instead of trying
to guess what the problem is.
Issue History
Date Modified Username Field Change
======================================================================
2008-08-24 08:26 Corydon76 Note Added: 0091676
======================================================================
More information about the asterisk-bugs
mailing list