-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Poly Phones
- Desk and IP Conference Phones
- Re: 100 @ EXTERNAL CALLS UNWANTED NUMERAL
Create an account on the HP Community to personalize your profile and ask a question
02-18-2014 02:07 PM
How do I block SIP calls from any IP the phone is not registered with? Other phone manufacturers all have a straightforward way to do this but I did not find it when I skimmed the 3.x.x or 4.x.x admin / provisioning guides? I have these phones in production and if the network is not locked down properly or if the user brings a phone home, they are helpless.
There must be a way. Thanks for your time.
Solved! Go to Solution.
Accepted Solutions
02-18-2014 04:15 PM
Hello Phlobot,
welcome to the Polycom Community.
I suggest you have a look at the Incoming Signal Validation section within the matching admin guide.
This has been discussed before so the community search should help.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
02-18-2014 04:15 PM
Hello Phlobot,
welcome to the Polycom Community.
I suggest you have a look at the Incoming Signal Validation section within the matching admin guide.
This has been discussed before so the community search should help.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
02-24-2014 03:50 PM
I made the following changes (in bold) to my server_3xx.cfg file and it did stop the calls from ringing the phone.
It does not, however, prevent an attack such as astroid from crashing the phone. Is there a work-around for the crashing, or a less CPU-intense way to check the traffic?
<requestValidation
voIpProt.SIP.requestValidation.1.request="INVITE"
voIpProt.SIP.requestValidation.1.method="source"
voIpProt.SIP.requestValidation.1.request.1.event="{$requestValidation_1_event}"
voIpProt.SIP.requestValidation.2.request="{$requestValidation_2_request}"
voIpProt.SIP.requestValidation.2.method="{$requestValidation_2_method}"
voIpProt.SIP.requestValidation.2.request.1.event="{$requestValidation_2_event}">
<digest voIpProt.SIP.requestValidation.digest.realm="{$digest_realm|PolycomSPIP}"/>
</requestValidation>.
EDIT for details:
Polycom IP 301
FW: 3.1.x (i will test with later, non-4.x.x series fw later, in case the crashing was solved in an update)
02-24-2014 04:08 PM
Hello Phlobot,
any issues causing the phone to crash or high CPU needs to be individually investigated by Polycom support.
Please raise a case via your Polycom reseller.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
02-26-2014 11:26 AM
"Please raise a case via your Polycom reseller."
Because the phone is not a current model I will not persue this option, I am satisfied with the nature of the fix on this occasion.
When I tested the same modification noted above on an IP650, the sip floor would certainly cause high CPU load, but not to the point of crashing the unit.
"any issues causing ... high CPU needs to be individually investigated by Polycom support."
Properly seperating the phones from an open WAN is the real solution so I am not relying on this safety net alone. It would be nice if there was a better way to stop this as it breaks some of the more forward-looking functionality of VOIP phones. Maybe a buddy list of known acceptable URIs or something, I'm not sure.
Didn't find what you were looking for? Ask the community