cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1364
Views
0
Helpful
2
Replies

ASA SIP inspection process is not working ?

wahidayat007
Level 1
Level 1

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

drolemc
Level 6
Level 6

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

View solution in original post

2 Replies 2

drolemc
Level 6
Level 6

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

lusandi
Level 1
Level 1

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.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: