Yealink Forums

On both models there is problem.
Phone's work correctly for 2-4 days.
After that period on both phones there is registration failed, doesn't help forcing to register or rebooting device.
Registering takes about 30 second to show failed (look's like there is no answer).

After changing local SIP port from 5061 to 5062 registers immediately, on next fail changing backward from 5062 to 5061 helps.

Both model have latest firmware 31.72.0.75, on previous version problem also existed.

I have dynamic public IP that changes every 24 hours from Internet provider, could this be problem with registering device on SIP provider?

Part of logs on first reg fail, there is error with "reg acc"

Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] REGISTER sip:sip.halonet.pl:5060 SIP/2.0^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] Via: SIP/2.0/UDP 192.168.2.26:5061;branch=z9hG4bK452954698^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] From: "xxx" <sip:xxx@sip.halonet.pl>;tag=505573743^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] To: "xxx" <sip:xxx@sip.halonet.pl>^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] Call-ID: 1624813433@192.168.2.26^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] CSeq: 1 REGISTER^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] Contact: <sip:kakaki@192.168.2.26:5061>^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] Max-Forwards: 70^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] User-Agent: Yealink SIP-T19P 31.72.0.75^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] Expires: 30^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] Allow-Events: talk,hold,conference,refer,check-sync^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] Content-Length: 0^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000] ^M
Jan 4 07:28:07 SIP [239]: SDL <6+info > [000]
Jan 4 07:28:07 SIP [239]: SDL <5+notice> [000] send request retransmission (id=10769)^M
Jan 4 07:28:07 SIP [239]: SUA <6+info > [000] Emb event:[0x00000002] recv
Jan 4 07:28:07 SIP [239]: SUA <3+error > [000] [Server0]: try reg again after (30) s
Jan 4 07:28:37 SIP [239]: SUA <5+notice> [000] reg acc:"xxx"<sip:xxx@sip.halonet.pl>
Jan 4 07:28:37 SIP [239]: SDL <5+notice> [000] Release terminated transaction
Jan 4 07:28:37 SIP [239]: SUA <5+notice> [000] host=sip.halonet.pl, transport=0, port=5060, family=2
Jan 4 07:28:37 SIP [239]: DNS <5+notice> [DNS] sip.halonet.pl is not found in dns cache
Jan 4 07:28:37 SIP [239]: DNS <5+notice> [DNS] set DNS timeout=3000, tries=2
Jan 4 07:28:37 SIP [239]: DNS <5+notice> [DNS] About to query 'sip.halonet.pl' IN A/AAAA
Jan 4 07:28:37 SIP [239]: DNS <5+notice> [DNS] dnsutils_dns_query succ !
Jan 4 07:28:37 SIP [239]: SUA <5+notice> [000] DNS query:Successful completion
Jan 4 07:28:37 SIP [239]: DNS <6+info > [DNS] dns record 0: sip.halonet.pl/193.43.148.37
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] DNS resolution with 193.43.148.37:5060
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] Message sent: (to dest=193.43.148.37:5060)
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000]
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] REGISTER sip:sip.halonet.pl:5060 SIP/2.0^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] Via: SIP/2.0/UDP 192.168.2.26:5061;branch=z9hG4bK514830366^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] From: "xxx" <sip:xxx@sip.halonet.pl>;tag=148870403^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] To: "xxx" <sip:xxx@sip.halonet.pl>^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] Call-ID: 958571259@192.168.2.26^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] CSeq: 1 REGISTER^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] Contact: <sip:xxx@192.168.2.26:5061>^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] Max-Forwards: 70^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] User-Agent: Yealink SIP-T19P 31.72.0.75^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] Expires: 30^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] Allow-Events: talk,hold,conference,refer,check-sync^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] Content-Length: 0^M
Jan 4 07:28:37 SIP [239]: SDL <6+info > [000] ^M

Does the T21 or T19 have a secondary SIP Server option that it can fail to? I do not have one to login to right now.
On server one - use port 5061
On server two - use port 5062
Ensure both ports are open to firewall.

BTW: You might want to obfuscate your public ip address.I know it is dynamic... but in the meantime, it could be current.

There is no secondary connection set (SIP Server 2). provider only has one domain available.
Port 5061/5062 is for LOCAL not remote (settings in Account-advanced-Local SIP Port)

There is no public IP address visible only local and IP of VOIP provider halonet.pl

(01-06-2015 06:07 AM)kakaki Wrote: [ -> ]Port 5061/5062 is for LOCAL not remote (settings in Account-advanced-Local SIP Port)

Do you have multiple endpoints assigned in the same building?I think I read the above as YES.
Does each phone us a different internal port?