Engenheiro

The OpenR2 Guide – January 2010 - Version 0.3 Moisés Silva Alexandre Alencar http://www.libopenr2.org/ http://code.google.com/p/openr2/ 1. About this guide. OpenR2 is a library that implements the MFC/R2 signaling over E1 lines using the Zapata Telephony Interface, DAHDI and in the near future the OpenZAP TDM abstraction library. This document DOES NOT describe the programming interfaces provided by OpenR2, please refer to the code for that :-) , and don't hesitate on asking me any question you may have. This document describes the installation of the library to be used by Asterisk and/or FreeSwitch. For questions regarding installation or deployment issues, please don't contact me directly, unless you are willing to pay me to give you support :-). Instead, use the Digium's asterisk-r2 mailing list at: http://lists.digium.com/mailman/listinfo/asterisk-r2, or join IRC in irc.freenode.org in the #openr2 channel. I usually hang out there with the nick 'moy'. If there is an MFC/R2 variant that is not supported and you need (or is not working as expected), send me an e-mail. I also will appreciate any contribution or correction to this document and/or the library code itself. 2. What is MFC/R2? MFC/R2 is a telephony signaling widely used in Mexico, Brazil and other countries in Latin America and Asia. MFC/R2 stands for Multi Frequency Compelled R2. Compared to more recent signaling protocols like ISDN PRI/BRI or SS7, R2 offers a limited set of functionality. The signaling is only used to setup the call and bring it down. Some MFC/R2 variants may send billing pulses during the call though, but those are rarely used. There is analog and digital MFC/R2 versions, any reference to MFC/R2 or R2 in this document refers to the digital version that uses E1 facilities. Most readers will not likely be interested in the analog version because is not widely used anymore. MFC/R2 is defined by the ITU, however most countires using MFC/R2 do not follow the ITU specification and