- Joined
- Nov 24, 2020
- Messages
- 78
- Reaction score
- 20
We use Asterisk as our SIP Trunk provider, while is a third party provider. It doesn't trigger the warning of unsupported trunks.
Update 2 made a change to how 3CX reads it's templates. The Asterisk template doesn't have the "authtype" tag in the template, and because of this the authentication dropdown is removed when adding an Asterisk trunk. Modifying the existing provider template via WinSCP for asterisk.pv.xml to include the "authype" in the tags fixed the issue.
<header>
<type>gateway-template</type>
<version>150005</version>
<time>2024-05-21 11:30:00</time>
<name>Asterisk</name>
<url>https://www.3cx.com/partners/sip-trunks/</url>
<image></image>
<description>Worldwide</description>
<priority>2</priority>
<tags>registrar,proxy,port,advanced,cert,authtype</tags>
<templatetype>thirdparty</templatetype>
</header>
My Idea is to ensure that the templates provided by 3CX have the appropriate tags to ensure they work as intended with future updates. Missing tags seem cause settings to be missing in future updates.
Update 2 made a change to how 3CX reads it's templates. The Asterisk template doesn't have the "authtype" tag in the template, and because of this the authentication dropdown is removed when adding an Asterisk trunk. Modifying the existing provider template via WinSCP for asterisk.pv.xml to include the "authype" in the tags fixed the issue.
<header>
<type>gateway-template</type>
<version>150005</version>
<time>2024-05-21 11:30:00</time>
<name>Asterisk</name>
<url>https://www.3cx.com/partners/sip-trunks/</url>
<image></image>
<description>Worldwide</description>
<priority>2</priority>
<tags>registrar,proxy,port,advanced,cert,authtype</tags>
<templatetype>thirdparty</templatetype>
</header>
My Idea is to ensure that the templates provided by 3CX have the appropriate tags to ensure they work as intended with future updates. Missing tags seem cause settings to be missing in future updates.
Upvote
2
