# ASL3 - Cannot connect using DTMF \*2 or \*3 commands from radio or Supermon

**URL:** https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670
**Category:** Archive
**Tags:** asl3
**Created:** [August 17, 2024, 7:44pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670 "2024-08-17T19:44:32Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![n7jrr](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n7jrr/32/3211_2.png) [@n7jrr](https://community.allstarlink.org/u/n7jrr)
#### Post date: [August 17, 2024, 7:44pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/1 "2024-08-17T19:44:32Z")

</div>

I am not able to connect to nodes using DTMF commands \*2 or \*3. All other DTMF commands defined in rpt.conf work. Yes I have checked ASL console and DTMF commands are being decoded when sent from a radio. Also when trying to issue \*2 or \*3 in Supermon does not work. \*1 does work to disconnect a node. It has to be a configuration issue somewhere.

---

<div class="post-metadata">

### Author: ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)
#### Post date: [August 17, 2024, 9:58pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/2 "2024-08-17T21:58:32Z")

</div>

Have you upgraded to the latest version of the software ?  
or  
What version are you using exactly ?

---

<div class="post-metadata">

### Author: ![n7jrr](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n7jrr/32/3211_2.png) [@n7jrr](https://community.allstarlink.org/u/n7jrr)
#### Post date: [August 19, 2024, 10:55am UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/3 "2024-08-19T10:55:15Z")

</div>

The latest version 3.0.11.

---

<div class="post-metadata">

### Author: ![n7jrr](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n7jrr/32/3211_2.png) [@n7jrr](https://community.allstarlink.org/u/n7jrr)
#### Post date: [August 20, 2024, 11:22am UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/4 "2024-08-20T11:22:51Z")

</div>

Asterisk will not even connect to another node using Asterisk CLI

```
 node58846*CLI> rpt fun 58846 *355553

```

No response, no connection. If I connect to a node via Allmon3 I can disconnect from the node using

```
 node58846*CLI> rpt fun 58846 *155553

```

I can reconnect to the node using:

```
 node58846*CLI> rpt fun 58846 *30

```

So, what is going on?

---

<div class="post-metadata">

### Author: ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)
#### Post date: [August 20, 2024, 12:35pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/5 "2024-08-20T12:35:31Z")

</div>

Surprised nobody on the dev team is answering these questions.  
I am not even a asl3 user yet.

v3.3.0-1

> **[GitHub - AllStarLink/ASL3: AllStarLink Version 3](https://github.com/AllStarLink/ASL3)**
>
> AllStarLink Version 3. Contribute to AllStarLink/ASL3 development by creating an account on GitHub.

---

<div class="post-metadata">

### Author: ![KB4MDD](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kb4mdd/32/3817_2.png) [@KB4MDD](https://community.allstarlink.org/u/KB4MDD)
#### Post date: [August 20, 2024, 12:46pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/6 "2024-08-20T12:46:33Z")

</div>

Lets start with the cli command - `core show version`

---

<div class="post-metadata">

### Author: ![n7jrr](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n7jrr/32/3211_2.png) [@n7jrr](https://community.allstarlink.org/u/n7jrr)
#### Post date: [August 20, 2024, 12:57pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/7 "2024-08-20T12:57:08Z")

</div>

So I am running the latest image 3.0.11.

From core show version

> node58846\*CLI\> core show version  
> Asterisk 20.8.1+asl3-3.0.3-1.deb12 built by builder @ [allstarlink.org](http://allstarlink.org) on a aarch64 running Linux on 2024-07-16 23:20:31 UTC

---

<div class="post-metadata">

### Author: ![n7jrr](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n7jrr/32/3211_2.png) [@n7jrr](https://community.allstarlink.org/u/n7jrr)
#### Post date: [August 20, 2024, 1:54pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/8 "2024-08-20T13:54:13Z")

</div>

A new phenomenon - I **can** connect to a node with **four digits**.

> rpt fun 58846 \*32462

This works.

Nodes greater then five digits = no joy.

---

<div class="post-metadata">

### Author: ![KB4MDD](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kb4mdd/32/3817_2.png) [@KB4MDD](https://community.allstarlink.org/u/KB4MDD)
#### Post date: [August 20, 2024, 2:03pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/9 "2024-08-20T14:03:02Z")

</div>

I think you need to update to [ASL3 3.0.4 Released](https://community.allstarlink.org/t/asl3-3-0-4-released/21628)

There was an issue with node lookup.

---

<div class="post-metadata">

### Author: ![n7jrr](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n7jrr/32/3211_2.png) [@n7jrr](https://community.allstarlink.org/u/n7jrr)
#### Post date: [August 20, 2024, 2:18pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/10 "2024-08-20T14:18:48Z")

</div>

Ran the update. Still no joy…

Posted issued to GitHub page [https://github.com/AllStarLink/app\_rpt/issues/386](https://github.com/AllStarLink/app_rpt/issues/386)

---

<div class="post-metadata">

### Author: ![n7jrr](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n7jrr/32/3211_2.png) [@n7jrr](https://community.allstarlink.org/u/n7jrr)
#### Post date: [August 20, 2024, 8:40pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/11 "2024-08-20T20:40:37Z")

</div>

Turned out to be a DNS issue. The DNS assigned by my router DHCP was the problem. Made a manual entry in the Networking page to use 8.8.8.8 and 8.8.4.4. I can finally use my HT’s keypad to connect to other nodes. The guys monitoring the GitHub page helped me narrow down the problem. Thanks.

73 Andrew  
de N7JRR

---

<div class="post-metadata">

### Author: ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)
#### Post date: [August 23, 2024, 8:41pm UTC](https://community.allstarlink.org/t/asl3-cannot-connect-using-dtmf-2-or-3-commands-from-radio-or-supermon/21670/12 "2024-08-23T20:41:03Z")

</div>

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