Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

ASA SIP inspection process is not working ?

Hi I have an issue with Cisco ASA 5520, The summary is below!

Packet # 1 on inside capture the Call-ID was: Call-ID: 2a54f680-

a5d1de2a-160c-164070a@10.7.100.1

Packet # 1 on outside interface the Call-ID was: Call-ID: 2a54f680-

a5d1de2a-160c-164070a@149.5.33.44 --- this bcz of the inspection.

Packet # 2 on outside capture the Call-ID was: Call-ID: 2a54f680-

a5d1de2a-160c-164070a@149.5.33.44

Packet # 2 on inside capture the Call-ID stay: Call-ID: 2a54f680-

a5d1de2a-160c-164070a@149.5.33.44 --- this is the problem.

(This suppose to be Call-ID: 2a54f680-a5d1de2a-160c-164070a@10.7.100.1)

The inspection should change the Call-ID for the incoming packet as it

did with the outgoing packet. Whenever, the CM receive the trying

message with different Call-ID it considered as new session and it keep

sending invitation messages for the SIP provider.

NAT is enabled.

How to fix the above problem ?

Any help will be appreciated.

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Silver

Re: ASA SIP inspection process is not working ?

Verify any Xlate entries on SIP server. You might also want to include inspect SIP in your global policy. There are also lots of bugs in 8.0(3) regarding SIP handling

2 REPLIES
Silver

Re: ASA SIP inspection process is not working ?

Verify any Xlate entries on SIP server. You might also want to include inspect SIP in your global policy. There are also lots of bugs in 8.0(3) regarding SIP handling

Bronze

Re: ASA SIP inspection process is not working ?

Can you post the ASA configuration?

Regards,

Luis Sandi

.:|:.:|:.

P.S Please mark this question as answered if it has been resolved. Do rate helpful posts.

923
Views
0
Helpful
2
Replies