Conference not dropped when initiator hangs up

Answered Question
May 30th, 2010
User Badges:

We have a new deployment of a UC560 and are having issues with the remote parties not being dropped when the call initiator hangs up.

If I'm internal and call client X and then conference in client B if I hang up client X and client B are still connected using eating up 2 of our lines while they potentially talk to each other.  We have tested just hanging up the phone and hitting the end call with the same results.  We would like all parties in the conference to be dropped if there are no local (Internal) left on the call if possible, otherwise if the initiator hangs up then all parties are dropped.


I've pasted some output below from our config.  Please let me know if you need any additional information to help diagnose the issue.  Thanks in advance for the help!


===============================================================================
sh dspfarm all
===============================================================================
Dspfarm Profile Configuration

Profile ID = 1, Service = CONFERENCING, Resource ID = 1 
Profile Description : DO NOT MODIFY, active CCA conference profile - CCA2.0 codec711
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 : 16
Number of Resource Available : 16
Codec Configuration
Codec : g711ulaw, Maximum Packetization Period : 30 , Transcoder: Not Required
Codec : g711alaw, Maximum Packetization Period : 30 , Transcoder: Not Required


SLOT DSP VERSION  STATUS CHNL USE   TYPE    RSC_ID BRIDGE_ID PKTS_TXED PKTS_RXED

0    5   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    5   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    5   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    5   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    6   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    6   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    6   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    6   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    7   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    7   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    7   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    7   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    8   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    8   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    8   26.6.0   UP     N/A  FREE  conf   1      -         -         -       
0    8   26.6.0   UP     N/A  FREE  conf   1      -         -         -      

Total number of DSPFARM DSP channel(s) 16



===============================================================================
sh sccp all
===============================================================================
SCCP Admin State: UP
Gateway Local Interface: Vlan90
        IPv4 Address: 10.1.10.2
        Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 192.168.200.1, Port Number: 2000
  Priority: N/A, Version: 4.0, Identifier: 1
  Trustpoint: N/A

Conferencing Oper State: ACTIVE - Cause Code: NONE
Active Call Manager: 192.168.200.1, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 1
Reported Max Streams: 256, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
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


SCCP Application Service(s) Statistics:

Profile Identifier: 1, Service Type: Conferencing
TCP packets rx 14212, tx 13822
Unsupported pkts rx 0, Unrecognized pkts rx 0
Register tx 3, successful 3, rejected 0, failed 0
Unregister tx 2, successful 0
KeepAlive tx 13706, successful 13706, failed 0
OpenReceiveChannel rx 99, successful 99, failed 0
CloseReceiveChannel rx 99, successful 0, failed 0
StartMediaTransmission rx 99, successful 99, failed 0
StopMediaTransmission rx 99, successful 0, failed 0
PortReq rx 0
PortRes tx 0, successful 0, failed 0
PortClose rx 0
QosListen rx 0
QosPath rx 0
QosTeardown rx 0, send 0, recv 0, sendrecv 0
QosResvNotify tx 0, send 0, recv 0, sendrecv 0
QosErrorNotify tx 0, send 0, recv 0, sendrecv 0
   err0 0, err1 0, err2 0, err3 0, err4 0, err5 0,
   err6 0, err7 0, err8 0, err9 0, err10 0, err11 0,
   err12 0
QosModify rx 0, send 0, recv 0, sendrecv 0
UpdateDscp rx 0
Reset rx 2, successful 2, failed 0
MediaStreamingFailure rx 99
MediaStreamingFailure tx 0
Switchover 0, Switchback 0

CCM Group Identifier: 1
Description: None
Binded Interface: None
Associated CCM Id: 1, Priority in this CCM Group: 1
Associated Profile: 1, Registration Name: confprof1
Registration Retries: 3, Registration Timeout: 10 sec
Keepalive Retries: 3, Keepalive Timeout: 30 sec
CCM Connect Retries: 3, CCM Connect Interval: 10 sec
Switchover Method: GRACEFUL, Switchback Method: GRACEFUL_GUARD
Switchback Interval: 10 sec, Switchback Timeout: 7200 sec
Signaling DSCP value: cs3, Audio DSCP value: ef


