[asterisk-bugs] [Asterisk 0010890]: When parking lot ring back times out, error is generated, line is hung up and timeout extension isn't reached.

noreply at bugs.digium.com noreply at bugs.digium.com
Thu Jan 3 12:47:02 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10890 
====================================================================== 
Reported By:                kenw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10890
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-04-2007 18:28 CDT
Last Modified:              01-03-2008 12:47 CST
====================================================================== 
Summary:                    When parking lot ring back times out, error is
generated, line is hung up and timeout extension isn't reached.
Description: 
The situation is repeated as follows:

1. Call is placed into parking lot
2. Call timesout from parking lot and rings back extension that put it
there to begin with
3. After http://bugs.digium.com/view.php?id=8#50 seconds of ringing back to
extension that placed the call in
the parking lot, the [park-dial] 't' extension should be invoked, instead
the following errors show up in the Asterisk-CLI:

[Oct  4 17:22:47] WARNING[7986]: chan_sip.c:12037 handle_response_invite:
Re-invite to non-existing call leg on other UA. SIP dialog
'224fe567089888351edffad76cdf16d9 at 10.200.26.202'. Giving up.
[Oct  4 17:38:18] WARNING[7986]: chan_sip.c:12536 handle_response: Remote
host can't match request CANCEL to call
'4c93b03d7f87f05950d21bd971edd97b at 10.200.26.202'. Giving up.

I'm not sure if this is a parking lot or SIP issue, but beings the errors
are from chan_sip.c I chose SIP Transfers.

I've attached CLI with debug & verbose set to 4 as well as sip debug
enabled.  I've also attached the parts of features.conf, extensions.conf &
sip.conf that apply.  Problem was noticed in 1.4.10.1, upgrade to 1.4.12
made no difference.

(1.4.12 not an option on Asterisk version btw).
====================================================================== 

---------------------------------------------------------------------- 
 aragon - 01-03-08 12:47  
---------------------------------------------------------------------- 
As per jvandal's note with some additional details provided:

The problem a few of us are having is that the park timeout does not
timeout to the correct context [default-local] instead of
[macro-default-dial] therefore the call forward busy and call forward no
answer rules are not followed (because the SIP device has no knowledge of
the proper forwarding contexts).
For example an extension has parked a call and then reached it's call
limit and then the park timeout returns the caller to the busy extension.
Since the SIP extension cannot accept more calls the caller is disconnected
and the call forward busy context is never invoked.

For us the only workaround is to set the park timeout to a ridiculous
timeout value so the timer is never invoked.

The timeout context seems to be the root cause and the forwarding rules
are not followed because of this.
When the caller is disconnected all kinds of evil things begin happening.
Here is a really good example from /var/log/asterisk/messages
Jan 2 15:33:01	chan_sip.c	ERROR	Call to peer '6003' rejected due to usage
limit of 1
Jan 2 15:33:05	chan_sip.c	WARNING	Maximum retries exceeded on transmission
717b6b7262fd92ea68ee81d262030648 at 192.168.30.254 for seqno 1 (Critical
Response)
Jan 2 15:33:11	pbx.c	WARNING	Timeout, but no rule 't' in context
'park-dial'

As per jvandal...
"If I watch for the ParkAndAnnounce option :

exten =>
7000,1,ParkAndAnnounce(pbx-transfer:PARKED|10|Local/console at default-app-callpark|default-local,${CALLERID(num)},1)

On Asterisk CLI, I've notice this log :

 == Parked SIP/6002-b7c04cc0 on 7001 at parkedcalls. Will timeout back to
extension [macro-default-dial] s, 6 in 10 seconds

and call is return to the SIP device, but we have specified a timeout
destination/return context (default-local,${CALLERID(num)},1) so output
must show something like :


== Parked SIP/6002-b7c04cc0 on 7001 at parkedcalls. Will timeout back to
extension [default-local], 6003, 1 in 10 seconds


I think the main issue is with the return_context" 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-03-08 12:47  aragon         Note Added: 0076259                          
======================================================================




More information about the asterisk-bugs mailing list