When the call comes in to your gateway, you will need an incoming and an outgoing dial-peer for the call to get completed. The incoming pots dial-peer is already configured. The outgoing dialpeer will point to your CUCM server as shown below
dial-peer voice 2 voip
session target ipv4:
Now when an outbound call is made from the CUCM, you will again need two dialpeers on your H323 gateway. You can use dialpeer 2 as the incoming dialpeer just by adding 'incoming called number .' command. The outbound dialpeer will be a pots dialpeer with destination pattern, port and forward digits command.
Check the following doc to help you out with dialpeer configs
If you do not see the incoming called number . command under any voip dialpeer the you would have to add it or else it will use the default dialpeer as the inbound dialpeers which has preconfigured parameters and cant be modified.
Yes you will need route pattern on the CUCM to route calls to the H323 gateway. Then on the gateway you would need dialpeers to route the calls to the PSTN since the call control protocol is peer to peer.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...