<table cellspacing='0' cellpadding='0' border='0' ><tr><td valign='top' style='font: inherit;'>which interface you bind as VOIP interface on the router<br>did u add the h.323 voip bind srcadd (IP)<br>thanks<br><br>--- On <b>Thu, 7/24/08, Erick Bergquist <i><erickbee@gmail.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">From: Erick Bergquist <erickbee@gmail.com><br>Subject: Re: [cisco-voip] One way audio with H323, works fine with MGCP<br>To: "Joe Cisco" <smetsysocsic@gmail.com><br>Cc: "cisco-voip@puck-nether.net" <cisco-voip@puck.nether.net><br>Date: Thursday, July 24, 2008, 1:11 AM<br><br><pre>Yes, the H323 interface is the Voice VLAN subinterface the IP Phones<br>are on. Sourced ping works fine.<br><br><br>On Wed, Jul 23, 2008 at 10:57 PM, Joe Cisco <smetsysocsic@gmail.com><br>wrote:<br>> You answered my first question of is the h323 bound to an
interface<br>> that is reachable across the vpn, but it still sounds like a routing<br>> issue. Do an extended ping from the voice gateway pinging a live<br>> phone. In the extended ping, use the ip of the h323 bound address as<br>> the source address of the ping.<br>><br>> If you don't know how to specify the source address in the ping,<br>> here's an example:<br>><br>> ping ip<br>> Target IP address:206.204.18.22<br>> Repeat count [5]:<br>> Datagram size [100]:<br>> Timeout in seconds [2]:<br>> Extended commands [n]: y<br>> Source address or interface: 10.0.0.1<br>> Type of service [0]:<br>> Set DF bit in IP header? [no]:<br>> Validate reply data? [no]:<br>> Data pattern [0xABCD]:<br>> Loose, Strict, Record, Timestamp, Verbose[none]:<br>> Sweep range of sizes [n]:<br>> Type escape sequence to abort.<br>> Sending 5, 100-byte ICMP Echos to 206.204.18.22, timeout is 2 seconds:<br>>
Packet sent with a source address of 10.0.0.1<br>> !!!!!<br>> Success rate is 100 percent (5/5), round-trip min/avg/max = 5/7/6 ms<br>><br>> -Joe C.<br>><br>> On Wed, Jul 23, 2008 at 10:42 PM, Erick Bergquist<br><erickbee@gmail.com> wrote:<br>>> Have a odd issue here, that I need some ideas on...<br>>><br>>> Have an existing working MGCP gateway (2800 series) with 3 analog<br>>> lines (FXO), but need inbound Caller ID so changed over to H323 and<br>>> receiving caller ID works fine now but getting one way audio with the<br>>> H.323 setup on same interfaces used for MGCP.<br>>><br>>> The outside caller can here the person on IP Phone, but the user on IP<br>>> Phone side can't hear the outside caller. The IP Phone user can<br>place<br>>> and receive calls in/out of the gateway fine so call setup and<br>>> teardown is working fine. Just seems like something with the
audio<br>>> cutover is not working correctly. The call flow between the gateway<br>>> and Call Manager is going over a VPN (Checkpoint box) and all H323<br>>> ports are open on the firewall I'm being told.<br>>><br>>> The IOS version is 12.4(15)T5 on the 2800, and I am not seeing any<br>>> routing issues (the IP's and binded interfaces for H323 are same<br>as<br>>> for the previous working MGCP setup). The audio works fine when I<br>>> change it back to MGCP.<br>>><br>>> Now, only if we had caller id support for analog MGCP endpoints.<br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> cisco-voip@puck.nether.net<br>>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>>><br>><br>_______________________________________________<br>cisco-voip mailing
list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip</pre></blockquote></td></tr></table><br>