Jim Dickenson wrote:
I am running version 1.4.x. Where do I get PRICAUSE?
NoOP(Hangup Cause: ${HANGUPCAUSE})
Doug
--
Ben Franklin quote:
"Those who would give up Essential Liberty to purchase a little Temporary Safety,
deserve neither Liberty nor Safety."
--
_
I am running version 1.4.x. Where do I get PRICAUSE? I tried making a call that
was not answered and I did not see any more information. The dumpchan of
DADHI/23-1 did not happen as that is in a macro that only gets called for an
answered call.
I only see this:
Executing [91112223...@empl:8]
On Jan 6, 2011, at 8:08 PM, Joel Maslak wrote:
> On Thu, Jan 6, 2011 at 7:06 AM, Jim Dickenson wrote:
>> Are there reasons to prefer the use of PRI over SIP or SIP over PRI?
[snip]
> I run the PBX for my organization which has about 160 extensions. I
> wouldn't even think of doing anything bu
PRICAUSE will give you lots of info on why a call was hungup on. Not
sure if SIP will give you the same.
On Thu, Jan 6, 2011 at 9:06 AM, Jim Dickenson wrote:
> Does Asterisk, currently using version 1.4, get any more information about
> the result of an outbound call made over a PRI line compare
On Thu, Jan 6, 2011 at 7:06 AM, Jim Dickenson wrote:
> Are there reasons to prefer the use of PRI over SIP or SIP over PRI?
Assuming you are talking to connect a PBX to the PSTN...
PRI advantages:
1. Relatively little equipment between the PTSN and the PBX. Less to
break or go wrong.
2. Simpl
Does Asterisk, currently using version 1.4, get any more information about the
result of an outbound call made over a PRI line compared to a call via a SIP
trunk?
As an example, in a PRI call there is this message that shows up on the console:
[2011-01-05 14:59:02] -- Channel 23 detected a