<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
I believe ptime is the number of frames per packet.
<div><br>
<div>-Ryan </div>
<br>
<div>
<div>On Jul 15, 2014, at 10:28 AM, Daniel Pagan <<a href="mailto:dpagan@fidelus.com">dpagan@fidelus.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Folks:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Quick question on the preCheckCapabilities step for MediaManager. After a new MediaManager is created, I’ve often referred to the preCheckCapabilities line for determining codec and DTMF relay capabilities based on codec type numbers (<b><i>Cap</i></b>,ptime)
and figured that ptime was simply the payload size in ms. While looking at a recent issue, I noticed that ptime didn’t exactly match up with packet time values specified in CCM service parameter settings. The environment was using default settings across the
board for packet size in milliseconds, but advertised capabilities shown in preCheckCapabilities for an IP phone to IP phone call showed:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">(Cap,ptime)= (25,40) (4,40) (2,40) (15,60) (16,60) (11,60) (12,60)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here I’m seeing g.711 with a ptime value of 40 and g.729 with 60. In this environment, g.711 and g.729 is configured for 20 ms packet size. So for clarification, assuming my understanding is incorrect, can someone tell me what the ptime
value represents? We also thought maybe maximum payload size in ms but service these values go beyond the allowable values in CUCM.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks ahead of time!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">- Daniel<o:p></o:p></p>
</div>
</div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</div>
</div>
<br>
</div>
</body>
</html>