Yealink T48S Phones constantly disconnecting from system

Status
Not open for further replies.

RubenPena

Silver Partner
Advanced Certified
Joined
Jan 4, 2018
Messages
8
Reaction score
0
We have a small office with 5 phones. 4 of the 5 phones are constantly losing their connection. When this happens they can call out but can't receive calls. Worst part is that this affects the main receptionist phone. When I look at the activity log I see the following:

05/25/2018 11:02:50 AM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478/UDP fk=0; ignored
05/25/2018 11:01:07 AM - [CM503003]: Call(C:220): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 11:00:43 AM - [CM503003]: Call(C:220): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 10:56:02 AM - [CM503003]: Call(C:219): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 10:55:46 AM - [CM503003]: Call(C:219): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 10:47:05 AM - [CM503003]: Call(C:217): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 10:46:57 AM - [CM503003]: Call(C:215): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 10:46:32 AM - x-call-control DROP: call is not found: zv3YqTLHEMk3FrN4QnAo8w..;from-tag=1c73b44b;to-tag=fdefb219
05/25/2018 10:46:31 AM - [CM503003]: Call(C:216): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 10:46:31 AM - [CM503003]: Call(C:216): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Cancelled/INVITE from 70.120.249.221:5065
05/25/2018 10:46:28 AM - [CM503003]: Call(C:215): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 10:46:26 AM - [CM503003]: Call(C:213): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 10:46:07 AM - [CM503003]: Call(C:212): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 10:46:04 AM - x-call-control DROP: call is not found: moCtd4Vk0vDJp_UOMBnkRw..;from-tag=8a11527d;to-tag=12a1dc69
05/25/2018 10:46:03 AM - [CM503003]: Call(C:214): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 10:46:03 AM - [CM503003]: Call(C:214): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Cancelled/INVITE from 70.120.249.221:5065
05/25/2018 10:46:01 AM - [CM503003]: Call(C:211): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 10:45:59 AM - [CM503003]: Call(C:213): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 10:45:52 AM - [CM503003]: Call(C:210): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 10:45:41 AM - [CM503003]: Call(C:212): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 10:42:50 AM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478/UDP fk=0; ignored
05/25/2018 10:39:50 AM - [CM503003]: Call(C:209): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 10:39:24 AM - [CM503003]: Call(C:209): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 10:38:06 AM - [CM503003]: Call(C:208): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 10:37:55 AM - [CM503003]: Call(C:208): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 10:22:50 AM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478/UDP fk=0; ignored
05/25/2018 10:02:50 AM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478/UDP fk=0; ignored
05/25/2018 9:42:50 AM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478/UDP fk=0; ignored
05/25/2018 9:22:50 AM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478/UDP fk=0; ignored
05/25/2018 9:02:49 AM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478/UDP fk=0; ignored
05/25/2018 8:42:49 AM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478/UDP fk=0; ignored
05/25/2018 8:42:46 AM - [CM503003]: Call(C:206): Call to <sip:[email protected]:5060> has failed; Cause: 408 Request Timeout/INVITE from local
05/25/2018 8:42:21 AM - [CM503003]: Call(C:206): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/25/2018 8:22:49 AM - There's another STUN server that resolves to the same IP: 158.69.11.6:3478/UDP fk=0; ignored

Rebooting fixes the problem temporarily. Would like to find a permanent fix.

This is a 3CX v 15.5 install on Google Cloud.
 
If you don't use an SBC, then the first step is to confirm that each set has a unique local port assigned. (not all using port 5060). Even doing this doesn't guarantee that it will be problem free. The type of router being used at the site can make a difference. A check of the 3CX Activity Log after each set attempts a registration will show how 3CX "sees" each set. It should be as PublicIP: port, with each port being unique.

As suggested, the best solution is to use an SBC.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,885
Messages
589,547
Members
164,745
Latest member
Herm77