CounterPath Solutions Inc. 5th Floor, 100 West Pender Street Vancouver, British Columbia Canada V6B1R8 Telephone: +1.604.320.3344 www.counterpath.com Release Notes for eyeBeam 1.1 – 3015k April 27, 2006 Release Notes for eyeBeam 1.1 – 3015k New Features New User Features Configuration of eyeBeam • The user interface for provisioning of eyeBeam (see the next page) can be handled through an HTTP proxy. If an HTTP proxy is used, the user can enter the address in Settings → System → Network → Connection → HTTP Proxy Server. Handling Calls • The TCP keep-alive interval can now be changed (Settings → your SIP account → Advanced → TCP/TLS Interval). Increase this amount if you experience unexpected disconnections when using SIP over TCP. Instant Messaging • Ability to find text in the IM window, using the binoculars icon. • Ability to save IM messages to a file, using the floppy disk icon. • Ability to delete IM messages in the IM window, using the eraser icon. Audio Quality • Ability to minimize background noise during calls. (Settings → Media → Audio → General. Check the field “Enable Microphone Noise Reduction”). Audio Codecs • The codec iLBC is now enabled by default. Audio and Video Devices The following USB devices are supported: • Actiontec IPW UP101 Clarisys Claritel i750 GN Netcom GN 8120 USB Plantronics CS50 TigerJet TjIP560 Handset VoIP Voice V55MLR VoIP Voice V652VVMLR Yealink USB-P1K • Legerity USB device • • • • • • • Diagnostics • Ability to include transport information in the diagnostics log (Settings → Diagnostics and check the field “Log transport information”). • Added extra logging information. General Features Crypto • Added ability to disable crypto random generator for SSRC if SRTP is disabled. Provisioning eyeBeam now supports a provisioning system. This system allows the VoIP service provider to: • Implement custom login dialogs, custom account creation dialogs, and automated changes to eyeBeam settings. • Provide remote storage. Page 2 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k • Provide online software upgrades. • Added enhancement for new macro $authorization_username$ to provisioning URLs These provisioning features are handled through HTTP, and can include communications via an HTTP proxy. Settings Settings-related enhancements to eyeBeam include: • Ability to pass parameters to installer via system:auto_update:install_parameter setting. • Ability to add two miscellaneous screen buttons screen_misc1 and screen_misc2 that can be enabled/disabled via ui:screen_miscX:show=[0|1]. Page 3 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k Fixed Problems The Severity field describes the impact of a problem: • B: Blocks development and/or testing work • C: Critical problem that crashes, or results in loss of data or severe memory leak • M: Major, resulting in major loss of function. • N: Normal. The priority field describes the importance and order in which a problem bug should be fixed. P1 problems have the highest priority. Problems Fixed in eyeBeam 1.1 Build 3012r Severity Priority ID Revised Description N P1 2571 When the local IP address changes and ISuaSocketConnectionManager notifies all subscribed parties of the new address, other eyeBeam components that try to open the socket receive a loopback address: 127.0.0.1, indicating that the network is not ready; this can cause network discovery to fail if a firewall type is reported incorrectly. N P2 2336 Bitmap used for video_paused notification should not be hardcoded but instead should be editable for SDK users. N P2 2355 NOTIFY messages from an MWI server must include both “messages-waiting: [yes][no]” line and “voicemail: x/x” line. N P2 2619 Starting eyeBeam with a proxy account enabled stores the initial DNS query in cache, but if a user edits their Primary DNS Server setting within eyeBeam and then Unregisters/re-resisters with the proxy eyeBeam will continue to use the cached DNS query. N P3 2994 When an eyeBeam user receives a response to an IM sent to a remote user, the response appears in a new IM window instead of the same IM window in which the local user originated the IM session request. Page 4 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k Problems Fixed in eyeBeam 1.1 Build 3013h Severity Priority ID Revised Description C P1 2991 If eyeBeam has custom routes enabled and a custom route requires a REGISTER, the “from: “ and “to: “ headers of the REGISTER message use the erroneous URLs of the custom route. C P1 3073 If an eyeBeam user cancels a pending call to a remote user who has a separate call established already with a third user, the remote party continues to hear a ringing sound. M P2 3097 Upon receipt of an INVITE request that includes no SDP description, eyeBeam will send back a 200 OK response containing only audio media; eyeBeam should be able to send a response containing both audio and video media information in the SDP description. N P1 3041 When eyeBeam receives an INVITE message request that does not include a SDP description, answering the call generates a 200 OK response that includes SDP information—which causes the remote User Agent to send back an ACK message that eyeBeam then responds to with a 400 Bad Request message. N P1 3106 eyeBeam must support SDP descriptions with a ptime value of 10. N P1 3135 eyeBeam must support use of TLS--and only TLS--as a preferred transport protocol. N P2 3083 eyeBeam deREGISTERs and then reREGISTERs upon receipt of a via header containing a “received” parameter and a “rport” parameter with no value; eyeBeam must compare the “received” address independent of the rport value, which (if greater than zero) will be compared to the “Contact” port number. N P2 3103 eyeBeam does not support negotiation parameters for basic H.263 video codec. N P2 3115 When a device configured within eyeBeam is unplugged and then plugged back in, the client should detect the device once more but fails to do so. N P3 3042 eyeBeam responds with 400 Bad Request when a remote User Agent requests a multipart/mime content type. N P3 3043 If two parties each try to place the other on hold at the same time, one party (correctly) receives a 491 since one re-INVITE is already in progress; this, however leaves the eyeBeam SDK in an unstable state, so that subsequent re-INVITES are answered immediately with a BYE N P3 3066 While using the tuning wizard the user is not notified if the device is muted. N P3 3074 SPEEX_WB codec is designed to be disabled if an eyeBeam user selects a connection speed of 128kbps (dial-up speed) within the Tuning Wizard. N P3 3144 eyeBeam’s diagnostic log functionality do not reflect use of the TLS transport protocol. Page 5 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k Problems Fixed in eyeBeam 1.1 Build 3013o Severity Priority ID Revised Description N P2 2624 When eyeBeam is set to use the TLS transport protocol (designed to work on top of TCP), UDP keep alives continue to be sent to the TLS port, causing potential DOS issues at the proxy server. N P3 3206 eyeBeam must generate strong crypto numbers to avoid allowing an input and an output RTP stream to use the same SSRC if they are generated using rand(). N P3 3244 When eyeBeam is started using a custom login dialog, buttons for redial, flash and record should be disabled but are not. Page 6 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k Problems Fixed in eyeBeam 1.1 Build 3013v Severity Priority ID Revised Description C P1 3289 The eyeBeam SDK can crash when a kmpl event subscription is made. M P1 3168 Ports do not always get shut down when the transport type is changed. M P1 3269 SIP port keep alives interval should be configurable in eyeBeam. M P2 3283 eyeBeam should include a setting that specifies the file folder where certificates are stored. N P1 3290 Altec brand of eyeBeam crashes if the license key page is deactivated in the settings dialog and an invalid license key is obtained through provisioning upon startup. N P2 2498 eyeBeam should support FMTP:34. N P2 3299 When using a brand with provisioning and a custom login dialog box set to display on startup, the option “Do not ask me this again” does not work as expected. N P2 3335 The TCP/TLS keep-alive interval should be configurable in eyeBeam. N P2 3375 Sometimes, when a video frame is split across RTP packets, the RTP timestamp does not remain the same for all RTP packets. N P3 2860 Sometimes the 200K for a RE-INVITE contains a different SRTP key from the RE-INVITE itself. N P3 3221 eyeBeam audio-only version crashes when started on Windows 98. N P3 3297 The XTunnels login should be performed using both the user name and the domain, but just the user name is used. N P3 3327 There should be a message on the display if an established call is hung up because the network connection is lost. Page 7 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k Problems Fixed in eyeBeam 1.1 Build 3014s Severity Priority ID Revised Description B P1 3744 When a call is attempted but the receiving party does not answer and then the calling party hangs up, ringing is still heard at the receiving eyeBeam. B P1 3750 For an incoming call, if the user answers the call by clicking the AA button, the GUI flickers. C P1 3652 When eyeBeam is configured to use WebDAV for remote storage, eyeBeam does not update presence status and does not respond to NOTIFY messages. In addition, clicking on the properties for one buddy causes eyeBeam to un-subscribe and re-subscribe to the entire buddy list resulting in an increased load on the network. M P1 3670 If eyeBeam has subscribed to a remote User Agent’s presence information and receives a subsequent NOTIFY message with updated status values, eyeBeam sends a re-SUBSCRIBE request but uses an erroneous “expires” value that the proxy server deems to low; the proxy server then responds with a 423 and will not accept further SUBSCRIBE requests from the local eyeBeam client (responding with 481 each time). M P2 2172 Incoming audio is corrupted or stops completely when adjusting the volume control. M P3 3735 The header in a SIP message should include the Accept-language field with the value automatically completed using the language set up for the operating system. N P1 2252 Subscribing to presence is not updated properly when the user name is changed in the contact editor dialog. N P1 2510 eyeBeam does not respond to a “302 Moved Temporarily” message. N P1 3183 When eyeBeam subscribes to a service (e.g. MWI), any subsequent subscription request that is challenged does not send another immediate SUBSCRIBE request. N P1 3245 Silence detection (VAD) does not work; eyeBeam continues to send even when there is silence. N P1 3294 If two User Agents A and B are registered with the same proxy account using different timer settings for re-registration, eyeBeam does not re-register according to the contact header. N P1 3637 When one user sends another a RE-INVITE with no SDP description, the request is not handled correctly: the eyeBeam receiving the RE-INVITE rejects the request with a 488 response and then hangs up the call. N P1 3706 When using a VoIP Voice USB Device and pressing a numeric key on the USB phone, an unending DTMF tone can occur. N P1 3718 The user should not be able to rename a buddy in the Privacy Rules dialog box. N P1 3725 Using the contact drawer to dial a number should not turn the speaker phone off. N P1 3743 During an IM session, if one user begins typing a message that triggers an “is composing” message to be sent to the other user, waiting until the “is composing” message to be resent after the refresh interval has expired causes the new “is composing” message to be sent with a new refresh value of 0. N P1 3765 If a call includes the remote-party-id header field in the header of the INVITE, eyeBeam uses this field when establishing the call, but then switches back to the display name in the "from" header. eyeBeam should continue to use the remote-party-id field. N P2 2165 When there are two incoming calls, the displays shows the second call, but the Ignore and Ban buttons affect the first call. N P2 2169 When the IM window pops up with a new incoming IM, the Windows focus switches to the IM window, so that the user is inadvertently typing in this window. N P2 2206 The eyebeam icon is removed from the Windows Task Manager Applications list when the "Hide in System Tray" button is selected. Page 8 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k Severity Priority ID Revised Description N P2 2321 When a call is placed by pressing Enter and then the Enter key is pressed quickly and repeatedly, multiple incoming calls are received at the other party’s eyeBeam. N P2 2553 “Launch when Windows starts” setting is not saved upon exiting eyeBeam. N P2 3125 The video Start button should be disabled when the call is on hold. N P2 3614 The user should not be able to display the Privacy Management dialog box if no account is enabled. N P2 3758 Values for settings in the settings.sok file should accept line feeds and Unicode characters. N P3 2551 A new entry within the Privacy Manager does not get saved. N P3 2552 The minimize button does not hide eyeBeam in the system tray. N P3 3328 Eyebeam does not support video-only calls. N P3 3409 In the reSIProcate stack, eyeBeam does not calculate the md5-sess digest properly in order to support md5-sess. N P3 3458 eyeBeam continues to send video even after the call has been put on hold by the other party. N P3 3622 Adding a “&” character to a contact list name causes all subsequent entries to produce an error. N P3 3641 The INVITE for a TLS and SRTP call is not formatted correctly. N P3 3751 If the user is using a Plantronics CS50-USB and does not have it configured yet, lifting the device off the stand can activate a line on eyeBeam. Page 9 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k Problems Fixed in eyeBeam 1.1 Build 3014w Severity Priority ID Revised Description B P1 When installing eyeBeam on Windows 98 with a Plantronics C250 USB device, the install gets a runtime error. However, eyeBeam can still be started. But it cannot be uninstalled. 3756 The problem is caused by a DLL provided for the Plantronics USB. This DLL cannot be registered in Windows 98. The solution for now is that eyeBeam cannot support Plantronics USB in Windows 98. C P1 3800 A runtime error may occur if the computer that is running eyeBeam is switched back and forth between a wireless and a wired connection. C P1 3897 Uncaught exceptions when parsing SIP messages causes eyeBeam to crash and may cause a temporary Denial of Service. The problem does not compromise the eyeBeam computer or cause heap corruption. This problem was reported by Secunia on 19 January 2006. For more information, see secunia.com/advisories/18516. N P1 2176 When eyeBeam receives a Presence NOTIFY that a buddy is offline and that buddy is a buddy in two accounts, then the buddy goes offline both for the requested account and for the other account. It should not go offline for the other account. N P1 3018 Due to certain kinds of personal firewall settings, connecting to a DSL router via Microsoft’s PPPoE mechanism can cause lost audio at both ends of a call. N P1 3451 eyeBeam shuts down too early so that the MWI (message waiting indicator) unsubscribe is never complete. N P1 3525 When the user right-clicks on a number in the Calls & Contacts drawer and places a call, the focus should switch to the central panel, so that the numeric keys on the computer can be used in eyeBeam. N P1 3606 The BYE reason in the header of the SIP message does not follow the syntax according to RFC 3326. N P1 3608 eyeBeam sends a PUBLISH with authorization information with content-length=0. N P1 3748 Call messages in the display get cut off. N P2 3243 eyeBeam does not un-register and then re-register when a TLS/TCP connection is torn down and then re-established. N P2 3831 CPU usage goes up for the first call (for a few seconds) on a new eyeBeam startup. N P3 3591 eyeBeam does not support dialog re-use for established calls. Page 10 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k Problems Fixed in eyeBeam 1.1 Build 3015c Severity Priority ID Revised Description B P1 2189 Some RTCP packets appear anomalous after negotiating a call. C P2 2220 Possible memory leak in SDK when allocated with VS_New and deleted with VsFree. M P1 3140 eyeBeam does not send RTP data based on the c-line for a re-INVITE. M P1 3826 When an eyeBeam running on a Mac calls an eyeBeam running on Windows and then toggles the Windows-based client several times between on/off hold, the eyeBeam running on the Mac can crash. M P2 2227 Delay in connecting after finished dialing. M P2 2281 CSuaAudioConvert calls Reset() too often. M P2 3104 Comfort noise sequence numbers are not the same, but they should be the same. N P1 3438 ICE HMAC construction/decoding is not backward-compatible N P1 3494 There are redundant line feeds and spaces in the diagnostic log that make it difficult to read all log messages. N P1 3554 After plugging in two cameras to the local system then starting eyeBeam and running the Tuning Wizard to the Video Configuration page, if a user selects the first camera device (waiting for the preview display for the first camera) and then selects the other, eyeBeam will continue to display the video feed from the first device even upon exiting the Tuning Wizard and even after restarting the softphone client. N P1 3555 After starting eyeBeam on a Mac without a camera plugged in, if a user then plugs in a camera and runs the Tuning Wizard the Video Configuration page of the Wizard is skipped; restarting eyeBeam and running the Tuning Wizard again displays the Video Configuration page as expected. N P1 3576 Video mix displays remote video as a conference even when there is only one remote endpoint. N P1 3832 When a server sends a re-INVITE to eyeBeam, one-way audio can occur. N P1 3833 eyeBeam fails to resolve STUN server if DNS SRV response has truncated the bit set to true. N P2 2343 One-way audio happens if the callee is behind a symmetric NAT. N P2 2385 One-way audio happens after a user is placed on/off hold by a party behind a symmetric NAT. N P2 2538 Plugging in and unplugging camera while in the Tuning Wizard causes the Wizard to not work properly. N P2 2549 Media negotiation fails when placing a video call. N P2 2576 eyeBeam does not register when server asks because of missing Contacts headers. N P2 2615 RTP payload types for DVI4 and G726-32 are both “5.” N P2 3281 No local video is displayed if eyeBeam starts with the video drawer open. N P2 3473 Once eyeBeam has been started successfully with a valid license key, changing the license key to one that is invalid will only challenge the user for so many tries until the client accepts the invalid key. N P2 3813 Contact list not loaded after an account is created via a custom login. N P2 3827 When an eyeBeam running on a Mac calls an eyeBeam running on Windows and both offer video to the other, the Mac’s remote video display appears tilted half-way up and does not display correctly. N P2 3905 Pitch shifting occurs when many packets arrive in a short period of time. N P3 2335 When calling direct to another IP address, pressing the Add To Contacts button adds the contact with an incorrect domain. Page 11 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k N P3 3063 During a video call for which at least one endpoint is a Mac, remote video sent from the Mac appears to have a black strip along its right edge. N P3 3552 The Tuning Wizard warning message does not display the CounterPath logo. N P3 3903 Upon receiving an INVITE message containing SRTP crypto attributes that have no MKI, eyeBeam answers with a 480 response. N P3 N/A Fixed issue whereby transfer to PSTN number resulted in one-way audio when using XTunnels. N P3 N/A Fixed issue regarding Hz rate adjustment. N P3 N/A Fixed call issue whereby with both AA and AV enabled only one client is able to send video. N P3 N/A Fixed inconsistent behaviour for “Send” button when AV is enabled. N P3 N/A Enhanced auto-upgrade to use “quiet” mode for the installer. Page 12 © Counterpath Solutions Inc. Release Notes for eyeBeam 1.1 – 3015k Problems Fixed in eyeBeam 1.1 Build 3015i Severity Priority ID Revised Description M P1 3794 eyeBeam may crash when adding a contact if a different contact is subscribing to you at the same time. N P1 3556 Mac: eyeBeam does not detect on-the-fly when a user plugs in an audio device. N P1 3982 Mac: eyeBeam crashes when receiving a call if the softphone application is hidden and another application has focus. N P2 3457 When the user cancels eyeBeam startup because the license key has expired, the GUI will close down, but the eyeBeam processes will still be running. eyeBeam must be shut down from the Task Manager. N P2 3983 Mac: The away timer for presence does not work. N P3 3981 Mac: If either the Contacts drawer or both the Contacts drawer and Video drawer are open when eyeBeam starts, the REC button is enabled. Problems Fixed in eyeBeam 1.1 Build 3015k Severity Priority ID Revised Description M P1 N/A Occasionally there is one-way video when eyeBeam receives a phone call from a non-eyeBeam VOIP hard phone. M P1 N/A Pressing Alt-Tab on the detached video drawer displays the wrong icon. N P1 4036 When a user add a new status message from the dropdown list of the Settings dialog, the new message appears within the user interface as nothing but blank spaces. N P2 3975 After unplugging a headset while eyeBeam is running, the application can crash. N P2 N/A Need to support 32-byte password hash (as well as of 16-byte). N P2 N/A Global voicemail number does not work if no phone_context is configured. Page 13 © Counterpath Solutions Inc.