Hi gents,

Got this weird "problem", where CANCEL request is relayed to both the right destination as well as the 255.255.255.255 broadcast address!? I have no such logic in my script, that's for sure.

I doesn't do anything harmful (as far as I can tell), but I'm just curious why it's doing that. Any ideas?

version: kamailio 5.3.4

SIP Trace:

U 2020/05/26 08:40:10.941722 PBXIP:5060 -> KAMAILIO_IP:5060
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
Max-Forwards: 69
From: "some callerid" <sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1@mypbx.mydomain.com
CSeq: 102 CANCEL
User-Agent: B2B
Content-Length: 0

U 2020/05/26 08:40:10.941799 KAMAILIO_IP:5060 -> 255.255.255.255:5060
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
Max-Forwards: 69
From: "some callerid" <sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1@mypbx.mydomain.com
CSeq: 102 CANCEL
User-Agent: B2B
Content-Length: 0

T 2020/05/26 08:40:10.941899 KAMAILIO_IP:5061 -> DOWNSTREAM_IP:10533
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/TLS proxy.mydomain.com:5061;branch=z9hG4bK3cbb.4c6a526982fa1fb93ca1ba73afd8484f.0
Max-Forwards: 69
From: "some callerid" <sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1@mypbx.mydomain.com
CSeq: 102 CANCEL
Content-Length: 0

U 2020/05/26 08:40:10.941935 KAMAILIO_IP:5060 -> PBXIP:5060
SIP/2.0 200 canceling
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
From: "some callerid" <sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-612a1516
Call-ID: 1511475b69f6379b08f04d110f534da1@mypbx.mydomain.com
CSeq: 102 CANCEL
Server: Edge
Content-Length: 0 

Thanks,
--Sergiu