Hi,
Thank you, this what i'm looked for, but how can i differenciate busy or
unreachable number.
I get this value in debug :
Call failed to go through, reason 5.
How can i get this value.
this doesn't work :
exten => failed,1,Set(CDR(userfield)=Call failed)
exten => failed,n,Set(CallTime=${STRFTIME(${EPOCH},GMT+2,%F %X)})
exten => failed,n,Set(FAXRECEIVER=${TONUMBER})
exten => failed,n,Set(DATEDEBUTEMISSION=${CallTime})
exten => failed,n,NoOp(TX: DIAlSTATUS is ${DIALSTATUS})
exten => failed,n,NoOp(TX: HANGUPCAUSE is ${HANGUPCAUSE})
exten => failed,n,NoOp(TX: REASON is ${REASON})
exten => failed,n,NoOp(TX: CAUSECODE is ${CAUSECODE})
exten => failed,n,Hangup()
-- Executing [fai...@faxout:1] Set("OutgoingSpoolFailed",
"CDR(userfield)=Call failed")
-- Executing [fai...@faxout:2] Set("OutgoingSpoolFailed",
"CallTime=2009-05-3 14:27:10")
-- Executing [fai...@faxout:3] Set("OutgoingSpoolFailed",
"FAXRECEIVER=0033145301111")
-- Executing [fai...@faxout:4] Set("OutgoingSpoolFailed",
"DATEDEBUTEMISSION=2009-05-13 14:27:10")
-- Executing [fai...@faxout:5] NoOp("OutgoingSpoolFailed", "TX:
DIAlSTATUS is ")
-- Executing [fai...@faxout:6] NoOp("OutgoingSpoolFailed", "TX:
HANGUPCAUSE is 0")
-- Executing [fai...@faxout:7] NoOp("OutgoingSpoolFailed", "TX: REASON
is ")
-- Executing [fai...@faxout:8] NoOp("OutgoingSpoolFailed", "TX:
CAUSECODE is ")
Best regards,
Patrice
----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Wednesday, May 13, 2009 12:00 PM
Subject: Callweaver-users Digest, Vol 26, Issue 7
> Send Callweaver-users mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.callweaver.org/mailman/listinfo/callweaver-users
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Callweaver-users digest..."
>
>
> Today's Topics:
>
> 1. FAILED CALL STATUS (Le Manach Patrice SEWAN)
> 2. Re: FAILED CALL STATUS (Brandon Mackie)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 12 May 2009 13:02:10 +0200
> From: "Le Manach Patrice SEWAN" <[email protected]>
> Subject: [Callweaver-users] FAILED CALL STATUS
> To: <[email protected]>
> Message-ID: <84f0322dfc564a1cbab515e2a688b...@rocroy>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> are there any solutions with last release ?
>
> Best regards,
>
> Patrice
>
> ----- Original Message -----
> From: Le Manach Patrice SEWAN
> To: [email protected]
> Sent: Tuesday, January 06, 2009 1:38 PM
> Subject: FAILED CALL STATUS
>
>
> Hi,
>
> I doesn't know how get the status of a call by outgoing spool way in case
> the line is busy or unreachable.
>
> The differents variables (DIALSTATUS, HANGUPCAUSE, REASON, CAUSECODE)
> doesn't return usefull value.
>
> the only way i found is EXTEN var who contains "failed".
>
> Best regards,
>
> Patrice
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.callweaver.org/pipermail/callweaver-users/attachments/20090512/f820d5a5/attachment.html
>
> ------------------------------
>
> Message: 2
> Date: Tue, 12 May 2009 07:26:51 -0400
> From: Brandon Mackie <[email protected]>
> Subject: Re: [Callweaver-users] FAILED CALL STATUS
> To: Users Mailing List - Non-Commercial Discussion
> <[email protected]>
> Message-ID:
> <06755e27d82faa4a957db71fb718408e14e32f6...@mse22be1.mse22.exchange.ms>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Good morning,
>
> I believe you're talking about how to get the status of a call that has
> been started by a .call file in the outgoing spool folder. If this is true
> then here's a quick example to point you in the right direction
>
> In the .call file you'd have to have something like
> Context: testcall
> Extension: start
> Priority: 1
>
> Once the call was connected the dialplan would begin in the start section.
> If for whatever reason the dialout failed then the dialplan would begin in
> the failed section. In this example it sets the userfield in the cdrs to a
> failed/success message.
>
> [testcall]
> exten => start,1,Set(CDR(userfield)=Call success)
> exten => start,2,Hangup()
> exten => failed,1,Set(CDR(userfield)=Call failed)
> exten => failed,2,Hangup()
>
> This is likely why the EXTEN var would contain "failed". I'm sure the
> Hangup under failed is not required but it's a good practice. If this is
> not what you're looking for please post more information.
>
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Le Manach
> Patrice SEWAN
> Sent: May-12-09 5:02 AM
> To: [email protected]
> Subject: [Callweaver-users] FAILED CALL STATUS
>
> Hi,
>
> are there any solutions with last release ?
>
> Best regards,
>
> Patrice
>
> ----- Original Message -----
> From: Le Manach Patrice SEWAN<mailto:[email protected]>
> To:
> [email protected]<mailto:[email protected]>
> Sent: Tuesday, January 06, 2009 1:38 PM
> Subject: FAILED CALL STATUS
>
> Hi,
>
> I doesn't know how get the status of a call by outgoing spool way in case
> the line is busy or unreachable.
>
> The differents variables (DIALSTATUS, HANGUPCAUSE, REASON, CAUSECODE)
> doesn't return usefull value.
>
> the only way i found is EXTEN var who contains "failed".
>
> Best regards,
>
> Patrice
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.callweaver.org/pipermail/callweaver-users/attachments/20090512/38583451/attachment-0001.htm
>
> ------------------------------
>
> _______________________________________________
> Callweaver-users mailing list
> [email protected]
> http://lists.callweaver.org/mailman/listinfo/callweaver-users
>
>
> End of Callweaver-users Digest, Vol 26, Issue 7
> ***********************************************
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
