[prev in list] [next in list] [prev in thread] [next in thread]
List: asterisk-dev
Subject: Re: [Asterisk-Dev] Re: Originate Call and Unique ID
From: "Stefan Reuter" <srt () reucon ! net>
Date: 2005-08-31 10:36:54
Message-ID: 1563.83.242.60.168.1125484614.squirrel () mail ! reucon ! net
[Download RAW message or body]
>> I already have the Async attribute set to true. The problem is, that
>> while I can recognize a successfully made Originate this way, through
>> its then available unique ID, I don't see any way to tell why a failed
>> call failed.
>> Unfortunately I need the failure reason (Busy, Noanswer, etc) to change
>> the way the IVR responds. (I.e. use a different way of alarming someone
>> if the outbound line is unavailable, etc)
>
[...]
> this problem also. The ability to set the Async attribute is a nice
> feature actually, but if you lose the ability to detect why a call failed.
> For LCR + retries to work we need to ability to do different types of call
> retries depending on the failure reason.
> This definitely needs to be fixed before release!
The OriginateFailure event contains an attribute called "Reason" for that
purpose.
=Stefan
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic