<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Unless I'm reading this documentation incorrectly, it looks like it supports all four. Now, I've read Cisco documentation before that was a little misleading, but I figure it sounded about right.<br><div style="margin-left: 40px;"><br><hr style="width: 100%; height: 2px;">http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/gatecont/ps2250/ps5516/product_data_sheet09186a00801d87f6.html<br><br><span class="content"><p style="font-size: 10pt; font-style: normal; font-variant: normal; font-weight: bold; margin-left: 0pt; margin-right: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none;" class="pSubhead1CMT">Protocols Supported</p>
<a name="wp9000359"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• SCCP</p>
<a name="wp9000360"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• H.323v4</p>
<a name="wp9000361"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• MGCP</p>
<a name="wp9000362"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• SIP</p>
<a name="wp9000363"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• Real-Time Transport Protocol (RTP)</p>
<a name="wp9000364"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• Secure Real-Time Transport Protocol (SRTP)</p>
<a name="wp9000365"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• Trivial File Transfer Protocol (TFTP)</p>
<a name="wp9000366"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• HTTP server</p>
<a name="wp9000367"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• SNMP</p>
<a name="wp9000368"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• Telnet</p>
<a name="wp9000369"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• Dynamic Host Configuration Protocol (DHCP)</p>
<a name="wp9000370"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• Domain Name System (DNS)</p>
<a name="wp9000371"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• VG224</p>
<a name="wp9000372"></a>
<p style="margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt;" class="pBullet2CMT">– Cisco Unified Communications Manager 3.3.3 SR2 and higher versions</p>
<a name="wp9000373"></a>
<p style="margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt;" class="pBullet2CMT">– Cisco Unified Communications Manager Express 4.3.2 and higher versions</p>
<a name="wp9000374"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• VG204 and VG202</p>
<a name="wp9000375"></a>
<p style="margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt;" class="pBullet2CMT">– Cisco Unified Communications Manager 6.1.3 and 7.0.1, and higher versions</p>
<a name="wp9000376"></a>
<p style="margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt;" class="pBullet2CMT">– Cisco Unified Communications Manager Express 7.0.1 and higher versions</p>
<a name="wp9000377"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">•
Cisco Unified Communications Manager or Cisco Unified Communications
Manager Express redundancy support using Hot Standby Router Protocol
(HSRP)</p>
<a name="wp9000378"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• Call survivability-MGCP failover to an H.323 connection to the SRST router</p>
<a name="wp9000379"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• Cisco fax relay, T.38 fax relay, and modem pass-through</p>
<a name="wp9000380"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• Coder/decoder (codec) support, G.711, G.729a</p>
<a name="wp9000381"></a>
<p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT">• RADIUS and TACACS+ for Telnet and authorization</p></span><hr style="width: 100%; height: 2px;"><span class="content"><p style="font-style: normal; font-variant: normal; font-weight: normal; margin-bottom: 3pt; margin-right: 0pt; margin-top: 0pt; text-decoration: none; text-transform: none;" class="pBulletCMT"><br></p></span><br></div><br><br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Paul" <asobihoudai@yahoo.com><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca>, "Scott Kee" <SKee@cmsstl.com><br>Cc: cisco-voip@puck.nether.net, "STEVEN CASPER" <SCASPER@mtb.com>, "Jonathan Charles" <jonvoip@gmail.com><br>Sent: Wednesday, April 29, 2009 9:59:15 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] VG224 issue<br><br><style></style><link href="/zimbra/css/msgview.css?v=081117021119" rel="stylesheet"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div>You have two choices for control protocol for your VG224 and H323 and SIP ain't either of them.<br><br>Paul<br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Lelio Fulgenzi <lelio@uoguelph.ca><br><b><span style="font-weight: bold;">To:</span></b> Scott Kee <SKee@cmsstl.com><br><b><span style="font-weight: bold;">Cc:</span></b> cisco-voip@puck.nether.net; Paul <asobihoudai@yahoo.com>; STEVEN CASPER <SCASPER@mtb.com>; Jonathan Charles <jonvoip@gmail.com><br><b><span style="font-weight: bold;">Sent:</span></b> Wednesday, April 29, 2009 4:25:57
PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [cisco-voip] VG224 issue<br></font><br><style>p {margin:0;}</style><div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">Gimme an "S". Gimme a "C". Gimme a "C". Gimme a "P".<br><br>whadaya got?<br><br>NOT H323!<br><br>Seriously, I think you will find H323 is a pain to configure with all the dial peers, etc. With SCCP it's configure three or four lines and your done. Each port needs an stcapp command or something like that, but it's over and done with after that.<br><br>Don't get me wrong, H323 has it's benefits. Especially for direct multiple cluster access, but I think that's better for actual gateways, not FXS ports.<br><br>Somewhere, there's a chart that compares H323, SCCP, MGCP, SIP so unless you really need H323, stick with SCCP. Try it, you'll like it. <br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Scott Kee" <SKee@cmsstl.com><br>To: "Paul" <asobihoudai@yahoo.com>, "STEVEN CASPER" <SCASPER@mtb.com>, "Jonathan Charles" <jonvoip@gmail.com>, "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: cisco-voip@puck.nether.net<br>Sent: Wednesday, April 29, 2009 4:19:56 PM GMT -05:00 US/Canada Eastern<br>Subject: RE: [cisco-voip] VG224 issue<br><br>How about H323?<br>I am just having too many issues with MGCP with the fax machines.<br><br><br>-----Original Message-----<br>From: Paul [mailto:asobihoudai@yahoo.com] <br>Sent: Wednesday, April 29, 2009 2:41 PM<br>To: STEVEN CASPER; Jonathan Charles; Lelio Fulgenzi<br>Cc: Scott Kee; cisco-voip@puck.nether.net<br>Subject: Re: [cisco-voip] VG224
issue<br><br><br><span><a target="_blank" href="http://www.cisco.com/en/US/docs/ios/12_4t/12_4t2/ht1vg224.html">http://www.cisco.com/en/US/docs/ios/12_4t/12_4t2/ht1vg224.html</a></span><br><br><span><a target="_blank" href="http://cisco.com/en/US/docs/ios/voice/fxs/configuration/guide/fxssccpsplmft.html">http://cisco.com/en/US/docs/ios/voice/fxs/configuration/guide/fxssccpsplmft.html</a></span><br><br>These two documents should give you plenty of information on how to configure the FXS ports to be controlled via Skinny.<br><br><br><br><br>________________________________<br>From: STEVEN CASPER <SCASPER@mtb.com><br>To: Jonathan Charles <jonvoip@gmail.com>; Lelio Fulgenzi <lelio@uoguelph.ca><br>Cc: Scott Kee <SKee@cmsstl.com>; cisco-voip@puck.nether.net<br>Sent: Wednesday, April 29, 2009 3:10:17 PM<br>Subject: Re: [cisco-voip] VG224 issue<br><br><br> All of our VG224s are MGCP and we have been experiencing a lot of fax
pain lately ourselves. When we talked to TAC they told us that MGCP or SCCP makes no difference and that we should change all of our fax machines to not use Super G and to reduce the speed of the fax machines. In a company of our size this is just not going to work. <br> <br>I am considering changing to SCCP to give it a try. Could someone share a sanitized SCCP config for a VG224 and what advantages they think there are to using SCCP as opposed to MGCP? Other than it works better :) I am going to have to give a couple of technical reasons.<br> <br>Thanks<br>Steve<br> <br>Please consider the impact on our environment before printing this e-mail. <br><br>>>> Lelio Fulgenzi <lelio@uoguelph.ca> 4/27/2009 1:27 PM >>><br><br>I third that opinion. I use SCCP and it was very easy to setup. I think SCCP debugs are also more helpful (I could be wrong there).<br><br>That being said, we are using modem/fax passthrough
and have downgraded our FAXes to 14.4/ECC off.<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Jonathan Charles" <jonvoip@gmail.com><br>To: "Paul" <asobihoudai@yahoo.com><br>Cc: "Scott Kee" <SKee@cmsstl.com>, cisco-voip@puck.nether.net<br>Sent: Monday, April 27, 2009 1:16:01 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] VG224 issue<br><br>Oh, wow, it is MGCP... I didn't even see that...<br><br>Yeah, ditto, go with SCCP.<br><br>J<br><br>On Mon, Apr 27, 2009 at 9:24 AM, Paul <asobihoudai@yahoo.com> wrote:<br>><br>> Personally, I'd ditch the MGCP and use Skinny for the VG224. I've had a lot more luck and flexibility using Skinny. Make sure
you update the IOS on the VG.<br>><br>> Paul<br>><br>><br>> ----- Original Message ----<br>> From: Scott Kee <SKee@cmsstl.com><br>> To: "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net><br>> Sent: Monday, April 27, 2009 8:58:18 AM<br>> Subject: [cisco-voip] VG224 issue<br>><br>><br>> I have VG224 with CM 6.1 and using MGCP. I have about 18 fax machines plugged into this Voice Gateway.<br>> Sometime early March people started complaining that they weren't receiving faxes from outside.<br>> They were hearing fast busy signal when outside people send faxes to the fax machines that were plugged into the VG 224.<br>> I reloaded VG 224 and power recycled fax machines but it did not make any difference.<br>> I called Cisco TAC and worked on the issue for about 20 hours but did not find any issues.<br>> We RMA the router but it did not make any difference. We ended up removing
the VG224 gateway from CM and recreated it. That seemed fixed the issues then.<br>><br>> This afternoon, I am seeing exact same issues with VG 224. It was working fine till now.<br>> I did not make any configuration changes on the VG224...<br>> I am going to call Cisco tomorrow morning but I don't know Cisco is going to do this time?<br>> Is this CM issue or VG?<br>><br>> Does anyone experience this issue?<br>><br>> Any help would really appreciated.<br>><br>> Thanks,<br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br><span>> <a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br><span>> <a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>><br>><br>><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br><span>> <a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>><br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br><span><a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br><br>************************************<br>This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing,
copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.<br>There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.<br>************************************<br><br><br><br>
<br></div></div></div></div><br>
</div></body></html>