SmartWare R5.T Release Notes

Transcription

1 Patton Electronics Company, Inc Rickenbacker Drive Customer Deliverable Documentation Revision 1.00, December 12, 2011 Gaithersburg, MD USA Tel. +1 (301) Fax +1 (301) SmartWare R5.T Release Notes Build Series SmartWare is the embedded application software of the SmartNode series of VoIP Gateways and Gateway Routers. SmartWare provides a full set of IP routing features, advanced Quality of Service and traffic management features plus industry leading Voice over IP functionality including SIP and H.323 Released Build Numbers SmartNode 4110 Series R5.T Build SmartNode 4300 Series R5.T Build SmartNode 4400 Series R5.T Build SmartNode 4520 Series R5.T Build SmartNode 4630 Series R5.T Build SmartNode 4830 Series R5.T Build SmartNode 4900 Series R5.T Build SmartNode 4940 Series R5.T Build SmartNode 4950 Series R5.T Build SmartNode 4960 Series R5.T Build SmartNode 5200 Series R5.T Build SmartNode 5400 Series R5.T Build SmartNode 4552 R5.T SIP Build SmartNode 4554 R5.T SIP Build Smart-DTA R5.T SIP Build About this Release R5.T is a SmartWare Technology Release. Please see the White Paper about SmartWare software releases for more information about this terminology Patton Electronics Company. All Rights Reserved. Copying of this document or parts of it is prohibited.

2 Supported Products SmartNode 4110 Series (HW Version: 1.x, 2.x, 4.x) SmartNode 4300 Series (HW Version: 2.x) SmartNode 4400 Series (HW Version: 2.x) SmartNode 4520 Series (HW Version: 1.x, 2.x, 4.x) SmartNode 4552, 4562 Series (HW Version: 4.x, 5.x) SmartNode 4554, 4564 Series (HW Version: 4.x, 5.x) SmartNode 4600 Series (HW Version: 1.x) SmartNode 4600 Large Series (HW Version: 1.x, 2.x) SmartNode 4830 Series (HW Version: 1.x, 2.x, 4.x) SmartNode 4830 Large Series (HW Version: 1.x, 2.x) SmartNode 4900 JS Series (HW Version: 1.x, 2.x) SmartNode 4900 JO Series (HW Version: 1.x) SmartNode 4940 Series (HW Version: 5.x) SmartNode 4950 Series (HW Version: 5.x) SmartNode 4960 Series (HW Version: 1.x, 2.x, 3.x, 4.x, 5.x) SmartNode 5200 Series (HW Version: 5.x) SmartNode 5400 Series (HW Version: 5.x) Smart-DTA Series (HW Version: 4.x, 5.x) Rev /36

3 History of Solved CTS Cases The following list refers to open cases in the Change Tracking System 'CTS'. This Build Series Fixed T.38 packets traffic-class T.38 packets were sent using the default traffic-class instead of local-voice. Therefore they were sent through the wrong path when traffic-class default and local-voice were using different paths HTTP User Agent enhancement From now on all HTTP requests sent out by SmartWare will have an enhanced User-Agent header. Earlier this header only contained the SmartNode keyword. Now this header content has been enhanced to contain the following additional descriptions of the SmartNode: Model, Serial Number, Software Version and Hardware version G.SHDSL power and reset spikes During boot phase of the SN4600 series some spikes/glitches were observed on the reset and power pins connected to the DSL interface. Such behavior could cause damage to the DSL interface in very rare cases. This problem has now been fixed. On the SN4960/SN4950/SN4940 series this erroneous behavior has not been observed Syslog-client no remote command crash When two or more remote destinations exist in the syslog-client configuration and the first remote that has been added is removed, any subsequent removal of another remote would cause a crash. This has been fixed Fixed display of mtu and mru max values in running-config The max values of mru and mtu in profile ppp were not displayed by the command show running-config Timestamp enhancement for milliseconds Now milliseconds can be added to all syslog packets and radius vendor specific attributes in the following format: HH:MM:SS:msmsms. It can be configured whether milliseconds appear or just seconds. Refer to the section New Configuration Commands for a detailed description Missing facility from running-config When two remote destinations exist in the syslog-client configuration and facilities are added to both remote hosts only the last one is visible in the running-config. This has been fixed. Rev /36

4 Build Series Improved configuration and display of bit rate for 4-wire G.S interface The handling of the bit rate for the 4-wire G.S interface has been changed at three levels which are detailed below: 1. Enhanced display of bit rate. Differentiation between line rate and payload rate. 2. Configuration now takes the payload rate instead of the line rate 3. Some unused bit rates have been removed Bit rate definitions The bit rate of a DSL connection can be given with two different references which may create confusion. The line rate is the total physically available bit rate on the line. However this also includes some overhead that is not usable for the actual payload data. This overhead is equal to 8 kbps per single pair (i.e. 2-wire) connection. This is why the payload data rate is defined to represent the actual bit rate available for payload data. The definition of the bit rate for a 2-wire connection is this: payload data rate = line rate 8 kbps The definition of the bit rate for a 4-wire connection is this: payload data rate = line rate 16 kbps According to the ITU-T standard G the payload data rate is divided into a base data rate and a sub-data rate. The former specifies the data rate in 64 kbps increments and the latter adds 8 kbps increments on top. The formula to calculate the possible payload rates is defined as: N * 64 kbps + I * 8 kbps, where 3 <= N <= 89 and 0 <= I <= Enhanced display of bit rate The show dsl line-state command displays the negotiated bit rate among other values. In previous version of SmartWare this would only display the line rate and call it Actual Bitrate : Actual Bitrate : 2312 kbps In this new version both, the line rate and the payload rate are displayed: Line Rate Payload Rate : 2312 kbps : 2304 kbps This example shows the values in case of a 2-wire connection. In case of a 4-wire connection these values become: Line Rate : 4624 kbps Rev /36

