[asterisk-users] OriginateEvent reason codes.

[DiegoF]

//////////////////////////////////////////////////////////////////
hello, I am developing something similar, but not of as I cosay are those
that you speak, can say to me as she takes them or of where. The form as I
am doing it is reading all the events that socket throws. When receipt the
message * "Originate successfully queued" * is because I answer the client.
When receipt the message * "Originate failed" *, depending on the time in
which it is delayed in giving the answer me I determine if "it is occupied"
or "it does not answer".
 //////////////////////////////////////////////////////////////////
texto original en español

hello, I am developing something similar, but not of as I cosay are those
that you speak, can say to me as she takes them or of where. The form as I
am doing it is reading all the events that socket throws. When receipt
the Originate
message successfully queued is because I answer the client. When receipt the
Originate message failed, depending on the time in which it is delayed in
giving the answer me I determine if "it is occupied" or "it does not
answer".

////////////////////////////////////////////////////////////////////
texto original en español
hola, yo estoy desarrollando algo parecido, pero no se de cuales codigo son
los que usted habla, me podria decir como los toma o de donde. La forma como
yo lo estoy haciendo es leyendo todos los eventos que arroja el socket.
Cuando recibo el mensaje Originate successfully queued  es porque contesto
el cliente. Cuando recibo el mensaje Originate failed, dependiendo del
tiempo en que se demore en darme la respuesta determino si es "ocupado" o
"no contesta".

DiegoF


On 10/13/06, Jan du Toit <jan.du.toit at decisionworx.com> wrote:
>
> Hi.
>
> I'm making calls via the Manager OriginateAction. My action is set to be
> async and therefore I receive originiate events. Within the originate
> event that I receive there is a reason code. In the event of failure I
> need to dermine why the call failed (no pickup, rejected, no such
> number, circuit busy, ect) and inform the user with a meaningful
> message. I assume that one is suppose to determine the failure cause by
> interpreting the reason code. But the reason is always 1. If the callee
> does not pickup the reason is 1, if the callee rejects the call the
> reason is 1, if the number does not exist the reason is 1. If the call
> was successful the reason is 4. Is this correct behaviour? Am I doing
> something wrong?
>
> What are all the different reason codes? Where can I find a list that
> explains what all the different codes mean? Are they the same as the
> hangup causes?
> If the reason code is not meant to determine failure causes, how else
> can I determine this?
>
> Thanks. Regards, Jan.
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>



-- 
//  DiegoF  //

// Dichosos aquellos que no esperan nada de la vida, porque nunca seran
defraudados
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20061013/c045b0ef/attachment.htm