Release Notes for -- Linksys SPA-2102 5.1.6

2102 -- 2 Port FXS, 2 Ethernet Interface (10/100 support)

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
========================================

### Since 5.1.6 01/12/07 17:21:15 ###

 - Removed Polarity Reversal from the "DTMF(Denmark)" caller-id 
   method. Instead  added a new "DTMF(Denmark) With PR" caller-id
   method that behaves the same as the  old "DTMF(Denmark)" method.

 - "strict" dtmf tx mode works for AVT.  Before it only works for
   SIP info.For spa2100, the min. duration for dtmf detection is as
   follows: strict mode for AVT: 70 ms normal mode for AVT: 40 ms 
   strict mode for SIP info: 90 ms normal mode for SIP info: 50 ms

 - Added IVR option 1910,1920, 1911, 1921 to check and set SIP 
   transport setting  for Line 1 and Line 2

 - Accept %xx escape syntax in <NAT Keep Alive Msg> paramter. For 
   example  %0d%0a will be unescaped into \r\n (CRLF)

 - Allow each SIP message to be as large as 5119 bytes

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

### Since 5.1.6 01/12/07 17:21:15 ###

 - 5.1.x only: When doing rtp packet loopback, unit sends encapsulated
   RTP packets  but also normal audio packets with the same SSRC

 - Fixed this problem: Unit does not use the same Authorization header 
   fields in the ACK as   in the corresponding INVITE, per RFC 3261

 - Fixed this problem: If <SIP Transport> is set to TCP or TLS, unit  
   might not send keep alive messages properly when destination is 
   $PROXY

 - Fixed this problem: When <SIP Transport> is TCP/TLS, unit does not  
   include transport=tcp or transport=tls, respectively in the Contact 
   header's URI  in the 200 OK response to an re-INVITE request