AP 3820 Can't Process Certain Calls

Asset ID:	1-72-2045459.1
Update Date:	2018-01-04
Keywords:

Solution Type Problem Resolution Sure

Solution 2045459.1 : AP 3820 Can't Process Certain Calls

Applies to:

Acme Packet 3820 - Version S-Cx6.3.x to S-Cx6.4.x [Release S-Cx6.0]
Information in this document applies to any platform.

Symptoms

We encountered an issue with our production AP3820 HA nodes is having trouble processing call from certain source IP.
Here is a scenario of our setup.

We setup 2 endpoints pointed to the same SIP interface: 172.17.64.3 in our production AP3820
When the call is made from one EndPoint (192.168.50.237), the call gets through and process properly.
However, call failed when the call is made from another source(172.31.244.210).

What we could not figure out is why does ACME return a 404 Not Found SIP response to the same exact, SIP request URI sent to it.
And the only distinction we see between the two separate INVITE is the source IP and FROM-Header.

Cause

record-route is added in INVITE, then SBC use that information to detect next route.
and in that case, SBC can't check DNS info about "acmelabISP-cctr-cctr-06:".

Aug 18 02:11:51.459 [SIP] Sipd_do_dns_query: DNS error, not sent; sts=404
Aug 18 02:11:51.459 [SIP] INVITE 1 check_top_route: DNS error; sts=404; cannot resolve:
Aug 18 02:11:51.459 [SIP] <sip:61731884023@acmelabISP-cctr-cctr-06:5060;user=phone;lr>
Aug 18 02:11:51.459 [SIP] INVITE 1 process-req: CONT

Solution

strip out the route Header and it works like charm!

References

<NOTE:166650.1> - Working Effectively With Oracle Support - Best Practices

Attachments

This solution has no attachment