SmartWare R5.6 Release Notes

Size: px

Start display at page:

Download "SmartWare R5.6 Release Notes"

Daniel Lucas
6 years ago
Views:

1 Patton Electronics Company, Inc Rickenbacker Drive Customer Deliverable Documentation Revision 1.00, May 19, 2011 Gaithersburg, MD USA Tel. +1 (301) Fax +1 (301) SmartWare R5.6 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.6 Build SmartNode 4400 Series R5.6 Build SmartNode 4520 Series R5.6 Build SmartNode 4630 Series R5.6 Build SmartNode 4830 Series R5.6 Build SmartNode 4900 Series R5.6 Build SmartNode 4960 Series R5.6 Build SmartNode 5200 Series R5.6 Build SmartNode 5400 Series R5.6 Build SmartNode 4552 R5.6 SIP Build SmartNode 4554 R5.6 SIP Build Smart-DTA R5.6 SIP Build About this Release R5.6 is a SmartWare Maintenance Release. Please see the White Paper about SmartWare software releases for more information about this terminology. R5.6 was spawned in August Bugs are fixed until August End of customer support is in February 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 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 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 /15

3 History of Solved CTS Cases The following list refers to open cases in the Change Tracking System 'CTS'. This 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. 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 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. Build Series Rev /15

4 11193 Fixed DTMF-Relay from TDM to SIP INFO on SN4960 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 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 RIP route removal with metric 16 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 Rev /15

5 11307 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. 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 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 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 /15

6 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 Inband-Info not passed through Hunt-Group To reach the different network requirements, the Hunt-Group behavior related to Inband- Information announcements has been made configurable. New, there exists a command in the Hunt-Group configuration mode that allows choosing between the options Transparent, Block and Succeed. For more details, please consult New Configuration Commands section No Echo-Cancellation with RBS On calls from RBS to SIP it could happen the remote SIP user heard a nasty echo due to a miss configuration of the echo cancellation settings. Reapplying the PSTN settings from the WEB interface temporally solved the problem. This issue has been fixed Timer now does not work When configuring a timer based on the time now with an offset, for example now + 2 minutes the timer was never executed. This has now been fixed DST Rule switching time wrong in running-config When a DST Rule was configured with a specified time of day, this was not displayed in the running-config, instead the default value was shown Handling incoming REGISTER requests in SIP The process of generating a negative answer for REGISTER requests has been improved for the case that the SmartNode is not configured as registrar PRI Channel restart follow up Follow up to rfe Incoming ISDN RESTART messages containing multiple channel identifiers were now correctly answered but the actual channels were not properly restarted. This has been fixed Time information lost on reboot Some SmartNode products could lose the time information when doing a warm reset, for example after a manual reset from the CLI or a software watchdog. This caused a boot-log and an event-log with the default time from This is fixed now, and therefore the only reason for losing the time remains a cold reset by removing the power Authentication didn t work using phone-context Rev /15

7 If the phone-context option has been configured to an identity in the location-service, authentication was not working even the correct credentials were available in the authentication-service. It happened in the case an outgoing call has been challenged as well as for incoming calls to be authenticated locally. This issue has been fixed and authentication works now as expected. Rev /15

8 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 /15

9 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 /15

10 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 /15

11 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.6, available from Current Revision: Part Number: 07MSWR56_SCG, Rev. A Revised: July 9, 2010 Inband-Information Behavior First appeared in build series: This command defines the behavior of a Hunt-Group service if a hunt-peer indicates the availability of inband information. It s possible to choose between three options: Transparent: This is the default behavior. Inband information is always passed through from hunt-peers to the call originator. Block: Inband information is never passed through from hunt-peers to the call originator. Succeed: If a hunt-peer announces inband information either in a provisional state or in disconnecting state, hunting is going to be stopped and the call is switched through the current destination. This happens even the peer disconnects the call with a cause that is configured as an indication to proceed hunting. Mode: Service Hunt-Group Step 1 Command [node](svc-hunt)[name]#inband-information{ transparent block succeed } Purpose Defines the Hunt-Group behavior if a destination announces inband information. Default: transparent Rev /15

12 Documentation CD-ROM The CD-ROM that is delivered with SmartNodes includes user documentation and tools for SmartWare R5.6: Software Configuration Guide SmartWare Release R5.6 SmartNode Hardware Installation Guide TFTP Server Telnet Acrobat Reader WWW Please refer to the following online resources: Software Configuration Guide SmartWare Release R5.6: SmartWare Configuration Library: Rev /15

13 How to Upgrade 1. You have the choice to upgrade to R5.6 with or without the GUI functionality. To upgrade to R5.6 without the GUI functionality, enter the following command (telnet, console): copy tftp://<tftp_server_address>/<server path>/b flash: To upgrade to R5.6 with the GUI functionality, enter the following command (telnet, console): copy tftp://<tftp_server_address>/<server path>/bw flash: 2. Load Patton-specific settings (preferences), if available: Extract the files b_patton_prefs and Patton.prefs into the same directory on the TFTP-server. copy tftp://<tftp_server_address>/<server path>/ b_patton_prefs flash: 3. Reboot the SmartNode afterwards: reload Rev /15

14 Notes about Upgrading from Earlier Releases Note that SmartWare Release R5.6 introduces some changes in the configuration compared to Release R4.xx, especially in the domain of SIP. Please refer to the SmartWare Migration Notes R4 to R5 available at upgrades.patton.com. Rev /15

15 How to submit Trouble Reports Patton makes every effort to ensure that the products achieve a supreme level of quality. However due to the wealth of functionality and complexity of the products there remains a certain number of problems, either pertaining to the Patton product or the interoperability with other vendor's products. The following set of guidelines will help us in pinpointing the problem and accordingly find a solution to cure it. Problem Description: Add a description of the problem. If possible and applicable, include a diagram of the network setup (with Microsoft tools). Product Description: When reporting a problem, always submit the product name, release and build number. Example: SmartNode 4960 V1 R5.6 Build This will help us in identifying the correct software version. In the unlikely case of a suspected hardware problem also submit the serial number of the SmartNode (s) and/or interface cards. Running Configuration: With the Command Line Interface command 'show running-configuration' you can display the currently active configuration of the system (in a telnet and/or console session). When added to the submitted trouble report, this will help us analyze the configuration and preclude possible configuration problems. Logs and Protocol Monitors: Protocol traces contain a wealth of additional information, which may be very helpful in finding or at least pinpointing the problem. Various protocol monitors with different levels of detail are an integral part of SmartWare and can be started (in a telnet and/or console session) individually ('debug' command). N.B.: In order to correlate the protocol monitors at the different levels in SmartWare (e.g. ISDN layer3 and Session-Router monitors) run the monitors concurrently. Network Traffic Traces: In certain cases it may be helpful to have a trace of the traffic on the IP network in order to inspect packet contents. Please use one of the following tools (supporting trace file formats which our tools can read): Ethereal (freeware; Your Coordinates: For further enquiries please add your address and phone number. Rev /15

SmartWare R6.10 Release Notes

SmartWare R6.10 Release Notes Patton Electronics Company, Inc. 7622 Rickenbacker Drive Customer Deliverable Documentation Revision 1.00, April 2, 2018 Gaithersburg, MD 20879 USA Tel. +1 (301) 975-1000 Fax +1 (301) 869-9293 support@patton.com