<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.3199" name=GENERATOR></HEAD>
<BODY>
<DIV>Thanks to all for your feedback. One more question/comment - Our experiences in the past using g729 have not been positive. Last time we tried to use it was back in the Nortel days using ITG cards and 9150 remote office devices. Our biggest problem was complaints on a lack of fidelity overall and distortion of higher frequency female and elderly voices. We have not tried this yet in production using Cisco, I am hoping there has been some improvement. The potential cost reduction on overall bandwidth costs makes it hard to resist.</DIV>
<DIV> </DIV>
<DIV>Steve<BR><BR>>>> "Scott Voll" <svoll.voip@gmail.com> 12/20/2007 2:06 PM >>><BR></DIV>
<DIV>As Griag stated, if the device supports G729 that won't be a problem.</DIV>
<DIV> </DIV>
<DIV>the only time it becomes a problem is when you have apps like UCCx that only support G711. then you need a transcoder next to that app.</DIV>
<DIV> </DIV>
<DIV>We are setup like you. G711 at central site (CM, VGW, Apps, etc) and G729 at remote sites. I have Transcoding resources at the central site so if they want to use the apps, they can. I also have Conferenece resources at the central site so that if one party is at the remote site they get a G729 stream while everyone else gets G711. </DIV>
<DIV> </DIV>
<DIV>So if you don't have apps that only support G711 you really don't need Transcoding. And personally A one point before transcoding resources I just had them call out the PSTN to our helpdesk which gets you around the G711 issue but in cures Toll charges. </DIV>
<DIV> </DIV>
<DIV>Scott<BR><BR></DIV>
<DIV class=gmail_quote>On Dec 20, 2007 10:44 AM, Craig Staffin <<A href="mailto:cmstaffin@gmail.com">cmstaffin@gmail.com</A>> wrote:<BR>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Steven,<BR><BR>Unity can support G729 as well as all of your endpoints and gateways.<BR><BR>The only time a transcoder would be needed is if you had a call start as G711 and then get transfered over the WAN thus needing to get transcoded from G711 to G729 This usually only happens during a conference call. <BR><BR>As far as your long distance calls they will simply get setup as a G729 call to begin with therefor no need for transcoders.<BR><BR>Craig<BR><BR>
<DIV class=gmail_quote>
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c>On Dec 20, 2007 12:34 PM, STEVEN CASPER < <A href="mailto:SCASPER@mtb.com" target=_blank>SCASPER@mtb.com</A>> wrote:<BR></DIV></DIV>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c>
<DIV style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma; font-size-adjust: none; font-stretch: normal">
<DIV> We have been using G711 to our branches for IPT and I am now looking at using G729. I am confused as to my transcoder requirements. I would think I would need to provision DSP based transcoder resources at the remote locations and also at the central location so G729 would always be used across the WAN. I think that transcoding resources would be required at both the remote location and the central location for the following scenarios across the WAN link: </DIV>
<DIV> </DIV>
<DIV>Calls to a centralized Unity</DIV>
<DIV>Calls to centralized PRI gateways for Long distance calling </DIV>
<DIV>Calls to/from IP phones at G711 locations?</DIV>
<DIV>Conferencing IP phones and an analog or digital trunk </DIV>
<DIV> </DIV>
<DIV>Does this look correct? For some reason determining when a transcoder is required is proving to be hard for me to grasp. Are there any other scenarios where transcoding would be required?</DIV>
<DIV> </DIV>
<DIV>Thanks!</DIV>
<DIV>Steve</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV><BR><BR>Steve Casper<BR>Voice Technologies<BR>M&T Bank<BR>(410) 347-6026
<P>************************************<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></P></DIV></DIV></DIV><BR>_______________________________________________<BR>cisco-voip mailing list<BR><A href="mailto:cisco-voip@puck.nether.net" target=_blank>cisco-voip@puck.nether.net </A><BR><A href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></DIV><FONT color=#888888><BR><BR clear=all><BR>-- <BR>Craig Staffin <BR><A href="mailto:Craig@staffin.org" target=_blank>Craig@staffin.org</A><BR>(H) 262-437-7313<BR>(C) 262-613-6003 </FONT><BR>_______________________________________________<BR>cisco-voip mailing list<BR><A href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></DIV><BR>
<P>************************************<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>
</P></BODY></HTML>