conference issue (4 calls ) on CME 7

[Younes Chafi]

Hello everyone,

I have a worry at conference,

I have a 7.0 CME, I can not seem to put a conference with 4 calls, conference calls with 3 it works, but when I add another call he waits, and I can not put in existing conference I followed the documentation for creating conference, but no worries: (

Please can someone help me and explain to me the "Ad-hoc Conference and hardware conference."

here is my config and show:

voice-card 0

dspfarm

dsp services dspfarm

!

!

voice logout-profile 1

pin 1234

user 100 password 1111

number 100 type normal

!

voice logout-profile 2

pin 1234

user 101 password 2222

number 101 type normal

!

voice user-profile 1

pin 1234

user 200 password 1111

number 200 type normal

!

!

voice user-profile 2

pin 1234

user 201 password 2222

number 201 type normal

!

hw-module pvdm 0/0

!

hw-module pvdm 0/1

!

hw-module sm 1

!

!

!

!

interface GigabitEthernet0/0

description $ES_LAN$

ip address 172.16.3.1 255.255.0.0

ip flow ingress

duplex auto

speed auto

!

!

!

sccp local GigabitEthernet0/0

sccp ccm 172.16.3.1 identifier 1 priority 1 version 7.0

sccp

!

sccp ccm group 1

bind interface GigabitEthernet0/0

associate ccm 1 priority 1

associate profile 1 register CME-CONF

!

dspfarm profile 1 conference 

codec g711ulaw

codec g711alaw

codec g729ar8

codec g729abr8

codec g729r8

codec g729br8

maximum sessions 4

associate application SCCP

!

!

!

dial-peer voice 5500 voip

escription ** cue voicemail pilot number **

destination-pattern 550.

b2bua

session protocol sipv2

session target ipv4:172.16.3.2

dtmf-relay sip-notify

codec g711ulaw

no vad

!

!

!

telephony-service

sdspfarm units 5

sdspfarm tag 1 CME-CONF

max-ephones 58

max-dn 300

ip source-address 172.16.3.1 port 2000

system message CME-7-0

voicemail 5500

max-conferences 22 gain -6

!

!

!

!

ephone-template  1

!

!

ephone-template  20

conference add-mode creator

softkeys hold  Join Newcall Resume Select

softkeys idle  Redial Newcall Pickup ConfList Gpickup Join Login RmLstC

softkeys seized  Redial Endcall Cfwdall Pickup Gpickup Callback Meetme

softkeys connected  Hold Trnsfer Park Endcall Confrn ConfList Join Select RmLstC

!

!

ephone-dn  1  dual-line

number 200

label Poste-200

name Poste-200

corlist outgoing user-international

!

!

ephone-dn  2  octo-line

number 201

label Poste-201

name Poste-201

corlist outgoing user-international

!

!

!

ephone-dn  1  dual-line

number 200

label Poste-200

name Poste-200

call-forward busy 5500

call-forward noan 5500 timeout 30

corlist incoming user-international

corlist outgoing user-international

!

!

ephone-dn  2  dual-line

number 201

label Poste-201

name Poste-201

call-forward busy 5500

call-forward noan 5500 timeout 30

corlist incoming user-international

corlist outgoing user-international

ephone-dn  223

number 8000...

mwi off

!

!

ephone-dn  224

number 8001...

mwi on

!

!

!

ephone  31

mac-address YYYY.YYYY.YYYY

ephone-template 20

type 7962

keep-conference

logout-profile 1

!

!

!

ephone  32

mac-address XXXX.XXXX.XXXX

ephone-template 20

type 7962

keep-conference

logout-profile 2

!

!

!                          

------------------------------------------------------------------------------------

CME_CME-7-0#sh sccp

SCCP Admin State: UP

Gateway Local Interface: GigabitEthernet0/0

        IPv4 Address: 172.16.3.1

        Port Number: 2000

IP Precedence: 5

User Masked Codec list: None

Call Manager: 172.16.3.1, Port Number: 2000

Priority: 1, Version: 7.0, Identifier: 1

Conferencing Oper State: ACTIVE - Cause Code: NONE

Active Call Manager: 172.16.3.1, Port Number: 2000

TCP Link Status: CONNECTED, Profile Identifier: 1

Reported Max Streams: 32, 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

Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30

Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30

TLS : ENABLED

------------------------------------------------------------------------------------

CME_CME-7-0#sh sdspfarm units

conf-1 Device:CME-CONF TCP socket:[20]  REGISTERED in SCCP ver 17/10

actual_stream:32 max_stream 32 IP:172.16.3.1  12243  Conference Dixieland keepalive 134 

Supported codec:

                 G711Ulaw

                 G711Alaw

                 G729

                 G729a

                 G729b

                 G729ab

max-mtps:5, max-streams:0, alloc-streams:0, act-streams:0

------------------------------------------------------------------------------------

CME_CME-7-0#show dspfarm profile

Dspfarm Profile Configuration

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

Profile Description : 

Profile Service Mode : Non Secure

Profile Admin State : UP

Profile Operation State : ACTIVE

Application : SCCP   Status : ASSOCIATED

Resource Provider : FLEX_DSPRM   Status : UP

Number of Resource Configured : 4

Number of Resource Available : 4

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

[Nishant Savalia · Accepted solution]

Hi Younes,

You have configured conference but it seems you are not using hardware conference and infact software resources is being used which is limited to 3 calls.

Check by using "show sccp connections" for which resource is utilized.

Solution:-

telephony-service

conference hardware

exit

ephone-dn 3 octo

number A123

conference ad-hoc

exit

Regards,

Nishant Savalia

[Younes Chafi]

Thank's savalia for your reply,

but when I set the "conference hardware" option at the time the ipphone does not allow the conference

  and just a question, do I need to add another ephone-dn 3 to apply ad-hoc or I apply it on existing ephone-dn (1.2)?

because I already applied ad-hoc but on ephone-dn 1 and 2 but without result.

[Nishant Savalia]

No, you can not use existing ephone-dn 1 & 2 because they both are dual line and for conference it needs octo line.

And your conference hardware will work only if you have dn configured with octo line as an ad-hoc conference.

Regards,

Nishant Savalia

[Younes Chafi]

So i have to delete all the ephone-dn created, and I have to create with octo-line?

I have noticed when I use the conference ad-hoc command on a ephone-dn octo-line and I connect with the profile, it does not let me make a call, or make a transfer .... as if the phone is locked.

[Nishant Savalia]

No, you don't have to delete any dn.

Just configure one dn with octo line as conference ad-hoc and that dn you don't have to connect with any profile.

Regards,

Nishant Savalia

[Younes Chafi]

Thank you for your reply, I will test and come again unto you.

So if I understand it, is the configuration in telephony-service and dspfarm and creates a single ephone-dn octo-line for ad-hoc?

Just a question, I saw on another configuration they configure multiple ephone-dn octo-line for ad-hoc conference but with preference, why?

Thank you in advance for your help.

[Nishant Savalia · Accepted solution]

Multiple ephone-dn are created with preference so that you have can have multiple conference of 8 parties in each conference.

Actually you can have conference with dual-line also but only 2 parties can have conference i.e. one channel for one participant.

Regards,

Nishant Savalia

[Younes Chafi]

Thank you very much , it's working