My guess is since the call was never answered you should be looking at
${DIALSTATUS}
--
Jim Dickenson
mailto:dicken...@cfmc.com
CfMC
http://www.cfmc.com/
On Apr 15, 2011, at 5:02 AM, Vlasis Hatzistavrou wrote:
> Hello,
>
> On an Asterisk 1.4.33.1 in a simple scenario:
>
> [test]
> exten => _X.,1,Dial(SIP/12345@peer01,,,)
>
> exten => i,1,Hangup(${HANGUPCAUSE})
> exten => t,1,Hangup(${HANGUPCAUSE})
> exten => h,1,Hangup(${HANGUPCAUSE})
>
>
> I have noticed that no matter what value we set in the Hangup(<cause code>)
> commands, if the call is not answered by peer01 for any reason, the actual
> cause code returned to the calling party is a 503, no matter what the
> ${HANGUPCAUSE} is.
>
> Even if we set a fixed value like Hangup(1) (which should give a 404) or
> Hangup(17) (which should give a 486), the cause code returned is always a 503.
>
> Has anyone else noticed this? I went through the issue tracker but I couldn't
> find any relevant bug posted in the past. I am certain that in previous
> versions I could set the reply message to the desired value, so I wonder if
> this is a bug in this particular version (1.4.33.1).
>
> --
> Best regards,
> Vlasis Hatzistavrou.
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
> http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
