Strange Messages after Update to 15.5 SP2

[narkumas]

11/21/2017 10:52:44 AM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
11/21/2017 10:52:44 AM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
11/21/2017 10:52:44 AM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
11/21/2017 10:52:20 AM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
11/21/2017 10:52:15 AM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
11/21/2017 10:52:15 AM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
11/21/2017 10:52:15 AM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393

 

[StefanW]

better ;-)

something (a sip endpoint) is sending the PBX a message which does not contain the SIP Contact Header or it is inclomplete. This is mandatory. Which SIP endpoints or provider do you use? Any other then defined in our supported list?

 

[narkumas]

Well, we have 1 or 2 Cisco SPA112... The rest is supported.
And this started happening after SP2 Upgrade...
Our Provider is QSC

 

[narkumas]

How can I identify which SIP endpoint is causing this?

 

[StefanW]

wireshark would be the simplest, QSC is not doing it for sure...

 

[narkumas]

should I send you a pcap dump?

 

[YiannisH_3CX]

Please send me a p.m. with a capture. We might also need to see the phones systems support info in verbose but lets start with the capture.
Please update the file to a web sharing service and send me the download link in a p.m.

 

[KOG]

I have the same issue after the update.

12/20/2017 3:27:59 PM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
12/20/2017 3:26:59 PM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
12/20/2017 3:25:59 PM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
12/20/2017 3:24:59 PM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
12/20/2017 3:23:59 PM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
12/20/2017 3:22:59 PM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
12/20/2017 3:21:59 PM - Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393

 

[Mark Tonino]

Same here...

 

[DrewHammond]

We are seeing this as well

 

[loyer]

Was this ever resolved? I am getting this now and not sure how to fix. Thank you for any info.

 

[YiannisH_3CX]

Please note that this is not an issue of the PBX. As mentioned above you are seeing this because an endpoint is trying to register to the PBX using an incorrect header. If you need assistance i will be happy to take a look if you provide me with the files mentioned above in a p.m.

 

[loyer]

Hi Yiannis,

I am using Yealink T48S phones. The phones were initially provisioned via Direct SIP / STUN and then recently switched to SBC. Another user said that the MAC address might be hardcoded for 14 days. Do you think this would cause this issue? My phones are on the latest supported firmware and were provisioned using the 3CX system (currently 15.5SP3).

Thank you

 

[YiannisH_3CX]

I do not think the messages you are receiving are related to that. These are probably register messages towards the PBX that are not correctly formatted.

 

[Robert Cook]

Greetings,
I too am having this issue:
Exception: SipMessage::Exception Missing header Contact @ SipMessage.cxx:1393
I'll PM you YiannisH my information.
Thank you,
Robert Cook

 

[Mischa Sz.]

Hi!

Same issue here. I cannot dial numbers through the web client anymore. Using a Yealink T48S connected through an SBC (Linux). 3CX version 15.5 Professional.

Regards
Mischa

 

[YiannisH_3CX]

Same issue here. I cannot dial numbers through the web client anymore. Using a Yealink T48S connected through an SBC (Linux). 3CX version 15.5 Professional.

Do you have Snom phones as well by any chance? In order to troubleshoot your issue we will need the PBX logs in verbose logging level and a wireshark capture from the PBX at the time of the issue. Please send me a p.m. with the requested files or for details on how to collect these files.

 

[Mischa Sz.]

After restarting all 3CX services, the issue has gone. Best regards, Mischa