[Asterisk-Dev] chan_capi and CDR documentation

Emanuele Pucciarelli ep at acm.org
Mon Jun 16 13:56:10 MST 2003


I noticed that early B3 setup in chan_capi was making unanswered calls
shown as answered in the CDR logs.  I wrote a simple patch for
chan_capi, but my knowledge of * internals is minimal: it might be
totally wrong, but it seems to work here.

The idea is: (1) not to trigger the UP state until the call is really
answered, and (2) to send a PROGRESS instead of an ANSWER frame during
B3 setup.  (Is it OK to send the frame twice?)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: earlyb3-without-triggering-channel-up.diff
Type: text/x-patch
Size: 884 bytes
Url : http://lists.digium.com/pipermail/asterisk-dev/attachments/20030616/c0ac1f70/earlyb3-without-triggering-channel-up.bin

More information about the asterisk-dev mailing list