Solved Unidentified incoming call

[JB-H]

Hello,

We have an on premise 3CX running v20. While perfoming the prerequisites for the update I noticed quite a few registrations in the log like the one below:

Unidentified Incoming Call. Review INVITE and adjust source identification: INVITE sip:810442037696739@**OURIP** SIP/2.0 Via: SIP/2.0/UDP 172.29.18.13:49355;branch=z9hG4bK1517490057;received=94.23.65.226 Max-Forwards: 70 Contact: <sip:[email protected]:49355> To: <sip:810442037696739@**OURIP**> From: <sip:500@**OURIP**>;tag=830079012 Call-ID: 1633750848-1007094813-890129456 CSeq: 1 INVITE Allow: ACK, BYE, CANCEL, INFO, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER, SUBSCRIBE, UPDATE, PUBLISH Content-Type: application/sdp User-Agent: Cisco-SIPGateway Content-Length: 207 v=0 o=500 16264 18299 IN IP4 192.168.1.83 s=call c=IN IP4 192.168.1.83 t=0 0 m=audio 25282 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11



Can somebody explain whats happening? My knowledge of VOIP is just basic.

 

[SOFTISS]

I have seen this a lot also. Maybe, someone will be able to throw more light on this.

 

[JB-H]

Somebody that can give a idea on what's causing this?

 

[bitn2]

Just hacking attempts...

 

[JB-H]

Just hacking attempts...

Thanks for replying. Is there anything specific I should do against this or is this just logging and is the system doing what it's supposed to do?

 

[bitn2]

The system is doing what its supposed to do. But you can restrict your sip port to the network of your provider. That would help here.

 

[JB-H]

The system is doing what its supposed to do. But you can restrict your sip port to the network of your provider. That would help here.

Thanks a bunch, I will look in to the SIP port restriction. Topic resolved.