5 Payload Rate : 4608 kbps 2. Configuration of payload rate Configuration of the bit rate on a dsl port needs to be given as the payload data rate using the new command payload-rate. The old command bit-rate has been removed. However the old command is still accepted for backwards compatibility with configuration created with earlier version of SmartWare. Please refer to the new commands section for details. 3. Removed bit rates Older versions of SmartWare supported various bit rates with values of i > 0 and n < 3. All these bit rates have been removed. Now SmartWare only supports payload rates with n >= 3 and i = 0. New payload rate configuration overview The following table gives an overview of the previous line rate (bit-rate) configuration and the new available payload rates. bit-rate (old) payloadrate (new) bit-rate (old) payloadrate (new) bit-rate (old) payloadrate (new) bit-rate (old) payloadrate (new) 72 n/a 720 n/a n/a 80 n/a n/a n/a 784 n/a n/a 144 n/a n/a n/a n/a 208 n/a n/a n/a n/a 272 n/a n/a n/a n/a 336 n/a n/a 2368 n/a n/a n/a 400 n/a n/a n/a n/a 464 n/a n/a 3392 n/a n/a n/a n/a 3840 n/a n/a n/a n/a 5056 n/a n/a n/a n/a 5696 n/a n/a Note that when upgrading to this SmartWare version and the configuration contained a bit-rate that is not supported anymore, then the configuration after bootup defaults to adaptive bit rate HTTP 302 Redirection now supported for provisioning Smartware is now able to handle HTTP 302 responses correctly. When an http location is configured for provisioning and the server responds with a HTTP 302, SmartWare will read the Rev /36

6 LOCATION header and retry to download the provisioned configuration from the new destination. No special configuration commands are needed for this. This is a built-in feature Additional parameters in G.SHDSL status: SNR, Loop Attenuation, Port States The DSL interface now also provides values for the SNR, Loop Attenuation and Port State parameters. These values are displayed using the show dsl line-state or show dsl all commands. The correct display of these values is supported by the version G06 of the G.S software Fixed police traffic class configuration option When using the police input rate limiting option in any of the traffic class definitions of a service policy profile ( profile service-policy <name> command, sub-mode source traffic-class <class> ) this would result in the whole profile becoming unusable. The profile definition would be accepted, but attempting to bind it would fail without an error message. This was a bug that has now been fixed RTP payload type configuration RTP payload type used for transparent and transparent-cisco codec can be now configured in the same way as for transparent-clearmode codec. Refer to the section New Configuration Commands for a detailed description Received maddr parameter is reflected in contact header SmartWare would copy the maddr parameter from the REQUEST URI of any received INVITE to the contact header of the response. This is wrong and has been completely removed Wrong factory-config for SN products with DSL The SN4600 large series and the SN4830 large series got provided a wrong factory configuration with the software delivery. This could lead to no or wrong connectivity when factory restoring such devices. These products get now a separate delivery providing the correct factory configuration. Build Series PPP: configurable check for magic number in LCP messages A new configuration option to enable/disable the validity check for the Magic Number in received LCP messages has been added. Refer to the section New Configuration Commands for a detailed description Invalid Re-INVITE in SIP-to-SIP hold scenario When issuing a HOLD request using the direction attribute in the SDP message of the Re- INVITE, the SmartNode would interpret the direction attribute in the 200 OK response as another HOLD request in the opposite direction. Consequently it issued another HOLD request Rev /36

