Invalid SIP message - rejected, no callid

Hi,

I just recently upgraded our 1.2 server to 1.4.23.1, and I’m going through the logs and I’m seeing this message a lot and not sure what it means. Hoping that someone here can shed some light on the problem, if there’s a problem at all.

[Feb 3 16:04:08] DEBUG[9932] chan_sip.c: Invalid SIP message - rejected , no callid, len 628
[Feb 3 16:04:20] DEBUG[9932] chan_sip.c: Invalid SIP message - rejected , no callid, len 513

And I am getting these messages as well:
[Feb 3 16:04:40] DEBUG[9932] chan_sip.c: = No match Their Call ID: 0018180e-4dcf000f-5b3fc623-711cceed@192.168.1.13 Their Tag 0018180e4dcf010c499a5a33-100db3d2 Our tag: as22882160
[Feb 3 16:04:40] DEBUG[9932] chan_sip.c: = No match Their Call ID: 0017e0f0-af43000d-02241cea-7370d571@192.168.1.12 Their Tag 0017e0f0af43010422d9e686-201279c6 Our tag: as144c020a

As far as I can tell, everything is working out ok so far. I’m just wondering why we are getting these messages.

Thanks,
Herb

On the surface, the first one indicates that the other side is violating the SIP protocol, and the second, that you are getting messages relating to a SIP call that you don’t think exists.