Summary:ASTERISK-10441: Asterisk 1.4 console repeatedly showing *CLI> on MacOSX Tiger 10.4.10
Reporter:Jacky Keung (jackykeung)Labels:
Date Opened:2007-10-04 00:14:14Date Closed:2011-06-07 14:00:31
Versions:Frequency of
Description:OS: MAX OSX Tiger 10.4.10
Platform: Intel x86  (MacBookPro 2.2G Core duo)

* 1.4.12 Compiled and Installed successfully without any problem.
* Make samples installed all required example configuration files.
* Asterisk launched with asterisk -cvvvvv without problem if using default configuration (make samples).

after insert a line to sip.conf :     register => xxx:xxx@vsp_hostname
starting asterisk : asterisk -cvvvvv
Asterisk 1.4.12 console repeatedly showing the following:

pbx_dundi.so => (Distributed Universal Number Discovery (DUNDi))
pbx_loopback.so => (Loopback Switch)
pbx_realtime.so => (Realtime Switch)
pbx_spool.so => (Outgoing Spool Support)
res_clioriginate.so => (Call origination from the CLI)
res_convert.so => (File format conversion CLI command)
Asterisk Ready.

Making Asterisk 1.4.12 virtually useless!!!


The problem has been reproduced on two other Mac OSX machines with same results.

The problem existed since 1.4.11, 1.4.12 has the same issue.

If asterisk is started in daemon mode, the internal system is working, (I think)

I suspect there is an issue in the console interface where it is incompatible with Mac's library ..etc

The problem is NOT reproducible on a separate linux machine, only on all other Mac OSX machines(BSD).

* Asterisk 1.2.24 works PERFECTLY normal without any issue on Mac OSX.  (Compiled from scratch)
* Asterisk 1.2 serious has no issue with Mac OSX Tiger ..., 1.4 is not stable ...

Comments:By: Sean Bright (seanbright) 2007-11-05 16:12:30.000-0600

Confirmed with 1.4.13 on MacOSX 10.4.10.

By: Sean Bright (seanbright) 2007-11-13 09:58:22.000-0600

I spent a ton of time trying to figure this one out, but I wasn't able to.  It looks to be related to chan_sip, but I can't be 100% sure.

As an aside, gethostbyname in Mac OS X is threadsafe even though they don't provide a gethostbyname_r implementation.  It apparently has been threadsafe (uses TLS) since 10.2ish.

By: Tilghman Lesher (tilghman) 2008-01-07 14:51:24.000-0600

Can you reproduce on 10.4.11 with 1.4.17?  That's what I'm running, and I don't have this issue.

By: Caio Begotti (caio1982) 2008-01-08 06:28:03.000-0600

I've been running the 1.4 branch on my 10.4.11 without any problems too, though the steps to reproduce this bug led to another issue better explained in ASTERISK-9876.

By: Tilghman Lesher (tilghman) 2008-01-28 14:36:15.000-0600

Given that this does not occur on the latest version of Tiger, I'm closing this as an OS bug solved in that version.  Reopen if you're able to reproduce on 10.4.11 with Asterisk 1.4.17 or later.