[cisco-voip] Meet Me won't die

[Fretz, EA Eric at IS]

Wes,

No we do not use ICT.  The only H323 interaction is between a 3745 Router
(equipped with E&M ports) and CCM itself.  During testing, we registered CTI
Ports (via JTAPI) and used the CTI Ports as place holders to hold open a
Meet-Me conference.  When the conferences won't die, we have verified that
all H323/IP Communicator devices are out of the conference....  I have even
gone as far as to unregister the CTI ports.  If I try to respawn the
conference with IP Communicator (via the MeetMe button), I get a fast busy.
If I dial the conference number like a normal call, I am put into the
conference.  In this situation, the only way we have found to effectively
kill the conference is to cycle the CallManager service.  

Weird, huh?

Eric  

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wes Sisk
Sent: Tuesday, January 24, 2006 8:38 AM
To: Cleaveland, AJ Allan @ IS
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Meet Me won't die


do you use intercluster trunk (or other h323 device) and/or use IOS 
conferencing ?

<crickets>....

take a look at CSCsd07174 just recently filed and resolved

/Wes

Cleaveland, AJ Allan @ IS wrote:
> Never drop a conference when the originator leaves is set.  That's for
> normal conferences.  There is no meet-me setting I see.  None of which 
> even begins to address why a meet-me with no devices of any sort 
> attached to it would stay in existance ("alive").  Since this is an 
> intermittent problem, I doubt the settings (which haven't changed) 
> have anything to do with it.  Since we weren't using any FSX ports 
> during the testign in which ths occurred, they couldn't have failed.
>  
> Allan
>  
> PS:  Sorry about the delayed response.
>
>     -----Original Message-----
>     *From:* Wes Sisk [mailto:wsisk at cisco.com]
>     *Sent:* Thursday, January 12, 2006 12:54 AM
>     *To:* Cleaveland, AJ Allan @ IS
>     *Cc:* cisco-voip at puck.nether.net
>     *Subject:* Re: [cisco-voip] Meet Me won't die
>
>     "on"?  on my 4.1(3)sr2 system it has 3 options.  perhaps you have
>     an fxo port not detecting disconnect supervision?
>
>     /wes
>     On Jan 11, 2006, at 10:45 AM, Cleaveland, AJ Allan @ IS wrote:
>
>     That service parameter is on.  But the meet me conference is still
>     supposed to cease to exist after everything else is out of it as
>     well.  Most of the time this works correctly.
>
>         -----Original Message-----
>         *From:* Wes Sisk [mailto:wsisk at cisco.com]
>         *Sent:* Wednesday, January 11, 2006 8:06 AM
>         *To:* Cleaveland, AJ Allan @ IS
>         *Cc:* cisco-voip at puck.nether.net
>         <mailto:cisco-voip at puck.nether.net>
>         *Subject:* Re: [cisco-voip] Meet Me won't die
>
>         we recently added a service param to allow conferences to
>         exist after the conf initiator dropped.  what is the advanced
>         CM service param "drop ad hoc conference" set to?
>
>         /Wes
>
>         On Jan 10, 2006, at 12:21 PM, Cleaveland, AJ Allan @ IS wrote:
>
>         We have a problem where a meet me conference with no devices
>         attached to it does not go away.  Has anyone else encountered
>         this?  It seems to be an intermittent bug.
>          
>         Allan
>         _______________________________________________
>         cisco-voip mailing list
>         cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>         https://puck.nether.net/mailman/listinfo/cisco-voip
>
>     _______________________________________________
>     cisco-voip mailing list
>     cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>     https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-voip
>