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