xample 12-1 MTP Configuration in CUBE sccp local Loopback0 sccp ccm 171.xx.xx.101 identifier 1 version 5.0.1 sccp ccm 171.xx.xx.102 . identifier 2 version 5.0.1 sccp ccm group 1 description SJC-CUCM -CLUSTER associate ccm 1 priority 1 associate ccm 2 priority 2 associate profile 30 register mtv5-pop-sbc1 dspfarm profile 30 mtp codec g711ulaw maximum sessions hardware 600 associate application SCCP As you know, CUBE works as a demarcation point between two networks. In this deploy- ment, CUBE communicates with Company P's internal devices over H.323 protocol; and it communicates with Company Q's devices over SIP protocol. Therefore, the communi- cation between CUBE and CUCM is done over H.323, whereas the communication between CUBE and Company Q's conference server is done over SIP. Because the router (CUBE) has multiple Ethernet interfaces a Loopback interface is con- figured to communicate with the CUCM. In Example 12-2, you can also see how the H.323 gateway is configured under that loopback address. It ensures the single IP address is used while communicating with CUCM over H.323 protocol. In the following example, EIGRP is also configured to enable the routing within the network. But, if you use a static route, you don't need to configure EIGRP. Example 12-2 Loopback Interface Configuration for H.323 interface Loopback0 ip address 10.18.225.17 255.255.255.255 h323-gateway voip interface h323-gateway voip bind srcaddr 10.18.225.17 interface GigabitEthernet0/0 description Connection to mtv5-rbb-gw1 4/1 ip address 10.18.225.66 255.255.255.252 duplex auto speed auto media-type rj45 continues 270 SIP Trunking Example 12-2 Loopback Interface Configuration for H.323 (continued) interface GigabitEthernet0/1 description Connection to mtv5-rbb-gw2 4/1 ip address 10.18.225.98 255.255.255.252 duplex auto speed auto media-type rj45 router eigrp 109 passive -interface default no passive - interface GigabitEthernet0/0 no passive - interface GigabitEthernet0/1 network 0.0.0.0 distribute - list 10 out no auto summary eigrp st