Under Review yealink templates

Status
Not open for further replies.

fox-net

Customer
Joined
Feb 9, 2022
Messages
1
Reaction score
0
Hello.
Why is the template used 2 times a line one line with no parameter and with parameter?
file - yealinkT4x.ph.xml
account.1.sip_server.1.transport_type =
account.1.sip_server.1.transport_type = 0 - for udp transport
it makes sense to make the parameter without a value? So that you can configure different protocols on different phones udp, tcp, tls.
Currently always using only udp.
I don't want to create a custom template.
 
Hello @fox-net

The one with no value is ignored by the phone so it's not relevant (we could remove this in the future as it is redundant).

The second one with the value is relevant, because by default we provision the phones in UDP mode.
We enforce UDP to ensure that the phones work as tested and as intended (this is the 3CX supported method).

We will consider removing the value in a future template revision once we get a chance to review all Yealink affected devices, but for now if you wish to change the behavior you will either need to switch to custom templates or remove the 3CX provisioning link from the device.
 
  • Like
Reactions: Evolute IT
Hello @fox-net

The one with no value is ignored by the phone so it's not relevant (we could remove this in the future as it is redundant).

The second one with the value is relevant, because by default we provision the phones in UDP mode.
We enforce UDP to ensure that the phones work as tested and as intended (this is the 3CX supported method).

We will consider removing the value in a future template revision once we get a chance to review all Yealink affected devices, but for now if you wish to change the behavior you will either need to switch to custom templates or remove the 3CX provisioning link from the device.
Any chance TLS/SRTP will come? I know there's a parameter for it, but it's commented out. Instead of forcing UDP (which I don't think you are), why not just leave it blank? After a reset, it should be UDP by default anyway.
 
I am trying to use a custom template to make sure the phone provisions to TLS / SRTP but I am not sure of the configuration. I realize this is not supported, but I figure if I can't get help on the forums where do I go ;)

When I add the SRTP section, I do get a selection box in the phone provisioning page. I also put the compulsory as the first option to be default. However the phone doesn't get this value for some reason, but one step at a time.

Code:
    <srtp>
      <option value="Enabled compulsory (forced)">
        <item name="srtpvalue">2</item>
      </option>
      <option value="Disabled">
        <item name="srtpvalue">0</item>
      </option>
      <option value="Optionally enabled (not enforced)">
        <item name="srtpvalue">1</item>
      </option>
    </srtp>



account.1.srtp_encryption = %%srtpvalue%%

For the SIP Transport, I can't find any documentation stating what this should be called to be included in the WebUI

Code:
    <siptransport>
      <option value="TLS">
        <item name="siptransportvalue">2</item>
      </option>
      <option value="UDP">
        <item name="siptransportvalue">0</item>
      </option>
      <option value="TCP">
        <item name="siptransportvalue">1</item>
      </option>
      <option value="DNS NAPTR">
        <item name="siptransportvalue">3</item>
      </option>
    </siptransport>

account.1.sip_server.1.transport_type = %%siptransportvalue%%
 
BTW I figured out the SRTP section, turns out it was nested within an IF block which was only for LAN provisioning, I moved it out to the top.

The SIP transport for now I just did as hard coded value since the variable is not stored if it's not in the webUI I guess.

If anyone is interested in the template and working on it together let me know.
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,832
Messages
589,285
Members
164,662
Latest member
DejanMDS