-- As of 5.0.0. 2761
• New Feature: Support the use of an HTTP/HTTPS proxy for all outbound HTTP requests.
• New Feature: Support DNS/SRV lookup of XMPP Domain Name, by enabling the new option: X_XmppDomainUseSRV (under SPn Service). The option is disabled by default.
• New Feature: Show the actual error code on screen, if available, if when connecting to an XMPP server results in an error.
-- As of 5.0.0.2765
• Resolved Issue: Packet loss rate and packet drop rate calculations were incorrect (TR69 version only).
-- As of 5.0.0.2792 --
• Resolved Issue: Silent ring if enabled on an SP service will cause reboot during call-waiting on that SP service.
• Resolved Issue: Fast digit entry during a connected call whle using the OPUS codec results in some digits to get lost during transmission.
• Resolved Issue: BLF signaling over SIP/NOTIFY (with Event=dialog) may not be processed correctly and if the dialog update is reported in partial state, results in the OBi phone not recognizing some BLF state changes.
-- As of 5.0.0.2815
• New Feature: Support customizable call screen and ring screen items using a <ScreenItem> parameter with two different pixel-heights per item when total number of items to draw is equal to one or more than one.
• New Feature: Obihai IP Phone XML (a.k.a. Action URL) Enhancements:
- Support embedding of a <ScreenItem> XML element within a CDATA block in an OBiPhone XML doc to define the layout for each MenuItem. In other words, users can specify a different layout per XML app dynamically.
- Added four optional anonymous text fields per menu item called F1, F2, F3, and F4. These fields can be referenced as $F1, $F2, $F3, and $F4 inside the embedded <ScreenItem> element to control how to layout these fields. The phone does not interpret the contents of these fields.
• New Feature: Support for HTTP or HTTPS URL in the <src> attribute of an <img> element in the Obihai IP Phone XML. The image, if downloaded, is cached until the OBi device reboots. There is no way to clear the XML image cache (yet).
• New Feature: Support <setvar> element in a <ScreenItem> with a value that is downloaded from an HTTP/HTTPS url. The result should be a valid xml tree with a value attribute for each tag. The root of the xml must be the name of the <setvar> element. The var names are formed by concatenating the element tag-name with a '.' (dot). For example:
<![CDATA[ <setvar name="cid" value="
http://abc.com/varlist.xml"/> ]]>
expects varlist.xml to be something like this:
<cid value="1">
<org value="ABC Broadcasting Inc">
<title value="VP of Sales"/>
</org>
<email value="tim@abc.com"/>
</cid>
Then the variables $cid, $cid.org, $cid.org.title, and $cid.email are defined.
• New Feature: Reference the HTTP response Cache-Control header to determine if and how long to cache downloaded temporary data via HTTP/HTTPS. The data is cached until it expires or when the phone is power cycled.
• New Feature: Support for the ClearDownloadedDataCache parameter and also to make it available under the Settings menu of the phone. This enables the HTTP downloaded data cache to be cleared.
• New Feature: Added a new Screen Saver Type to load the screen save picture from a user configured URL only.
• New Feature: <ScreenItem> accepts bgimg attribute that can be a HTTP/HTTPS URL to download a background picture for the corresponding widget element.
-- As of 5.0.0.2824
• New Feature: <ScreenItem> (root) element accepts the bgimg attribute that can be an HTTP/HTTPS URL.
• New Feature: Added AutoAnswerOffWhenBusy parameter – Found in the User Preferences area of the OBi device web page. Busy means the call is in any of the following states: Connected, Dialing, Trying, or Peer Ringing. Note that: Ringing and Holding are not considered busy.
• New Feature: Support $coachState, $recst, $charges, and $muted macros in a CallItem <ScreenItem>.
• Resolved Issue: Wrong entry highlighted on screen in the Phone Book when entering the first letter of a name using the number pad.
• New Feature: Support ;send=... attribute in the Number field of a Speed Dial Feature Key . The value of this attribute specifies a number of digits to send to the remote party, with optional pauses and user input digits in-between.
• Resolved Issue: Mute key is not processed correctly when switching from handset to a Bluetooth headset.
-- As of 5.0.0.2829
• Resolved Issue: DTMF tone playback from incoming RFC2833 RTP events does not stop when using a Bluetooth headset.
• New Feature: Accept Obihai Phone XML pushed to the phone via HTTP/Post in addition to SIP/NOTIFY.
• New Feature: Support reporting of <obi-status> using HTTP in addition to SIP.
• New Feature: Support filtering of <obi-status> to report only those elements enabled and send update only when those selected elements have changed.
• New Feature: Support reporting <obi-status> using the more standard <dialog-info> format (for calls only), in addition to proprietary Obihai format.
• New Feature: Added parameters OBiStatusFormat and OBiStatusFilter under every SPn service.
• New Feature: Support sending back a message body that is an <ObihaiIPPhoneExecuteResponse> to include the status of the execution of each <ExecuteItem> in an Obihai IP Phone XML received via HTTP/Post or SIP/Notify. The MIME type is application/xml. The xml is a list of <ExecuteItem> with a one-to-one correspondence to the <ExecuteItem> in the received request, in the same order. Each item in the response, has a result attribute that indicates the status of the execution. For example, if an execute item URL is not found, result="404 Not Found" will be sent. For a successful execution a, result="200 OK"will be sent. For "DIAL" URI, it would include a call-id attribute to later identify the call in an obi-status XML, and to allow further control of the call using the same call-ref.
• New Feature: Support the URI="Answer:{call-ref-id}" in <ExecuteItem>.
• New Feature: Support the 'id' attribute in each <ExecuteItem> for easy matching with the <ExcuteItem> in <ObihaiIPPhoneExecuteResponse>.
-- As of 5.0.0.2855
• New Feature: Added the Baltimore CyberTrust Root Cert
• Resolved Issue: Do not show the time of the call down to the second in call history; only show hour and minute of the call.
• New Feature: A screen saver picture refresh from an HTTP downloaded and cached picture may cause the phone to reboot.
• New Feature: Added an option to show current time and date super-imposed on the screen saver picture. The option is enabled by default.
• Resolved Issue: Some HTTP download and cached image files are not removed from internal cache when the cache timer expires.
• Resolved Issue: A Call Ended event should restart the screen saver timer (count down).
-- As of 5.0.0.2860
• Resolved Issue: Phone may reboot if the OBiStatusNotifyURL cannot be resolved by DNS.
• Resolved Issue: When there is a call on hold or in any state, do not allow Screen Saver to start.
-- As of 5.0.0.2870
• New Feature: Support for call diversion on an incoming call using the new "divert" soft key.
• New Feature: Support for BlindTransfer:{Call-Ref};{Target-Number} URI in <ExecuteItem> using attended transfer method, but complete the transfer automatically as soon as the target rings
• New Feature: Support for Forward:{Call-Ref};{Target-Number} URI in <ExecuteItem> to forward a ringing call.
• New Feature: Support for Transfer:{Call-Ref};{Target-Call-Ref} URI in <ExecuteItem> for attended transfer.
• New Feature: Support for Add2Conf:{ Call-Ref} URI in <ExecuteItem>.
• Resolved Issue: When executing the Resume:{Call-Ref} URI via <ExecuteItem>, other calls should be either put on hold or ended automatically.
• Resolved Issue: When carrying out Answer URI, need to hold or end any on-going call, and turn on default audio device, if necessary.
• New Feature: Add "Reboot to apply WiFi change" to warn the user to reboot the device as appropriate.
-- As of 5.0.0.2877
• New Feature: Use the OnDialing soft key set (that is configurable) to enter ablind transfer and divert target number.
• New Feature: Support for blind transfer by bridging if SIP/REFER cannot be applied.
-- As of 5.0.0.2895
• Resolved Issue: <ScreenItem> changes via provisioning did not trigger a cold boot, so that the changes could not take effect.
• New Feature: Added support for French GUI.
• New Feature: Added the CallTransferItem parameter – which takes a <ScreenItem> as its value – to customize the attended call transfer screen.
• New Feature: Added the SoftKeyStyles parameter to specify up to 32 <style> elements to be chosen by an id attribute in each customizable softkey. Total size is limited to 8KB.
• Resolved Issue: When multiple <img> widgets are using the same HTTP URL in their src attribute, the phone should only download the same file once to be shared by all widgets.
• Resolved Issue: In a Obihai IP Phone XML App, do not URL-encode the '=' character when submiting a form.
• Resolved Issue: When exiting the current OBi Phone XML App, the phone should execute cancelAction, only if the exit is triggered by the "Back" or "Cancel" command.
• Resolved Issue: The OBi Phone should exit the current Obihai IP Phone XML App after submitting a form.
• New Feature: Expanded speed dial (using a soft key or feature key) to allow specifying a send parameter to transmit a sequence of DTMF digits to the call peer during a connected call.
• Resolved Issue: Support for the vartree object in <ScreenItem> that is not part of a table.
• New Feature: Support for icon and icon1 attributes for configurable soft keys that have two states – with label and label1 attributes specifiable.