> Am 07.08.2017 um 05:45 schrieb Michael Knill
> :
>
> Thanks Christopher for the info.
>
> Regards
> Michael Knill
Hi Michael,
I often use the h-extension (or hangup-handler) to get the HANGUPCAUSE, e.g.:
exten => h,1,Set(CDR(userfield)=${CDR(userfield)} Hangup:${HANGUPCAUSE})
Then you can
> Am 07.08.2017 um 06:33 schrieb Michael Knill
> :
>
> Yes I know FXS is dead but I have a customer who wants to build lots of
> single or more port FXS appliances running Asterisk.
> Astlinuk is perfect for this but hardware cost is the major driving factor
> here.
> What are the best FXS car
I have found hangup handlers to be MUCH more accurate than the h extension..
it seemed whe ni was using the h extension that it wouldnt trigger.. or
triggered in a different context than I expected when calls failed.-Christopher
From: Michael Keuter
To: AstLinux Users Mailing List
Thanks Michael and yes I do too but he wants it all in one appliance (
Regards
Michael Knill
-Original Message-
From: Michael Keuter
Reply-To: AstLinux List
Date: Monday, 7 August 2017 at 7:56 pm
To: AstLinux List
Subject: Re: [Astlinux-users] FXS ports
> Am 07.08.2017 um 06:33 schri
Cool I didn't know about Hangup Handlers. I need to use them I think.
Thanks all. Looks like the dial plan is the go here.
Regards
Michael Knill
From: AstLinux List
Reply-To: The Cadillac Kid , AstLinux List
Date: Monday, 7 August 2017 at 9:48 pm
To: AstLinux List
Cc: The Cadillac Kid
Subje
