03-27-2012 04:49 PM - edited 03-17-2019 10:58 PM
Mar 27 16:49:27 | tvcs: Event="Response Sent" Service="SIP" Src-ip="my ip address" Src-port="5060" Dst-ip="95.211.169.4" Dst-port="5062" Protocol="UDP" Method="OPTIONS" To="sip:100@1.1.1.1" Response-code="482" Level="3" UTCTime="2012-03-27 21:49:27,038" |
Mar 27 16:49:27 | tvcs: Event="Search Loop Detected" Service="SIP" Src-alias-type="SIP" Src-alias="100@1.1.1.1" Dst-alias-type="SIP" Dst-alias="sip:100@1.1.1.1" Call-serial-number="b95c3454-7856-11e1-906c-0010f320f8b6" Tag="b95c353a-7856-11e1-898b-0010f320f8b6" Level="2" UTCTime="2012-03-27 21:49:27,037" |
Saw this in the event log of our VCS. Seems as if someone is querying the VCS with fake identity. What do you think?
Solved! Go to Solution.
03-29-2012 03:06 AM
Thats exactly what it is. You can setup a call policy though to deny this.
03-29-2012 05:03 AM
Its two things,
* there are ways to use a CPL to block these kind of calls we discussed that earlier, like in:
https://supportforums.cisco.com/message/3401571#3400843
* but if he has a call loop it might be interesting if he has some search/transform rules coursing that.
I could assume its most likely towards his traveral zone or the dns zone.
Its interesting to look in the search history of that call or a signaling trace to see what's causing the loop.
Regards DNS loops you find some info here:
https://supportforums.cisco.com/message/3562638#3561491
Please rate the answers with the stars below the message!
Please remember to rate helpful responses and identify
03-29-2012 03:06 AM
Thats exactly what it is. You can setup a call policy though to deny this.
03-29-2012 05:03 AM
Its two things,
* there are ways to use a CPL to block these kind of calls we discussed that earlier, like in:
https://supportforums.cisco.com/message/3401571#3400843
* but if he has a call loop it might be interesting if he has some search/transform rules coursing that.
I could assume its most likely towards his traveral zone or the dns zone.
Its interesting to look in the search history of that call or a signaling trace to see what's causing the loop.
Regards DNS loops you find some info here:
https://supportforums.cisco.com/message/3562638#3561491
Please rate the answers with the stars below the message!
Please remember to rate helpful responses and identify
03-29-2012 08:58 AM
Thanks for the input Martin and Matt!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide