YeaLInk Wireless DECT 60B not working 1

[LRB45]

Aside from the system issues I had on another thread I have a wireless phone not working properly

Using a Yealink W60P wireless phone that I can make calls on however it will not ring. I've verified it is not forwarded and DND is not enabled and SSA doesn't show anything atypical.

 

[derfloh]

Show a SIP trace

Need some help with IP Office?

https://www.fwilke.com/home

IP Office SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[LRB45]

trace of ext 202(k175) calling 205(wireless)

I pulled the trace and will get a better version when possible. AND since I left all of the public info in the post like a dumba** when i know better. Thanks for pointing that out hairlessupportmonkey

 

[TheSmash]

I don't see any packets from the extension 205 in that trace, only invites sent from the IPO to the handset.

It looks like both handsets, 202 and 205 are sitting behind the same NAT (108.84.88.237) and connecting over the Public internet using TCP.

Also, your IPO is visible to the public internet. Please make sure you've disabled all non essential user accounts and you have a strong password. Better still, lock down access to IPO ports to just addresses that you trust.

I'd recommend you use TLS and switch on Media security.

ACSS (SME)

 

[janni78]

I assume this is hosted on Amazon based on the IP information, would been important information to include from the beginning.

It tries to send the INVITE to the DECT base on port 5060 on the far end.
It's very unlikely that it would used this port when registering to the IP Office.

Does the accounts on the DECT base show as registered extension in System Status?

"Trying is the first step to failure..." - Homer

 

[hairlessupportmonkey]

Sheesh

https://www.shodan.io/host/108.84.88.237

You must also see SIP Vicious agent hammering your IPO

https://www.shodan.io/host/54.196.108.5

Recommend you edit this post and sanitise it.

ACSS - SME
General Geek

 

[LRB45]

Turns out this was a firewall issue on my CheckPoint 730 appliance
Even though I added SIP ports 5060/5061 to the exceptions list it was still blocking them. Oddly enough the Security logs showed them as accepted but upon doing a SSH capture found out it was actually still blocking them.
Had to disable inspection on the service to get it working. Seems odd that the other SIP phones worked fine except this one.