jigjag
Junior Member
Posts: 2
Joined: Apr 2020
|
T46s won't try to register to server on local subnet
I have a Yealink T46s running v85.05 firmware with static IP 172.16.0.11 and DNS 8.8.8.8. The phone server 172.16.0.5 is in the same subnet 172.16.0.0/23 (literally on the same switch). I won't detail what type of phone server because its not even receiving packets from the Yealink phone, so the issue is on phone side.
Using the webpage of the phone / Settings / Configuration / Pcap, start
and configure phone like:
(Register Name, Username and Password are set as appropriate)
account.1.sip_server.1.address=172.16.0.5
account.1.sip_server.1.port=5060
account.1.sip_server.1.transport_type=1 (tcp)
account.1.sip_server.2.address=sip2.example.com
account.1.sip_server.2.port=5060
account.1.sip_server.2.transport_type=1 (tcp)
The registration to sip2.example.com works, but 172.16.0.5 fails.
I stop the pcap and see that the phone does have register traffic to sip2.example.com, but no packets, NONE AT ALL, are sent to 172.16.0.5.
When I export the log with Settings / Configuration / Export Local Log
(which by the way exports a zip file that's really a tar, confusing window's built in unzip program)
Anyways, the log shows the following messages over and over again:
<131>Sep 8 11:50:22 WEB [911:921]: WEB <3+error > 622.372.946:Send msg : [DONOW:NULL] [app_vpPhone], 0x60d02, 0, 0, , 5000
<131>Sep 8 11:50:22 WEB [911:921]: WEB <3+error > 622.373.614:CallDskMsgTimeoutEx [0x60d02] lret[2]
<131>Sep 8 11:51:05 sua [579.650]: NET <3+error > [255] close err socket=19!
<131>Sep 8 11:51:05 sua [579.650]: DLG <3+error > [255] out_socket is 0
<131>Sep 8 11:51:05 sua [579.650]: DLG <3+error > [000] <AEM> code=0x04030000, cb_transport_error (id=58), target=172.16.0.5:5060
I checked to make sure the phone can reach the phone server... Network / Diagnostics / Ping 172.16.0.5
# ping 172.16.0.5
PING 172.16.0.5 (172.16.0.5): 56 data bytes
64 bytes from 172.16.0.5: seq=0 ttl=64 time=0.484 ms
64 bytes from 172.16.0.5: seq=1 ttl=64 time=0.323 ms
64 bytes from 172.16.0.5: seq=2 ttl=64 time=0.336 ms
64 bytes from 172.16.0.5: seq=3 ttl=64 time=0.333 ms
--- 172.16.0.5 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.323/0.369/0.484 ms
I also double-checked that certificate checking was disabled at
Security / Trusted Certificates /
- Only Accept Trusted Certificates: Disabled
- Common Name Validation: Disabled
- CA Certificates: All Certificates
I even tried only having account.1.sip_server.1.address as sip1b.example.com (pointing to 172.16.0.5) and the phone still refused to sending a single packet.
If I switch the transport_mode to 0 (udp) it DOES send packets, but I don't want my phone server to allow UDP packets. Eventually I want to set up TLS/SRTP, so don't want to depent on UDP.
I really need to register to both servers. The first one is intentionally kept within the subnet to be resilient against DNS failure. The second server is in the cloud to allow remote users to reach a server if the primary goes down.
Any suggestions? or anyone know if this is a firmware bug?
|
|
09-08-2020 10:52 PM |
|