This is the Firmware V10 Roadmap Document.

The release date of the next beta is planed for the third monday of a month. Please note that this a scheduled and no fix date.

This article is generated automatically. Do not edit! Please see the disclaimer before using the information presented here!

V10 Beta 2

Changes included in Version 10 beta2 Definition

New Features

PBX: Show conference object online state

Status	Closed
Id	89440

The PBX broadcast conference object supports the online state in myPBX dependent on its configuration and its group members' online state now.

myPBX: Encoding of conference video stream

Status	To-decide
Id	89455

If a participant starts a 3rd party conference while it is already receiving a video conference stream, it has to adapt the conference stream to fit the encoder size. We have to downscale the image.

H.323: Automatically connect signaling TCP if NAT router is detected

Status	Closed
Id	89497

When regestering an endpoint from a private network to a PBX within the public network, the signaling TCP connection must be established and maintained by the endpoint. Otherwise calls to the endpoint are not possible.

myPBX: Pickup calls

Status	Closed
Id	89536

Pickup calls that are alerting at a favourite contact.

myPBX: Show needed browser features that are deactivated

Status	Closed
Id	89542

To be implemented in version 10.

PRI-QSIG: Interop config for channel numbering

Status	Closed
Id	89578

The QSIG standard defines to use Channel numbers (1-30) instead of timeslot (1-15, 16-31) as it is defined for EDSS1. There are many 'old' QSIG implementations around, which do it wrong. The QSIG-ECMA1 protocol setting is used for these 'old' implementations and the QSIG-ECMA2 setting for standard conform inplementations.

With the QSIG-ECMA1 also 'old' facility coding is used. There is also the combination of standard facility coding and timeslots for channels around so an independent mechanism to configure the channel numbering is needed.

PBX: Support of long user-user-informations by SOAP

Status	Closed
Id	90029

Support of long user-user-informations (UUI) for SOAP sessions added. A long UUI is split into multiple short UUIs supported by Q.931.
It is required by the FAX interface.

Relay: Support of long user-user-informations by FAX

Status	Closed
Id	90030

Support of long user-user-informations (UUI) for the FAX interface added. A long UUI is split into multiple short UUIs supported by Q.931.

Gateway: Support of a header line for FAX documents

Status	Closed
Id	90374

Support of a header line for FAX documents is added in the FAX interface.

ISDN: No alarms for link down in case of interop flag "passive Layer2"

Status	To-decide
Id	90383

The passive Layer2 interop flag is needed if the other side (e.g. the ISDN network) does not support to a have an active Layer2 (LAPD) on point to point links all the time, but controls establishment and release on a per call basis. This could generate an Alarm each time there is no call.

PBX Waiting: Support of RTP-DTMF for two-stage dialing

Status	To-decide
Id	90425

If the announcement interface for a Waiting queue is not the PBX internal one and the calling endpoint can only do RTP-DTMF, the announcement interface sends back the received DTMF as USER-INFO to the PBX.
This feature ist needed for a Hosting Scenario where the PBX is located in a private network and the Media interface on a different system in the public network.

Gateway: Only transparent (clearmode) coder in offer if data call

Status	To-decide
Id	90483

This is a SIP interop issue. Some equipment cannot ignore clearmode coder offers, if not supported.

Bug Fixes

myPBX: Dial directly from outlook

Status	Closed
Id	87416

Start call immediately instead of copying the number/URI to myPBX.

myPBX: Select im session when focusing chat window

Status	Closed
Id	89490

In order to simplify adding users to the chat.

PBX Mobility: Conference ID not set for outgoing calls initiated by myPBX

Status	Closed
Id	89502

This could cause several problems:
- When the call was sent to a local user with multiple registrations, the call to each registration had a different conferenceID, so myPBX could not match these calls to actually being only a single call, so multiple calls were dissplayed
- The CDRs created for this call could not be matched

SIP: Auto answer with SDP in ACK

Status	To-decide
Id	89539

Auto answer results into no-audio when INVITE comes w/o SDP offer.

SIP: Don't tell application that registration is down when handling redirect response

Status	To-decide
Id	89582

Don't tell application that registration is down when handling redirect response for REGISTER.

Gateway: Missed FAX pages received with the FAX interface

Status	Closed
Id	89587

If the FAX interface is used to receive a FAX document with ECM mode and the transmitting terminal appends additional EOLs, the page counter is wrong and document pages are not written. This is fixed now.

