Re: MGCP and H.323 with SRST Gateway Configuration
SRST is sepearate component or feature on IOS GW than H323/SIP/MGCP.
No matter what protocol you run, you may or may not have SRST.
When the phone do not have any call manager to connect to, it will try to register to SRST GW no matter whether it is MGCP, SIP or H323 Gateway.
But based on the protocol you run to connect to CUCM, you need some other configuration.
Like if it MGCP, when phones are registered to SRST GW, you need to terminate the ISDN msg local to the gateway. So you need to configure
This command will remove the isdn l3-bind command from the serial interface when no call manager is available. So PRI can be used locally.
If it is MGCP analog lines, you need to configure
call application alternate default
for the same purpose
If it is H323, the PRI and analog ports are always termincate locally. But then dial-peer selection could cause problem. Like when the phones are registered in callmanager, you want to send the call to callmanager. But if you have CME as SRST, you'll also have ephone-dn created with more specific. So Gateway will try to send the call to ephone-dn where phones aren't register. So call may fail.
In that case, you need to modify preference and routing rule on the gateway. Smae goes for SIP
Regarding the MGCP and H323 on same gateway. You can have it. But you can not share a PRI with MGCP and H323 at the same time.
Analog ports can be shared by both H323 and MGCP at the sametime but only for outgoing. Incoming call will trigger MGCP application. So H323 will not be able to use it.
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...