7 to the other peer as well, which is incorrect. This behavior has now been corrected and the invalid Re-INVITE in the opposite direction has been eliminated Clock offset problem when non-full hour is specified With the command clock local, when specifying a clock offset that was not a full hour, the system would incorrectly interpret the minutes part (e.g. +09:30 would be stored as +09: ). This has been fixed user and phone-context parameters handled in all cases Previously the "user" and "phone-context" parameters had only been looked up in the identities of the location-service if the numbers had explicitly been labeled as E.164. This is not the case for e.g. fix address-translation which can set any type of user part in the URI, not only E.164. This behavior has now been changed to allow adding "user" and "phone-context" parameters in all cases. This has been implemented for the From-Header, the To-Header and the Request URI Missing information if output on CLI over telnet is very large (typically for show commands) The SmartNode did have a limitation when the output that needs to be sent over a telnet connection becomes larger than 64 kbytes. Typically this limitation would have the consequence that larger output of show commands can have missing pieces in the middle of the message. This limitation has been removed One-way voice in FXS hold scenario In a scenario having a SmartNode between an FXS connection and a SIP softswitch, when the SmartNode would get from the SIP side a 200 OK message with a zero IP in the SDP part, it would put the FXS side on hold, but would not un-hold it when receiving the un-hold from the SIP side. This has been fixed Warning against power-feed option on BRI port with point-to-point protocol Using power-feed on BRI ports using point-to-point protocol is generally not recommended and can lead to instable links. Therefore a warning has been added to the help text of the powerfeed command against using power-feed together with point-to-point protocol Enable digit collection while the stutter dial tone is played on an FXS interface On the SmartNode s FXS interfaces a waiting message can be indicated with a stutter dial tone using the command message-waiting-indication stutter-dial-tone. Previously the SmartNode would not accept any dialed digits while playing the stutter dial tone for 3 seconds. This behavior has been changed and the SmartNode now accepts dialed digits while the stutter dial tone is being played. Once the first digit has been detected, the stutter dial tone is stopped as it is also the case for the normal dial tone. Rev /36

8 11595 Acceptance of SIP AOC messages from Genband with content type application/vnd.cirpack.isdn-ext Genband sends AOC messages in SIP INFO packets using the content type application/vnd.cirpack.isdn-ext. The actual content is identical to application/qsig. The SmartNode now supports both content types and handles them accordingly No alerting tone on FXS port when first call is on hold On an FXS port a first call is established. When now this first call is put on hold and a second call is being established, then no alerting tone was being played by the SmartNode on the FXS port. This has been corrected and the alerting tone is also played for the second call. Build Series Error on Web Interface of SN4554 The SN4554 was mistakenly enabled to switch from Advanced GUI to Basic GUI. Trying to configure the Call Services on SN4554 after switching from Advanced GUI to Basic GUI created an error. This has been fixed by removing the Basic GUI feature on SN Broken T.38 connection If between the SIP voice call establishment and the T.38 re-negotiation the SmartNode never received some RTP packets, T.38 connection was broken and the FAX transmission failed. This was only the case if the SmartNode was the originator of the call and T.38 re-negotiation had been issued by the called device Broadsoft SIP Session Audit: SDP version must remain unchanged See SIP Session Timer: SDP version must remain unchanged The SmartNode increased the SDP version (i.e. the version in the o= line in the SDP) in every 200 OK message in reply to a Re-INVITE. The standard (RFC 3264, Ch. 8, p. 12) defines that the version MUST increment when the session is modified and that the SDP MUST be identical if the version does not increment. It does not specify however whether the version MAY increase even if the session is not modified. This third case had not been considered by the SmartNode because the standard does not say anything about it. It would always increase the version even if the session is not modified. This behavior has now been modified. Whenever the session is not modified the SmartNode does not increase the version anymore. One particular case where this is of importance is in 200 OK messages to Re-INVITEs from the session timer Border Gateway Protocol Rev /36

9 The Border Gateway Protocol (BGP) according to RFC4271 is implemented and functional. Refer to the section New Configuration Commands for detailed explanation DSL Modem Supervisor The DSL modem supervisor in its boot mode behaves slightly differently from the way it used to. Instead of stopping to monitor the modem as soon as it has started and been configured, it will now check the line state until that is reported as OK once; only then will the supervisor cease to operate and leave the modem alone The bit rate in 4 wire mode displaying only one DSL link bit rate Whether in 4 wire mode or 2 wire mode, the actual bit rate that was displayed on DSL-enabled SmartNodes was the bit rate retrieved from a single DSL link. Now, when in 4 wire mode, the displayed bit rate represents the DSL bit rate of both links together DSL configuration on the Web Interface The current commands on the CLI for the dsl port are configurable from the web interface for the DSL-enabled SmartNodes: supervisor, service-mode, bit-rate and annex-type Additional information for the DSL status Statistical values have been added to the displayed DSL status provided when executing the show dsl all command on DSL-enabled SmartNodes: Cell Delineation: LOSW Errors: CRC Errors: number of correct HEC* calculations assumed to indicate cell boundaries Number of loss of signal defect errors. Three or more consecutively received frames contained one or more errors in the framing bits. Number of cyclic redundancy check errors Segments Anomaly: Number of segment anomaly errors. A regenerator operating on a segment received corrupted data Last State Failing: Cells Received: Cells Dropped: The last state reached by the device following startup but before startup fails. Each int value has a different meaning as specified on the table below Number of UTOPIA cells received Number of UTOPIA cells dropped HEC Cells Received: Number of UTOPIA cells received having HEC* errors Cells Transmitted: Number of UTOPIA cells transmitted *HEC stands for header error checksum field found in the ATM cell header Table: Values of the Last State Failing Last State Failing Field Value Rev /36

