• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The Poly Phones Knowledge Base is live! We look forward to helping you with common issues and troubleshooting advice!
HP Recommended

I have found the solution below in numerous locations that successfully blocks phantom calls when the phone is registered against a single server:

<voIpProt>
<voIpProt.server voIpProt.server.1.address="xxx.xxx.xxx.xxx" voIpProt.server.1.port="0" />
<voIpProt.SIP voIpProt.SIP.enable="1">
<voIpProt.SIP.outboundProxy voIpProt.SIP.outboundProxy.address="xxx.xxx.xxx.xxx" />
<voIpProt.SIP.requestValidation voIpProt.SIP.requestValidation.1.method="source" voIpProt.SIP.requestValidation.1.request="INVITE" />
</voIpProt.SIP>
</voIpProt>

 

The problem is we have some phones that are registered with two phone servers, and I have been unable to figure out a configuration that allows calls to come in through both, but still blocks phantom calls.

 

I have tried:

<voIpProt>
<voIpProt.SIP>
<voIpProt.server voIpProt.server.1.address="xxx.xxx.xxx.xxx" voIpProt.server.1.port="0" />
<voIpProt.server voIpProt.server.2.address="yyy.yyy.yyy.yyy" voIpProt.server.2.port="0" />
<voIpProt.SIP voIpProt.SIP.enable="1">
<voIpProt.SIP.outboundProxy voIpProt.SIP.outboundProxy.address="xxx.xxx.xxx.xxx" />
<voIpProt.SIP.requestValidation voIpProt.SIP.requestValidation.1.method="source" voIpProt.SIP.requestValidation.1.request="INVITE" />
<voIpProt.SIP.requestValidation voIpProt.SIP.requestValidation.2.method="source" voIpProt.SIP.requestValidation.2.request="INVITE" />
</voIpProt.SIP>
</voIpProt>

 

and 

<voIpProt>
<voIpProt.SIP>
<voIpProt.server voIpProt.server.1.address="xxx.xxx.xxx.xxx" voIpProt.server.1.port="0" />
<voIpProt.server voIpProt.server.2.address="yyy.yyy.yyy.yyy" voIpProt.server.2.port="0" />
<voIpProt.SIP voIpProt.SIP.enable="1">
<voIpProt.SIP.requestValidation voIpProt.SIP.requestValidation.1.method="source" voIpProt.SIP.requestValidation.1.request="INVITE" />
<voIpProt.SIP.requestValidation voIpProt.SIP.requestValidation.2.method="source" voIpProt.SIP.requestValidation.2.request="INVITE" />
</voIpProt.SIP>
</voIpProt>

 

But neither work. Calls from server 1 reach the phone properly, but calls from server 2 get this:

[Jan 14 13:24:55] VERBOSE[5825] logger.c:     -- Called <Extension>
[Jan 14 13:24:55] VERBOSE[4754] logger.c:     -- Got SIP response 400 "Bad Request" back from <PHONE IP>
[Jan 14 13:24:55] VERBOSE[5825] logger.c:     -- SIP/<Extension> is circuit-busy
[Jan 14 13:24:55] VERBOSE[5825] logger.c:   == Everyone is busy/congested at this time (1:0/1/0)

 

Anyone know if there's a way to configure it such that calls from two phone servers work while phantom calls are still blocked?

 

Thanks in advance!

 

2 REPLIES 2
HP Recommended

I never had to do this but on the mean time, until you find a solution, change the local SIP port of the phone to something else that 5060. This will fix the issue temporarily until you find a permanent solution. The parameter is "voIpProt.SIP.local.port"

HP Recommended

Try voIpProt.SIP.strictUserValidation="1"

 

That should stop most anonymous calls and require that the INVITE is sent to the specific user in the registration.

example:

your phone is registered as 555@example.com

 

only calls sent to 555@example.com in the request URI will ring.

calls to unregistered lines like anonymous@example.com, 1000@example.com, or example.com will all be dropped

my testing
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.