[asterisk-bugs] [LibPRI 0016477]: [patch] Add pri_new_bri_cb() API - Create BRI D-channel with user defined I/O callbacks and data
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jul 22 12:59:57 CDT 2010
The following issue has been ASSIGNED.
======================================================================
https://issues.asterisk.org/view.php?id=16477
======================================================================
Reported By: nic_bellamy
Assigned To: rmudgett
======================================================================
Project: LibPRI
Issue ID: 16477
Category: NewFeature
Reproducibility: N/A
Severity: feature
Priority: normal
Status: assigned
Asterisk Version: SVN
JIRA: SWP-1686
libpri Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 1395
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2009-12-20 16:15 CST
Last Modified: 2010-07-22 12:59 CDT
======================================================================
Summary: [patch] Add pri_new_bri_cb() API - Create BRI
D-channel with user defined I/O callbacks and data
Description:
There currently exists a pri_new_cb() API call that allows you to create a
PRI with user-defined I/O read and write callbacks, and option userdata.
I'm using this to hook read/write calls and log the raw data to PCAP files
for later analysis with Wireshark, among other bits and pieces such as
using userdata to point back to the related zt_pri structure for logging
the span number with any libpri messages.
The attached patch adds the same capability for BRI interfaces by adding a
pri_new_bri_cb() API function.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-07-22 12:59 svnbot Status ready for testing =>
assigned
2010-07-22 12:59 svnbot Assigned To => rmudgett
======================================================================
More information about the asterisk-bugs
mailing list