[asterisk-bugs] [Asterisk 0011091]: autopark strange behaviour if canreinvite=update, nonat

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11091 
====================================================================== 
Reported By:                agx
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   11091
Category:                   Resources/res_features
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             10-26-2007 08:35 CDT
Last Modified:              01-15-2008 21:25 CST
====================================================================== 
Summary:                    autopark strange behaviour if
canreinvite=update,nonat
Description: 
The documentation says that re-invites are automatically disabled if a dial
option is included. If i try to call from SIP/13 to SIP/12 and i try to
park the call with *7 (autopark) i get a very strange behaviour:
- me (SIP/13) do not hear "701" that is the first extension slot;
- me (SIP/13) can still hear SIP/12 talking to me
- me (SIP/13) hear a low volume MOH as background;
- SIP/12 hear MOH

The call is started with: Dial(SIP/12|120|rtwkTWK)
i assume that this will disable re-invites.

The problem does not appear if in sip.conf i've canreinvite=no but only
when i use canreinvite=update,nonat

====================================================================== 

---------------------------------------------------------------------- 
 file - 01-15-08 21:25  
---------------------------------------------------------------------- 
I have confirmed that in latest versions this is all fixed. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-15-08 21:25  file           Status                   new => resolved     
01-15-08 21:25  file           Resolution               open => no change
required
01-15-08 21:25  file           Assigned To               => file            
01-15-08 21:25  file           Note Added: 0080735                          
======================================================================