10 No Startup Preactivation Activation Check Bit rate Transmit Receive Wait for ARP CO Line AGC FD EC Training Equalizer Training Tip Ring Aligned Load 0x00 0x01 0x04 0x07 0x30,0x32,0x34,0x36, 0x38,0x39,0x45,0x47,0x4A 0x31,0x33,0x46,0x49,0x4B 0x35 0x40,0x41 0x42 0x43 0x44 0x80,0x81,0x82,0x83,0x90, 0x91,0x92,0x93,0xA0,0xA1,0xB0,0xB1 Build Series Web GUI: Removed unnecessary note and fixed check for running VoIP gateways on software import page The SmartNode has some integrated web pages that are used if the standard web pages are not found during an update procedure. On the software import page one of the download steps referred to the interface card firmware. These interface cards do not exist anymore on SmartNodes supported by the current SmartWare. Thus, this notice is unnecessary and has been removed. Additionally the check for running VoIP gateways has not been working on these integrated pages. This has been corrected as well Accepting re-invite after reboot A SmartNode rebooted while having an open call, and for this call a re-invite was sent from the remote device. The SmartNode treated this re-invite as an initial invite and initiated a new call, because after the reboot the existence of the previous and ongoing call was lost. That behavior is wrong, and the re-invite has to be rejected. There is no possibility to recreate the call state as it was before the reboot. To distinguish the re-invite from an initial invite SmartWare examines if a header-parameter tag is present in the To header. If that To-tag is present and the re-invite does not match to any ongoing call, it is rejected with a 481 Call/Transaction Does Not Exist answer. For backward compatibility it is possible to disable this new behavior with a command Configurable packetisation time for Fax/Modem bypass Previously the SmartNode automatically selected a packetisation time for fax/modem bypass depending on the configuration of voice codec, the voice codec packetisation time and the configured fax/modem bypass method. The selected value could be either 10ms or 20ms. Rev /36

11 To have a consistent behavior the packetisation time for fax/modem bypass can now be configured. See more details in the chapter new configuration commands SIP Peer Flood Blocking SmartWare's SIP application can now be configured to prevent SIP packet flooding. This is useful to defend against SIP attacks of any sort where lots of SIP packets are being received from the same peer with-in a short period of time. Disabled by default, this new feature can be enable using a simple "switch"-style command, and fine-tuned with a separate configuration command Proper termination of call during outgoing re-invite During an established call SmartWare sent a re-invite to the remote side and is waiting for an answer to the re-invite. When in that state the local connected device wants to release the call, the re-invite was canceled, and the call was considered as terminated. This is not correct because the cancel terminates only the re-invite and the call itself remains in connected state after the re-invite is terminated. Therefore the ongoing call itself needs to be terminated after the canceling of the re-invite with sending a BYE request, which is the new and corrected behavior Crash in hold scenario in SIP-to-SIP setup In a SIP-to-SIP scenario the issuing of a re-invite to one side of the call could cause an undesired re-invite to be issued to the other side as well depending on the exact state of the codec negotiation. One possibility of such a scenario is a re-invite due to a hold request in which case the SmartNode would ultimately crash. The undesired re-invite is not sent anymore MFR2 protocol blocks on request for calling-party information Using the MFR2 protocol together with the configurable option for requesting the calling-party information during the request for called-party number caused a problem. If for example the protocol had been configured to request the calling-party information after the 3 rd called digit, the protocol stopped and didn't proceed after collecting the calling-party information Displaying the DSP Software Version String of the 4-wire G.SHDSL card The show dsl version and show dsl all commands display the DSP Software version as a combination of both the ISOS Driver and DSP firmware versions Configuration commands for 4-wire G.SHDSL for AnnexType and Mode On SmartNodes supporting a 4-wire G.SHDSL card, a new command to configure the Annex Type is provided. It is also possible to configure additional 4-wire CPE modes for the servicemode command. For more details, please consult the New Configuration Commands section. Build Series Fixed DTMF-Relay from TDM to SIP INFO on SN4960 Rev /36

12 The DTMF digits received on the ISDN side while playing inband voice going to SIP were not detected by the SN4960 Gateway anymore. This has been fixed Support for SN4950 and SN4940 New SN4950 and SN4940 products deriving from the SN4960 Apollo product are introduced. Both SN4950 and SN4940 products have no transcoding license and the number of free SIP legs is limited. The SN4940 product only has 1 Ethernet port unlike the SN4950 which still has 2 Ethernet ports as the original SN Fixed memory leak occurring with fragmented, NATted IP packets Fragmented IP packets would cause a memory leak when routed through the NAT. This has been fixed Hanging DSP channels with distribution-group On SN4960, the DSP channels are not released when the call arrives from ISDN and is routed back to a second ISDN channel going through a distribution-group. This has been fixed and the DSP channels are released as soon as the call is connected Clock setting in Web UI When applying clock setting to the SmartNode from the Web UI, the "Command not found" error would be reported to the user. This feature has been re-enabled and both, time and offset, can be set and successfully applied again from the Web UI Speedtest: improved display of results The speedtest command displays the measured download rate on the CLI. Before the displayed rate was in kbps while the given value actually was in kilo-bytes-per-second. The display has been improved to display both, bytes and bits per second with the correct tags. The value is now given in kbps (kilo-bits-per-second) and the same value is also displayed in kbps (kilo-bytes-per-second). The display looks like this: Download kbytes, 3 seconds, 7800 kbps ( 975 kbps) RIP Default Route Metric The RIP default route metric can be configured with values between 0 up to 16. However, only 0 and 1 values were taken into account in the RIP algorithm. This has been fixed and now all configurable values from 0 to 16 are correctly set and taken into account in the RIP algorithm. Build Series Playing RBT (Ring-Back Tone) on ISDN if no RTP is arriving from the SIP side Rev /36

