|Summary:||ASTERISK-00997: can't hear ringing or busy signal when calling from within a meetme conference|
|Reporter:||Matt Florell (mflorell)||Labels:|
|Date Opened:||2004-02-05 09:40:09.000-0600||Date Closed:||2011-06-07 14:10:48|
|Environment:||Attachments:||( 0) ring_events.txt|
|Description:||When I am in a meetme conference with another person and I send an Originate Action through the Manager interface to place a call from within the meetme conference I do not hear the ringing tone or any potential busy tones. This is annoying because you don't know if a phone is ringing on the other end or if it is busy it just never connects.|
I'm guessing that this was done intentionally, but I was wondering if there was a way to disable it.
If someone could point me at a different way of bringing a new outbound call into an existing meetme so that the meetme participants can hear the ringing of the new call. Or at the very least if there is a place in the code for meetme that could be changed on my installation so that the ringing could be heard that would be very helpful.
|Comments:||By: Brian West (bkw918) 2004-02-05 20:16:28.000-0600|
Show us the options you use for this... and what devices you are using ie zap/capi/sip what... and if you included the "r" flag on the orginate command or any of the dial commands for that matter.
By: Matt Florell (mflorell) 2004-02-05 20:39:31.000-0600
I'm actually not using any options that I know of. It's a straight meetme extension in the dialplan:
exten => 1234,1,meetme,1234
it doesn't matter if both parties already in the meetme conference are SIP/ZAP, ZAP/ZAP or SIP/SIP the new originated call that I call with the following manager action never rings, it just connects if the third party picks up:
Callerid: asterisk sample call
I would love to know how to add options to originate commands like this and what options are available. There isn't anything in the documentation or wiki about what options will work with Originate manager actions, a little list with examples would be wonderful.
By: Brian West (bkw918) 2004-02-06 00:10:41.000-0600
Try do the exten as the outbound number and the channel via chan_local. Do the exten as the outbound number and channel as Local/1234@default
or the reverse.
By: Matt Florell (mflorell) 2004-02-06 08:59:57.000-0600
That seems to work, although that does result in some strange <ZOMBIE> messages showing up when the call goes from RING to ANSWERED. I've posted the output file from the manager interface for the initiation of the call to when it hangs up.
It looks like Asterisk creates 2 separate Local/ channels while it is ringing and then when the call is picked up it kills them and renames the Zap/ channel for some reason. Is this normal? It seems like that ties up a lot of resources for what it is doing, not criticizing, just curoius.
By: Matt Florell (mflorell) 2004-02-06 09:15:35.000-0600
It's also strange that 3 call uniqueIDs are created in this process of calling as opposed to the reverse method that only creates one
By: Brian West (bkw918) 2004-02-07 20:13:05.000-0600
Yes its normal.. NEXT!! :P find me on IRC I have some of your other bugs I wanna go over.