|Summary:||ASTERISK-18556: Call parking causes announcment and ringback to caller channel|
|Date Opened:||2011-09-14 21:00:54||Date Closed:||2011-09-15 11:44:42|
|Environment:||Fedora 13 x64||Attachments:|
|Description:||When using multiple call parking lots, announcements are being played to caller, rather than to callee. Ring back on timeout occurs to the caller channel rather than to the correct channel (the extension that actually parked the call).|
|Comments:||By: David Woolley (davidw) 2011-09-15 05:19:13.490-0500|
There isn't enough information here. However, if you are parking via a SIP blind transfer, this is expected hehaviour. I believe there may be some special code to direct announcements to the transferror if you use features.conf methods,
By: JoshE (n8ideas) 2011-09-15 07:39:13.981-0500
This is trivially reproducible and can be done via a SIP blind transfer to the parking lot extension or by a simple invocation of the Park() application after setting the channel variable.
I don't know in what universe a ring back to a caller channel (100% disconnect ratio for external callers) is acceptable or "expected behavior", but this one is broken - at least if you want a working parking application.
By: Richard Mudgett (rmudgett) 2011-09-15 10:46:30.052-0500
This is expected behavior.
The Park application has *one and only one* channel available. That channel is the channel being parked. The Park application can only send an announcement to the channel being parked. You can use the s option of Park to silence the announcement. You may also want to look into the ParkAndAnnounce application.
Performing a SIP blind transfer to park is not going to announce the parking space to the transferor because the transferor is no longer involved with the call. That is why it is called a blind transfer. If you are going to do a SIP transfer to the parking lot, you *must* do an attended transfer to hear the parking announcement.
By: JoshE (n8ideas) 2011-09-15 10:53:06.645-0500
I can live with the announcement being played to the caller. But you haven't addressed the ringback issue. The time out ring back happens onto the channel that was just parked. You can't tell me that is expected behavior. Doing a park between two internal extensions generates ringback on the second appearance of the person being parked. That is, without question, broken.
By: Richard Mudgett (rmudgett) 2011-09-15 11:44:42.551-0500
Reclosing in favor or the replacement issue ASTERISK-18562.