cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2129
Views
0
Helpful
5
Replies

MeetMe Conference Error - No Conference Bridge, Adhoc Cannot Complete Conference

erikjbrown
Level 1
Level 1

We have a new Cisco 2951 ISR with CME installed by consultants a few months ago(due to my lack of knowledge and time).  The system replaced an older 2801.  The 2801 ISR would support either ad-hoc or meetme conferencing as i was told and now i suspect that was due to a lack of dsp's.

With the new system, the consultants setup a meetme extension and i'm positive we tested the meetme bridge successfully.  .  The problem is that people are trying to use adhoc conferencing and it does not work.  The phone says Cannot complete conference.  Meetme also gives error No Conference Bridge.  Cisco tech says we need a dsp upgrade.  I know at least meetme worked on this new system when installed. 

We do have a few branch offices connecting to the isr over the Wan - these sites have 911 translations setup so that when they dial 911, the call comes back to us and goes out over a vonage phone line with their office address registerd.  I cannot be positive we tested the meetme conference before this 911 testing was done.  i think this would be the only explanation for not having enough dsp's but i could be way off.

What i'd like to do is get at least adhoc conferencing to work because no one even knows how to use meetme and adhoc worked on old system

Any help would be appreciated.  This is the info on the dspfarm.  please inform me of any other pieces of config you might need to help guide us in the right direction.

           


NOVA-CME#sh dspfarm all
Dspfarm Profile Configuration

Profile ID = 2, Service = TRANSCODING, Resource ID = 1
Profile Description :
Profile Service Mode : Non Secure
Profile Admin State : DOWN
Profile Operation State : DOWN
Application : SCCP   Status : NOT ASSOCIATED
Resource Provider : FLEX_DSPRM   Status : NONE
Number of Resource Configured : 0
Number of Resource Available : 0
Codec Configuration: num_of_codecs:6
Codec : g729br8, Maximum Packetization Period : 60
Codec : g729r8, Maximum Packetization Period : 60
Codec : g711ulaw, Maximum Packetization Period : 30
Codec : g711alaw, Maximum Packetization Period : 30
Codec : g729ar8, Maximum Packetization Period : 60
Codec : g729abr8, Maximum Packetization Period : 60
Dspfarm Profile Configuration

Profile ID = 1, Service = CONFERENCING, Resource ID = 2
Profile Description :
Profile Service Mode : Non Secure
Profile Admin State : DOWN
Profile Operation State : DOWN
Application : SCCP   Status : NOT ASSOCIATED
Resource Provider : FLEX_DSPRM   Status : NONE
Number of Resource Configured : 0
Number of Resource Available : 0
Maximum conference participants : 8
Codec Configuration: num_of_codecs:2
Codec : g711ulaw, Maximum Packetization Period : 30 , Transcoder: Not Required
Codec : g711alaw, Maximum Packetization Period : 30 , Transcoder: Not Required

Total number of DSPFARM DSP channel(s) 0

5 Replies 5

Jaime Valencia
Cisco Employee
Cisco Employee

Your profiles are down and not associated, review your configuration:

Profile Admin State : DOWN

Profile Operation State : DOWN

Application  : SCCP   Status : NOT ASSOCIATED

Associate the profiles and do a no shut on them.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

We also have two Call Park extensions setup that were not on the original system.  Could we remove those to free up dsp's?

Call park does not use DSPs.

TDM interfaces, CFB, XCODER, MTP DO use DSPs.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

Call park does not use DSPs. If you are running low on dsp resources th eonly thing you can do is to reduce your e1/t1 channel confugred. I wouldnt advise this since you are not a techie...

Can you post your

sh run

and a "sh sccp status"

Please rate all useful posts

Ran command no conference hardware to turn off the need for dsp's.  now can do software ad-hoc conference.

Thanks for everyone's help.