200 OK Response logging as errorr

JTBell · Post by **JTBell** » Tue May 16, 2023 5:45 am

1. Brekeke Product Name and Version: Brekeke SIP

2. Java version:11

3. OS type and the version: Server 2019

4. UA (phone), gateway or other hardware/software involved: CUCM

5. Your problem: I have rule setup to respond with 200 when an Options message comes in, to monitor the health of the SIP trunk to CUCM. All of these responses are logging as an Error. I have not seen this before, can I get these to stop logging as an error?

Rule Name: Options Ping
MP: $Request = ^OPTIONS
DP: $Response = 200

Error Example:

2023-05-16 00:00:01.126 xx.xxx.xxx.17:44357 OPTIONS 200 $response=200 sip:xx.xxx.xxx.201:5060 sip:xx.xxx.xxx.17 sip:xx.xxx.xxx.201 Options Ping Cisco-CUCM11.5

.17 is CUCM
.201 is Brekeke

Tata · Post by **Tata** » Wed May 17, 2023 8:10 pm

It is logged in Error Log because $response is usually used for sending an error response code.

Because the SIP Server sends "200 OK" to OPTIONS, it meets the requirement.

So you don't have to worry about it.