Forum Discussion
Log SIp info in UDP payload with scan
Hi!
I am trying to analyse SIP UDP messages and log some info elements from them. For example:
- From:
- To:To:.
- Call-ID: Call-ID:.1d4635275f628cb07fbac8d3d77b4187@83.174.6.108
getting this info from traffic like the attached at the bottom (it is a tcpdumped fragment of a typical SIP packet).
The irule I am using is:
when CLIENT_DATA {
scan [UDP::payload] "%*s From:=%s , To:=%s , Call-ID:=%s" Client Dest Call-ID
log local0.info "Client: $Client, Destination: $Dest, Call-ID: $Call-ID"
}
but I get:
Nov 28 18:05:03 tmm tmm[1080]: 01220001:3: TCL error: Rule SIP-log - can't read "Client": no such variable while executing "log local0. "Client: $Client, Destination: $Dest, Call-ID: $Call-ID""
Can you help to find the mistake?
Thanks a lot!!!!
AC
0x00f0 32352d33310d0a46726f6d3a203c7369 25-31..From:.0x0100 703a42324255414038332e3137342e36 p:B2BUA@83.174.6
0x0110 2e3130383a353036303e3b7461673d34 .108:5060>;tag=4
0x0120 316431663836340d0a546f3a203c7369 1d1f864..To:.0x0130 703a3931313637383632363430403231 p:91167862640@21
0x0140 332e33302e39322e3130353e3b746167 3.30.92.105>;tag
0x0150 3d376465626131613737626630303738 =7deba1a77bf0078
0x0160 61636437363762383634643437333261 acd767b864d4732a
0x0170 340d0a43616c6c2d49443a2031643436 4..Call-ID:.1d46
0x0180 33353237356636323863623037666261 35275f628cb07fba
0x0190 6338643364373762343138374038332e c8d3d77b4187@83.
0x01a0 3137342e362e3130380d0a435365713a 174.6.108..CSeq:
- It looks like you have some variables in your log statement that don't ever get set in the iRule. Make sure that the variables you're using to log are the same as the ones you're setting earlier in the rule.
Colin
