5

Is it correct that the SIP inspection in the ASA 5500 firewalls only kicks in for traffic on port 5060? The referenced document below states so (this doc is specifically for the newer generation 5500-x series). And I have trouble to get audio working when my IP PBX is configured to receive inbound calls on another port than 5060. 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. Traffic between IP PBX and ITSP goes via an ASA 5505 firewall (that's the older generation).

Inbound Calls do connect, but then I have one-way audio. The RTP does not flow from external to internal. (Outbound calls are no problem, all fine with 2-way audio - but they are sent with destination port 5060). This would make sense if the ASA won't start the SIP inspection due to the different port 5080.

But is that really the case? And 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 ... but I would like to avoid that)

Cisco documentation ASA 5500

  • Did any answer help you? if so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could provide and accept your own answer. – Ron Maupin Aug 10 '17 at 15:16
2

Seems that the trick is like that (credit to Alex over at serverfault.com):

First go in your configuration terminal and create the class-map;

asa(config)# class-map SIP_5080
asa(config-cmap)# match port tcp eq 5080
asa(config-cmap)# exit

Then create a policy-map;

asa(config)# policy-map SIP_Policy
asa(config-pmap)# class SIP_5080
asa(config-pmap-c)# inspect sip
asa(config-pmap-c)# exit

Finally, assign the policy-map to an interface; asa(config)# service-policy SIP_Policy interface [name of your interface]

-1

The well-known port 5060 must be used on the initial call setup ...

[Configuring Inspection of Voice and Video Protocols]

  • Actually it is more complex than that - the ITSP sends inbound calls dutifully on port 5060. The ASA uses static NAT with port translation to translate it to port 5080. Per Cisco docs on ASA packet flow, any inspection occurs BEFORE the IP header rewrite, so theoretically the "inspect sip" should see port 5060 - isn't that correct? – nepdev Sep 5 '14 at 12:49
  • I was merely pointing out you cannot change the port on which SIP inspection works. Yes, NAT Order of Operations suggests inspection should happen pre-rewrite, in the inbound direction at least where it's 5060. – Ricky Beam Sep 5 '14 at 15:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.