Release Notes for -- Linksys PAP2/PAP2T 5.1.6

PAP2 -- 2 Port FXS, 1 Ethernet Interface
PAP2T -- 2 Port FXS, 1 Ethernet Interface

Copyright (C) 2007 by Linksys, a Division of Cisco Systems, Inc.

All Rights Reserved.

* * * * * * * * * * IMPORTANT * * * * * * * * * * * * * * * *  *
* Use of Proprietary Information and Copyright Notice:         *
* This release note document contains proprietary information  *
* that is to be used only by Sipura Technology, Linksys(R),    *
* and Cisco Systems, Inc. customers.  Any unauthorized         *
* disclosure, copying, distribution, or use of this            *
* information is prohibited. This restriction includes         *
* ALL Internet based discussion forums, e.g. DSLreports.       *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *  *

/** NOTICE **/
official release

========================================
	New Features
========================================

--- External Notes ---

 - If REGISTER results in a 301 response with a Contact header 
   that has a maddr URI parameter,  and if the <Outbound Proxy> 
   is an IP address, the SPA will change the outproxy proxy 
   address to the  value of the maddr address. This value will 
   remain valid until the next 301 response, if any, or will 
   restore  to the originally configured value upon reboot.

 - When swapping calls in a call-waiting or similar situation, 
   the SPA will order the operations to make sure that call hold 
   is invoked before call resume.

 - New RC blink pattern. Power LED red-orange slow blink while 
   contacting server.  Red-orange double blink if file not found 
   or  corrupt.

 - 1. Make DHCP DISCOVER retry longer (120 Seconds)2. Reboot the 
   device in 10 minutes if the device is using last konwn good 
   IP address.

========================================
	Bug Fixes
========================================

--- External Notes ---

 - SDP in INVITE response, includes annexb=yes/no if present in 
   INVITE message

 - Fixed this problem: A,B,C,D digits are dropped when dialing

 - SPA should escape occurrences of '#' in the dial string with 
   %23 in outbound INVITE

 - Fixed this problem: Unit stops playing incoming RTP audio once  
   it receives a 180/183 w/o SDP; regardless setting of <Sticky 183> 
   parameter

 - bug fix: Bogus IP may be used if dns srv failed when querying 
   the proxy server.

 - Worked around this problem: some server will change the Contact 
   header's  address in their response to the SPA's SIP REGISTER 
   request, so that the SPA cannot find the  corresponding Contact 
   in the response and therefore may not be able to extract the  
   proper expires value inserted by the server. This is a problem 
   if the expires  value inserted by the server in the response is 
   smaller than the value in the original  SIP REGISTER request. 
   The work around is to use the first entry in the Contact header 
   if  an exactly matching address is not found.

 - Fixed this problem: If unknown response is received, such as 101, 
   SPA  might misinterpret it as a 6xx response. In some other cases, 
   an unknown response, such as 188, might be dropped by the SPA as 
   a bad message. The proper way is to treat it  as the corresponding 
   base response, such as 100.

 - Fixed this problem: Daylight Saving Time is not correct if start 
   time is later then end time of the year in the <Daylight Saving 
   Time Rule> parameter

 - Fixed this problem: Unit should ignore in-dialog re-INVITE if it 
   has not received ACK to the 200 response to the initial INVITE 
   from the caller. This condition might happen if the ACK was lost 
   but the first re-INVITE has already been  sent by the peer.

 - Fixed this problem: Unit should not filter out leading * or #  
   digit in the incoming caller id number, as these can be legitimate 
   phone number  digits

 - Fixed this problem: PAP2T cannot detect DTMF digits at 50ms on/off  
   during a call, even if <DTMF Tx Mode> is "normal". 

 - Fixed missing '*' and '#' in on-hook caller-id number generation

 - Eliminated cause of spurious reboot on resync for  customized units 
   with read-only parameters and value mismatch.
