"realm" is required.

Since the device is registered in the SIP Server, so you can disable the Auth for INVITE with the following DialPlan rule.

[Matching Patterns]
$request = ^INVITE
$registeredSender = true

[Deploy Patterns]
$auth = false
$continue = true

Does Authorization: header have "realm" ?

Are you sure you uploaded the valid certificate file?
Compare signature of the certificate.

Use a comma as a separator.

Contact = sip:%1@10.10.10.200,sip:%1@10.10.10.300,sip:%1@10.10.10.400

> but what I heard was "if Qualys's scan is a problem, bypass Qualys's scan." Right. If all of SIP clients which access to your SIP Server support INVITE/REGISTER authentication, simply remove $auth=false from all DialPlan rules. > Would it be safer to say perhaps that if an invite comes from a ...

> each individual rule having $auth=false in the deploy pattern. It is the issue... you should not put $auth=false in the DialPlan rule which matches the Qualys's INVITE. or... add another new DialPlan rule which matches only an INVITE sent from the Qualys. You can check the remote IP address or ...

Have you set REGISTER and INVITE Authentication in [Configuration]->[SIP] page??

Yes. It is the variable $auth.
so let you set $auth=false in the DeployPattern of the rule.
If so, the SIP Server doesn't require an INVITE to send an authentication.

FYI:
https://docs.brekeke.com/sip/auth

To enable both proxy and register authorizations, set the following settings at [Configuration]->[SIP] page -> [Authentication]. REGISTER = on INVITE = on They are On in the default but it seems you set "Off" for INVITE. The B2B-UA mode is not related . Anyway let you change INVITE Authentication to ...

If you still have the issue with the alphanumeric username, set "no" for the following settings in the [Configuration]->[SIP] page. With these settings, the SIP Server doesn't check whether the Auth name is same as SIP username. [Auth-user=user in "To:" (Register) ] = no [Auth-user=user in "From ...

> Any ideas as to why $registeredSender worked at first and then started to fail, It seems that 3CX changes a source port number after while. The $registeredSender method checks whether both remote IP address and port number are same as the latest accepted REGISTER request. Is the 3CX located behind ...

Can you find the record like "customer4171112222001" in the [Registered Clients] page after the SIP Server sends SIP 603?

If yes.. the SIP Server didn't receive subsequent REGISTER packets from the 3CX.

Are you using Auth for REGISTER too?

> $registered("4171112222001") = true > $addr = ^11.22.33.44$ The above rule will match even if a REGISTER was not sent from 11.22.33.44. If you want to accept an INVITE sent from the same remote IP address of REGISTER, let you rewrite Matching Patterns like the following. [Matching Patterns ...

I think there are several ways to avoid the issue without having many DialPlan rules.

Let you contact Brekeke's support to report the issue.

This is because the SIP Server re-selects a destination side interface IP address. If you use some tricks, you can avoid the issue. Rule-1: ==================== [Matching Patterns] $request = ^INVITE $localhost = ^false $addr = 192.168.10.10$ To = sip:123456(.+)@ From = sip:(.+)@ [Deploy Patterns ...

Have you switched these Auth-user settings to "no"?

Check the [Logs]->[Error Logs] if the problem still happens.

Are both SIP username and auth username same?

In your example, is 4171112222001 a SIP username?

Let you set "no" at [Auth-user=user in "To:" (Register) ] and [Auth-user=user in "From:"] in Configuration->SIP page.

I tried the both Matching Pattern and Deploy Patten without any issues...

Check the log to see whether the rule is executed..

My first rule will meet the requirement because sip:99(16.+)@ will pick any 16xxxxx values if it starts with 99.

%1 in Deploy Patterns refers the first () in the Matching Patterns.

so the rule matches from "16000" to "16999" if these Yealink phones are registered.

If a caller dials 9916998, do you want to route a call to 16998 which is Yealink's registered username? If so, try the DialPlan I suggested in my previous post. Or do you want to route any matched calls to the certain Yealink phone always? If so, try the DialPlan rule below. [Matching Patterns ...

Is "99" a prefix of the dialed number? If you have ( ) in the Matching pattern, you can refer the matched value with %1 in the Deploy Pattern For example: [Matching Pattern] $request=^INVITE To = sip:99(16.+)@ [Deploy Pattern] To = sip:%1@ sip:%1@ in Deploy Pattern means that SIP Server routes a ...

There are several ways.
Can you paste your Matching Pattern here?

Have you tuned &failover.timer.inviting and &failover.timer.provisional?

Other options are... D. using own plugin written by Java. E. using SIP Redirect Server Do you host a database on your premises? If so, easiest way will be method B. "using the $db.query method". However, $db.query doesn't cache a result, so the method D "using own plugin" will be a most flexible ...

At Brekeke SIP Server, disable REGISTER Authentication at [Configuration]->[SIP] page, and make sure the [Thru Registration] is "On". (For applying changes, you need to restart the SIP Server). At the SIP client, set the following. [Outbound Proxy] = Brekeke SIP Server's IP address [Registrar (or ...