Re: [asterisk-dev] Re: autoconf issues for FreeBSD
On Thu, Oct 05, 2006 at 03:22:24PM +0200, Benny Amorsen wrote:
> > "DN" == Dinesh Nair <[EMAIL PROTECTED]> writes:
>
> DN> FreeBSD has a policy of separating what's part of the base system
> DN> which sits in /usr/bin, /usr/sbin, /usr/lib etc and what comes in
> DN> from ports which goes into /usr/local/{bin,sbin,lib,etc}. while
> DN> this may seem confusing to non-FreeBSD users, it has become second
> DN> nature to FreeBSD users.
>
> So why doesn't the C compiler in FreeBSD look in /usr/local/ for
> includes and libraries?
See my previous reply to Russ. /usr/local/ is only the prefered,
but not the fixed, prefix for third party installed software via
the FreeBSD ports collection.
Edwin
--
Edwin Groothuis |Personal website: http://www.mavetju.org
[EMAIL PROTECTED]| Weblog: http://weblog.barnet.com.au/edwin/
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
Generic Manager API Client Apps (was: Re: [asterisk-dev] Another bounty - app_reload)
On Thu, 2006-10-05 at 09:00 -0500, Moises Silva wrote: > > Actually, what seems missing from the diaplan apps is one that just > > writes to the Manager API socket any passed string, and one to read from > > the Manager API socket any sent data. > app_event should be enough for your needs of writting to the manager socket > > http://www.pbxfreeware.org/archives/2005/06/new_download_--_3.html That app doc is a little confusing: I guess it sends *actions* to Asterisk, not "events" - events are internal state changes inside Asterisk which the Manager notifies to clients connected to its API socket. "Actions" are messages into Asterisk's Manager API socket that change Asterisk's state. But it does seem to do what I want (if it works ;). > Just need something else to read from? But, could you show me some use > for it, im missing that :( app_event calls don't seem to return the response from Asterisk after app_event sends the action message. Not even whether the message was successfully received by Asterisk. And many actions have asynchronous results inside Asterisk, eventually indicated only when Asterisk reports an event. Some state info cannot be polled, and some polling actions seem to be broken. "ExtensionState" seems broken when an AGI (not a channel) is mapped to an extension, returning only -1 without a dialplan hint, and 4 with a hint. The only way to determine ExtensionState is by subscribing (connecting to, and reading from, the Manager API socket) for events, which can at least show when an extension becomes busy (though not when it becomes available again, another apparent Asterisk bug). Even if I'm just using ExtensionState wrong (not configuring the AGI right, or failing to make the AGI somehow register its state), the general case of using the detailed events reported by the Manager API seems missing. Unless you've got another app that does do this, in which case I stand happily educated :). > Thanks > > Moises Silva -- (C) Matthew Rubenstein ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Another bounty - app_reload
Actually, what seems missing from the diaplan apps is one that just writes to the Manager API socket any passed string, and one to read from the Manager API socket any sent data. app_event should be enough for your needs of writting to the manager socket http://www.pbxfreeware.org/archives/2005/06/new_download_--_3.html Just need something else to read from? But, could you show me some use for it, im missing that :( Thanks Moises Silva -- "Su nombre es GNU/Linux, no solamente Linux, mas info en http://www.gnu.org"; ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] autoconf issues for FreeBSD
On Thu, Oct 05, 2006 at 03:34:02PM +0200, Tzafrir Cohen wrote: > On Thu, Oct 05, 2006 at 04:09:29AM -0700, Luigi Rizzo wrote: > > > The problem is that platform-specific _defaults_ should be provided > > by the tool (which should aware of platform issues) not by the > > asterisk or perl or gzip or ghostscript programmer (who cannot know > > what's the default location of stuff on FreeBSD, Knoppix, Ubuntu, > > RedHat, Fedora, DragonFly, minix, you-name-it). > > Have you bothered providing those defaults? Has FreeBSD bothred > providing those defaults? > > http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_mono/autoconf.html#SEC138 > > Generally: /usr/share/config.site , /usr/local/share/config.site , > /etc/config.site , /usr/local/etc/config.site or something similar. > > Do we know how to take sane defaults from there? apparently not - at least i cannot see a config.site as part of the installed autoconf package on any of my FreeBSD boxes (there isn't one on a Fedora installation either; Maybe it is not a popular feature. I wonder how is the situation for other platform). But thanks for the pointer, at least that's a good starting point (or something to document). > BTW: I believe ./configure --silent is what you're after. that's a bit too silent, it doesn't report anything :( cheers luigi ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] autoconf issues for FreeBSD
On Thu, Oct 05, 2006 at 04:09:29AM -0700, Luigi Rizzo wrote: > The problem is that platform-specific _defaults_ should be provided > by the tool (which should aware of platform issues) not by the > asterisk or perl or gzip or ghostscript programmer (who cannot know > what's the default location of stuff on FreeBSD, Knoppix, Ubuntu, > RedHat, Fedora, DragonFly, minix, you-name-it). Have you bothered providing those defaults? Has FreeBSD bothred providing those defaults? http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_mono/autoconf.html#SEC138 Generally: /usr/share/config.site , /usr/local/share/config.site , /etc/config.site , /usr/local/etc/config.site or something similar. Do we know how to take sane defaults from there? BTW: I believe ./configure --silent is what you're after. -- Tzafrir Cohen sip:[EMAIL PROTECTED] icq#16849755 iax:[EMAIL PROTECTED] +972-50-7952406 jabber:[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.xorcom.com ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
[asterisk-dev] Re: autoconf issues for FreeBSD
> "DN" == Dinesh Nair <[EMAIL PROTECTED]> writes:
DN> FreeBSD has a policy of separating what's part of the base system
DN> which sits in /usr/bin, /usr/sbin, /usr/lib etc and what comes in
DN> from ports which goes into /usr/local/{bin,sbin,lib,etc}. while
DN> this may seem confusing to non-FreeBSD users, it has become second
DN> nature to FreeBSD users.
So why doesn't the C compiler in FreeBSD look in /usr/local/ for
includes and libraries?
/Benny
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Re: SIP to IAX (Jeremy McNamara)
On Thursday 05 October 2006 04:30, Brian Candler wrote: > On Thu, Oct 05, 2006 at 03:47:22AM -0400, Jeremy McNamara wrote: > > I suggest you purchase the Asterisk book. You seem to be missing > > quite a few major core concepts of how Asterisk functions. > > > > > > http://www.oreilly.com/catalog/asterisk/ > > Or just download the whole book for free: > http://www.asteriskdocs.org/modules/tinycontent/index.php?id=11 While it's no doubt useful to have the book available online, if you appreciate the effort that went into having the book written, you should buy a copy, in part to encourage the authors to write more books. -- Tilghman ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] autodial
On 10/5/06, Santhosh N <[EMAIL PROTECTED]> wrote: Oct 5 17:33:06 NOTICE[29913]: pbx.c:1741 pbx_extension_helper: Cannotfind extension context 'incoming' > Channel SIP/5000-092c35e0 was answered. == Starting SIP/5000-092c35e0 at santhosh,s,1 failed so falling back to exten 's' == Starting SIP/5000-092c35e0 at santhosh,s,1 still failed so fallingback to context 'default'Oct 5 17:33:06 WARNING[29923]: pbx.c:2357 __ast_pbx_run: Channel'SIP/5000-092c35e0' sent into invalid extension 's' in context 'default', but no invalid handlerOct 5 17:33:06 NOTICE[29923]: pbx_spool.c:279 attempt_thread: Callcompleted to SIP/5000this is a -users questions, you have a mismatch in the context between sip.conf and extensions.conf-- wasim h. baig | principal consultant | convergence pk | +92(300)8508070 ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
[asterisk-dev] autodial
Hi, I am trying to initiate call from asterisk using *.call *file. I am able to make a call but when i receive the call my UA will hangup. The files i have used are 500.call Channel: SIP/5000 Callerid: Automated call MaxRetries: 10 RetryTime: 30 WaitTime: 10 Context: santhosh Extension: s Priority: 1 extension.conf [santhosh] exten => s,1,SayDigits(1224) and the below msg i am getting in the astersik CLI. -- Attempting call on SIP/5000 for [EMAIL PROTECTED]:1 (Retry 1) Oct 5 17:33:06 NOTICE[29913]: pbx.c:1741 pbx_extension_helper: Cannot find extension context 'incoming' > Channel SIP/5000-092c35e0 was answered. == Starting SIP/5000-092c35e0 at santhosh,s,1 failed so falling back to exten 's' == Starting SIP/5000-092c35e0 at santhosh,s,1 still failed so falling back to context 'default' Oct 5 17:33:06 WARNING[29923]: pbx.c:2357 __ast_pbx_run: Channel 'SIP/5000-092c35e0' sent into invalid extension 's' in context 'default', but no invalid handler Oct 5 17:33:06 NOTICE[29923]: pbx_spool.c:279 attempt_thread: Call completed to SIP/5000 Regards, Santhosh ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
[asterisk-dev] autodial
Hi, I am trying to initiate call from asterisk using *.call *file. I am able to make a call but when i receive the call my UA will hangup. The files i have used are 500.call Channel: SIP/5000 Callerid: Automated call MaxRetries: 10 RetryTime: 30 WaitTime: 10 Context: santhosh Extension: s Priority: 1 extension.conf [santhosh] exten => s,1,SayDigits(1224) and the below msg i am getting in the astersik CLI. -- Attempting call on SIP/5000 for [EMAIL PROTECTED]:1 (Retry 1) Oct 5 17:33:06 NOTICE[29913]: pbx.c:1741 pbx_extension_helper: Cannot find extension context 'incoming' > Channel SIP/5000-092c35e0 was answered. == Starting SIP/5000-092c35e0 at santhosh,s,1 failed so falling back to exten 's' == Starting SIP/5000-092c35e0 at santhosh,s,1 still failed so falling back to context 'default' Oct 5 17:33:06 WARNING[29923]: pbx.c:2357 __ast_pbx_run: Channel 'SIP/5000-092c35e0' sent into invalid extension 's' in context 'default', but no invalid handler Oct 5 17:33:06 NOTICE[29923]: pbx_spool.c:279 attempt_thread: Call completed to SIP/5000 Regards, Santhosh ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] autoconf issues for FreeBSD
On Thu, Oct 05, 2006 at 11:11:00AM +0200, Tzafrir Cohen wrote:
> On Thu, Oct 05, 2006 at 12:15:33AM -0700, Luigi Rizzo wrote:
...
> > Besides, the "failures" are often subtle - it's not that configure
> > fails completely, it just gives you a suboptimal build because it
> > doesn't find 8 codecs and 4 libraries and so it doesn't build the
> > dependent modules.
> > And it does it so noisily (currently the output of asterisk's
> > configure is 332 lines!) that it is easy to miss the failures
> > while the text scrolls.
>
> Which of those are unnecessary? That is: will not fail?
>
> Do you thin that some of them are not worth reporting?
when there are 303 successful checks and 29 failed ones,
i would much like a simple option to only report the failures.
I blame myself for not knowing how this --useful-output
option is spelled.
> > Also the choice of using "ancient greek" (pre-1977 shell)
>
> huh?
>From
>http://www.gnu.org/software/autoconf/manual/autoconf-2.60/html_node/Portable-Shell.html#Portable-Shell
When writing your own checks, there are some shell-script
programming techniques you should avoid in order to make
your code portable. The Bourne shell and upward-compatible
shells like the Korn shell and Bash have evolved over the
years, but to prevent trouble, do not take advantage of
features that were added after Unix version 7, circa 1977
(see Systemology).
i agree it could have been worse - they might have used MIX assembly.
> > as the
> > language for expressing the logic in the configure script doesn't
> > help correctness: e.g. without local variables, i think macros are
> > not reentrant and things like
> >
> > saved_CFLAGS="${CFLAGS}"
> > ...
> > CFLAGS="${saved_CFLAGS}"
> >
> > could easily be trashed.
>
> That's for portability. autoconf's configure scripts is testerd on various
> shells. Luckily you don't have to write them more than you have to
> write binary code. It is usually more handy to debug it through the end
the "configure.ac" scripts don't look very different from machine code.
They are generally huge and obfuscated and often buggy because people
have no time to waste on them and rely on copying from other equally
poor examples.
But yes, it's great to be able to run them on a PDP-11 :)
> of config.log rather than through the configure script .
>
> >
> > > Once again (I'll agree with Russell here) it makes absolutely no sense
> > > for /usr/local to be the standard place for libraries to be installed,
> > > but that they are not in the search path for the compiler and linker.
> > > All this does is require every package that wants to build on FreeBSD
> > > to require special logic to add them to the search path, when the
> > > FreeBSD toolchain could easily have these paths embedded into the
> > > toolchain
> > > by default. How frustrating :-)
>
> What happens if you simply hint autoconf? pass it proper values of PATH,
> LD_LIBRARY_PATH, CFLAGS , LDFLAGS ?
>
> It's been a while since I've used custom build environments. But I
> remember autoconf using such hints well (e.g: on my old Solaris
> account). Those were the standard settings in my environment as I had a
> non-standard environment.
>
> So for starters: does autoconf take those hints? Which variables exactly
> need settings?
it does take the hints. That is not the problem.
The problem is that platform-specific _defaults_ should be provided
by the tool (which should aware of platform issues) not by the
asterisk or perl or gzip or ghostscript programmer (who cannot know
what's the default location of stuff on FreeBSD, Knoppix, Ubuntu,
RedHat, Fedora, DragonFly, minix, you-name-it).
Basically the problem is that a lot of autoconf-based packages only work
on the platform where they were developed, and everywhere else they need
massive porting efforts.
cheers
luigi
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] autoconf issues for FreeBSD
On Wed, Oct 04, 2006 at 08:37:45PM -0500, Kevin P. Fleming wrote: > - Luigi Rizzo <[EMAIL PROTECTED]> wrote: > > I am pretty sure that the code below (which was my patch at the time) > > is NOT a proper fix - i would expect autoconf to deal with platform > > issues > > without having us deal with them on each and every port. > That fix probably won't work correctly any longer, since the change to use > ASTCFLAGS and ASTLDFLAGS for the build system. > autoconf itself does nothing to increase platform compatibility; it is a tool > that allows a package builder to increase compatibility. The benefits from > autoconf are derived entirely from the logic that we put in the configure > script, not autoconf itself. > Once again (I'll agree with Russell here) it makes absolutely no sense for > /usr/local to be the standard place for libraries to be installed, but that > they are not in the search path for the compiler and linker. All this does is > require every package that wants to build on FreeBSD to require special logic > to add them to the search path, when the FreeBSD toolchain could easily have > these paths embedded into the toolchain by default. How frustrating :-) Sun does similar things. Standard stuff goes into /usr/bin etc Optional Sun packages (or some 3rd party stuff) into /opt as a base Sunfreeware into various areas with config under /etc/sfw binaries /usr/sfw/bin etc BSD's system stuff normal, everything else /usr/local Steve -- NetTek Ltd UK mob +44-(0)7775 755503 UK +44-(0)20 79932612 / US +1-(310)8577715 / Fax +44-(0)20 7483 2455 Skype/GoogleTalk/AIM/Gizmo/Mac stevekennedyuk / MSN [EMAIL PROTECTED] Euro Tech News Blog http://eurotechnews.blogspot.com ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Re: SIP to IAX (Jeremy McNamara)
On Thu, Oct 05, 2006 at 03:47:22AM -0400, Jeremy McNamara wrote: > I suggest you purchase the Asterisk book. You seem to be missing quite a > few major core concepts of how Asterisk functions. > > > http://www.oreilly.com/catalog/asterisk/ Or just download the whole book for free: http://www.asteriskdocs.org/modules/tinycontent/index.php?id=11 ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] autoconf issues for FreeBSD
On Thu, Oct 05, 2006 at 12:15:33AM -0700, Luigi Rizzo wrote:
> On Wed, Oct 04, 2006 at 08:37:45PM -0500, Kevin P. Fleming wrote:
> > - Luigi Rizzo <[EMAIL PROTECTED]> wrote:
> > > I am pretty sure that the code below (which was my patch at the time)
> > > is NOT a proper fix - i would expect autoconf to deal with platform
> > > issues
> > > without having us deal with them on each and every port.
> >
> > That fix probably won't work correctly any longer, since the change to use
> > ASTCFLAGS and ASTLDFLAGS for the build system.
>
> as russel said, here i only patched CFLAGS and LDFLAGS which is
> what the configure script uses. AST* variables were already (more
> or less) set properly.
>
> > autoconf itself does nothing to increase platform compatibility; it is a
> > tool that allows a package builder to increase compatibility. The benefits
> > from autoconf are derived entirely from the logic that we put in the
> > configure script, not autoconf itself.
>
> i am sure this has been discussed at length many times.
>
> I think the goal of autotools was to ease portability, both
> cross-platform and within a single platform with different packages
> installed. Maybe for the latter, autoconf still makes sense.
>
> But if you have to explicitly put in checks for what are platform
> defaults, the first goal is defeated.
>
> Besides, the "failures" are often subtle - it's not that configure
> fails completely, it just gives you a suboptimal build because it
> doesn't find 8 codecs and 4 libraries and so it doesn't build the
> dependent modules.
> And it does it so noisily (currently the output of asterisk's
> configure is 332 lines!) that it is easy to miss the failures
> while the text scrolls.
Which of those are unnecessary? That is: will not fail?
Do you thin that some of them are not worth reporting?
There are probably more than a screenfull of features tested, so even a
"summary scrren" won't be really useful.
>
> Also the choice of using "ancient greek" (pre-1977 shell)
huh?
> as the
> language for expressing the logic in the configure script doesn't
> help correctness: e.g. without local variables, i think macros are
> not reentrant and things like
>
> saved_CFLAGS="${CFLAGS}"
> ...
> CFLAGS="${saved_CFLAGS}"
>
> could easily be trashed.
That's for portability. autoconf's configure scripts is testerd on various
shells. Luckily you don't have to write them more than you have to
write binary code. It is usually more handy to debug it through the end
of config.log rather than through the configure script .
>
> > Once again (I'll agree with Russell here) it makes absolutely no sense
> > for /usr/local to be the standard place for libraries to be installed,
> > but that they are not in the search path for the compiler and linker.
> > All this does is require every package that wants to build on FreeBSD
> > to require special logic to add them to the search path, when the
> > FreeBSD toolchain could easily have these paths embedded into the toolchain
> > by default. How frustrating :-)
What happens if you simply hint autoconf? pass it proper values of PATH,
LD_LIBRARY_PATH, CFLAGS , LDFLAGS ?
It's been a while since I've used custom build environments. But I
remember autoconf using such hints well (e.g: on my old Solaris
account). Those were the standard settings in my environment as I had a
non-standard environment.
So for starters: does autoconf take those hints? Which variables exactly
need settings?
--
Tzafrir Cohen sip:[EMAIL PROTECTED]
icq#16849755 iax:[EMAIL PROTECTED]
+972-50-7952406 jabber:[EMAIL PROTECTED]
[EMAIL PROTECTED] http://www.xorcom.com
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] autoconf issues for FreeBSD
On 10/05/06 06:45 Russell Bryant said the following:
- Luigi Rizzo <[EMAIL PROTECTED]> wrote:
I am pretty sure that the code below (which was my patch at the time)
is NOT a proper fix - i would expect autoconf to deal with platform
issues without having us deal with them on each and every port.
It really does seem odd that /usr/local/ would be the default prefix
where things are installed on FreeBSD, yet it is not one of the default
paths that the compiler and linker on the same system would look. If
that were the case, none of this would be a problem.
FreeBSD has a policy of separating what's part of the base system which
sits in /usr/bin, /usr/sbin, /usr/lib etc and what comes in from ports
which goes into /usr/local/{bin,sbin,lib,etc}. while this may seem
confusing to non-FreeBSD users, it has become second nature to FreeBSD users.
as Asterisk is included in the FreeBSD ports system, having autoconf do
this would greatly ease porting work.
--
Regards, /\_/\ "All dogs go to heaven."
[EMAIL PROTECTED](0 0) http://www.openmalaysiablog.com/
+==oOO--(_)--OOo==+
| for a in past present future; do|
| for b in clients employers associates relatives neighbours pets; do |
| echo "The opinions here in no way reflect the opinions of my $a $b." |
| done; done |
+=+
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] Re: SIP to IAX (Jeremy McNamara)
Thong Lam Hai wrote: In that case, I wonder how an SIP phone which is use SIP protocol to set up a call session can communicate with a SIP phone which is use H.323 if there is no module to convert two types of message Actually, we can use extension.conf to redirect from SIP channel to H.323 channel but we really need an converted module or converted function. Is that right? Asterisk translates the signaling methods for you via the Dialplan. Setup your sip.conf to accept calls from your SIP phone(s), which will include a specific context where you wants those calls to go into the dialplan (extensions.conf). That dialplan then can call any other channel type (Zap, IAX, H.323, SCCP, MGCP) by using the Dial application for the specific extension you wish to dial. I suggest you purchase the Asterisk book. You seem to be missing quite a few major core concepts of how Asterisk functions. http://www.oreilly.com/catalog/asterisk/ Jeremy McNamara ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
[asterisk-dev] Re: SIP to IAX (Jeremy McNamara)
_reload?
To: Kristian Kielhofner <[EMAIL PROTECTED]>
Cc: asterisk-dev@lists.digium.com
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Kristian Kielhofner wrote:
> Does app_reload set any channel variables based on status? I don't
> want this to turn into some kind of albatross for you, but I thought I'd
> ask :).
No, but it is trivial to set them - What were you thinkin?
Jeremy McNamara
--
Message: 6
Date: Thu, 5 Oct 2006 14:09:44 +0700
From: "Thong Lam Hai" <[EMAIL PROTECTED]>
Subject: [asterisk-dev] SIP to IAX
To:
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Hi,
Where is the code to change from SIP message to IAX message in Asterisk?
How do 2 channels (such as channel_sip and channel_iax2) communicate with
each other?
Regards,
Thong Lam
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-dev/attachments/20061005/df78304b
/attachment-0001.htm
--
Message: 7
Date: Thu, 05 Oct 2006 03:11:03 -0400
From: Jeremy McNamara <[EMAIL PROTECTED]>
Subject: Re: [asterisk-dev] SIP to IAX
To: Asterisk Developers Mailing List
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Thong Lam Hai wrote:
> Hi,
>
>
>
> Where is the code to change from SIP message to IAX message in Asterisk?
There is no 'code'
> How do 2 channels (such as channel_sip and channel_iax2) communicate
> with each other?
The Asterisk Dialplan (extensions.conf)
Jeremy McNamara
--
Message: 8
Date: Thu, 5 Oct 2006 00:15:33 -0700
From: Luigi Rizzo <[EMAIL PROTECTED]>
Subject: Re: [asterisk-dev] autoconf issues for FreeBSD
To: Asterisk Developers Mailing List
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
On Wed, Oct 04, 2006 at 08:37:45PM -0500, Kevin P. Fleming wrote:
> - Luigi Rizzo <[EMAIL PROTECTED]> wrote:
> > I am pretty sure that the code below (which was my patch at the time)
> > is NOT a proper fix - i would expect autoconf to deal with platform
> > issues
> > without having us deal with them on each and every port.
>
> That fix probably won't work correctly any longer, since the change to use
ASTCFLAGS and ASTLDFLAGS for the build system.
as russel said, here i only patched CFLAGS and LDFLAGS which is
what the configure script uses. AST* variables were already (more
or less) set properly.
> autoconf itself does nothing to increase platform compatibility; it is a
tool that allows a package builder to increase compatibility. The benefits
from autoconf are derived entirely from the logic that we put in the
configure script, not autoconf itself.
i am sure this has been discussed at length many times.
I think the goal of autotools was to ease portability, both
cross-platform and within a single platform with different packages
installed. Maybe for the latter, autoconf still makes sense.
But if you have to explicitly put in checks for what are platform
defaults, the first goal is defeated.
Besides, the "failures" are often subtle - it's not that configure
fails completely, it just gives you a suboptimal build because it
doesn't find 8 codecs and 4 libraries and so it doesn't build the
dependent modules.
And it does it so noisily (currently the output of asterisk's
configure is 332 lines!) that it is easy to miss the failures
while the text scrolls.
Also the choice of using "ancient greek" (pre-1977 shell) as the
language for expressing the logic in the configure script doesn't
help correctness: e.g. without local variables, i think macros are
not reentrant and things like
saved_CFLAGS="${CFLAGS}"
...
CFLAGS="${saved_CFLAGS}"
could easily be trashed.
> Once again (I'll agree with Russell here) it makes absolutely no sense for
/usr/local to be the standard place for libraries to be installed, but that
they are not in the search path for the compiler and linker. All this does
is require every package that wants to build on FreeBSD to require special
logic to add them to the search path, when the FreeBSD toolchain could
easily have these paths embedded into the toolchain by default. How
frustrating :-)
Yes, frustrating. But blaming the platform (or autoconf as i did above,
or my own ignorance as i often do privately) doesn't fix the build, so
let's work on the latter :)
cheers
cheers: Command not found.
/usr/local/cheers :)
luigi
--
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
End of asterisk-dev Digest, Vol 27, Issue 16
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