Total number of active session(s) 0, and connection(s) 0


Total number of active session(s) 0, and connection(s) 0


Total number of active session(s) 0, connection(s) 0, and callegs 0

SCCP Application Service(s) Statistics Summary:
Total Conferencing Sessions: 0, Connections: 0
Total Transcoding Sessions: 0, Connections: 0
Total MTP Sessions: 0, Connections: 0
Total ALG-Phone Sessions: 0, Connections: 0
Total BRI-Phone Sessions: 0, Connections: 0
Total SCCP Sessions: 0, Connections: 0


Total active sessions 0, connections 0, rsvp sessions 0
Statistic                  Count
-------------------------  -----------
Send queue enqueue error   0
Socket send error          94
Msgs discarded upon error  54



===============================================================================
sh run pieces
===============================================================================

!
stcapp ccm-group 1
stcapp
!
stcapp feature access-code
!

sccp local Vlan90
sccp ccm 192.168.200.1 identifier 1 version 4.0
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register confprof1
!
dspfarm profile 1 conference 
description DO NOT MODIFY, active CCA conference profile - CCA2.0 codec711
codec g711ulaw
codec g711alaw
maximum conference-participants 16
maximum sessions 16
conference-join custom-cptone CCAjointone
conference-leave custom-cptone CCAleavetone
associate application SCCP
!
!
telephony-service
sdspfarm conference mute-on 111 mute-off 222
sdspfarm units 5
sdspfarm tag 1 confprof1
conference hardware

Correct Answer by David Harper about 6 years 11 months ago

The CLI that Dave Trad is hunting for is the 'conference drop-mode ...' and 'keep-conference ...' commands - both found under the ephone config.  Setting of these options is not currently supported in CCA, so you will have to use CLI to apply these, and you will need to be careful using CCA afterwards as it will remove these commands if you make changes to the phones.  But bearing all that in mind, you should be fine.  The documentation for these commands can be found at:


http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_c1ht.html#wp1102971

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_k1ht.html#wp1013267


Have a read of both those pages and you'll see that you have quite a few options available to you here.


Cheers,

Dave.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
David Trad Sun, 05/30/2010 - 14:46
User Badges:
  • Gold, 750 points or more
  • Cisco Designated VIP,

    2013 Small Business

Hi Data Path,



Can you please post your Conference DN's and also your Ephone templates as well.


There is a setting that you can enable (Turn on or Off I guess) that ends a conference bridge when the administrator hangs up, it will come to me soon which one it is, but for the time being can you post those two things.




Cheers,



David.

Correct Answer
David Harper Sun, 05/30/2010 - 18:10
User Badges:
  • Cisco Employee,

The CLI that Dave Trad is hunting for is the 'conference drop-mode ...' and 'keep-conference ...' commands - both found under the ephone config.  Setting of these options is not currently supported in CCA, so you will have to use CLI to apply these, and you will need to be careful using CCA afterwards as it will remove these commands if you make changes to the phones.  But bearing all that in mind, you should be fine.  The documentation for these commands can be found at:


http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_c1ht.html#wp1102971

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_k1ht.html#wp1013267


Have a read of both those pages and you'll see that you have quite a few options available to you here.


Cheers,

Dave.

DataPathInc Sun, 05/30/2010 - 19:07
User Badges:

Thanks David T. and David H.!


Here is the ephone-template:


ephone-template  16
softkeys remote-in-use  CBarge Newcall
softkeys idle  Redial Cfwdall Dnd Login Mobility Pickup Gpickup Newcall
softkeys seized  Cfwdall Meetme Redial Pickup Endcall Gpickup Callback
softkeys alerting  Callback
softkeys connected  Trnsfer Confrn Park RmLstC ConfList Mobility LiveRcd Flash TrnsfVM Endcall
keep-conference local-only
!


