cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3182
Views
0
Helpful
3
Replies

VCS-E search loop detected...

Mar 27 16:49:27tvcs: 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?

2 Accepted Solutions

Accepted Solutions

mattjenkins
Level 1
Level 1

Thats exactly what it is. You can setup a call policy though to deny this.

View solution in original post

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

View solution in original post

3 Replies 3

mattjenkins
Level 1
Level 1

Thats exactly what it is. You can setup a call policy though to deny this.

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

Thanks for the input Martin and Matt!