[cisco-voip] H.323 with multiple bindings...

[Jonathan Charles]

Only downside is I am also sending SIP down this interface... (the public
side)....

However, the plan is to convert it to H.323 on Thursday, and that could
work...



Jonathan

On Tue, May 3, 2011 at 12:38 PM, Ryan Ratliff <rratliff at cisco.com> wrote:

> Or change to SIP between the CUBE and CUCM so you can bind SIP to a
> separate interface than H.323.
>
> I don't know if you can bind H.323 per dial-peer.
>
> -Ryan
>
> On May 3, 2011, at 12:06 PM, ccieid1ot wrote:
>
> Paste the configs and how this router is bind to ccm.
>
> duy
> ccie #27737 voice
>
> tmobile g2
> On May 3, 2011 11:05 AM, "Jonathan Charles" <jonvoip at gmail.com> wrote:
> > Ping works. but not between interfaces..
> >
> > This is a binding isssue... we need to change the binding per call...
> >
> > On Tue, May 3, 2011 at 11:02 AM, ccieid1ot <ccieid1ot at gmail.com> wrote:
> >
> >> Can u do a source ping out from the private ip? Could be a routing
> issue.
> >>
> >> duy
> >> ccie #27737 voice
> >>
> >> tmobile g2
> >> On May 3, 2011 10:59 AM, "Jonathan Charles" <jonvoip at gmail.com> wrote:
> >> > We have a customer with an H.323 trunk to a provider. The router this
> >> > terminates on has a private and public IP.
> >> >
> >> > However, we have bound the inside (private IP) as the H.323 address
> for
> >> CCM.
> >> > Calls are getting dead air because H.323 is bound to the private IP.
> >> >
> >> > Can I set on the dial-peer a binding for that peer, so if I match an
> >> > outgoing peer I can bind to the public interface, and if I match an
> >> inbound
> >> > peer I can bind tot he private interface?
> >> >
> >> > There is no NAT between the public and private.
> >> >
> >> >
> >> >
> >> > Jonathan
> >>
> _______________________________________________
> 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/20110503/a9d8cd6e/attachment.html>