Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Fetching latest commit…
Cannot retrieve the latest commit at this time.
=== THIS PROJECT HAS BEEN DEPRECATED === Please consider using the reConServer project instead - it is far more powerful and includes a B2BUA module: https://github.com/resiprocate/reConServer Introduction ============ This is a reSIProcate-based B2BUA library. The library is libb2bua.so It is built on top of reSIProcate's dialog usage manager (DUM) It was distributed with reSIProcate releases up to and including the reSIProcate 1.8.x release series. It is known to work with those releases but may not work with releases beyond 1.8.x Building ======== TODO: a configure.ac script needs to be created for this project. It can probably be created by copying the configure.ac script from reSIProcate itself and removing many things that don't relate to this B2BUA project. Background and technical notes ============================== The code has been adapted from a previous project. Consequently, the initial import to the reSIProcate repository doesn't fully adhere to reSIProcate coding standards. Nonetheless, it is working code, so a decision was taken to commit the code as-is, without modification, and then gradually overhaul it in subsequent commits. Some key points about this code: - It produces a shared object - to produce an executable, the B2BUA class must be instantiated and put to work. Such an example exists in the apps/basicB2BUA directory. A typical implementation of a B2BUA must implement the following classes: - b2bua::CallRoute - b2bua::CallHandle - b2bua::AuthorizationManager - b2bua::B2BUA - It relies on rtpproxy from http://www.rtpproxy.org to relay the media streams. There are also various patches for rtpproxy 0.2: - rtpproxy sends notification to the B2BUA on media timeout - fix a file descriptor bug - timeout on either direction The rtpproxy patches have been posted on the rtpproxy mailing list: http://lists.rtpproxy.org/pipermail/users/2008-May/000016.html Daniel Pocock http://danielpocock.com email@example.com /* ==================================================================== * * Copyright 2012 Daniel Pocock. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. Neither the name of the author(s) nor the names of any contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) AND CONTRIBUTORS "AS IS" AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR(S) OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * ==================================================================== * * */