Last night I started compiling all the components of the Unicall stack. So far I've been able to successfully do a "testcall". A couple of questions: 1) If you download the "snapshot" libraries, a funcion that used to be called "dtmf_put" now has been changed to "dtmf_tx_put", however the client code from the other library (I forget which one atm) still uses the old name so I had to fix it. 2) the Makefile patch for the Asterisk channel seems to be for the 1.1.x versions of Asterisk. In the snapshots there's a patch that seems to be for the 1.2.x versions but I haven't tried it yet. Does it work as is or do I have to "patch the patch"? for Asterisk 1.2.9? In sum, what is the most up-to-date AND stable combination of libraries for the Unicall stack? P.S. 1: A lot of Unicall seems to be hardcoded in the .h and .c files, like the countries and how they behave... I *might* attempt to do something more flexible if I have time *and* brush up my C which I haven't used much in the last 4 years. P.S. 2: A lot of behavior in the Asterisk ecosystem seems to be replicated over and over in the different parts of the code, for example the reading of configuration files, which each programmer does in their own way. How about some generalized configuration code module? Maybe this question is better for the dev list. BarZ
On 8/1/06, Barzilai <barcho@creacion.com.uy> wrote:> Last night I started compiling all the components of the Unicall stack. > So far I've been able to successfully do a "testcall".Congratulations! :)> 1) If you download the "snapshot" libraries, a funcion that used to be > called "dtmf_put" now has been changed to "dtmf_tx_put", however the > client code from the other library (I forget which one atm) still uses > the old name so I had to fix it.This does not seems to be a question. But yes, in fact sometimes steve seems forget to update the libraries to match those changes. I had a hard to find problem with logical incorrect argument passing from a function of spandsp used by unicall.> 2) the Makefile patch for the Asterisk channel seems to be for the 1.1.x > versions of Asterisk. > In the snapshots there's a patch that seems to be for the 1.2.x versions > but I haven't tried it yet. > Does it work as is or do I have to "patch the patch"? for Asterisk 1.2.9? > > In sum, what is the most up-to-date AND stable combination of libraries > for the Unicall stack?I think the only way to go is actually trying. I doubt someone has made a list of the "right" versions. Most of people is so happpy of getting unicall finally working that nobody cares wich version they have :p I would recommend use the more recent versions, and only downgrade if you have problems.> > P.S. 1: A lot of Unicall seems to be hardcoded in the .h and .c files, > like the countries and how they behave... I *might* attempt to do > something more flexible if I have time *and* brush up my C which I > haven't used much in the last 4 years. >That would be great :)> P.S. 2: A lot of behavior in the Asterisk ecosystem seems to be > replicated over and over in the different parts of the code, for example > the reading of configuration files, which each programmer does in their > own way. How about some generalized configuration code module? Maybe > this question is better for the dev list.hum, as far as i know every programmer should be using ast_config() and friends to read configuration files, since the user could choose to use database configuration files, or some other "config engine". What do you mean with this? Regards. Moises Silva -- "Su nombre es GNU/Linux, no solamente Linux, mas info en http://www.gnu.org"
Barzilai wrote:> Last night I started compiling all the components of the Unicall stack. > So far I've been able to successfully do a "testcall". > > A couple of questions: > > 1) If you download the "snapshot" libraries, a funcion that used to be > called "dtmf_put" now has been changed to "dtmf_tx_put", however the > client code from the other library (I forget which one atm) still uses > the old name so I had to fix it.Don't use the snapshots. If you use the latest releases this won't happen.> 2) the Makefile patch for the Asterisk channel seems to be for the > 1.1.x versions of Asterisk. > In the snapshots there's a patch that seems to be for the 1.2.x > versions but I haven't tried it yet. > Does it work as is or do I have to "patch the patch"? for Asterisk 1.2.9?There hasn't been a need to update the software for some time. The 1.1.x directory works fine with 1.2.x. I should have changed that. Sorry.> > In sum, what is the most up-to-date AND stable combination of > libraries for the Unicall stack?The latest release is, well, the latest release.> > P.S. 1: A lot of Unicall seems to be hardcoded in the .h and .c files, > like the countries and how they behave... I *might* attempt to do > something more flexible if I have time *and* brush up my C which I > haven't used much in the last 4 years.Bad idea. Its like that for a reason. The present arrangements make support much much simpler. Things like Dialogic, where R2 is alsmost completely configured in config files still end up hard coding a few things. Those config files cause support trouble, though. In my code the variations needed within countries are already allowed for. The whole Unicall scheme is being heavily reworked right now, to separate out the hardware specific elements into their own modules. Hard coded support for countries is something I won't be changing, though.> > P.S. 2: A lot of behavior in the Asterisk ecosystem seems to be > replicated over and over in the different parts of the code, for > example the reading of configuration files, which each programmer does > in their own way. How about some generalized configuration code > module? Maybe this question is better for the dev list.Chaos seems to be the Asterisk way. :-) Steve
Thanks for the info... I was able to make if work after recompilation and relocation of library files. Regards, Leonimar --- Steve Underwood <steveu@coppice.org> wrote:> leonimar cape wrote: > > >Hi Steve, > > > >I need to enable the Unicall channel in my asterisk > >box to be able to interconnect to a local telco > >provider using MFCR2. I use the unicall release > >unicall-0.0.3pre9 and a patch for asterisk 1.2. > >Compilation was done with ease. The problem is that > I > >got an error "Unable to read supervisory tone set > hk" > >once I load the chan. I am using 1.2.9.1 version. > Is > >there any new version that could use. > > > >Regards, > > > >Leonimar > > > > > Install everything in the same place. You probably > have some of the > stuff in /usr and some in /usr/local. This causes > problems with the > current versions. I should sort this out for future > versions. > > Steve > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com > -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > >http://lists.digium.com/mailman/listinfo/asterisk-users>__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com