Warning 30051 Unidentified Incoming Call. Review INVITE and adjust source identification

[Kristoffel_Loos]

Hi,

Since we are running on V20 we notice allot of Warnings with EventID30051.
We don't have a forward from an external number to one of our DID's like I've read in a older post.

FOR EXAMPLE:

Unidentified Incoming Call. Review INVITE and adjust source identification: INVITE sip:[email protected]:5060;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---973163815;rport=5080 Via: SIP/2.0/UDP OUR-STATIC-WAN-IP-OFFICE:39593;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=sbc.c09c985a Via: SIP/2.0/UDP OUR-STATIC-WAN-IP-OFFICE:62968;branch=z9hG4bK973163815 Max-Forwards: 68 Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.c09c985a> Record-Route: <sip:[email protected]:5060;user=proxy;tnlid=sbc.c09c985a> Contact: <sip:joni@OUR-STATIC-WAN-IP:62968> To: <sip:280016164005032@OUR-FQDN:5060> From: <sip:joni@OUR-FQDN:5060>;tag=1041084421 Call-ID: 65486881-776147677-1445414268 CSeq: 1 INVITE Allow: ACK, BYE, CANCEL, INFO, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER, SUBSCRIBE, UPDATE, PUBLISH Content-Type: application/sdp Content-Length: 212 v=0 o=joni 16264 18299 IN IP4 OUR-STATIC-WAN-IP-OFFICE s=call c=IN IP4 OUR-STATIC-WAN-IP-OFFICE t=0 0 m=audio 29778 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

The contact en From are always users that don't make any sence, that never existed on our system: sip:joni@OUR-STATIC-WAN-IP:62968

What is the cause, how to fix?

I also look into this with the 3CX Log Reader:



User-Agent: Avaya one-X Deskphone
Content-Length: 0

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

Level = 2
Severity = Warning
Tread = 11

We only have Snom Devices in our network!

Best regards,
Kristof

 

[bitn2]

You can restrict your sip port on your firewall to your sip company, thats the only way. This are users from external who trying to login to your pbx / make calls. That is normal if your sip port isnt restricted.

 

[Kristoffel_Loos]

@bitn2 Our 3CX V20 was deployed on Microsoft Azure using the Market place image.

We configured everything like was explained on the 3CX website:

 

[bitn2]

Sure... but did you have a firewall in front? If yes, you need to restrict 5060 to your sip provider or just ignore the messages.