# Regarding ASL, HamVoIP and default codec priority

**URL:** <https://community.allstarlink.org/t/regarding-asl-hamvoip-and-default-codec-priority/22648>\
**Category:** AllStarLink\
**Created:** [January 9, 2025, 5:17am UTC](https://community.allstarlink.org/t/regarding-asl-hamvoip-and-default-codec-priority/22648 "2025-01-09T05:17:51Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [October 31, 2025, 12:37am UTC](https://community.allstarlink.org/t/regarding-asl-hamvoip-and-default-codec-priority/22648/22 "2025-10-31T00:37:09Z")

</div>

For every stanza in `iax.conf` add or change `codecpriority=host`. That forces the server to set the ordered list.

---

<div class="post-metadata">

**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\
**Post date:** [October 31, 2025, 12:57am UTC](https://community.allstarlink.org/t/regarding-asl-hamvoip-and-default-codec-priority/22648/23 "2025-10-31T00:57:51Z")

</div>

Yup.

@K2CB's incoming `[general]` stanza specifies `codecpriority = caller`.

```auto

```

---

<div class="post-metadata">

**Author:** ![K2CB](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@K2CB](https://community.allstarlink.org/u/K2CB)\
**Post date:** [October 31, 2025, 3:46am UTC](https://community.allstarlink.org/t/regarding-asl-hamvoip-and-default-codec-priority/22648/24 "2025-10-31T03:46:30Z")

</div>

A while back I had a separate issue where ClearNode users could not successfully negotiate a connection to my hub node, so I switched [radio] to _codecpriority=caller_, which solved that issue.

I would prefer to leave my hub node to caller, then have the other nodes set their codec priority accordingly, which is what led me to this concern.

---

<div class="post-metadata">

**Author:** ![K2CB](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@K2CB](https://community.allstarlink.org/u/K2CB)\
**Post date:** [October 31, 2025, 3:48am UTC](https://community.allstarlink.org/t/regarding-asl-hamvoip-and-default-codec-priority/22648/25 "2025-10-31T03:48:49Z")

</div>

I just realized that my [radio] stanza is actually pointing to the radio-secure context, so I'm guessing it won't help to create a new stanza called radio-secure. Or would it?

_; Incoming radio connections_

_[radio]_  
_type = user_  
_disallow = all_  
_;allow = slin16_  
_;allow = slin_  
_allow = ulaw_  
_allow = adpcm_  
_allow = g722_  
_allow = g726aal2_  
_allow = gsm_  
_allow = ilbc_  
_codecpriority = caller_  
_context = radio-secure_  
_transfer = no_

_[iaxrpt] ; Connect from iaxrpt Username field (PC AllStar Client)_  
_type = user ; Notice type is user here \<---------------_  
_context = iaxrpt ; Context to jump to in extensions.conf_  
_auth = md5_  
_secret = Motorola1rola1_  
_host = dynamic_  
\*disallow = all \*  
_allow = ulaw_  
_allow = adpcm_  
\*allow = gsm \*  
_transfer = no_

_[phone-iaxrpt]_  
_type = friend_  
_context = phone-iaxrpt_  
_auth = md5_  
_secret = Motorola1rola1_  
_host = dynamic_  
_disallow = all_  
_;allow = slin_  
_allow = ulaw_  
_allow = adpcm_  
_allow = gsm_  
_transfer = no_

_[iaxclient] ; Connect from iax client (Zoiper...)_  
_type = friend ; Notice type here is friend \<--------------_  
_context = iax-client ; Context to jump to in extensions.conf_  
_auth = md5_  
_secret = af8e76d867961118710cb9e125f1ad29_  
_host = dynamic_  
_disallow = all_  
_allow = ulaw_  
_allow = adpcm_  
_allow = gsm_  
_transfer = no_

_[allstar-sys]_  
_type = user_  
_context = allstar-sys_  
_auth = rsa_  
_inkeys = allstar_  
_disallow = all_  
_allow = ulaw_  
_allow = adpcm_  
_allow = gsm_

_[allstar-public]_  
_type = user_  
_context = allstar-public_  
_auth = md5_  
_secret = allstar_  
_disallow = all_  
_;calltokenoptional=0.0.0.0/0.0.0.0_  
_requirecalltoken=no_  
_allow = ulaw_  
_allow = adpcm_  
_allow = gsm_

---

<div class="post-metadata">

**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\
**Post date:** [October 31, 2025, 3:34pm UTC](https://community.allstarlink.org/t/regarding-asl-hamvoip-and-default-codec-priority/22648/26 "2025-10-31T15:34:35Z")

</div>

I have to admit that "I" continue to get confused with Asterisk contexts and the dialplan. So, I posed a few questions to my favorite AI 🙂

If you recall, exec'ing `rpt lookup 12345` in the Asterisk CLI returns something like :

```auto
Node: 12345 Data: radio@127.0.0.1/12345,NONE

```

The "radio" would be the context in the `iax.conf` file.

Now, within the `[radio]` context in `iax.conf ` you have `context = radio-secure` and that would be the context in `extensions.conf` ... and that's why the extension logging are saying @radio-secure.

As for the codec priority, if you have a server/node where you prefer one codec over another then don't forget to specify `codecpriority=host`.

and, hopefully, this helps to clear up some of the confusion.

[Previous page](https://community.allstarlink.org/t/regarding-asl-hamvoip-and-default-codec-priority/22648.md?page=1)