[asterisk-bugs] [Asterisk 0012509]: [patch] MFC/R2 support for chan_zap
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Apr 29 13:12:08 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12509
======================================================================
Reported By: moy
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 12509
Category: Channels/chan_zap
Reproducibility: always
Severity: feature
Priority: normal
Status: new
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 114097
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 04-24-2008 01:31 CDT
Last Modified: 04-29-2008 13:12 CDT
======================================================================
Summary: [patch] MFC/R2 support for chan_zap
Description:
Here we go. This is my first try to give R2 support to chan_zap. I'm sure I
am missing locks and/or features here and there but I have tested it
internally with success with a considerable amount of concurrent channels
(64). That's the best I can do with the hardware I currently have (more
coming!).
======================================================================
----------------------------------------------------------------------
viniciusfontes - 04-29-08 13:12
----------------------------------------------------------------------
The BR variant works fine, there are just some minor bugs:
- In outbound calls, the most significant digit of ANI is stripped out.
For example, if my CallerID is 1000, the other side receives 000.
- The call is answered immediately instead of signal RINGING. As soon as I
dial, the softphone reports Connected instead of Ringing. The CLI shows the
following:
[Apr 29 05:04:34] -- Executing [01000 at default:1]
Dial("SIP/1000-b7a52168", "Zap/g1/1000,60") in new stack
[Apr 29 05:04:34] -- Called g1/1000
[Apr 29 05:04:34] -- Zap/1-1 answered SIP/1000-b7a52168
Note that there is no interval between the last two lines. There should be
a line saying "Zap/1-1 is ringing" or something equivalent.
Inbound calls are working fine.
Issue History
Date Modified Username Field Change
======================================================================
04-29-08 13:12 viniciusfontes Note Added: 0086149
======================================================================
More information about the asterisk-bugs
mailing list