On Dec 27, 2006, at 7:13 AM, Max CtRiX wrote:

> As you have probably noticed waiting for an answer, OSX community  
> is not
> so active involved in the Openpbx.org developement.
> The OSX discussions are (As you have noticed because i saw the same
> request there) on lists.mactelephony.net.
>
> At the moment we have serious problems supporting OSX both because
> - it has very personalized libraries
> - no one of the *active* developers has a mac to properly test the  
> code

I'm willing to offer an Xserve G4 on a static IP running the latest  
PowerPC release of Mac OS X Server for developer testing. Anyone  
interested?

> - no one of the OSXers (if any) seems really interested in fixing the
> few remaining issues (the CLI problem, for example)

There are a number of us OSXers which _are_ really interested in  
getting these issues fixed. I for one haven't done much in this area  
of porting, so I don't have the experience, but I'm happy to help out  
in any way possible (see above offering of an Xserve for testing).

> I'd also like to point out that the only problem (the CLI one), as  
> seen
> from my perspective after some tests, comes from a different behaviour
> of poll/select in OSX which seems to be considerably slower than the
> other unices flavours out there.

 From what I gather, there is a known issue with post()/select() in  
Mac OS X 10.4.x (Tiger; Server and client) and it doesn't really work  
with any BPF devices (or tty/pty). post() was not emulated at all  
under Mac OS X 10.3.x (Panther) and earlier.

The slowness seems to be due to select() -- which is used to emulate/ 
implement poll() -- and kqueue. I only have a very granular (boulder  
sized, at that) understanding of the issue so far, but it seems like  
the queue is too long. Lots of traffic will result in good select()  
performance, but low traffic (e.g. the OpenPBX CLI, I'm assuming)  
means poor performance.

I'm not sure exactly what doesn't work about using poll() with BPF  
devices yet.

Some of my sources:

http://www.clapper.org/software/poll/
http://lists.apple.com/archives/darwin-dev/2005/May/msg00220.html
http://article.gmane.org/gmane.network.tcpdump.devel/1916

Any additional details that you can provide?

> The solution is ready for the CLI issue on my iMac, but that doesn't
> solve the slow select/poll issue on Darwin. If my assumptions and  
> tests
> are correct, OSX would never be my preferred platform to run a PBX on
> (excepting the environments for a very limited number of devices
> attached) [1].

What was the solution?

Not to say your preference doesn't count, but it's my personal  
preference (and others') to run OpenPBX on Apple hardware running Mac  
OS X Server, so I want to help make that more of a reality.

I'm already running Asterisk 1.2 on Xserves running Tiger Server and  
it works well for the current requirements, but as those requirements  
grow (music on hold, MeetMe conferencing, etc.) I want to be running  
something which doesn't require Zaptel hardware or Linux. I really  
like the ideals of the OpenPBX project and it's nice to see it  
branched off the software I'm currently using and comfortable with.

> Anyway i would be glad to see some OSX people who can actively test
> *and* _develop_ on Darwin joining us so that OSX can be supported  
> better
> in the future (and not ignored because of a lack on interest).
>
> Max
>
> [1]: i have an OLD iMac G4 and i don't know if the kernel is the  
> same on
> OSX servers. I don't even know if OSX servers have a GUI.

Mac OS X Server does have a GUI and runs on top of the same Darwin  
architecture used for the client OS. There are some differences in  
the kernel, but it's really just tuned for better performance when  
running server-type tasks as opposed to user-type tasks.

The goal of Sunrise Telecom and MacTelephony is to get a  native GUI  
installation & management software built ontop of OpenPBX, but I'm  
happy with the CLI.

Sincerely,

Morgan Aldridge
--
[EMAIL PROTECTED]
http://www.makkintosshu.com/
_______________________________________________
Openpbx-users mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-users

Reply via email to