If there are multiple versions, start with the oldest ones first. If there are corresponding versions of ASA and ASDM on there, update the config to use them - this will allow you to access ASDM and you can upgrade via that if necessary. If you don't have the files you expect in place, look at what is there. NB - you will see more files listed than this! You may see multiple version of the ASA and ASDM files, which is ok, but can cause problems if the config isn't quite right or a file is corrupt. Now you need to check what files are actually on the ASA: ASA# sh disk These should all match what is in your config, but if they don't then you would see problems as the loaded versions of ASA and ASDM have to match. This shows that the ASA is configured to use compatible versions of the ASA and ASDM images.Ĭheck which versions have loaded: ASA# sh bootvarĬurrent BOOT variable = disk0:/asa832-k8.binĭevice Manager image file, disk0:/asdm-633.bin Get to command line on your ASA and run the following commands and check they look similar to the following: ASA# sh run boot This would make sense if the ASA won't start the SIP inspection due to the different port 5080.Īnd if that is so, can I configure somewhere which SIP port the ASA should look for? Or is there any workaround? (I can probably open all inbound RTP ports. (Outbound calls are no problem, all fine with 2-way audio - but they are sent with destination port 5060). The RTP does not flow from external to internal. Inbound Calls do connect, but then I have one-way audio. Traffic between IP PBX and ITSP goes via an ASA 5505 firewall (that's the older generation). The IP PBX I am using is a SIP proxy with a built-in SBC and it demands that inbound traffic shall be sent to port 5080. The referenced document below states so (this doc is specifically for the newer generation 5500-x series).Īnd I have trouble to get audio working when my IP PBX is configured to receive inbound calls on another port than 5060. Is it correct that the SIP inspection in the ASA 5500 firewalls only kicks in for traffic on port 5060?

Cisco asa 5505