Conferencing on PVDM2-8

Unanswered Question
Feb 27th, 2008
User Badges:

I am trying to configure a conference bridge on a 2801 router, with a PVDM2-8.

No FXOs or FXSs are installed on this router.


The scenario I am trying is connecting from an IP Phone to a PSTN phone. Then calling another IP Phone in the LAN then trying a conference. The initiator's screen shows "Can not complete conference" and the PSTN call is dropped, sustaining only the call between the 2 IP Phones.


I have a callmanager 4.1, I created the Enhanced IOS conference Bridge, it's registered fine. I put this conference bridge in the MRG and the phones with the proper device pool and MRGL.


ROUTER#!

!

voice-card 0

dsp services dspfarm

!

!

!

sccp local FastEthernet0/0

sccp ccm 192.168.0.34 identifier 1 version 4.0

sccp

!

sccp ccm group 1

associate ccm 1 priority 1

associate profile 1 register HWCONFBRIDGE

!

dspfarm profile 1 conference

codec g711ulaw

codec g711alaw

codec g729ar8

codec g729abr8

codec g729r8

codec g729br8

maximum sessions 1

associate application SCCP

!

!

ROUTER#sh dspfarm all

Dspfarm Profile Configuration


Profile ID = 1, Service = CONFERENCING, Resource ID = 1

Profile Description :

Profile Admin State : UP

Profile Operation State : ACTIVE

Application : SCCP Status : ASSOCIATED

Resource Provider : FLEX_DSPRM Status : UP

Number of Resource Configured : 1

Number of Resource Available : 1

Codec Configuration

Codec : g711ulaw, Maximum Packetization Period : 30 , Transcoder: Not Required

Codec : g711alaw, Maximum Packetization Period : 30 , Transcoder: Not Required

Codec : g729ar8, Maximum Packetization Period : 60 , Transcoder: Not Required

Codec : g729abr8, Maximum Packetization Period : 60 , Transcoder: Not Required

Codec : g729r8, Maximum Packetization Period : 60 , Transcoder: Not Required

Codec : g729br8, Maximum Packetization Period : 60 , Transcoder: Not Required



SLOT DSP VERSION STATUS CHNL USE TYPE RSC_ID BRIDGE_ID PKTS_TXED PKTS_RXED


0 1 1.1.1 UP N/A FREE conf 1 - - -


Total number of DSPFARM DSP channel(s) 1

ROUTER#sh sccp

SCCP Admin State: UP

Gateway IP Address: 192.168.0.1, Port Number: 2000

IP Precedence: 5

User Masked Codec list: None

Call Manager: 192.168.0.34, Port Number: 2000

Priority: N/A, Version: 4.0, Identifier: 1


Conferencing Oper State: ACTIVE - Cause Code: NONE

Active Call Manager: 192.168.0.34, Port Number: 2000

TCP Link Status: CONNECTED, Profile Identifier: 1

Reported Max Streams: 8, Reported Max OOS Streams: 0

Supported Codec: g711ulaw, Maximum Packetization Period: 30

Supported Codec: g711alaw, Maximum Packetization Period: 30

Supported Codec: g729ar8, Maximum Packetization Period: 60

Supported Codec: g729abr8, Maximum Packetization Period: 60

Supported Codec: g729r8, Maximum Packetization Period: 60

Supported Codec: g729br8, Maximum Packetization Period: 60

Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30


I did a couple of reloads even restarted the callmanager.

Is it an IOS issue? or a misconfiguration?

Can anyone help me out in this?...


Thanks,


Ahmed El-Eraky

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Paolo Bevilacqua Wed, 02/27/2008 - 02:18
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Hi, which exact IOS are you using ?

Paolo Bevilacqua Wed, 02/27/2008 - 06:44
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Can you try 12.4(3j) that is the most stable ?

AhmedEl-Eraky Wed, 02/27/2008 - 07:52
User Badges:

Thank you for your response.

I did as you've suggested but still no luck.

same exact behavior, the message still appears.


I can't seem to find any problems with my configuration, I rechecked. Each side (the router's and the callmanager's) seem to be fine by itself. But it still isn't working together.

Do you have any ideas?...

Thanks....


Ahmed El-Eraky

Michael Owuor Wed, 02/27/2008 - 08:19
User Badges:
  • Cisco Employee,

If you have CCM traces collected at the time the test is performed, they may give further insight into the cause of the problem. For example it could be that the CFB is allocated but there's insufficient bandwidth to connect one of the conference call participants, maybe due to Locations configuration. Or perhaps a different CFB resource is being allocated than the one we expect. Either way, if you can collect the CCM SDI traces, and search for 'Can not Complete Conference', then the lines of traces just before that will likely point to a definitive cause of the problem. Attach those traces here if need be.


Regards,

Michael.

Jaime Valencia Thu, 02/28/2008 - 07:56
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    2011

Check the MRGL from the conference initiator to have in 1st place the HWCFB.

If you have in 1st place a SW CFB you will try to use it and the conference will drop, CCM won't go thru any other CFB to try the conference. In the best scenario the SW CFB would reach for a XCODER.


HTH

AhmedEl-Eraky Thu, 02/28/2008 - 12:28
User Badges:

Hello everyone....


It worked.... I just didn't get the chance to feedback you guys....

Not one thing in the configuration was changed. I double checked all of the configuration then I simply restarted everything, the router, the CCM, even resetted the IP Phones. Not sure exactly what was wrong!!...


but anyway thank you all for your support. Appreciate the help.


Regards,

Ahmed El-Eraky

Actions

This Discussion