VCSc returning 404:Not Found without running a search for the endpoint

ben.english · ‎04-11-2013

Hi,

At a high level, I'm having an issue where the VCSc is returning a 404:Not Found message when a SIP call is placed to an endpoint registered to the Default SubZone of that VCSc. The calling endpoint is registered to a VCSe with a Neighbor Zone setup to the VCSc. I have also tried calling the same endpoint from another endpoint which is registered locally to the VCSc, which works.

The setup is this.

Calling EP -> VCSe -> Neighbor Zone -> Acme SBC with NAT -> VCSc -> Called EP

The strange this is that the VCSc is not even searching for the endpoint.

Network Log:

Apr 11 09:32:06 tvcs: UTCTime="2013-04-11 09:32:06,933" Module="network.sip" Level="INFO": Dst-ip="192.168.2.1" Dst-port="34558" Detail="Sending Response Code=404, Method=INVITE, To=sip:4321@domain.com, Call-ID=7e0920-e191fac-13c4-45026-5166832c-49c5a6b1-5166832c"

Apr 11 09:32:06 tvcs: UTCTime="2013-04-11 09:32:06,928" Module="network.sip" Level="INFO": Src-ip="192.168.2.1" Src-port="34558" Detail="Receive Request Method=INVITE, Request-URI=sip:4321@domain.com, Call-ID=7e0920-e191fac-13c4-45026-5166832c-49c5a6b1-5166832c"

Event Log:

Apr 11 10:08:41 tvcs: Event="Search Completed" Service="SIP" Src-alias-type="SIP" Src-alias="CallingEndpoint@<public IP>" Dst-alias-type="SIP" Dst-alias="sip:4321@domain.com" Call-serial-number="c9198b12-a28f-11e2-8c71-0010f3159674" Tag="d62c0640-a28f-11e2-b65b-0010f3274bc8" Detail="found:FALSE, searchtype:INVITE" Level="1" UTCTime="2013-04-11 10:08:41,247"

Apr 11 10:08:41 tvcs: Event="Call Attempted" Service="SIP" Src-ip="192.168.2.1" Src-port="5060" Src-alias-type="SIP" Src-alias="sip:CallingEndpoint@<PublicIP>;transport\=TCP" Dst-alias-type="SIP" Dst-alias="sip:4321@domain.com" Call-serial-number="c9198b12-a28f-11e2-8c71-0010f3159674" Tag="d62c0640-a28f-11e2-b65b-0010f3274bc8" Protocol="TCP" Auth="YES" Level="1" UTCTime="2013-04-11 10:08:41,247"

Apr 11 10:08:41 tvcs: Event="Search Attempted" Service="SIP" Src-alias-type="SIP" Src-alias="CallingEndpoint@<PublicIP>" Dst-alias-type="SIP" Dst-alias="sip:4321@domain.com" Call-serial-number="c9198b12-a28f-11e2-8c71-0010f3159674" Tag="d62c0640-a28f-11e2-b65b-0010f3274bc8" Detail="searchtype:INVITE" Level="1" UTCTime="2013-04-11 10:08:41,247"

Any help would be appreciated.

Thanks.

Martin Koch · ‎04-11-2013

Hello Ben!

To be honest that would not be the deployment I would go for, connecting the VCS-C to a VCS-E via

a 3rd party SBC might bring in additional problems and can cause strange symptoms if the SBC is

doing some magick which it better should not do.

Especially handling the media or things like BFCP can be a bit trickey in that scenario.

Whats the reason for this kind of deployment?

Could you share a more information, like which VCS versions you use, how your zone settings and search rules look like?

It can be that your search rule simply is not hit, like you have a specific zone or protocol set up, ..

But anyhow, consider using a traversal zone, thats the better way to handle that setup!

Please remember to rate helpful responses and identify

ben.english · ‎04-11-2013

Hi Martin,

I wouldn't usually be using a VCSe through the SBC to VCSc, I'd be using VCSc through SBC to VCSc (neighboring). But at this stage all I have to play with is a VCSe. So I've neighbored the VCSe to VCSc.

The reason why I'm using an Acme Packet SBC is that I will have multiple VCSc trunking to our VCSc with overlapping subnets, and I need a SBC that is VLAN aware.

I have VCSc version x7.0.1 and VCSe version x7.2.1

The only zone I have setup is the Default SubZone, and the search rule is set to Source=Any. Also I've tried using the Locate Tool which finds the SIP URI with no issue.

ahmashar · ‎04-11-2013

Hi,

first thing you need to do to upgrade VCSc to x7.2.1 to be the same version as VCSe.

secondly, with even neighbor zone between VCSc and VCSe with ACM in between, that's asking for trouble.

Check the logs in ACM, what is getting through and what is not. my guess is ACM breaking the SIP communication between VCSc and VCSe.

ben.english · ‎04-12-2013

Hi,

I've taken the VCSe out of the mix and just registered an endpoint to VCSc through the Acme SBC and am getting the same issue. I'm almost certain it's the SBC causing the issue but the SIP headers coming through look ok.

I guess if someone can answer this question it would be very helpful. Keeping in mind that I have a search rule which is set to Source=Any.

What would cause a VCSc to not run the search rules and return a 404 message? Maybe something in the SIP header?

Thanks.

ahmashar · ‎04-12-2013

one reason for search rules not getting executed would be a CPL script for some authentication purpose and if incoming inquiries are not authenticated (do not match the criteria specified there), then the SIP/H323 inquiry would be terminated. have you checked the "search history" page and are you sure the search rule are skipped?

404 error could have different reasons for example; endpoint registered at some zone that there is not search rule to that zone (there is no AOR for that endpoint) or the server does not have information about the dialed domain of endpoint or etc.