13 Due to a mistake, the command user-side-ringback-tone, using which the above behavior can be configured, was missing from 46xx SmartNodes. That command has now been made available Preferred codec This feature allows selecting a specific codec to be the unique codec to be returned to any incoming SDP offer if it is listed in the suggested codecs to negotiate of the aforementioned incoming SDP offer. Otherwise the normal codec negotiation is carried out. For more details, please consult the New Configuration Commands section Configurable H.323 display information Up to now the H.323 display information field had the value of the calling party E.164 number. Now the H.323 display information field is configurable: it takes the value of the mapping-table <to calling-name>. If no mapping table < to calling-name> is defined, then the calling-name is empty, thus the H.323 display information will also be empty No inband information with Hunt-group The inband information was not mirrored if a hunt-group was configured with the transparent option and if there was no peer state change. This has been fixed SIP registration using TCP The Smartnode can now be configured to explicitly use TCP or UDP as its preferred transport protocol for outbound registration. For more details, please refer to the New Configuration Commands section OAM support on the G.SHDSL interface The G.SHDSL interfaces now support responding to OAM F5 loopback tests Removed codec switching delay When transitioning from G729 to G711 on the fly, SmartWare used to insert a 400ms delay before reconfiguring the DSP, during which the CED tone could be muted out. This release removes the 400ms delay, unless a fax or modem bypass has been configured Support for G.SHDSL Firmware G03 This SmartWare release is compatible with Firmware release G03 of the G.SHDSL daughter card interface Call outbound settings ignored in registration outbound The changes of non-invite-transaction-timeout and penalty-box in call outbound configuration settings were not taken into account in the registration outbound. This has been fixed RIP route removal with metric 16 Rev /36

14 The SmartNode was not disabling a route that should have been invalidated when receiving a RIP update with a metric equal or greater than 16. Such a route is now properly removed from the routing table. Build Series Weaken tei assignment procedure on ISDN A new configuration option on ISDN net port to support certain PBX, which don t comport according the standard, is introduced. See details in section new commands Correct behavior on 423 Interval Too Brief When receiving a 423 Interval Too Brief answer to a REGISTER request SmartWare did not behave according RFC 3261 and re-issued the REGISTER with the old and too brief expiration time again. This is corrected now, and SmartWare adapts the expiration time in the following REGISTER request to the required minimum time Fax and Modem detection timeout It was possible to disable the fax detection after a certain time to not disturb voice calls. Unfortunately this command worked not in combination with modem bypass which is required for super G3 faxes. The previous fax detection timeout command is now replaced with a media detection timeout to consider fax and modem. See more in the section new commands Support broken SIP outbound proxy Some SIP proxy or SBC do not support the correct handling of proxy headers in SIP requests. To communicate with them SmartNodes must direct SIP requests to them without having a proxy header in the message. This can be configured with a new command called forced destination. See description in section new commands Crash in distribution service Fix a crash in the distribution service. It could occur when a call state changed in combination with the change of other call related information Displaying wrong time in DynDNS The time of last IP address check was displayed wrong, which is corrected now SNMP walk loop Some tools that perform an SNMP walk also try other OIDs at the end of the walk when the SmartNode returns with the No such name message. Usually these OIDs are unsupported on the SmartNode. If the tool tries such OIDs, the SmartNode erroneously jumped back to a lower OID that had previously been walked over. This behavior can result in an endless loop if the SNMP tool tries on forever. Rev /36

15 The SNMP walk feature has been fixed such as to always return either valid OIDs or the no such name message whenever an unsupported OID is queried SIP registration with NAT keep-alive The possibilities to keep the NAT after registering open were enhanced. See details in the section new commands Crash caused by timer during startup When short configured timers elapsed, while the startup configuration was still being parsed, the device could crash. The timers are started now after the device is fully up and configured Re-Invite to different modem codec refused When doing modem transmissions over SIP in combination of a service limiter or priority it could happen that Re-Invites to a configured modem codec were refused. For example: in the voip profile of the SmartNode are g729 is configured as voice codec and g711alawk as modem transmission bypass, but not as voice codec. Then a call on g729 could be opened, but the reinvite for g711alawk to transmit the modem data was refused. This behavior is fixed now, and re-invites to a configured codec are accepted ADSL Annex B layer one activation For SmartNodes with ADSL annex B the layer one of the DSL access was not properly activated. This broke the complete ADSL functionality and is fixed now Release tone on ISDN net interface A new option to configure whether to play a release tone or not is introduced. This is applied on the ISDN dss1 net interface when sending a disconnect message. See more in the section new commands SIP call licensing 1. SN4960 is now able to support transcoding for IP to IP calls. The total number of transcoding calls is half of the voice channels. For example, SN4960/1E30V/UI has 30 voice channel capacity and it can support 15 transcoding channels. 2. SN4960 is now also able to support mediation of IP to IP calls without transcoding. The total number of IP to IP call mediation sessions is the same as the total voice channel capacity. For example, SN4960/1E30V/UI can support either 30 PSTN calls or 15 transcoding IP-IP calls. In addition, it can also support 30 IP-IP calls without transcoding capacity at the same time. 3. The IP-IP call capacity can also be used to connect SmartNodes in parallel. For example, SN4960/4E120V/UI can support 120 IP-IP calls in addition to PSTN or transcoding channels. This allows installing another SN4960/4E120V/UI in parallel. Rev /36

