Of Wes
Sisk (wsisk)
Sent: Wednesday, July 16, 2014 9:12 AM
To: cisco-voip voyp list
Subject: Re: [cisco-voip] CCM Trace Question || MediaManager PTime
+1. Wouldn't be the first time I've thought wrong but I think of these values
as the max msec supported for each codec. I always thought
+1. Wouldn’t be the first time I’ve thought wrong but I think of these values
as the max msec supported for each codec. I always thought there was an
interesting underlying assumption that devices could do less than the
advertised max msec. i.e. this device support codec 12 with maximum of 60
Folks:
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
(Cap,ptime) and figured that ptime was simply the
I believe ptime is the number of frames per packet.
-Ryan
On Jul 15, 2014, at 10:28 AM, Daniel Pagan
dpa...@fidelus.commailto:dpa...@fidelus.com wrote:
Folks:
Quick question on the preCheckCapabilities step for MediaManager. After a new
MediaManager is created, I’ve often referred to the
I've always seen medimanager use msec in that second field.
in sip there are ptime and maxptime parameters, ptime is supposed to
be msec per packet in the context of SIP SDP, which is really where
that term comes from. i dont think i've ever seen anything handle
maxptime correctly. ptime tends to
