Summary:ASTERISK-02898: Did the new cvs update break oh323???
Reporter:brads (brads)Labels:
Date Opened:2004-11-27 20:20:41.000-0600Date Closed:2011-06-07 14:05:20
Versions:Frequency of
Description:During a previous bug note for authentication, we cvs updated and recompiled to patch asterisk. Yes, you guys fixed the problem, but immediatedly after we broke the oh323 driver, and now a recompile of oh323 seems impossible. There are 3 very high level unix engineers all hitting road blocks on this one.
Before we get all detailed on this one, has there been any new releases that might be causing this?
Comments:By: Brian West (bkw918) 2004-11-27 20:38:47.000-0600

You'll have to contact the maintiner of the oh323 driver.


By: brads (brads) 2004-11-27 22:31:43.000-0600

yes, understood, but we have a seious irony brewing here. I have 3 asterisk sip servers here in front of me. 1 master "which has a broke oh323 drive. 1 with no updates "running fine" and one "new attempt" which broke the same driver.
Ummmm, do you see the irony?

By: brads (brads) 2004-11-27 22:32:54.000-0600

I am not pointing fingures, but do you see the irony?

By: Brian West (bkw918) 2004-11-27 23:36:57.000-0600

You're running CVS-HEAD?  And your running chan_oh323?  In addition you provide ZERO details of the problem... No backtraces or anything that could even help narrow it down.  This is not a proper bug report.

edited on: 11-27-04 23:47

By: damin (damin) 2004-11-27 23:59:47.000-0600

How about posting some useful data? Something along the lines of a text-capture of the compile process, perhaps specifically detailing WHAT the error is?

By: twisted (twisted) 2004-11-28 02:17:02.000-0600

You will need to contact the maintainer of the oh323 driver.  oh323 is supplied seperate from asterisk, and is maintained by a completely different party.  The asterisk code should not be adjusted just to make 3rd party channel drivers happy.