|
Home > Archive > Voice over IP Cisco > January 2006 > Meet Me won't die
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Cleaveland, AJ Allan @ IS 2006-01-13, 9:10 pm |
| 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
| |
| Erick Bergquist 2006-01-13, 9:10 pm |
|
Can you give more details? What do you mean by "won't
die"?
When you call the meet me # after the meet me is not
active, does it join meeting or do you get busy like
meet-me isn't open?
Or does it give error when someone tries to open the
meet-me bridge again via softkey?
What version CCM?
--- "Cleaveland, AJ Allan @ IS"
<Allan.J.Cleaveland@L-3com.com> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| |
| Wes Sisk 2006-01-13, 9:11 pm |
| 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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Cleaveland, AJ Allan @ IS 2006-01-13, 9:11 pm |
| The meet-me conference will not go away. All connections to it are removed
yet it is still up. It cannot be recreated because it's still in service
and if you dial into it you are connected just like a normal meet-me
conference. We're using 4.1.3.
-----Original Message-----
From: Erick Bergquist [mailto:erickbe@yahoo.com]
Sent: Tuesday, January 10, 2006 6:39 PM
To: Cleaveland, AJ Allan @ IS; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Meet Me won't die
Can you give more details? What do you mean by "won't
die"?
When you call the meet me # after the meet me is not
active, does it join meeting or do you get busy like
meet-me isn't open?
Or does it give error when someone tries to open the
meet-me bridge again via softkey?
What version CCM?
--- "Cleaveland, AJ Allan @ IS"
<Allan.J.Cleaveland@L-3com.com> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| |
| Cleaveland, AJ Allan @ IS 2006-01-13, 9:11 pm |
| 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@cisco.com]
Sent: Wednesday, January 11, 2006 8:06 AM
To: Cleaveland, AJ Allan @ IS
Cc: cisco-voip@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@puck.nether.net <mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip>
| |
| Wes Sisk 2006-01-13, 9:11 pm |
| "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@cisco.com]
Sent: Wednesday, January 11, 2006 8:06 AM
To: Cleaveland, AJ Allan @ IS
Cc: cisco-voip@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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Cleaveland, AJ Allan @ IS 2006-01-18, 5:45 pm |
| 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@cisco.com]
Sent: Thursday, January 12, 2006 12:54 AM
To: Cleaveland, AJ Allan @ IS
Cc: cisco-voip@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@cisco.com <mailto:wsisk@cisco.com> ]
Sent: Wednesday, January 11, 2006 8:06 AM
To: Cleaveland, AJ Allan @ IS
Cc: cisco-voip@puck.nether.net <mailto:cisco-voip@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@puck.nether.net <mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip>
| |
|
|
| Wes Sisk 2006-01-24, 5:47 pm |
| 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@cisco.com]
> *Sent:* Thursday, January 12, 2006 12:54 AM
> *To:* Cleaveland, AJ Allan @ IS
> *Cc:* cisco-voip@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@cisco.com]
> *Sent:* Wednesday, January 11, 2006 8:06 AM
> *To:* Cleaveland, AJ Allan @ IS
> *Cc:* cisco-voip@puck.nether.net
> <mailto:cisco-voip@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@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ------------------------------------------------------------------------
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Fretz, EA Eric @ IS 2006-01-24, 5:47 pm |
| 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@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Wes Sisk
Sent: Tuesday, January 24, 2006 8:38 AM
To: Cleaveland, AJ Allan @ IS
Cc: cisco-voip@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@cisco.com]
> *Sent:* Thursday, January 12, 2006 12:54 AM
> *To:* Cleaveland, AJ Allan @ IS
> *Cc:* cisco-voip@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@cisco.com]
> *Sent:* Wednesday, January 11, 2006 8:06 AM
> *To:* Cleaveland, AJ Allan @ IS
> *Cc:* cisco-voip@puck.nether.net
> <mailto:cisco-voip@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@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ----------------------------------------------------------------------
> --
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Fretz, EA Eric @ IS 2006-01-24, 5:47 pm |
| I am not sure what "Meet Me" you are talking about. "Meet Me" is a style of
conferencing provided by CallManager out-of-the-box...no extra purchase
necessary. If you have CallManager, you have everthing you need, unless you
want to do hardware transcoding (software conferene bridge provided with CCM
only supports G.711 codec). hardware transcoding/conference bridge requires
you have a router or Catalyst 6000/7200 series switch with certain DSP
modules installed to do the conversion.
A cisco 3800 series router with the -K9 voice package (basically IPVOICE
software with a PVDM2-64) can easily exceed $10,000.
--Eric
-----Original Message-----
From: Leetun, Rob [mailto:rleetun@co.boulder.co.us]
Sent: Tuesday, January 24, 2006 1:30 PM
To: Fretz, EA Eric @ IS
Subject: RE: [cisco-voip] Meet Me won't die
Hi Eric,
We are getting ready to purchase Meet Me. I would like to know your opinion
on the product. Thank you in advance.
Rob
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Fretz, EA Eric @ IS
Sent: Tuesday, January 24, 2006 11:40 AM
To: 'Wes Sisk'; Cleaveland, AJ Allan @ IS
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Meet Me won't die
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@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Wes Sisk
Sent: Tuesday, January 24, 2006 8:38 AM
To: Cleaveland, AJ Allan @ IS
Cc: cisco-voip@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@cisco.com]
> *Sent:* Thursday, January 12, 2006 12:54 AM
> *To:* Cleaveland, AJ Allan @ IS
> *Cc:* cisco-voip@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@cisco.com]
> *Sent:* Wednesday, January 11, 2006 8:06 AM
> *To:* Cleaveland, AJ Allan @ IS
> *Cc:* cisco-voip@puck.nether.net
> <mailto:cisco-voip@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@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ----------------------------------------------------------------------
> --
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Wes Sisk 2006-01-27, 8:48 pm |
| try changing from 'Never drop a conference when the originator leaves is
set.'. I suspect this may be your problem.
you can kill the conference w/o restarting CM.
1. restart the cisco IP Voice Media Streaming App service.
if that does not clear it
1. access the callmanager desktop
2. right click on my computer and select manage
3. select device manager
4. select view, show hidden devices
5. expand non-plug and play drivers
6. right click on cisco IP Voice Media Streaming Driver
7. select properties, then select the driver tab
8. stop the driver, then start it back.
This restarts the kernel mode driver that does the mixing for the
software conference bridge.
/Wes
Fretz, EA Eric @ IS wrote:[vbcol=seagreen]
> 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@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Wes Sisk
> Sent: Tuesday, January 24, 2006 8:38 AM
> To: Cleaveland, AJ Allan @ IS
> Cc: cisco-voip@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:
>
|
|
|
|
|