I am testing VoIP termination with a telco in the following scenario:
Our test CCM (CCM 3.3(3)SR4) using H225 trunk registered in IOS gatekeeper (Cisco 2610) through a PIX firewall (CCM in inside, gatekeeper in outside). Telco termination gateway (AS5350) also registered in the gatekeeper. AS5350 configured to use dial-peer ras.
The CCM is behind a PIX (6.3(4) but also tried with 7.0(2).
I am using static IP NAT for both
the CCM and one test IP phone in the firewall, as I experienced problems if using static PAT for H323 and Cisco recommends not using static PAT for H323. All fixups for H323 activated in PIX.
Outgoing calls from CCM to PSTN work fine via gatekeeper->AS5350.
Incoming calls from PSTN to the CCM via AS5350 and gatekeeper: I get one-way audio (I only achieved correct call setup activating H323 Fast Start Inbound in CCM 3.3)
We discovered the AS5350 is seeing
the phone private IP address for the RTP flow, and that´s why I get one-way audio
for incoming calls.
The weird thing is that if we don´t use the gatekeeper, but pointing instead incoming calls directly from AS5350 -> PIX -> CCM,
incoming calls work fine!
I guess the fixup should work fine in either scenarios and show the phone public IP address, but I have problems
To verify that the RTP packet flows through the network, perform these steps...
Check to see if the IP phone is sending and receiving packets to and from its default gateway.
Press the I button twice on a Cisco 7900 series IP phone and check if the RxCnt and TxCnt statistics are incrementing.
If the IP phone is not sending RTP packets, it may not have knowledge of its default gateway. Check the DHCP scope of the IP phone to ensure it is providing the correct default gateway to the IP phone.
Check to see if the default gateway is sending and receiving packets to and from the IP phone.
For a single test call, issue the debug voip rtp command on the default gateway. To check connectivity, issue the ping command. An IP phone may not respond to all pings to guard against denial of service attacks.
If the default gateway is not sending packets to the IP phone, it may not have routing enabled. Check that the ip routing global command is configured.
If packets are being sent and received between the IP phone and its default gateway, the problem lies in the IP routing network or beyond. Continue working to resolve the issue at the voice gateway.
Check to see if the voice gateway is sending and receiving RTP packets to and from the default gateway.
For a single test call, issue the debug voip rtp command on the voice gateway. To check connectivity, issue the ping command.
The ping command allows you to check IP layer connectivity but does not give you an indication of whether RTP packets are traversing in both directions.
If the voice gateway is not sending and receiving RTP packets to and from the default gateway, there is likely an IP routing problem. Ensure that the ip routing command is enabled. Use the normal techniques for a resolution, including the traceroute and ping commands to resolve a routing problem. The problem can involve a range of issues, including intermittent router hardware failure.
If pings are successfully sent and received, the problem may lie with RTP packet transmission. Check for these possibilities:
If compressed RTP (cRTP) is being used, check that it has been configured at both sides of any WAN link.
If NAT, or a PIX Firewall, is in the path of the connectivity, check that the appropriate ports are open on the PIX Firewall and that the version of NAT supports Skinny Client Control Protocol (SCCP).
Ensure that SCCP default port 2000 is open on the PIX Firewall. If you are using a different port, ensure that the port is open on the PIX Firewall and also that NAT is aware of the port being used. For Cisco IOS NAT, the default port of 2000 is supported by default and the ip nat service skinny tcp port command is required to support other ports.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.