<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body style="font-family: Arial; font-size: 13px;" bgcolor="#FFFFFF"
text="#000000">
<div style="font-family:Arial;font-size:13px;"><font face="Arial">As
long as the default intraregion codec is set to G711, this
should be fine.</font><br>
<pre class="moz-signature" cols="72">Adam</pre>
<br>
<span style="color:#000000;" class="headerSpan"><br>
<hr tabindex="0"><font style="font-size:x-small" face="Tahoma"><!--@A@--><b>From:</b>
Lelio Fulgenzi <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a><!--@A@--><br>
<!--@D@--><b>Sent:</b> Mon, Jan 09, 2012 1:16:44 PM<!--@D@--><br>
<!--@R@--><b>To:</b> Adam Frankel (afrankel)
<a class="moz-txt-link-rfc2396E" href="mailto:afrankel@cisco.com"><afrankel@cisco.com></a><!--@R@--><br>
<!--@C@--><b>CC:</b> Cisco VoIPoE List
<a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><!--@C@--><br>
<!--@S@--><b>Subject:</b> Re: [cisco-voip] regions,
transcoders and bears, oh my!<!--@S@--><br>
</font><br>
</span>
<blockquote style="border: medium none ! important; padding-left:
0px ! important; padding-right: 0px ! important; margin-left:
0px ! important; margin-right: 0px ! important; font-family:
serif;"
cite="mid:608383915.1084447.1326133004466.JavaMail.root@erie.cs.uoguelph.ca"
type="cite">
<style type="text/css">p { margin: 0; }</style>
<div style="font-family: Verdana; font-size: 10pt; color:
#000000">OK, so if all three objects, the transcoder, the
iPhone Jabber client, and the UCCx ports are all in the
Default region, and I update the MRG(L) of the UCCx ports to
include the transcoder, I should be OK then?<span><br>
<br>
<span name="x"></span>---<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 (ANNU)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr.
Popeil)<br>
<span name="x"></span><br>
</span><br>
<hr id="zwchr"><b>From: </b>"Adam Frankel (afrankel)"
<a class="moz-txt-link-rfc2396E" href="mailto:afrankel@cisco.com"><afrankel@cisco.com></a><br>
<b>To: </b>"Lelio Fulgenzi" <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a><br>
<b>Cc: </b>"Cisco VoIPoE List"
<a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><br>
<b>Sent: </b>Monday, January 9, 2012 12:41:20 PM<br>
<b>Subject: </b>Re: [cisco-voip] regions, transcoders and
bears, oh my!<br>
<br>
<div style="font-family:Arial;font-size:13px;"><font
face="Arial">A transcoder will be required in the MRGL of
the UCCX Port. <br>
<br>
The transcoder should have a device pool who's region
relation to the UCCX Port is G711, and to the Jabber
client it can be either G711 or G729. Since Region config
only specifies the max bitrate between the two devices, if
the Jabber client is only offering G729, a G711 region
config will still allow the connection between the Jabber
client and Transcoder to be G729.<br>
<br>
HTH,<br>
Adam<br>
</font><br>
<span style="color:#000000;" class="headerSpan">
<hr><font style="font-size:x-small" face="Tahoma"><!--@A@--><b>From:</b>
Lelio Fulgenzi <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:lelio@uoguelph.ca" target="_blank"><lelio@uoguelph.ca></a><!--@A@--><br>
<!--@D@--><b>Sent:</b> Mon, Jan 09, 2012 12:31:40 AM<!--@D@--><br>
<!--@R@--><b>To:</b> Cisco VoIPoE List <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:cisco-voip@puck.nether.net"
target="_blank"><cisco-voip@puck.nether.net></a><!--@R@--><br>
<!--@C@--><b>CC:</b>
<!--@C@--><br>
<!--@S@--><b>Subject:</b> [cisco-voip] regions,
transcoders and bears, oh my!<!--@S@--><br>
</font><br>
</span>
<blockquote style="border: medium none ! important;
padding-left: 0px ! important; padding-right: 0px !
important; margin-left: 0px ! important; margin-right: 0px
! important; font-family: serif;"
cite="mid:603168548.1079433.1326130300567.JavaMail.root@erie.cs.uoguelph.ca">
<style>p { margin: 0; }</style>
<div style="font-family: Verdana; font-size: 10pt; color:
#000000"><br>
OK, so in fooling around with the Cisco iPhone Jabber
client, I've realized that I can put aside the concept
of regions and transcoders no longer. The iPhone, when
using g729 (in low bandwidth mode) can not communicate
to some systems, most notably, IPCCx.<br>
<br>
As far as I understood, regions were used to dictate
which codec to use and the transcoder is used to do the
translations.<br>
<br>
So, what do I have to do to get the iPhone using G.729
to be able to talk to UCCx (presumably using G711)?<br>
<br>
Is a transcoder enough? If I create the transcoder and
put it into an Media Resource Group that both devices
can access, should that work?<br>
<br>
I don't understand how I would use regions to classify
the iPhone Jabber client, especially since the iPhone
Jabber client can dynamically select between codecs
depending on bandwidth availability. <br>
<br>
<br>
<span><br>
<span></span>---<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 (ANNU)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget
it. <br>
- LFJ (with apologies to
Mr. Popeil)<br>
<span></span><br>
</span><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</div>
</div>
</blockquote>
<br>
</div>
</body>
</html>