well the first two we were in a major hurry and I didnt have time to play and make it work.
The 3rd we are in slightly less of a hurry AND this gateway has multiple tie lines in it so in order for me to route different partitions out particular trunks I need to have this one as an MGCP endpoint..
I suppose I could do it with dial-peers maybe.
Phone 82001000 in partition A to use trunk A
and phone 82002000 in partition B to use trunk B
Again with those trunks on the same physical gateway. If you have a clean way of doing it on h323 I am all ears.
Well, I'm going to go against the steam here and disagree with Paulo..but definitely no disrespect intended.
I much prefer MGCP. I enjoy h323's stability, however in most situations, MGCP's ease of configuration makes it my preferred method. Especially when dealing with alot of gateways in an environment.
Following are some excerpts from my mgcp config script. Couple things that will get you:
1) Issue a show ccm and verify the router name is identical to the one you program in CCM. If there is a domain name programmed on the router, either remove it from the router or add it to the gateway in CCM, but they must match.
2) A dial-peer is not necessary for the PRI if there are no other configs...like SRST. Basically, you only need it if you have an overlapping config on the gateway and you need to make sure it hits the MGCP dial-peer first. Again, most common in SRST environments.
controller T1 3/0
pri-group timeslots 1-24 service mgcp
isdn bind-l3 ccm-manager
! Optional...See #2 above.
dial-peer voice 1000 pots
incoming called-number .
service alternate default
no ccm-manager fax protocol cisco
mgcp call-agent service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
no mgcp package-capability fxr-package
no mgcp timer receive-rtcp
mgcp fax t38 inhibit
mgcp bind control source-interface GigabitEthernet0/1
mgcp bind media source-interface GigabitEthernet0/1
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...