SIP traffic is identified as unknown-udp
5272
Created On 04/29/21 13:37 PM - Last Modified 07/03/25 04:42 AM
Symptom
- Fax calls were failing when SIP traffic was being identified as unknown-udp.
- Session information shows the sip traffic as unknown-udp
admin@Lab92-38-PA-VM> show session all
--------------------------------------------------------------------------------
ID Application State Type Flag Src[Sport]/Zone/Proto (translated IP[Port])
Vsys Dst[Dport]/Zone (translated IP[Port])
--------------------------------------------------------------------------------
6299 unknown-udp ACTIVE FLOW 172.16.100.10[5060]/vwire/17 (172.16.100.10[5060])
vsys1 192.168.100.50[5060]/vwire (192.168.100.50[5060])
admin@Lab92-38-PA-VM> show session id 6299
Session 6299
c2s flow:
source: 172.16.100.10 [vwire]
dst: 192.168.100.50
proto: 17
sport: 5060 dport: 5060
state: ACTIVE type: FLOW
src user: unknown
dst user: unknown
s2c flow:
source: 192.168.100.50 [vwire]
dst: 172.16.100.10
proto: 17
sport: 5060 dport: 5060
state: ACTIVE type: FLOW
src user: unknown
dst user: unknown
- Global counters confirmed that App-ID was recognizing the SIP traffic as unknown-udp
admin@Lab92-38-PA-VM> show counter global filter packet-filter yes delta yes appid_proc 1 0 info appid pktproc The number of packets processed by Application identification appid_unknown_udp 1 0 info appid pktproc The number of unknown UDP applications after app engine
Environment
- PAN-OS 9.1.7
- Fax Calls
- App-version 8397-6642
Cause
SIP traffic was being misidentified because the AppID function could not identify SIP PRACK messages as being SIP packets.
Resolution
Update to Applications and Threats content version 8410-6722 or higher.