Asterisk Console logging "Request 'OPTIONS'..." each 1 minute


#1

I don’t know why my server is logging the messages bellow exactly each 1 minute, the IP of origin is one extension connected with another Asterisk server.

I am using Asterisk 13 with PJSIP.

[Nov 28 11:15:29] NOTICE[14260]: res_pjsip/pjsip_distributor.c:649 log_failed_request: Request ‘OPTIONS’ from ‘“asterisk” sip:asterisk@192.168.0.3’ failed for ‘xxx.xxx.xxx.xxx:5060’ (callid: 57925f7b5695e5cc7d7e71b86a15eae8@192.168.0.3:5060) - No matching endpoint found
[Nov 28 11:16:29] NOTICE[20572]: res_pjsip/pjsip_distributor.c:649 log_failed_request: Request ‘OPTIONS’ from ‘“asterisk” sip:asterisk@192.168.0.3’ failed for ‘xxx.xxx.xxx.xxx:5060’ (callid: 0f5b5f065514e9de2476ddea039bf79d@192.168.0.3:5060) - No matching endpoint found
[Nov 28 11:17:29] NOTICE[16061]: res_pjsip/pjsip_distributor.c:649 log_failed_request: Request ‘OPTIONS’ from ‘“asterisk” sip:asterisk@192.168.0.3’ failed for ‘xxx.xxx.xxx.xxx:5060’ (callid: 27e0796544868ee70b69581c22a96e35@192.168.0.3:5060) - No matching endpoint found

The Asterisk server connected is with qualify parameter actived (yes) I suspected that be it that causes this messages, if yes is it possible doesn’t show that in the console log?


#2

Server is often misused and I can’t work out how you are using it here.

The system that sends OPTIONS is the client. That is the only system on which qualify has any effect. If you are really talking about a server, it appears that it has a peer that it doesn’t know about, and the correct solution is either to stop that peer trying to access it, at the remote end, or tell it how to recognize that peer.


#3

The qualify was used in the Asterisk client, and theses logs are showing in the Asterisk server.

The answer is that this log was not caused by the qualify=yes?


#4

It is caused by the equivalent of qualify=yes on a client that isn’t actually a client of the server. qualify has no effect on the server.


#5

It’s too weird because in the client log files didn’t have none ‘asterisk’ user and the time of the retry is exactly 1 minute.