16 4. The IP-IP call capacity is also supported in small SmartNodes like SN463/50 and SN4520/4110. All of them support an additional 8 IP-IP calls. This will allow using two SmartNodes, like a SN4638 and a SN4528, in parallel. Build Series SIP-Client rport support New SIP stack Inband-Info not passed through Hunt-Group No Echo-Cancellation with RBS SIP identity alias enhancement Timer now does not work DST Rule switching time wrong in running-config Handling incoming REGISTER requests in SIP Nortel CS2K conference support SIP-Registration using Nortel NAT-Traversal DSL supervisor boot Handle 301 moved permanently PRI Channel restart follow up Time information lost on reboot Authentication didn t work using phone-context FXS voltage level during ring pause New FXS country profile for Italy Time between ring and CLIP transmission on port FXS Configure 4-wire G.S HDSL WAN Card BitRate Support for SN Setting to send COLP on ISDN always Build Series DTMF C connect signal on FXS Support for 4-Wire G.S HDSL WAN access Rev /36

17 11196 SSH session dropped after 1 hour Possible endless loop during monitoring DSL Modem Supervisor Software Watchdog in security framework Software Watchdog in configuration Framework Handle SIP OPTIONS request out of dialog SIP and ISDN debug information on syslog Crash when deleting context sip-gateway Improved BRI port control on SN46xx devices ISDN User-Side Timer T Channel identifier on ISDN PRI Support for testing of link speed Support for authentication with integrity protection in SIP From-URI of SIP request with phone-context User representation in SIP requests Missing Progress Indicator, ISDN Progress SIP Ping to keep NAT open URI to E.164 conversion with phone-context PRI channel restart with multiple channel identifiers ISDN User-Side Ringback-Tone on SN46xx devices Sending RTCP on SIP side when call is on HOLD Build Series PPPoE session stayed up even when DSL link was down Web UI: Profile VoIP page did not accept rtp traffic-class local-voice Wrong execution Time of Timer Phone-Context in the INVITE message wrong placed Use of tone-set profile on service 2nd dial-tone did not work Rev /36

18 11200 DHCP DISCOVER messages sent with LAN IP when using NAPT Sending RTCP with the call ONHOLD Handling re-invite without SDP offer Rejecting unsupported media in SDP Name lookup with german ääööüü force reset due to HW-WATCHDOG Horrible sound when changing from a polyphonic tone to a monophonic one Playing Ring-Back-Tone on ISDN if no RTP from SIP Daylight saving time rule not shown in the running-config Build Series Packet side Modem/Fax answer tone detection on SN Datapath opened by mistake if hunt-group is involved AAL2-G k SDP signaling Napt inside does not work Resolved Crash when receiving a second 200 OK from a forked call Reboot during configuration Duplicated T.38 attributes in SDP Crash on retrieving running configuration from WEB Wrong drop cause when using SIP overlap dialing Autonomous transitioning broken with re-invite Reboot if show syslog is entered Daylight-savings-time rules corrections Make SN4960 generic transcoding license Build Series Improved loop-break detection on FXO ports 0953 Sending of progress-indicator on ISDN DSL modem supervisor COLP from ISDN to SIP Rev /36

19 11145 Daylight saving time switching according rules Dynamic spoofed contact Possible cause of software watchdog Signaling System R Calling party number missing in ISDN SETUP request from network side Provisioned dialplan Build Series Behavior of service distribution-group Re-INVITE Fax and Modem Codec Negotiation Crash on unregistering non-existent user Configuration upload through provisioning Changing the maximal lock-out time PRACK for Reliable Provisional Responses in SIP Sending ACK request to retransmitted 200 OK response SmartNode crashes when using SSH V.34 Fax re-invitation problem with V.150-VBD Crossing Re-INVITE not properly handled IPSec interoperability with Openswan Number of SIP Sessions Autonomous transitioning for SIP Disabling the fax detection for voice calls Build Series Accessing through VPN tunnel with no LAN Service Second Dialtone does not work for SIP calls IPoA for G.SHDSL SmartNodes Possible clocking problem Duplicated DTMFs in DTMF-Dialing Rev /36

