Ad-Hoc Conference on CCM 5.X

Unanswered Question
Apr 21st, 2009

Hi all,

I have CCM 5.1 configured with GW via H.323 protocol .. i have to configure Ad-hoc conference .. i have dsp of 24 channels,, after configuring the 1 session 7 dsps are utilizing for conference and rest for incoming and outgoing .... is there any way to configure Ad-Hoc conference by utilizing less number of dsps ????

Regards

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jaime Valencia Tue, 04/21/2009 - 03:24

conference demands a whole DSP, there is no way to change this.

even if you configure 1 session with G711 you'll use the whole DSP as the FW on it can only do CFB.

that of course depends of availability of DSPs, codecs configured and amount of sessions configured.

but bottom line, if a DSP is going to be used for CFB there is no other use for it

1 DSP are 16 channels, your calculations does not make sense.

HTH

java

if this helps, please rate

Ahmed Nasry Abd... Wed, 04/22/2009 - 10:56

hi java

thanks for your nice explaination ...

i had pri with 20channels and after configured one conference session it reserves 7 and rest of 13 are available for configure on controller ...

Regards

Chris Deren Wed, 04/22/2009 - 11:24

As Java stated above you cannot share DSPs between voice ports and conferencing.

If you have 24 PVDM channels that means you have PVDM2-16 and PVDM2-8 modules, with that configuration and a full PRI in flex codec complexity mode you will not be able to allocate any DSP conference bridges.

You need to ensure you have a full DSP (PVDM2-16 = 1 DSP) allocated to conferencing.

Please provide "sh diag" and "sh run" from the router and we can tell you exactly what you can run.

HTH,

Chris

Ahmed Nasry Abd... Thu, 04/23/2009 - 15:10

thanks guys below is the sh diag and sh run of router ...

TGRTR1#sh diag

Slot 0:

C2851 Motherboard with 2GE and integrated VPN Port adapter, 2 ports

Port adapter is analyzed

Port adapter insertion time unknown

EEPROM contents at hardware discovery:

PCB Serial Number : FOC11243QJ7

Hardware Revision : 1.0

Top Assy. Part Number : 800-26922-03

Board Revision : A0

Deviation Number : 0

Fab Version : 03

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

Processor type : 87

Hardware date code : 20070621

Chassis Serial Number : FCZ113171Z0

Chassis MAC Address : 001c.584b.2bf8

MAC Address block size : 32

CLEI Code : COM7N00ARA

Product (FRU) Number : CISCO2851

Part Number : 73-8480-05

Version Identifier : V04

EEPROM format version 4

EEPROM contents (hex):

PVDM Slot 0:

48-channel (G.711) Voice/Fax PVDMII DSP SIMM PVDM daughter card

Hardware Revision : 4.0

Part Number : 73-8540-05

Board Revision : B0

Deviation Number : 0

Fab Version : 04

PCB Serial Number : FOC11296UCH

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

Processor type : 00

Product (FRU) Number : PVDM2-48

Version Identifier : V01

EEPROM format version 4

EEPROM contents (hex):

WIC Slot 0:

VWIC2-2MFT-T1/E1 - 2-Port RJ-48 Multiflex Trunk - T1/E1

Hardware Revision : 0.0

Top Assy. Part Number : 800-22629-05

Board Revision : B0

Deviation Number : 0

Fab Version : 04

PCB Serial Number : FOC1138371E

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

Product (FRU) Number : VWIC2-2MFT-T1/E1

Version Identifier : V01

EEPROM format version 4

EEPROM contents (hex):

*****************************************

sh run

TGRTR1#sh run

Building configuration...

Current configuration : 8188 bytes

!

!

card type e1 0 0

!

ip cef

!

!

isdn switch-type primary-net5

!

voice-card 0

no dspfarm

dsp services dspfarm

!

!

controller E1 0/0/0

framing NO-CRC4

pri-group timeslots 1-20

!

controller E1 0/0/1

framing NO-CRC4

pri-group timeslots 1-13,16

!

ip tcp path-mtu-discovery

!

!

!

!

interface GigabitEthernet0/0

description ******** Connected to 4506 gig5/4 *******

ip address 172.16.20.5 255.255.255.0

duplex auto

speed auto

h323-gateway voip interface

h323-gateway voip bind srcaddr 172.16.20.5

!

!

interface Serial0/0/0:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

no cdp enable

!

interface Serial0/0/1:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

no cdp enable

!

ip forward-protocol nd

ip route 0.0.0.0 0.0.0.0 172.16.20.254

!

!

!

voice-port 0/0/0:15

translation-profile incoming DID

!

voice-port 0/0/1:15

translation-profile incoming DID

!

!

!

sccp local GigabitEthernet0/0

sccp ccm 172.16.20.2 identifier 1 version 5.0.1

sccp

!

sccp ccm group 10

associate ccm 1 priority 1

associate profile 10 register CFBTGRTR1

switchover method immediate

switchback method immediate

!

dspfarm profile 10 conference

codec g711ulaw

codec g711alaw

codec g729ar8

codec g729abr8

codec g729r8

codec g729br8

maximum sessions 1

associate application SCCP

!

!

dial-peer voice 1 voip

translation-profile outgoing PSTNIN

destination-pattern 1...

session target ipv4:172.16.20.2

dtmf-relay h245-alphanumeric

codec g711alaw

no vad

!

thanks in advance

Regards,

Jaime Valencia Thu, 04/23/2009 - 20:53

you have 48 channels, 3 DSPs

1 for CFB the other two are already being used for voice termination

pri-group timeslots 1-20

pri-group timeslots 1-13,16

you're out of channels

HTH

java

if this helps, please rate

Ahmed Nasry Abd... Thu, 04/23/2009 - 23:55

hi java,

thanks for your guide .... i will tell customer to increase the Dsp's ...

Java one more question if you have time can you please have a look on my other post having subject " H.323 GW for Branch Location " ...

can you please guide me urgently how to setup the network and fix out the calling issues ..

this is my first installation for configuring SRST Network & sorry to ask basic questions !!! plz help urgently if you can

Regards

Chris Deren Fri, 04/24/2009 - 05:36

It looks like you have only 1 conference session configured, you can safely change it to 2 as a DSP with high complexity codec listed (g729) can provide 2 conference sessions of up to 8 participants in each. So if you create 1 or 2 sessions it makes no difference as you are commiting full DSP to the conference resources anyway.

Another way to get more out of DSPs is instead of listing g729 in your conference profile is to only include G711, and add a transcoder with G711 and G729 listed. This way you can have 8 conference sessions and transcoding DSPs can be shared between voice sessions. Also, in most deployments most conferences are local which only use G711 anyway, and if remote party has to be conferenced in then the transcder is invoked.

HTH, please rate all posts!

Chris

Actions

This Discussion