Yes, you can indeed use SCCP to control FXS ports that are in any IOS gateway. In CUCM, build a new gateway (DEVICE > GATEWAY, add new) and choose this IOS type (2801, etc.  My 6.1.3 doesn't show the 29xx-series yet, but you should be OK using 28xx if not.  You don't need adapters, and VIC-FXS card or EVM module will be supported in gateways.  Choose SCCP and you can define the DNs in CUCM just as you would with MGCP.  Be sure to specify the MAC address of the 2x01 gateway in CUCM (last 10-digits). In the IOS gateway, you'll need to enable SCCP and the STCAPP (SCCP Telephony Control Appliaction) like this or similiar: stcapp ccm-group 1 ! ccm-manager config server {TFTP Server 1}{TFTP Server 2} ccm-manager sccp local {Loopback} ! sccp local {Loopback} sccp ccm {SRST Reference} identifier 4 priority 4 sccp ccm {CallManager 3} identifier 3 priority 3 version xxxx sccp ccm {CallManager 2} identifier 2 priority 2 version xxxx sccp ccm {CallManager 1} identifier 1 priority 1 version xxxx ! sccp ccm group 1   bind interface {Loopback}   associate ccm 1 priority 1   associate ccm 2 priority 2   associate ccm 3 priority 3   associate ccm 4 priority 4 ! sccp ! stcapp ! ccm-manager sccp ! Once SCCP and the STCAPP are running use "show sccp" and "show stcapp device summary" to check if it's registered to CUCM.  CUCM will also give you a "registered" status, and show you the IP address as well.  When the FXS ports are controlled by SCCP, there are 'psuedo-dial peers' created on the IOS gateway automatically...you'll see something like this that the STCAPP process puts in: ! dial-peer voice 999200 pots service stcapp port 2/0/0 ! dial-peer voice 999201 pots service stcapp port 2/0/1 ! And certainly you can mix-and-match protocols for a given interface on the same gateway.  You can have FXS ports controlled by SCCP, and the PRIs controlled by H323/SIP/whatever.  But each interface must only have one protocol. On all my gateways, I run SCCP to control FXS ports, H.323 to control T1s for PRI or FXO/DID ports if it's an analog site.(PSTN in and out).  I generally use H.323 for all my SRST-branch gateways PSTN services and station-side stuff for fax and analog phones stays at SCCP.  I only use MGCP at my headquarter's office where I need it for QSIG or other reasons that H.323 can't due to limitations. I hope this helps. Regards, Mark ... View more

Hi  - As the others have noted, stay away from MGCP for your branch offices.  It adds a layer of complexity and flakeyness that you don't need.  Just yesterday we had a major outage due to MGCP's inability to fail-over from one subscriber to another (still trying to find root cause).  H.323, in my opinion is the most stable of all for remote branch gateways. While H323/SIP will allow you more control of digit manipulation at the gateway layer, I don't think you want or need it there.  Yes, translation profiles can indeed be powerful, but I think for maintenance purposes you can and should do them in CUCM.  You don't want to have to go into IOS each time you add a new phone at the site, for example.  Also, be mindful of the limitations with voice translation profiles.  I believe you can have 128 rules, but only 15 translations per rule.  That's bitten me before and forced me into NUM-EXPs.  You may be able to use them, or simply prefix all inbound DIDs that come from the PRI with a unique code such as "*123" before passing along to CUCM.  CUCM would then apply an appropriate translation pattern, unique to that site. I hope this helps. Regards, Mark ... View more