20 11106 New call-control location-service URI lookup behavior DTMF relay forwarding on a SIP to SIP call Loosing memory on INFO messages Crash on broken IP connection during debugging Call re-routing from SIP Accounting start trigger SETUP does not work UPDATE for SIP command 'sniff dsl' Static on E1/T1 during dial procedure Caller Name does not match in mapping-table Crash on malicious IP options Hanging ISDN resources Crash on T.38 to G.711 fax transcoding Build Series SIP registration status of show context sip-gateway Removing PVC Comma in SIP display name SN4400 introduced Allowed content size in SIP too small SIP codec negotiation Missing V.21-Preamble Refused Register Requests with default port Framerelay acts as DCE V.34 to G.3 fallback didn t work Virtual Router Redundancy Protocol Sending SIP REFER for different IP networks Crash when parsing incoming INVITE with no content Rev /36

21 11119 ACL does not allow new IPSec policy on startup Build Series Missing Contact Check in SIP Caller Name not parsed in ISDN Call toggle not working in Ringing state Loopback Interface Distinctive-ringing Play Broadsoft call waiting tone on FXS T.38 CNG-Tone relay T.38 version indication Re-INVITE Voice Codec Negotiation Possible Crash on AOC handling in SIP Crash on malformed Diversion Header in SIP Build Series Access Restriction CNG-Tone Player Web GUI Cleanup Case sensitive comparing No RTP after re-invite back to voice Static-Data dejitter-buffer for Transparent/Clearmode coder Lost inband information on hunt-group T.38 CED-Packet is not transmitted SIP over TCP doesn t work SIP Cancel/200 OK mid-air collision Losing direction information in SIP SDP media Event-driven user-programmed hook system FXS-profile ww53rt Rev /36

22 11038 SIP Stack upgrade to Sending 200 Ok for CANCEL request to wrong port Media reconfiguration disturbs Fax transmission DSCP full match doesn t work in ACL ADSL Annex B not working Wrong DTMF detection Webserver cannot be disabled CNG Tone Relay from TDM to T.38 Build Series HW Watchdog Radius Missing notify if 404 is received SIP Call pickup after transfer More detailed information on notification after REFER in SIP SIP Call forking not working Broadsoft flash-hook support Packet side Modem/Fax answer tone detection Restart channel 1 and 2 on an ISDN BRI Reboot on Receiving a too short ISDN Message DHCP request option File Transfer Manager Fails on Ctrl-C Overlap dialing in SIP Annex information missing for codec G729 in SIP SDP connection info in media description Three SIP Registrations without License Web Server is enabled by default Build Series Calling Name support for Siemens Hipath PBX Rev /36

23 10925 System Exception caused trough removal of SIP interface Wrong output of show profile acl Introduce default responsibility for Location-Service Configurations larger than 32 kb not completely printed Direct T RAI and E-Bit assertion not according to TBR Partial rerouting works only with debug monitors enabled FAX Transcoding Half-duplex Ethernet on the SN Wrong ISDN T1 line-build-out values for application short-haul Ignoring SIP INFO request SmartNode 455X, 456X, S-DTA feature drop HTTP client did not fetch batch files Syslog DNS deadlock Check available memory before accepting a new SIP call Accept SIP INVITE request despite unsupported content type Build Series Missing ISDN status response ISDN location field network beyond interworking point configurable Inconsistency Daylight Timer Clock offset Message Waiting Indication for ISDN Wrong IGMP Checksum HTTP Client SIP Flash Hook Message in BroadSoft format Syslog boot traps Configuration files web-accessible Continue parsing on invalid SDP content Rev /36

24 10963 ISDN Connected number information element was removed SIP transaction timeout and penalty box Support for ADSL annex M Buld Series Message Waiting Indication Sip, Call Control and FXS DynDNS client inactive Missing audio line in SDP Call drop after 200 OK because of the SIP multipart header Call drop after 200 OK because of the unsupported charset parameter in SIP contenttype header Radius accounting timestamps shifted one month Multiple applications could listen on the same TCP/UDP port Configurable Ringing-cadence on FXS Buid Series GRE packets through NAT are swapped between different IP's SIP stack update SIP debug default level changed RTP port range SmartNode does not play busy tone in T.38 mode Call loop in SIP conference when inviting a 4th party NAPT drops out of order IP fragments Secure shell SSH Spoofed contact address does not work properly Build Series Call retrieval after failed transfer Disconnect-signal loop-break configuration problem T38 Problem with M-ATA and SN4960 Rev /36

25 10859 Dejitter buffer is not working as configured Hunt Group does not hunt on DISCONNECT message from ISDN FXO: CID Checksum FXO: Direct Dialable Number in CID Context Sip Gateway forwards Calls to SIP Interface without route. Build Series Confusing TFTP Error Messages DHCP Relay Agent T Call Log with quality Command map in Precall Service Table not working T.38 max datagram size indication Playing alerting tone stops after 60s Hunt group working in the wrong direction SIP Connected-Number to ISDN SIP Debug Output RIP default route not accepted Wrong order in media line not accepted NI2 protocol errors Sending connected party number configurable ICMP redirect messages to the wrong subnet Compliance with ETSI No ringback tone towards H No second T.38 fax transmission over FXO FXS service to park call on SIP server Inheritance in identity Fax failover doesn't work Rev /36