I just added the keep-conference local-only this afternoon to the template.  I'm going to go by the office and test it real quick.  I'm going to grab a couple SPA525g's so I can test them from home without having to go back into the office.  I will try to post in the next couple hours wheter it worked or not.  Thanks for the heads up about CCA.  We have already worked with someone from Cisco to do some other cool tweaks to the sytem that prevent us from using the Voice tab in CCA or it will wipe out some settings as well.  We are able to use the rest of CCA though.


Here are the conference DN’s for both MeetMe and Ad-Hoc
!
ephone-dn  558  octo-line
number 772 no-reg primary
name Meet Me Conf Bridge 2
conference meetme
preference 1
!
!
ephone-dn  559  octo-line
number 772 no-reg primary
name Meet Me Conf Bridge 2
conference meetme
no huntstop
!
!
ephone-dn  560  octo-line
number 771 no-reg primary
name Meet Me Conf Bridge 1
conference meetme
preference 1
!
!
ephone-dn  561  octo-line
number 771 no-reg primary
name Meet Me Conf Bridge 1
conference meetme
no huntstop
!
!
ephone-dn  562  octo-line
number C0014 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  563  octo-line
number C0014 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  564  octo-line
number C0013 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  565  octo-line
number C0013 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  566  octo-line
number C0012 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  567  octo-line
number C0012 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  568  octo-line
number C0011 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  569  octo-line
number C0011 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  570  octo-line
number C0010 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  571  octo-line
number C0010 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  572  octo-line
number C009 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  573  octo-line
number C009 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  582  octo-line
number C008 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  583  octo-line
number C008 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  584  octo-line
number C007 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  585  octo-line
number C007 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  586  octo-line
number C006 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  587  octo-line
number C006 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  588  octo-line
number C005 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  589  octo-line
number C005 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  590  octo-line
number C004 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  591  octo-line
number C004 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  592  octo-line
number C003 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  593  octo-line
number C003 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  594  octo-line
number C002 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  595  octo-line
number C002 no-reg primary
conference ad-hoc
no huntstop
!
!
ephone-dn  596  dual-line
number C001 no-reg primary
conference ad-hoc
preference 1
!
!
ephone-dn  597  dual-line
number C001 no-reg primary
conference ad-hoc
no huntstop
!

DataPathInc Sun, 05/30/2010 - 19:11
User Badges:

I just added the conference drop-mode local to the ephone template as well.  Do I need both the conference drop-mode and the keep-conference commands in the template?  Just curious what the difference is between them.  I'm off to go test!

DataPathInc Sun, 05/30/2010 - 20:39
User Badges:

I tested and it is working as it should with the configuration.  When there are no local parties left on the call it is dropping everyone else.  Thanks so much for the help!

David Harper Sun, 05/30/2010 - 20:43
User Badges:
  • Cisco Employee,

My previous reply must have passed your in the ether.   Glad to hear it is all working ok.


Cheers,

Dave.

DataPathInc Sun, 05/30/2010 - 20:45
User Badges:

Yes, it must have!  I just marked this as answered.  Now I have to figure out why some of our phones can make ad-hoc conference calls and some can't, but I'll start a new thread for that.

David Harper Sun, 05/30/2010 - 20:41
User Badges:
  • Cisco Employee,

The different commands enable slightly different behaviours. The conference drop-mode command will, depending on what keywords you specify, drop the conference either when the initiator leaves, or when the last local phone leaves.  The keep-conference CLI controls what happens with the last two members of a conference when the third-last party drops off.  Again, there are a few subtle variations here as well.


Your best bet is to read the documentation carefully, and then test out the different behaviours to make sure you get exactly the behaviour you want.


Cheers,

Dave.

Actions

This Discussion

Related Content