# Asterisk Dialstatus for individual sip endpoint

**URL:** <https://community.asterisk.org/t/asterisk-dialstatus-for-individual-sip-endpoint/99153>\
**Category:** Asterisk Endpoints\
**Created:** [October 18, 2023, 7:42am UTC](https://community.asterisk.org/t/asterisk-dialstatus-for-individual-sip-endpoint/99153 "2023-10-18T07:42:34Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![disolaterX](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/disolaterx/32/6666_2.png) [@disolaterX](https://community.asterisk.org/u/disolaterX)\
**Post date:** [October 18, 2023, 7:42am UTC](https://community.asterisk.org/t/asterisk-dialstatus-for-individual-sip-endpoint/99153/1 "2023-10-18T07:42:34Z")

</div>

In asterisk dialplan is there any way to find out what happened to all sip endpoint that I parallel dialed in dial function on one-by-one basis

---

<div class="post-metadata">

**Author:** ![tootai](https://avatars.discourse-cdn.com/v4/letter/t/e480ec/32.png) [@tootai](https://community.asterisk.org/u/tootai)\
**Post date:** [October 18, 2023, 8:04am UTC](https://community.asterisk.org/t/asterisk-dialstatus-for-individual-sip-endpoint/99153/2 "2023-10-18T08:04:45Z")

</div>

You could use DEVICE\_STATE before calling endpoints

---

<div class="post-metadata">

**Author:** ![disolaterX](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/disolaterx/32/6666_2.png) [@disolaterX](https://community.asterisk.org/u/disolaterX)\
**Post date:** [October 18, 2023, 8:17am UTC](https://community.asterisk.org/t/asterisk-dialstatus-for-individual-sip-endpoint/99153/3 "2023-10-18T08:17:45Z")

</div>

But does DEVICE\_STATE check at sip level what is happening to that endpoint as my users are actual connected to kamailio and asterisk is dumb machine I think it would not work

---

<div class="post-metadata">

**Author:** ![jcolp](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/jcolp/32/8848_2.png) [@jcolp](https://community.asterisk.org/u/jcolp)\
**Post date:** [October 18, 2023, 8:50am UTC](https://community.asterisk.org/t/asterisk-dialstatus-for-individual-sip-endpoint/99153/4 "2023-10-18T08:50:43Z")

</div>

If you mean check all the SIP response codes, there is hangup cause[1]. If this isn’t what you mean then you’d need to further elaborate. For example there is no “DIALSTATUS” per endpoint, it represents the over all dialing.

[1] [Hangup Cause - Asterisk Documentation](https://docs.asterisk.org/Configuration/Miscellaneous/Hangup-Cause/?h=hangup+cause)

---

<div class="post-metadata">

**Author:** ![disolaterX](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/disolaterx/32/6666_2.png) [@disolaterX](https://community.asterisk.org/u/disolaterX)\
**Post date:** [October 18, 2023, 11:57am UTC](https://community.asterisk.org/t/asterisk-dialstatus-for-individual-sip-endpoint/99153/5 "2023-10-18T11:57:39Z")

</div>

I updated the dialplan and added  
app.NoOp\*\*(**“Channels with hangup cause information” … (channel.HANGUPCAUSE\_KEYS:get() or ‘’**))\*\*

but its not giving any output, for info I am using lua dialplan

---

<div class="post-metadata">

**Author:** ![jcolp](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/jcolp/32/8848_2.png) [@jcolp](https://community.asterisk.org/u/jcolp)\
**Post date:** [October 18, 2023, 12:24pm UTC](https://community.asterisk.org/t/asterisk-dialstatus-for-individual-sip-endpoint/99153/6 "2023-10-18T12:24:22Z")

</div>

I have no experience with the lua dialplan, so can’t help with that. I can say that the functionality itself does work.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/asterisk/original/2X/4/475d0c889911cfb84ac4881ad6df8b523e3f9105.png) [@system](https://community.asterisk.org/u/system)\
**Post date:** [November 17, 2023, 12:25pm UTC](https://community.asterisk.org/t/asterisk-dialstatus-for-individual-sip-endpoint/99153/7 "2023-11-17T12:25:07Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