SIP: No T.38 parameter when indicating capabilitity only

Status	To-decide
Id	89617

No T.38 parameter when indicating capabilitity only.

Offer
\tv=0
\to=- 2 1 IN IP4 172.16.16.124
\ts=-
\tt=0 0
\tm=audio 16386 RTP/SAVP 8 101 13
\tc=IN IP4 172.16.16.124
\ta=rtpmap:101 telephone-event/8000
\ta=fmtp:101 0-15
\ta=ptime:20
\ta=silenceSupp:off - - - -
\ta=sendrecv
\ta=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:WJl714I+mpSr47ld1YjYMf8t9xQo0xYHUng1CnDi
\tm=image 0 udptl t38
\tc=IN IP4 172.16.16.124

Instead of
\tv=0
\to=- 2 1 IN IP4 172.16.16.124
\ts=-
\tt=0 0
\tm=audio 16394 RTP/SAVP 8 101 13
\tc=IN IP4 172.16.16.124
\ta=rtpmap:101 telephone-event/8000
\ta=fmtp:101 0-15
\ta=ptime:20
\ta=silenceSupp:off - - - -
\ta=sendrecv
\ta=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:sPngj1zoO9wI1pc1tMTymWCzTgwMoamPuJAFIhga
\tm=image 0 udptl t38
\tc=IN IP4 172.16.16.124
\ta=T38FaxVersion:0
\ta=T38MaxBitRate:14400
\ta=T38FaxFillBitRemoval:0
\ta=T38FaxTranscodingMMR:0
\ta=T38FaxTranscodingJBIG:0
\ta=T38FaxRateManagement:transferredTCF
\ta=T38FaxUdpEC:t38UDPRedundancy

OS: Potential trap when starting a timer, which is already deleted

Status	Closed
Id	89628

Could result in a strange trap with PBX transfer/recall

myPBX launcher: Multi-screen support for video window

Status	Closed
Id	89630

Detect if the window has been moved to a different screen.

PBX Admin UI: Reconfiguring user visibility (Access) did not work correctly

Status	Closed
Id	89636

If a setting for a user/group was deleted, it could happen that some of the settings (Group, Online, Presence, Dialog, Ids) where copied to the next entry.

Media: Redirecting SRTP streams for NAT clients only after successful SRTP authentication

Status	To-decide
Id	89661

Media endpoints support NAT.
If receiving RTP/SRTP from an address other than negotiated one
media endpoints redirecting their media stream towards source of incoming media stream.
In case of SRTP, this NAT workaround is only executed if incoming media stream has passed authentication.
For securitiy reasons.

Office2010 Integration: Own presence did always show the IM presence

Status	Closed
Id	89722

Outlook always showed the IM presence. It should display the mixed presence from all sources.

IP-DECT: Trap with call transfer

Status	Closed
Id	89786

A trap occurs if a call transfer is received in the IP-DECT radio module. This is fixed now.

myPBX: IE8 script error in chat window

Status	Closed
Id	89788

Focusing invisible elements causes an exception in IE8

Zeile: 386
Zeichen: 9
Code: 0
Fehlermeldung: Das Steuerelement kann den Fokus nicht erhalten, da dieses unsichtbar oder nicht aktiviert ist oder keinen Fokus zulässt.
URL: http://xxx.xxx.xxx.xxx/PBX0/MY/mypbx10_im.js?lang=de

IP-DECT: Trap with anonymous login

Status	Closed
Id	89814

A trap can occur during login feature in the IP-DECT radio module. This is fixed now.

'power-off loop' relay switching function failure

Status	Closed
Id	89942

Especially POE-switches with higher supply voltages than 48V lead to a decreased timespan of powering the build-in relays of a ip6010/ip810 gateway. The detection of a power-fail condition is therefore derived from the POE ICs which react earlier and thus increases powering time of the relays.

myPBX: Default group visibility was not displayed correctly

Status	Closed
Id	89954

The default group visibility can be configured from v9hotfix17. Regardless of that configuration myPBX showed full visibility in the visibilty settings.

IP0010 IP1060 IP3010 IP6010 IP810 IP22 IP24 IP28 IP302 IP305: DSP Update to Version 680.07

Status	Closed
Id	89956

Fixed modem bypass with slow modems

myPBX: Make activity area scrollable

Status	Closed
Id	89977

This was a problem when there were more than 3 calls and chats.

