Log in

ctiefel · 05-05-2014 09:29 PM

We were getting many complaints from our users that they were getting "ghost calls" from random numbers like 101, 1001, etc. The phone would ring incessantly and when they picked it up it would just be dead air. We discovered this was a symptom of port scanning by scammers. The setting in the newer firmware "Allow IP Calls" when disabled stopped this from happening. However, the issue has cropped up again on phones where this setting is set to disabled. Any ideas?

***Yealink Support*** · 05-06-2014 03:09 PM

Can you check your phone's config.bin has below settings?
---------------------------
[ account ]
SIPTrustCtrl =1
---------------------------
or you can try to auto provisioning (Higher than V70).Please tell me your firmwares.
---------------------------
#!version:1.0.0.1
# X means the account number.
# For example: account.1.sip_trust_ctrl=1
account.x.sip_trust_ctrl=1
---------------------------

realcalls · 09-12-2014 04:41 AM

Hi, So how do you define a list of "allowed" IPs that calls will be accepted from?

***Wilson_Yealink*** · 09-12-2014 02:19 PM

If you set the SIPTrustCtrl =1 parameter, the phone only will accept the call which have accpeted by your PBX server.

thanks

Lansalot · 09-12-2014 05:55 PM

Hi
We have had similar reports from some of our users and I have come to this conclusion:
The 'cause' of this is BT Hubs.

I found this very useful free site:
http://sipscanner.voicefraud.com/
(Note: I am in no way affiliated with this site)

If you run a scan against an IP address of a BT Hub with a SIP phone behind it (home or business, doesn't seem to make a difference) then you will see SIP services exposed.

If you run a scan against an IP address of another router with a SIP phone behind it, we have a lot of Technicolor (was Thomson) routers - the results show NO SIP services exposed.

The firmware of the phone doesn't seem to make a difference, we have T20s, T22s and Yealink cordless units on various firmwares.

That's as far as I have gotten with our troubleshooting. I haven't tried any of the suggested Yealink settings but if I find out more, I will let you know.
Thanks

***Wilson_Yealink*** · 09-16-2014 04:03 PM

thank you for your share, Lansalot. Smile

Abe1048 · 12-26-2014 05:00 AM

(09-16-2014 04:03 PM)Yealink_Wilson Wrote: thank you for your share, Lansalot.

Hi all,

We have found that using a router with the tomato firmware fixes all theese issues.

Possibly Related Threads...
Thread:		Author	Replies:	Views:	Last Post
	Yealink T58W and Grandstream UCM6308 delayed audio on outgoing calls	waltersjo	2	1,902	12-19-2023 11:10 PM Last Post: waltersjo
	T33G - Unknown Symbol - Can't Make Outbound Calls	bbopp	0	704	12-09-2023 03:21 AM Last Post: bbopp
	WH67 (UC) Not Working for Outbound Calls	Chepino96	0	955	10-04-2023 05:26 AM Last Post: Chepino96
	View call logs for dropped calls	computersense	0	1,025	08-15-2023 11:26 AM Last Post: computersense
	Issue with headsets, calls are spontaneously ended	sanderv85	3	2,519	06-15-2023 06:44 PM Last Post: complex1
	W78P wont receive calls	dleather	1	1,896	12-22-2022 12:15 AM Last Post: dleather
	From field user part incomplete on some outbound calls	oliv	1	2,018	11-25-2022 06:14 PM Last Post: oliv
	W80 Emergency Calls with Locked Keypad	sandro84	0	3,008	10-18-2021 07:57 PM Last Post: sandro84
	Silencing / Rejecting Queue Calls	asafayan	1	4,768	07-13-2021 03:45 AM Last Post: complex1
	RTCP-XR MOS-CQ scores 0 on many calls	CyVon	0	3,258	04-01-2021 04:18 AM Last Post: CyVon

Threaded Mode \| Linear Mode Ghost Calls Round 2
Author	Message