ASA SIP inspection process is not working ?

[wahidayat007]

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

[drolemc · Accepted solution]

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]

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.