Video: minimum size of the jitter buffer was zero at the beginning

Status	To-decide
Id	90001

this made rtp packet processing to start immediately instead of waiting for the jitter buffer to contain at least one whole video frame.

IP-DECT: Don't show DTMF in radio call list

Status	Closed
Id	90034

User dialled digits during calls which are sent as DTMF should not be shown in the radio call list. This is fixed now.

myPBX: Different background for activity area

Status	Closed
Id	90049

Do not use CSS gradients but an image for the background of the activity area.

myPBX: Remove unneeded tooltips

Status	Closed
Id	90051

- Deactivate tooltips for presence description when presence drop down is active.
- Remove tooltips for prompted input fields. They were always the same as the displayed text.
- Remove tooltips for icons of drop down menu items. They were always the same as the displayed text.

H.323: Allow media offers with 0.0.0.0 as address

Status	To-decide
Id	90053

Needed for SIP interoperability. Some third party SIP PBXs use addresses of 0.0.0.0 to indicate that they don't receive media. This may happens if an endpoint is put on hold. We did not forward such an offer and thus no Music on Hold was heard.

PBX: Busy On ... Calls at PBX objects did not take into acccount that a call may be routed back to Slave

Status	To-decide
Id	90054

The busy on ... calls on PBX objects can be used to limit bandwidth usage between a master and a slave to a certain number of calls. Some calls are sent from a slave to the master and back to the slave if the routing decision cannot be done on the slave alone. This happens if escapes are used which overlap other obects (e.g. the local trunk). It is a common configuration the the E.164 routing scheme.
With this fix, these calls are not counted for this purpose.

Video: memory was not freed

Status	To-decide
Id	90086

- memory belonging to the dxva2 context.
- decoder object in the windows decoder.
- Buffer in device3D.

H.323: Support for registration from a private network thru NAT

Status	To-decide
Id	90306

In case an endpoint registers to a PBX from within a private network thru a NAT router, the signaling TCP connection must be maintained in order to be able to receive calls. When the registration is up a dummy call is sent to the PBX to establish the signaling TCP. This TCP connection is maintained after the dummy call is cleared. If this TCP connection is lost (e.g. NAT Router reset), the Registration is cleared and restarted, so that after the re-registration another dummy call is sent.

This is a fix for the previous fix

fix: #89497: H.323: Automatically connect signaling TCP if NAT router is detected

which did not work well

HTTP: Force HTTPs did not work with websocket protocol

Status	Closed
Id	90355

Use wss: URI scheme for redirecting websocket requests to the TLS port.

myPBX launcher: Allow non-ASCII characters in user names and passwords for RemoteVideo

Status	Closed
Id	90398

Conversion from UTF-16 to UTF-8 is needed when calling the websocket DLLs.

PBX: CC Requests were sent with wrong number if a SendNumber was configured at the user

Status	To-decide
Id	90432

Usually this is no problem only when interworking with some QSIG PBX's this causes the call-completion to fail.

myPBX: Use the same presence contact as the phones

Status	Closed
Id	90434

myPBX no longer sets the im: presence but the tel: presence. This means that the same presence can be managed on the phone and in myPBX.

If an old im: presence is stored in the PBX it is removed the next time the user sets the presence from myPBX.

Possible trap when doing a leak check

Status	To-decide
Id	90451

When many leaks exist or leak check is done when much tracing is turned on. The leak check itself could cause a watchdog trap, because the collecting of the leaks is done on highest priority so not even the timer interrupt could trigger the watchdog.

myPBX launcher: Possible exception when starting myPBX

Status	Closed
Id	90453

Depending on the timing there could be an exception when starting myPBX. This happened because the flow for initializing the video and webcam window was unsafe.

IP-DECT: Busy state on maximum call count

Status	Closed
Id	90461

The base station does not go to the busy state if the maximum call count is reached and the last call is an incoming call. This is fixed now.

PBX: Support for Opticaller Data Callthru did not work

Status	To-decide
Id	90480

Support for Opticaller data callthru was added, but did not work

PBX: Forking a call to a Trunk with "Outgoing call restricted", causes the original call to be restricted as well

Status	To-decide
Id	90487

The "Outgoing call restricted" flag on the trunk object to which the call was forked caused the call as a whole to be marked as Calling Line Presentation Restricted.

Other Bug Fixes

89840

dde

Restart COM-Server after failed method call to an Office application

ReleaseNotes10:Firmware