[cisco-voip] PVDMs, DSP farms, et al.... next steps?
Eric Pedersen
PedersenE at bennettjones.com
Thu Apr 26 11:27:10 EDT 2012
If you configure a fractional PRI with "pri-group timeslots" on the T1 controller and are using G.711 then you will only need 10 channels so the PVDM3-16 will work. It definitely works with H.323. As I recall you can do it with MGCP also, but Callmanager won't know it's fractional so you might run into problems.
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ruben Montes (Europe)
Sent: 26 April 2012 8:36 AM
To: 'matthnick at gmail.com'; 'avholloway+cisco-voip at gmail.com'
Cc: 'cisco-voip at puck.nether.net'
Subject: Re: [cisco-voip] PVDMs, DSP farms, et al.... next steps?
Basic stuff, but I haven't found the definitive answer yet. If I have one PRI but using only 10 channels (and H323), with one PVDM3-16 is enough? Is it the same for MGCP?
Thanks!
De: Nick Matthews [mailto:matthnick at gmail.com]
Enviado: Thursday, April 26, 2012 04:28 PM
Para: Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
CC: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Asunto: Re: [cisco-voip] PVDMs, DSP farms, et al.... next steps?
Take the simplest example - PVDM3-16 on a partial PRI.
The 16 channels will be allocated to the PRIs, but as soon as one of those calls is G.729 you won't be able to get 16 calls through.
I haven't played with the allocation on the PVDM3's as much as in the back end it's a lot more complex than the 2's.
-nick
On Thu, Apr 26, 2012 at 12:31 AM, Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>> wrote:
Nick,
Could you clarify your point of being able to over provision here? From my experience, as you add sessions to one service, it dynamically reduces the available sessions on the other services.
I.e., If you do a ? on sessions for transcoding, it might say <1-40>. But if you go and add a few more conferencing sessions first, and come back, it will be lower. Say <1-32>. I'm making these numbers up, but the fact remains, the maximum number you can type in, is limited by the available resources at config time.
Thanks for sharing. I look forward to your response.
Anthony Holloway
On Wed, Apr 25, 2012 at 11:05 PM, Nick Matthews <matthnick at gmail.com<mailto:matthnick at gmail.com>> wrote:
You can still overprovision.
Examples:
-In the PVDM3's conferences are not reserved upon configuration.
-You are locking up G.711 (low complexity) codec, not a high complexity codec
-Transcoding sessions are not locked upon configuration
-Video transcoding/switching sessions are not locked
So if you're using non G711 codecs, transcoding, conferencing, MTPs, or video, you can overprovision. If all you're doing is G711 termination to POTS/PRI I don't think you can.
-nick
On Wed, Apr 25, 2012 at 11:26 AM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:
cool! thanks.
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
________________________________
From: "Ted Nugent" <tednugent73 at gmail.com<mailto:tednugent73 at gmail.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: "Erick Wellnitz" <ewellnitzvoip at gmail.com<mailto:ewellnitzvoip at gmail.com>>, "cisco-voip voyp list" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Wednesday, April 25, 2012 11:04:12 AM
Subject: Re: [cisco-voip] PVDMs, DSP farms, et al.... next steps?
Once you build the channels on the controller "pri-group timeslots 1-24" the DSP resources are locked, FXS and FXO lock on bootup.
I think that command you're looking at will show you what you want, you can see the transcoding towards the bottom
PS-RTRPSTN-01#show dsp-group all
DSP groups on slot 0:
dsp 1:
State: UP, firmware: 28.3.3
Max signal/voice channel: 43/43
Max credits: 645, Voice credits: 645, Video credits: 0
num_of_sig_chnls_allocated: 43
Transcoding channels allocated: 0
Group: FLEX_GROUP_VOICE, complexity: FLEX
Shared credits: 645, reserved credits: 0
Signaling channels allocated: 43
Voice channels allocated: 0
Credits used (rounded-up): 0
Slot: 0
Device idx: 0
PVDM Slot: 0
Dsp Type: SP2600
dsp 2:
State: UP, firmware: 28.3.3
Max signal/voice channel: 43/43
Max credits: 645, Voice credits: 645, Video credits: 0
num_of_sig_chnls_allocated: 43
Transcoding channels allocated: 0
Group: FLEX_GROUP_VOICE, complexity: FLEX
Shared credits: 645, reserved credits: 0
Signaling channels allocated: 43
Voice channels allocated: 0
Credits used (rounded-up): 0
Slot: 0
Device idx: 0
PVDM Slot: 0
Dsp Type: SP2600
dsp 3:
State: UP, firmware: 28.3.3
Max signal/voice channel: 42/43
Max credits: 645, Voice credits: 645, Video credits: 0
num_of_sig_chnls_allocated: 42
Transcoding channels allocated: 0
Group: FLEX_GROUP_VOICE, complexity: FLEX
Shared credits: 645, reserved credits: 0
Signaling channels allocated: 42
Voice channels allocated: 0
Credits used (rounded-up): 0
Slot: 0
Device idx: 0
PVDM Slot: 0
Dsp Type: SP2600
dsp 4:
State: UP, firmware: 28.3.3
Max signal/voice channel: 43/43
Max credits: 645, Voice credits: 645, Video credits: 0
num_of_sig_chnls_allocated: 43
Transcoding channels allocated: 0
Group: FLEX_GROUP_VOICE, complexity: FLEX
Shared credits: 645, reserved credits: 0
Signaling channels allocated: 43
Voice channels allocated: 0
Credits used (rounded-up): 0
Slot: 0
Device idx: 1
PVDM Slot: 0
Dsp Type: SP2600
dsp 5:
State: UP, firmware: 28.3.3
Max signal/voice channel: 43/43
Max credits: 645, Voice credits: 645, Video credits: 0
num_of_sig_chnls_allocated: 13
Transcoding channels allocated: 22
Group: FLEX_GROUP_VOICE, complexity: FLEX
Shared credits: 201, reserved credits: 0
Signaling channels allocated: 13
Voice channels allocated: 0
Credits used (rounded-up): 0
Group: FLEX_GROUP_XCODE, complexity: MEDIUM
Shared credits: 0, reserved credits: 444
Transcoding channels allocated: 0
Credits used (rounded-up): 0
Slot: 0
Device idx: 1
PVDM Slot: 0
Dsp Type: SP2600
dsp 6:
State: UP, firmware: 28.3.3
Max signal/voice channel: 42/43
Max credits: 645, Voice credits: 645, Video credits: 0
num_of_sig_chnls_allocated: 0
Transcoding channels allocated: 28
Group: FLEX_GROUP_VOICE, complexity: FLEX
Shared credits: 80, reserved credits: 0
Signaling channels allocated: 0
Voice channels allocated: 0
Credits used (rounded-up): 0
Group: FLEX_GROUP_XCODE, complexity: MEDIUM
Shared credits: 0, reserved credits: 565
Transcoding channels allocated: 0
Credits used (rounded-up): 0
Slot: 0
Device idx: 1
PVDM Slot: 0
Dsp Type: SP2600
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
itevomcid
The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120426/ac633db2/attachment.html>
More information about the cisco-voip
mailing list