The simple answer is that you will have to pick one interface to use to define your h323 inteface. Your router cannot present itself as two differnt devices. Let me take one the following configuration and explain it further.
h323-gateway voip bind srcaddr 192.168.6.18
What this command is instructing the router to do is to source all h323 traffic from the interface it is configured under (in this case the loopback) The reason for this is that you want to guarantee that rtp packets from a voice flow are always sent and received through the same interface. This alleviates the problem of one way audio where you have rtp traffic destined for an interface that the remote side may not be able to route to.
In either case, if the router allowed you to bind h323 traffic to multiple interfaces, you would in essence be creating the same scenario that the command was designed to fix.
The bottom line is that the gateway can only have a single h323 id as well as only a single interface to bind h323 traffic to.
The Cisco EPN system incorporates a network architecture designed to consolidate multiples services on a single Multiprotocol Label Switching (MPLS) transport network. This network is designed primarily based on Application Engineered...
Internet security is important with the increasing attacks that are happening every day. Many internet and browsing security solutions exist, but some are not very easy to use or maybe the question is how can I enable them?
Cisco Software Manager Server
This document describes the programmatic interfaces, RESTful APIs, which are supported by Cisco Software Manager Server (CSM Server).
CSM Server supports a set of finite RESTful APIs. The fir...