26 10862 User-Agent header without device model Build Series H323 License Rev /36

27 Caveat - Known Limitations The following list refers to open cases in the Change Tracking System 'CTS' CTS2236 Only G.723 high rate (6.3kbps) supported by H.323 (receive and transmit). CTS2702 TFTP may not work with certain TFTP servers, namely the ones that change the port number in the reply. When using the SolarWinds TFTP server on the CD-ROM this problem will not occur. CTS2980 With 10bT Ethernet ports, only the half duplex mode works. (With 10/100bT Ethernet ports, all combinations work.) CTS3233 The SolarWinds TFTP server version (1999) does not correctly handle file sizes of n * 512 Bytes. Use version (2000) or higher. CTS3760 The SIP penalty-box feature does not work with TCP. When the penalty box feature is enabled, the TCP transport protocol must be disabled using the no transport tcp command in the SIP gateway configuration mode. CTS3924 Changing a call-progress tone has no effect. Adding a new call-progress tone and using it from the tone set profile works however. CTS4031 The Caller-ID message length on FXS hardware with Chip Revision numbers below V1.5 is restricted to 32 bytes. If the message is longer the message will be truncated. The FXS Chip Revision can be displayed using the show port fxs detail 5 CLI command. CTS4038 When doing 'shutdown' and then 'no shutdown' on an ethernet port that is bound to an IP interface that receives its IP address over DHCP, the IP interface does not renew the lease. CTS4077 Using the command terminal monitor-filter with regular expressions on systems under heavy load can cause a reboot. CTS4335 The duration of an on-hook pulse declared as flash-hook has been raised from 20ms to 1000ms, to cover the most country specific flash hook durations. Existing installations should not be affected, as all on-hook pulses lower than 1000ms are declared as flash-hook, including the previous default of 20ms. Rev /36

28 However, care should be taken in analog line extension applications, to make sure that the flash-hook event is allowed to be relayed over SIP or H.323. This can be achieved by disabling all local call features in the fxs interface on context cs: no call-waiting, no additional-call-offering, no call-hold. CTS10392 The internal timer configuration command is only able to execute commands that produce an immediate result. Some commands that execute asynchronously cannot be executed by the timer. The following commands (among others) cannot be executed by the timer: ping traceroute dns-lookup copy any kind of files from or to a TFTP server reload without the forced option CTS10553 The command no debug all does not fully disable the ISDN debug logs. As soon as any other ISDN debug monitor is enabled, all the ISDN monitors that were disabled by no debug all are re-enabled. CTS10586 The codecs G.723 and G.729 cannot be used at the same time on all platforms, except on the SmartNode CTS10610 SmartNode 4960 Gigabit Ethernet does not properly work with Dell 2708 Gigabit Ethernet Switch. A work-around is to configure 100Mbit. CTS10730 Due to memory limitations it is not possible to download a software image to the SN4552 when two SIP gateways are active. CTS11114 On SN46xx units it can happen that there are more open phone calls requiring a DSP channel than DSP channels are available. This leads to the situation where a phone connected on a bri port rings and has no voice after the user picks it up. To limit the number of calls using DSP channels it is suggested to create a limiter service where each call from and to a bri port has to pass. When the total number of calls on the bri ports is limited to the number of DSP channels each call is going to have audio on picking up. CTS11214 SmartWare supports on Ethernet ports only the full functionality when the remote device does auto negotiation for link speed and duplex mode. Even when there is a setting configured auto negotiation is proceeded, but only with the configured capabilities. If connected switches do not auto negotiation there can be limited speed or even no link. Rev /36

29 General Notes Factory Configuration and Default Startup Configuration The SmartNodes as delivered from the factory contain both a factory configuration and a default startup configuration. While the factory configuration contains only basic IP connectivity settings, the default startup configuration includes settings for most SmartWare functions. Note that if you press and hold the system button (Reset) for 5 seconds the factory configuration is copied onto the startup configuration (overwrite). The default startup config is then lost. IP Addresses in the Factory Configuration The factory configuration contains the following IP interfaces and address configurations bound by the Ethernet ports 0/0 and 0/1. interface eth0 ipaddress dhcp mtu 1500 interface eth1 ipaddress mtu 1500 Rev /36

30 New Configuration Commands The commands documented in the Release Notes only cover new additions which are not yet included in the Software Configuration Guide for R5.8, available from Current Revision: Part Number: 07MSWR58_SCG, Rev. A Revised: July 28, 2011 Configuring timestamp granularity for syslog-client First appeared in build series: The timestamp granularity can be configured in the syslog-client. The timestamp is stored in the following format: HH:MM:SS[:msmsms] Note that the date format has not changed. Mode: syslog-client Step 1 Command [node](syslog-client)#[no] use-ms-in-time Purpose Specifies whether syslog timestamp contains milliseconds or not. Default: disabled. Configuring timestamp granularity for Radius First appeared in build series: The timestamp granularity can be configured in Radius for vendor specific attributes. The timestamp is stored in the following format: HH:MM:SS[:msmsms] Note that the date format has not changed. Mode: profile aaa Rev /36