I am having a hard time getting VoIP to work. I have a PBX using an IP trunk that is accessed over NAT.
I did port forwarding on UDP 5060 to my internal address. I can make calles but no audio. Whay is happening is that the RTP streams are assigned dynamically when the call is created. i can see the NAT translations outgoing but i don't think it is coming back in.
I tried doing
ip inspect name Incoming sip
ip inspect name Incoming tcp router-traffic
ip inspect name Incoming udp router-traffic
ip inspect name Incoming icmp router-traffic
and bounded it to my interface by:
ip inspect Incoming out
Still no audio but i can initiate out and also receive calls but can't talk to anyone :-(
I am having a NAT issue hard to resolve (at least I am still trying to figuring out).
The most likely problem with no way audio is the inability of the phone or gateway to route IP Packets to the other device. Check this out and if everything looks ok then please provide Detailed CCM traces of a problem call. If a gateway is involved please provide a show version and show run from the gateway.
I have SIP working with my 877, however I have outbound inspection of SIP enabled as well as inbound:
ip inspect name Outbound sip
ip inspect name Inbound sip
ip inspect Inbound in
ip inspect Outbound out
Obviously there is more to the inspection rules however these are the relevent bits. Have you tried debugging? When I initially set this up I was debugging it and found the inbound traffic being denied as there was no knowledge of the SIP call without the outbound SIP inspection.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.