ReleaseNotes10:Firmware: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
← Older editNewer edit →
VisualWikitext
m regular roadmap update
m regular roadmap update
Line 26: Line 26:
|[http://mantis.innovaphone.com/view.php?id=89440 89440]
|[http://mantis.innovaphone.com/view.php?id=89440 89440]
|}
|}
The PBX broadcast conference object supports the online state in myPBX dependent on its configuration and its group members' online state now.<br/><br/><!--<br/>Changed files:<br/>pbx_bc_conf.h<br/>pbx_bc_conf.cpp<br/>-->
The PBX broadcast conference object supports the online state in myPBX dependent on its configuration and its group members' online state now.<br/><br/><!--<br/>Changed files:<br/>pbx_bc_conf.h<br/>pbx_bc_conf.cpp<br/>--><!---->
      
      
=== myPBX: Encoding of conference video stream ===
=== myPBX: Encoding of conference video stream ===
Line 37: Line 37:
|[http://mantis.innovaphone.com/view.php?id=89455 89455]
|[http://mantis.innovaphone.com/view.php?id=89455 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.<br/><!--<br/>videoWriter.cpp<br/>formatConversion.cpp<br/>formatConversion.h<br/>-->
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.<br/><!--<br/>videoWriter.cpp<br/>formatConversion.cpp<br/>formatConversion.h<br/>--><!---->
      
      
=== H.323: Automatically connect signaling TCP if NAT router is detected ===
=== H.323: Automatically connect signaling TCP if NAT router is detected ===
Line 48: Line 48:
|[http://mantis.innovaphone.com/view.php?id=89497 89497]
|[http://mantis.innovaphone.com/view.php?id=89497 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.<br/><!--<br/>h323sig.cpp<br/>h323ras.cpp<br/>h323.h<br/>h323asn1.h<br/>-->
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.<br/><!--<br/>h323sig.cpp<br/>h323ras.cpp<br/>h323.h<br/>h323asn1.h<br/>--><!---->
      
      
=== myPBX: Pickup calls ===
=== myPBX: Pickup calls ===
Line 59: Line 59:
|[http://mantis.innovaphone.com/view.php?id=89536 89536]
|[http://mantis.innovaphone.com/view.php?id=89536 89536]
|}
|}
Pickup calls that are alerting at a favourite contact.<br/><!--<br/>pbx_client.cpp<br/>pbx_client.h<br/>pbx.cpp<br/>-->
Pickup calls that are alerting at a favourite contact.<br/><!--<br/>pbx_client.cpp<br/>pbx_client.h<br/>pbx.cpp<br/>--><!---->
      
      
=== myPBX: Show needed browser features that are deactivated ===
=== myPBX: Show needed browser features that are deactivated ===
Line 70: Line 70:
|[http://mantis.innovaphone.com/view.php?id=89542 89542]
|[http://mantis.innovaphone.com/view.php?id=89542 89542]
|}
|}
To be implemented in version 10.<br/><!--<br/>mypbx10.htm<br/>mypbx10.js<br/>mypbx10.css<br/>mypbx10_browser_nok.png<br/>mypbx10_browser_ok.png<br/>pbx/pbx.mak<br/>pbx_client_localisation.cpp<br/>-->
To be implemented in version 10.<br/><!--<br/>mypbx10.htm<br/>mypbx10.js<br/>mypbx10.css<br/>mypbx10_browser_nok.png<br/>mypbx10_browser_ok.png<br/>pbx/pbx.mak<br/>pbx_client_localisation.cpp<br/>--><!---->
      
      
=== PRI-QSIG: Interop config for channel numbering ===
=== PRI-QSIG: Interop config for channel numbering ===
Line 81: Line 81:
|[http://mantis.innovaphone.com/view.php?id=89578 89578]
|[http://mantis.innovaphone.com/view.php?id=89578 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.<br/><br/>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.<br/><!--<br/>q931.cpp<br/>q931.h<br/>isdn_interop.xsl<br/>-->
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.<br/><br/>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.<br/><!--<br/>q931.cpp<br/>q931.h<br/>isdn_interop.xsl<br/>--><!---->
      
      
=== PBX: Support of long user-user-informations by SOAP ===
=== PBX: Support of long user-user-informations by SOAP ===
Line 92: Line 92:
|[http://mantis.innovaphone.com/view.php?id=90029 90029]
|[http://mantis.innovaphone.com/view.php?id=90029 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.<br/>It is required by the FAX interface.<br/><br/><!--<br/>Changed files:<br/>pbx_xml.h<br/>pbx_xml.cpp<br/>-->
Support of long user-user-informations (UUI) for SOAP sessions added. A long UUI is split into multiple short UUIs supported by Q.931.<br/>It is required by the FAX interface.<br/><br/><!--<br/>Changed files:<br/>pbx_xml.h<br/>pbx_xml.cpp<br/>--><!---->
      
      
=== Relay: Support of long user-user-informations by FAX ===
=== Relay: Support of long user-user-informations by FAX ===
Line 103: Line 103:
|[http://mantis.innovaphone.com/view.php?id=90030 90030]
|[http://mantis.innovaphone.com/view.php?id=90030 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.<br/><br/><!--<br/>Changed files:<br/>webfax.h<br/>webfax.cpp<br/>-->
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.<br/><br/><!--<br/>Changed files:<br/>webfax.h<br/>webfax.cpp<br/>--><!---->
      
      
=== Gateway: Support of a header line for FAX documents ===
=== Gateway: Support of a header line for FAX documents ===
Line 114: Line 114:
|[http://mantis.innovaphone.com/view.php?id=90374 90374]
|[http://mantis.innovaphone.com/view.php?id=90374 90374]
|}
|}
Support of a header line for FAX documents is added in the FAX interface.<br/><br/><!--<br/>Changed files:<br/>webfax.h<br/>webfax.cpp<br/>t30.h<br/>t30.cpp<br/>t4.h<br/>t4.cpp<br/>facsimile_g3.h<br/>facsimile_g3.cpp<br/>--><br/>
Support of a header line for FAX documents is added in the FAX interface.<br/><br/><!--<br/>Changed files:<br/>webfax.h<br/>webfax.cpp<br/>t30.h<br/>t30.cpp<br/>t4.h<br/>t4.cpp<br/>facsimile_g3.h<br/>facsimile_g3.cpp<br/>--><br/><!---->
      
      
=== ISDN: No alarms for link down in case of interop flag "passive Layer2" ===
=== ISDN: No alarms for link down in case of interop flag "passive Layer2" ===
Line 125: Line 125:
|[http://mantis.innovaphone.com/view.php?id=90383 90383]
|[http://mantis.innovaphone.com/view.php?id=90383 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.<br/><!--<br/>q931.cpp<br/>-->
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.<br/><!--<br/>q931.cpp<br/>--><!---->
      
      
=== PBX Waiting: Support of RTP-DTMF for two-stage dialing ===
=== PBX Waiting: Support of RTP-DTMF for two-stage dialing ===
Line 136: Line 136:
|[http://mantis.innovaphone.com/view.php?id=90425 90425]
|[http://mantis.innovaphone.com/view.php?id=90425 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.<br/>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.<br/><!--<br/>pbx_wait.cpp<br/>pbx_wait.h<br/>pbx_edit_waiting.xsl<br/>-->
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.<br/>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.<br/><!--<br/>pbx_wait.cpp<br/>pbx_wait.h<br/>pbx_edit_waiting.xsl<br/>--><!---->
      
      
=== Gateway: Only transparent (clearmode) coder in offer if data call ===
=== Gateway: Only transparent (clearmode) coder in offer if data call ===
Line 147: Line 147:
|[http://mantis.innovaphone.com/view.php?id=90483 90483]
|[http://mantis.innovaphone.com/view.php?id=90483 90483]
|}
|}
This is a SIP interop issue. Some equipment cannot ignore clearmode coder offers, if not supported.<br/><!--<br/>channels.cpp<br/>-->
This is a SIP interop issue. Some equipment cannot ignore clearmode coder offers, if not supported.<br/><!--<br/>channels.cpp<br/>--><!---->
      
      
=== SIP: New interop tweak "No Remote Hold Signaling" ===
=== SIP: New interop tweak "No Remote Hold Signaling" ===
Line 158: Line 158:
|[http://mantis.innovaphone.com/view.php?id=90532 90532]
|[http://mantis.innovaphone.com/view.php?id=90532 90532]
|}
|}
New config option on gateway interfaces "No Remote Hold Signaling".<br/>Disables interworking of "inactive" into remoteHold.<br/><br/><!--<br/>voip.h<br/>sip.cpp<br/>gk.cpp/h<br/>relay_edit_voip.xsl<br/>-->
New config option on gateway interfaces "No Remote Hold Signaling".<br/>Disables interworking of "inactive" into remoteHold.<br/><br/><!--<br/>voip.h<br/>sip.cpp<br/>gk.cpp/h<br/>relay_edit_voip.xsl<br/>--><!---->
      
      
=== PBX-SOAP: Support for 'rc' and 'srce164' on UserCall on Waiting Queue ===
=== PBX-SOAP: Support for 'rc' and 'srce164' on UserCall on Waiting Queue ===
Line 169: Line 169:
|[http://mantis.innovaphone.com/view.php?id=90537 90537]
|[http://mantis.innovaphone.com/view.php?id=90537 90537]
|}
|}
If a Waiting Queue is used for outgoing calls, these features can be usefull for some applications<br/><!--<br/>pbx_api.h<br/>pbx_xml.cpp<br/>pbx_wait.cpp<br/>pbx_wait.h<br/>-->
If a Waiting Queue is used for outgoing calls, these features can be usefull for some applications<br/><!--<br/>pbx_api.h<br/>pbx_xml.cpp<br/>pbx_wait.cpp<br/>pbx_wait.h<br/>--><!---->
      
      
== Bug Fixes ==
== Bug Fixes ==
Line 184: Line 184:
|[http://mantis.innovaphone.com/view.php?id=87416 87416]
|[http://mantis.innovaphone.com/view.php?id=87416 87416]
|}
|}
Start call immediately instead of copying the number/URI to myPBX.<br/><!--<br/>mypbx10.js<br/>-->
Start call immediately instead of copying the number/URI to myPBX.<br/><!--<br/>mypbx10.js<br/>--><!---->
      
      
=== myPBX: Select im session when focusing chat window ===
=== myPBX: Select im session when focusing chat window ===
Line 195: Line 195:
|[http://mantis.innovaphone.com/view.php?id=89490 89490]
|[http://mantis.innovaphone.com/view.php?id=89490 89490]
|}
|}
In order to simplify adding users to the chat.<br/><!--<br/>mypbx10.js<br/>-->
In order to simplify adding users to the chat.<br/><!--<br/>mypbx10.js<br/>--><!---->
      
      
=== PBX Mobility: Conference ID not set for outgoing calls initiated by myPBX ===
=== PBX Mobility: Conference ID not set for outgoing calls initiated by myPBX ===
Line 206: Line 206:
|[http://mantis.innovaphone.com/view.php?id=89502 89502]
|[http://mantis.innovaphone.com/view.php?id=89502 89502]
|}
|}
This could cause several problems:<br/>- 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<br/>- The CDRs created for this call could not be matched
This could cause several problems:<br/>- 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<br/>- The CDRs created for this call could not be matched<!---->
      
      
=== SIP: Auto answer with SDP in ACK ===
=== SIP: Auto answer with SDP in ACK ===
Line 217: Line 217:
|[http://mantis.innovaphone.com/view.php?id=89539 89539]
|[http://mantis.innovaphone.com/view.php?id=89539 89539]
|}
|}
Auto answer results into no-audio when INVITE comes w/o SDP offer.<br/><br/><!--<br/>sip.cpp<br/>-->
Auto answer results into no-audio when INVITE comes w/o SDP offer.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== SIP: Don't tell application that registration is down when handling redirect response ===
=== SIP: Don't tell application that registration is down when handling redirect response ===
Line 228: Line 228:
|[http://mantis.innovaphone.com/view.php?id=89582 89582]
|[http://mantis.innovaphone.com/view.php?id=89582 89582]
|}
|}
Don't tell application that registration is down when handling redirect response for REGISTER.<br/><br/><!--<br/>sip.cpp<br/>-->
Don't tell application that registration is down when handling redirect response for REGISTER.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== Gateway: Missed FAX pages received with the FAX interface ===
=== Gateway: Missed FAX pages received with the FAX interface ===
Line 239: Line 239:
|[http://mantis.innovaphone.com/view.php?id=89587 89587]
|[http://mantis.innovaphone.com/view.php?id=89587 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.<br/><br/><!--<br/>Changed files:<br/>t30.cpp<br/>facsimile_g3.h<br/>facsimile_g3.cpp<br/>facsimile_ECM.h<br/>facsimile_ECM.cpp<br/>-->
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.<br/><br/><!--<br/>Changed files:<br/>t30.cpp<br/>facsimile_g3.h<br/>facsimile_g3.cpp<br/>facsimile_ECM.h<br/>facsimile_ECM.cpp<br/>--><!---->
      
      
=== SIP: No T.38  parameter when indicating capabilitity only ===
=== SIP: No T.38  parameter when indicating capabilitity only ===
Line 250: Line 250:
|[http://mantis.innovaphone.com/view.php?id=89617 89617]
|[http://mantis.innovaphone.com/view.php?id=89617 89617]
|}
|}
No T.38  parameter when indicating capabilitity only.<br/><br/>Offer<br/>\tv=0<br/>\to=- 2 1 IN IP4 172.16.16.124<br/>\ts=-<br/>\tt=0 0<br/>\tm=audio 16386 RTP/SAVP 8 101 13<br/>\tc=IN IP4 172.16.16.124<br/>\ta=rtpmap:101 telephone-event/8000<br/>\ta=fmtp:101 0-15<br/>\ta=ptime:20<br/>\ta=silenceSupp:off - - - -<br/>\ta=sendrecv<br/>\ta=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:WJl714I+mpSr47ld1YjYMf8t9xQo0xYHUng1CnDi<br/>\tm=image 0 udptl t38<br/>\tc=IN IP4 172.16.16.124<br/><br/>Instead of<br/>\tv=0<br/>\to=- 2 1 IN IP4 172.16.16.124<br/>\ts=-<br/>\tt=0 0<br/>\tm=audio 16394 RTP/SAVP 8 101 13<br/>\tc=IN IP4 172.16.16.124<br/>\ta=rtpmap:101 telephone-event/8000<br/>\ta=fmtp:101 0-15<br/>\ta=ptime:20<br/>\ta=silenceSupp:off - - - -<br/>\ta=sendrecv<br/>\ta=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:sPngj1zoO9wI1pc1tMTymWCzTgwMoamPuJAFIhga<br/>\tm=image 0 udptl t38<br/>\tc=IN IP4 172.16.16.124<br/>\ta=T38FaxVersion:0<br/>\ta=T38MaxBitRate:14400<br/>\ta=T38FaxFillBitRemoval:0<br/>\ta=T38FaxTranscodingMMR:0<br/>\ta=T38FaxTranscodingJBIG:0<br/>\ta=T38FaxRateManagement:transferredTCF<br/>\ta=T38FaxUdpEC:t38UDPRedundancy<br/><br/><br/><!--<br/>sdpmsg.cpp<br/>-->
No T.38  parameter when indicating capabilitity only.<br/><br/>Offer<br/>\tv=0<br/>\to=- 2 1 IN IP4 172.16.16.124<br/>\ts=-<br/>\tt=0 0<br/>\tm=audio 16386 RTP/SAVP 8 101 13<br/>\tc=IN IP4 172.16.16.124<br/>\ta=rtpmap:101 telephone-event/8000<br/>\ta=fmtp:101 0-15<br/>\ta=ptime:20<br/>\ta=silenceSupp:off - - - -<br/>\ta=sendrecv<br/>\ta=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:WJl714I+mpSr47ld1YjYMf8t9xQo0xYHUng1CnDi<br/>\tm=image 0 udptl t38<br/>\tc=IN IP4 172.16.16.124<br/><br/>Instead of<br/>\tv=0<br/>\to=- 2 1 IN IP4 172.16.16.124<br/>\ts=-<br/>\tt=0 0<br/>\tm=audio 16394 RTP/SAVP 8 101 13<br/>\tc=IN IP4 172.16.16.124<br/>\ta=rtpmap:101 telephone-event/8000<br/>\ta=fmtp:101 0-15<br/>\ta=ptime:20<br/>\ta=silenceSupp:off - - - -<br/>\ta=sendrecv<br/>\ta=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:sPngj1zoO9wI1pc1tMTymWCzTgwMoamPuJAFIhga<br/>\tm=image 0 udptl t38<br/>\tc=IN IP4 172.16.16.124<br/>\ta=T38FaxVersion:0<br/>\ta=T38MaxBitRate:14400<br/>\ta=T38FaxFillBitRemoval:0<br/>\ta=T38FaxTranscodingMMR:0<br/>\ta=T38FaxTranscodingJBIG:0<br/>\ta=T38FaxRateManagement:transferredTCF<br/>\ta=T38FaxUdpEC:t38UDPRedundancy<br/><br/><br/><!--<br/>sdpmsg.cpp<br/>--><!---->
      
      
=== OS: Potential trap when starting a timer, which is already deleted ===
=== OS: Potential trap when starting a timer, which is already deleted ===
Line 261: Line 261:
|[http://mantis.innovaphone.com/view.php?id=89628 89628]
|[http://mantis.innovaphone.com/view.php?id=89628 89628]
|}
|}
Could result in a strange trap with PBX transfer/recall
Could result in a strange trap with PBX transfer/recall<!---->
      
      
=== myPBX launcher: Multi-screen support for video window ===
=== myPBX launcher: Multi-screen support for video window ===
Line 272: Line 272:
|[http://mantis.innovaphone.com/view.php?id=89630 89630]
|[http://mantis.innovaphone.com/view.php?id=89630 89630]
|}
|}
Detect if the window has been moved to a different screen.<br/><!--<br/>IRemoteVideoDisplay.cs<br/>RemoteVideoConnection.cs<br/>ctiwin.cs<br/>VideoForm.cs<br/>VideoDll.cs<br/>Video/dll_interface.h<br/>Video/dll_interface.cpp<br/>Video/videoReader.cpp<br/>Video/videoReader.h<br/>Video/videoWriter.cpp<br/>Video/videoWriter.h<br/>-->
Detect if the window has been moved to a different screen.<br/><!--<br/>IRemoteVideoDisplay.cs<br/>RemoteVideoConnection.cs<br/>ctiwin.cs<br/>VideoForm.cs<br/>VideoDll.cs<br/>Video/dll_interface.h<br/>Video/dll_interface.cpp<br/>Video/videoReader.cpp<br/>Video/videoReader.h<br/>Video/videoWriter.cpp<br/>Video/videoWriter.h<br/>--><!---->
      
      
=== PBX Admin UI: Reconfiguring user visibility (Access) did not work correctly ===
=== PBX Admin UI: Reconfiguring user visibility (Access) did not work correctly ===
Line 283: Line 283:
|[http://mantis.innovaphone.com/view.php?id=89636 89636]
|[http://mantis.innovaphone.com/view.php?id=89636 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.<br/><!--<br/>pbx_admin.cpp<br/>-->
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.<br/><!--<br/>pbx_admin.cpp<br/>--><!---->
      
      
=== Media: Redirecting SRTP streams for NAT clients only after successful SRTP authentication ===
=== Media: Redirecting SRTP streams for NAT clients only after successful SRTP authentication ===
Line 294: Line 294:
|[http://mantis.innovaphone.com/view.php?id=89661 89661]
|[http://mantis.innovaphone.com/view.php?id=89661 89661]
|}
|}
Media endpoints support NAT.<br/>If receiving RTP/SRTP from an address other than negotiated one<br/>media endpoints redirecting their media stream towards source of incoming media stream.<br/>In case of SRTP, this NAT workaround is only executed if incoming media stream has passed authentication.<br/>For securitiy reasons.<br/><br/><!--<br/>media.cpp<br/>-->
Media endpoints support NAT.<br/>If receiving RTP/SRTP from an address other than negotiated one<br/>media endpoints redirecting their media stream towards source of incoming media stream.<br/>In case of SRTP, this NAT workaround is only executed if incoming media stream has passed authentication.<br/>For securitiy reasons.<br/><br/><!--<br/>media.cpp<br/>--><!---->
      
      
=== Office2010 Integration: Own presence did always show the IM presence ===
=== Office2010 Integration: Own presence did always show the IM presence ===
Line 305: Line 305:
|[http://mantis.innovaphone.com/view.php?id=89722 89722]
|[http://mantis.innovaphone.com/view.php?id=89722 89722]
|}
|}
Outlook always showed the IM presence. It should display the mixed presence from all sources.<br/><!--<br/>MyPBXOfficeIntegration.cs<br/>-->
Outlook always showed the IM presence. It should display the mixed presence from all sources.<br/><!--<br/>MyPBXOfficeIntegration.cs<br/>--><!---->
      
      
=== IP-DECT: Trap with call transfer ===
=== IP-DECT: Trap with call transfer ===
Line 316: Line 316:
|[http://mantis.innovaphone.com/view.php?id=89786 89786]
|[http://mantis.innovaphone.com/view.php?id=89786 89786]
|}
|}
A trap occurs if a call transfer is received in the IP-DECT radio module. This is fixed now.<br/><br/><!--<br/>Changed file:<br/>dectradio.cpp<br/>-->
A trap occurs if a call transfer is received in the IP-DECT radio module. This is fixed now.<br/><br/><!--<br/>Changed file:<br/>dectradio.cpp<br/>--><!---->
      
      
=== myPBX: IE8 script error in chat window ===
=== myPBX: IE8 script error in chat window ===
Line 327: Line 327:
|[http://mantis.innovaphone.com/view.php?id=89788 89788]
|[http://mantis.innovaphone.com/view.php?id=89788 89788]
|}
|}
Focusing invisible elements causes an exception in IE8<br/><br/>Zeile: 386<br/>Zeichen: 9<br/>Code: 0<br/>Fehlermeldung: Das Steuerelement kann den Fokus nicht erhalten, da dieses unsichtbar oder nicht aktiviert ist oder keinen Fokus zulässt.<br/>URL: http://xxx.xxx.xxx.xxx/PBX0/MY/mypbx10_im.js?lang=de<br/><br/><!--<br/>mypbx10_im.js<br/>-->
Focusing invisible elements causes an exception in IE8<br/><br/>Zeile: 386<br/>Zeichen: 9<br/>Code: 0<br/>Fehlermeldung: Das Steuerelement kann den Fokus nicht erhalten, da dieses unsichtbar oder nicht aktiviert ist oder keinen Fokus zulässt.<br/>URL: http://xxx.xxx.xxx.xxx/PBX0/MY/mypbx10_im.js?lang=de<br/><br/><!--<br/>mypbx10_im.js<br/>--><!---->
      
      
=== IP-DECT: Trap with anonymous login ===
=== IP-DECT: Trap with anonymous login ===
Line 338: Line 338:
|[http://mantis.innovaphone.com/view.php?id=89814 89814]
|[http://mantis.innovaphone.com/view.php?id=89814 89814]
|}
|}
A trap can occur during login feature in the IP-DECT radio module. This is fixed now.<br/><br/><!--<br/>Changed file:<br/>dectradio-call.cpp<br/>-->
A trap can occur during login feature in the IP-DECT radio module. This is fixed now.<br/><br/><!--<br/>Changed file:<br/>dectradio-call.cpp<br/>--><!---->
      
      
=== Restart COM-Server after failed method call to an Office application ===
=== Restart COM-Server after failed method call to an Office application ===
Line 349: Line 349:
|[http://mantis.innovaphone.com/view.php?id=89840 89840]
|[http://mantis.innovaphone.com/view.php?id=89840 89840]
|}
|}
If the connection between an Office application and myPBX gets lost, the COM Server is now restarted.<br/>This forces a reload of the web UI and a reset of the video connection too.<br/><br/><!--<br/>ctiwin.cs<br/>MessengerContacts.cs<br/>UCOfficeIntegration.cs<br/>COMServer.cs<br/>-->
If the connection between an Office application and myPBX gets lost, the COM Server is now restarted.<br/>This forces a reload of the web UI and a reset of the video connection too.<br/><br/><!--<br/>ctiwin.cs<br/>MessengerContacts.cs<br/>UCOfficeIntegration.cs<br/>COMServer.cs<br/>--><!---->
      
      
=== 'power-off loop' relay switching function failure ===
=== 'power-off loop' relay switching function failure ===
Line 360: Line 360:
|[http://mantis.innovaphone.com/view.php?id=89942 89942]
|[http://mantis.innovaphone.com/view.php?id=89942 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.
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 ===
=== myPBX: Default group visibility was not displayed correctly ===
Line 371: Line 371:
|[http://mantis.innovaphone.com/view.php?id=89954 89954]
|[http://mantis.innovaphone.com/view.php?id=89954 89954]
|}
|}
The default group visibility can be configured from v9hotfix17. Regardless of that configuration myPBX showed full visibility in the visibilty settings.<br/><!--<br/>pbx_api.h<br/>pbx.h<br/>pbx_client.cpp<br/>-->
The default group visibility can be configured from v9hotfix17. Regardless of that configuration myPBX showed full visibility in the visibilty settings.<br/><!--<br/>pbx_api.h<br/>pbx.h<br/>pbx_client.cpp<br/>--><!---->
      
      
=== IP0010 IP1060 IP3010 IP6010 IP810 IP22 IP24 IP28 IP302 IP305: DSP Update to Version 680.07 ===
=== IP0010 IP1060 IP3010 IP6010 IP810 IP22 IP24 IP28 IP302 IP305: DSP Update to Version 680.07 ===
Line 382: Line 382:
|[http://mantis.innovaphone.com/view.php?id=89956 89956]
|[http://mantis.innovaphone.com/view.php?id=89956 89956]
|}
|}
Fixed modem bypass with slow modems<br/><br/><!-- <br/>DSP code details at <br/>\\\\innovaphone.sifi\\dfs\\Dokumente\\Hardware\\G7xx\\Audiocodes\\firmware\\firmware_ac49x\\680.07<br/><br/>ac49x_680/ac49*.h  ac_494e.cpp ac_491.cpp ac_dsp3.cpp<br/><br/>Also AC494 DSP clock changed from 100 to 125MHz and report interval changed to 5seconds. <br/>-->
Fixed modem bypass with slow modems<br/><br/><!-- <br/>DSP code details at <br/>\\\\innovaphone.sifi\\dfs\\Dokumente\\Hardware\\G7xx\\Audiocodes\\firmware\\firmware_ac49x\\680.07<br/><br/>ac49x_680/ac49*.h  ac_494e.cpp ac_491.cpp ac_dsp3.cpp<br/><br/>Also AC494 DSP clock changed from 100 to 125MHz and report interval changed to 5seconds. <br/>--><!---->
      
      
=== myPBX: Make activity area scrollable ===
=== myPBX: Make activity area scrollable ===
Line 393: Line 393:
|[http://mantis.innovaphone.com/view.php?id=89977 89977]
|[http://mantis.innovaphone.com/view.php?id=89977 89977]
|}
|}
This was a problem when there were more than 3 calls and chats.<br/><!--<br/>mypbx10.htm<br/>mypbx10.js<br/>mypbx10.css<br/>-->
This was a problem when there were more than 3 calls and chats.<br/><!--<br/>mypbx10.htm<br/>mypbx10.js<br/>mypbx10.css<br/>--><!---->
      
      
=== Video: minimum size of the jitter buffer was zero at the beginning ===
=== Video: minimum size of the jitter buffer was zero at the beginning ===
Line 404: Line 404:
|[http://mantis.innovaphone.com/view.php?id=90001 90001]
|[http://mantis.innovaphone.com/view.php?id=90001 90001]
|}
|}
this made rtp packet processing to start immediately instead of waiting for the jitter buffer to contain at least one whole video frame.<br/><br/><!--<br/>videoWriter.cpp<br/>-->
this made rtp packet processing to start immediately instead of waiting for the jitter buffer to contain at least one whole video frame.<br/><br/><!--<br/>videoWriter.cpp<br/>--><!---->
      
      
=== IP-DECT: Don't show DTMF in radio call list ===
=== IP-DECT: Don't show DTMF in radio call list ===
Line 415: Line 415:
|[http://mantis.innovaphone.com/view.php?id=90034 90034]
|[http://mantis.innovaphone.com/view.php?id=90034 90034]
|}
|}
User dialled digits during calls which are sent as DTMF should not be shown in the radio call list. This is fixed now.<br/><br/><!--<br/>Changed files:<br/>dect_comcerto/platform/config.h<br/>ip1201/platform/config.h<br/>ip4001/platform/config.h<br/>dectradio.h<br/>dectradio.cpp<br/>dectradio_mastercall.cpp<br/>-->
User dialled digits during calls which are sent as DTMF should not be shown in the radio call list. This is fixed now.<br/><br/><!--<br/>Changed files:<br/>dect_comcerto/platform/config.h<br/>ip1201/platform/config.h<br/>ip4001/platform/config.h<br/>dectradio.h<br/>dectradio.cpp<br/>dectradio_mastercall.cpp<br/>--><!---->
      
      
=== myPBX: Different background for activity area ===
=== myPBX: Different background for activity area ===
Line 426: Line 426:
|[http://mantis.innovaphone.com/view.php?id=90049 90049]
|[http://mantis.innovaphone.com/view.php?id=90049 90049]
|}
|}
Do not use CSS gradients but an image for the background of the activity area.<br/><!--<br/>mypbx10_background_activity_gradient.png<br/>mypbx10_background_activity_logo.png<br/>mypbx10_background_activity_spot.png<br/>mypbx10.css<br/>pbx.mak<br/>-->
Do not use CSS gradients but an image for the background of the activity area.<br/><!--<br/>mypbx10_background_activity_gradient.png<br/>mypbx10_background_activity_logo.png<br/>mypbx10_background_activity_spot.png<br/>mypbx10.css<br/>pbx.mak<br/>--><!---->
      
      
=== myPBX: Remove unneeded tooltips ===
=== myPBX: Remove unneeded tooltips ===
Line 437: Line 437:
|[http://mantis.innovaphone.com/view.php?id=90051 90051]
|[http://mantis.innovaphone.com/view.php?id=90051 90051]
|}
|}
- Deactivate tooltips for presence description when presence drop down is active.<br/>- Remove tooltips for prompted input fields. They were always the same as the displayed text.<br/>- Remove tooltips for icons of drop down menu items. They were always the same as the displayed text.<br/><!--<br/>mypbx10_drop_down.js<br/>mypbx10_presence_input.js<br/>mypbx10_prompted_input.js<br/>-->
- Deactivate tooltips for presence description when presence drop down is active.<br/>- Remove tooltips for prompted input fields. They were always the same as the displayed text.<br/>- Remove tooltips for icons of drop down menu items. They were always the same as the displayed text.<br/><!--<br/>mypbx10_drop_down.js<br/>mypbx10_presence_input.js<br/>mypbx10_prompted_input.js<br/>--><!---->
      
      
=== H.323: Allow media offers with 0.0.0.0 as address ===
=== H.323: Allow media offers with 0.0.0.0 as address ===
Line 448: Line 448:
|[http://mantis.innovaphone.com/view.php?id=90053 90053]
|[http://mantis.innovaphone.com/view.php?id=90053 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.<br/><!--<br/>h323ch.cpp<br/>-->
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.<br/><!--<br/>h323ch.cpp<br/>--><!---->
      
      
=== PBX: Busy On ... Calls at PBX objects did not take into acccount that a call may be routed back to Slave ===
=== PBX: Busy On ... Calls at PBX objects did not take into acccount that a call may be routed back to Slave ===
Line 459: Line 459:
|[http://mantis.innovaphone.com/view.php?id=90054 90054]
|[http://mantis.innovaphone.com/view.php?id=90054 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.<br/>With this fix, these calls are not counted for this purpose.<br/><!--<br/>pbx.cpp<br/>pbx.h<br/>pbx_api.h<br/>pbx_wait.cpp<br/>pbx_wait.h<br/>pbx_trunk.h<br/>pbx_gw.h<br/>pbx_exec.h<br/>pbx_bc_conf.cpp<br/>pbx_bc_conf.h<br/>-->
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.<br/>With this fix, these calls are not counted for this purpose.<br/><!--<br/>pbx.cpp<br/>pbx.h<br/>pbx_api.h<br/>pbx_wait.cpp<br/>pbx_wait.h<br/>pbx_trunk.h<br/>pbx_gw.h<br/>pbx_exec.h<br/>pbx_bc_conf.cpp<br/>pbx_bc_conf.h<br/>--><!---->
      
      
=== Video: memory was not freed ===
=== Video: memory was not freed ===
Line 470: Line 470:
|[http://mantis.innovaphone.com/view.php?id=90086 90086]
|[http://mantis.innovaphone.com/view.php?id=90086 90086]
|}
|}
- memory belonging to the dxva2 context.<br/>- decoder object in the windows decoder.<br/>- Buffer in device3D.
- memory belonging to the dxva2 context.<br/>- decoder object in the windows decoder.<br/>- Buffer in device3D.<!---->
      
      
=== H.323: Support for registration from a private network thru NAT ===
=== H.323: Support for registration from a private network thru NAT ===
Line 481: Line 481:
|[http://mantis.innovaphone.com/view.php?id=90306 90306]
|[http://mantis.innovaphone.com/view.php?id=90306 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.<br/><br/>This is a fix for the previous fix<br/><br/>fix: #89497: H.323: Automatically connect signaling TCP if NAT router is detected<br/><br/>which did not work well<br/><!--<br/>h323sig.cpp<br/>h323.h<br/>voip.h<br/>gk.cpp<br/>relay.cpp<br/>relay_api.h<br/>relay.h<br/>-->
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.<br/><br/>This is a fix for the previous fix<br/><br/>fix: #89497: H.323: Automatically connect signaling TCP if NAT router is detected<br/><br/>which did not work well<br/><!--<br/>h323sig.cpp<br/>h323.h<br/>voip.h<br/>gk.cpp<br/>relay.cpp<br/>relay_api.h<br/>relay.h<br/>--><!---->
      
      
=== HTTP: Force HTTPs did not work with websocket protocol ===
=== HTTP: Force HTTPs did not work with websocket protocol ===
Line 492: Line 492:
|[http://mantis.innovaphone.com/view.php?id=90355 90355]
|[http://mantis.innovaphone.com/view.php?id=90355 90355]
|}
|}
Use wss: URI scheme for redirecting websocket requests to the TLS port.<br/><!--<br/>http.cpp<br/>test/10.00/unit-tests/http/websocket/110-ws-handshake-redirect-wss.xml<br/>-->
Use wss: URI scheme for redirecting websocket requests to the TLS port.<br/><!--<br/>http.cpp<br/>test/10.00/unit-tests/http/websocket/110-ws-handshake-redirect-wss.xml<br/>--><!---->
      
      
=== myPBX launcher: Allow non-ASCII characters in user names and passwords for RemoteVideo ===
=== myPBX launcher: Allow non-ASCII characters in user names and passwords for RemoteVideo ===
Line 503: Line 503:
|[http://mantis.innovaphone.com/view.php?id=90398 90398]
|[http://mantis.innovaphone.com/view.php?id=90398 90398]
|}
|}
Conversion from UTF-16 to UTF-8 is needed when calling the websocket DLLs.<br/><!--<br/>Native.cs<br/>DevicesWebsocketDll.cs<br/>VideoWebsocketDll.cs<br/>-->
Conversion from UTF-16 to UTF-8 is needed when calling the websocket DLLs.<br/><!--<br/>Native.cs<br/>DevicesWebsocketDll.cs<br/>VideoWebsocketDll.cs<br/>--><!---->
      
      
=== PBX: CC Requests were sent with wrong number if a SendNumber was configured at the user ===
=== PBX: CC Requests were sent with wrong number if a SendNumber was configured at the user ===
Line 514: Line 514:
|[http://mantis.innovaphone.com/view.php?id=90432 90432]
|[http://mantis.innovaphone.com/view.php?id=90432 90432]
|}
|}
Usually this is no problem only when interworking with some QSIG PBX's this causes the call-completion to fail.<br/><!--<br/>pbx.cpp<br/>-->
Usually this is no problem only when interworking with some QSIG PBX's this causes the call-completion to fail.<br/><!--<br/>pbx.cpp<br/>--><!---->
      
      
=== myPBX: Use the same presence contact as the phones ===
=== myPBX: Use the same presence contact as the phones ===
Line 525: Line 525:
|[http://mantis.innovaphone.com/view.php?id=90434 90434]
|[http://mantis.innovaphone.com/view.php?id=90434 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.<br/><br/>If an old im: presence is stored in the PBX it is removed the next time the user sets the presence from myPBX.<br/><!--<br/>pbx_client.cpp<br/>pbx_client.h<br/>-->
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.<br/><br/>If an old im: presence is stored in the PBX it is removed the next time the user sets the presence from myPBX.<br/><!--<br/>pbx_client.cpp<br/>pbx_client.h<br/>--><!---->
      
      
=== Possible trap when doing a leak check ===
=== Possible trap when doing a leak check ===
Line 536: Line 536:
|[http://mantis.innovaphone.com/view.php?id=90451 90451]
|[http://mantis.innovaphone.com/view.php?id=90451 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.<br/><!--<br/>os.cpp<br/>-->
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.<br/><!--<br/>os.cpp<br/>--><!---->
      
      
=== myPBX launcher: Possible exception when starting myPBX ===
=== myPBX launcher: Possible exception when starting myPBX ===
Line 547: Line 547:
|[http://mantis.innovaphone.com/view.php?id=90453 90453]
|[http://mantis.innovaphone.com/view.php?id=90453 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.<br/><!--<br/>ctiwin.cs<br/>VideoForm.cs<br/>-->
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.<br/><!--<br/>ctiwin.cs<br/>VideoForm.cs<br/>--><!---->
      
      
=== IP-DECT: Busy state on maximum call count ===
=== IP-DECT: Busy state on maximum call count ===
Line 558: Line 558:
|[http://mantis.innovaphone.com/view.php?id=90461 90461]
|[http://mantis.innovaphone.com/view.php?id=90461 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.<br/><br/><!--<br/>Changed files:<br/>dectradio.cpp<br/>dectradio_dectcall.cpp<br/>-->
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.<br/><br/><!--<br/>Changed files:<br/>dectradio.cpp<br/>dectradio_dectcall.cpp<br/>--><!---->
      
      
=== PBX: Support for Opticaller Data Callthru did not work ===
=== PBX: Support for Opticaller Data Callthru did not work ===
Line 569: Line 569:
|[http://mantis.innovaphone.com/view.php?id=90480 90480]
|[http://mantis.innovaphone.com/view.php?id=90480 90480]
|}
|}
Support for Opticaller data callthru was added, but did not work<br/><!--<br/>pbx_admin.cpp<br/>-->
Support for Opticaller data callthru was added, but did not work<br/><!--<br/>pbx_admin.cpp<br/>--><!---->
      
      
=== PBX: Forking a call to a Trunk with "Outgoing call restricted", causes the original call to be restricted as well ===
=== PBX: Forking a call to a Trunk with "Outgoing call restricted", causes the original call to be restricted as well ===
Line 580: Line 580:
|[http://mantis.innovaphone.com/view.php?id=90487 90487]
|[http://mantis.innovaphone.com/view.php?id=90487 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.<br/><!--<br/>pbx_trunk.cpp<br/>-->
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.<br/><!--<br/>pbx_trunk.cpp<br/>--><!---->
      
      
=== SIP: Locally configured DNS entries were not used if no DNS server configured ===
=== SIP: Locally configured DNS entries were not used if no DNS server configured ===
Line 591: Line 591:
|[http://mantis.innovaphone.com/view.php?id=90508 90508]
|[http://mantis.innovaphone.com/view.php?id=90508 90508]
|}
|}
If no DNS server was configured, but DNS names are to be resolved,<br/>local DNS entries can be added (Services/DNS/Hosts).<br/>SIP stack fails with SRV query and does not try A query which would deliver IP address.<br/><br/><!--<br/>sip.cpp<br/>-->
If no DNS server was configured, but DNS names are to be resolved,<br/>local DNS entries can be added (Services/DNS/Hosts).<br/>SIP stack fails with SRV query and does not try A query which would deliver IP address.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== PBX: CDR was missing for a call rejected because of Busy on ... Calls ===
=== PBX: CDR was missing for a call rejected because of Busy on ... Calls ===
Line 602: Line 602:
|[http://mantis.innovaphone.com/view.php?id=90518 90518]
|[http://mantis.innovaphone.com/view.php?id=90518 90518]
|}
|}
On the user with Busy on ... calls set no CDR was generate for a call which was rejected because of this. The user would like to see this as a missed call in this case.<br/><!--<br/>pbx.cpp<br/>-->
On the user with Busy on ... calls set no CDR was generate for a call which was rejected because of this. The user would like to see this as a missed call in this case.<br/><!--<br/>pbx.cpp<br/>--><!---->
      
      
=== PBX: Registration with name was possible even without matching device ===
=== PBX: Registration with name was possible even without matching device ===
Line 613: Line 613:
|[http://mantis.innovaphone.com/view.php?id=90531 90531]
|[http://mantis.innovaphone.com/view.php?id=90531 90531]
|}
|}
This is a security issue, because of this it was not possible to enforce a police which allows registration by hardware id only. No fix in version 9, because of compatibility reasons.<br/><!--<br/>pbx.cpp<br/>-->
This is a security issue, because of this it was not possible to enforce a police which allows registration by hardware id only. No fix in version 9, because of compatibility reasons.<br/><!--<br/>pbx.cpp<br/>--><!---->
      
      
=== IP-DECT: RTP stream ===
=== IP-DECT: RTP stream ===
Line 624: Line 624:
|[http://mantis.innovaphone.com/view.php?id=90539 90539]
|[http://mantis.innovaphone.com/view.php?id=90539 90539]
|}
|}
If a remote hold event is received, no RTP data should be sent by the IP-DECT device.<br/>A CTI initiated call is established with a call transfer and a "No Media data received" error event can occur.<br/>This is fixed now.<br/><br/><!--<br/>Changed files:<br/>h323ch.cpp<br/>dectradio_call.cpp<br/>dectradio_mastercall.h<br/>dectradio_mastercall.cpp<br/>-->
If a remote hold event is received, no RTP data should be sent by the IP-DECT device.<br/>A CTI initiated call is established with a call transfer and a "No Media data received" error event can occur.<br/>This is fixed now.<br/><br/><!--<br/>Changed files:<br/>h323ch.cpp<br/>dectradio_call.cpp<br/>dectradio_mastercall.h<br/>dectradio_mastercall.cpp<br/>--><!---->
      
      
=== PBX: Twin-Phones: On connect from twin-phone endpoint disconnect additional ringing calls ===
=== PBX: Twin-Phones: On connect from twin-phone endpoint disconnect additional ringing calls ===
Line 635: Line 635:
|[http://mantis.innovaphone.com/view.php?id=90567 90567]
|[http://mantis.innovaphone.com/view.php?id=90567 90567]
|}
|}
If two calls are ringing at a twin phone user with multiple endpoints, and no call is conneceted, these calls are ringing at all endpoints. When the first call is connected, the remaining call legs ringing at other endpoints should be disconnected.<br/><!--<br/>pbx.cpp<br/>-->
If two calls are ringing at a twin phone user with multiple endpoints, and no call is conneceted, these calls are ringing at all endpoints. When the first call is connected, the remaining call legs ringing at other endpoints should be disconnected.<br/><!--<br/>pbx.cpp<br/>--><!---->
      
      
=== SIP: Trap on IP-DECT ===
=== SIP: Trap on IP-DECT ===
Line 646: Line 646:
|[http://mantis.innovaphone.com/view.php?id=90569 90569]
|[http://mantis.innovaphone.com/view.php?id=90569 90569]
|}
|}
Trap in GK-CHANNEL when Dectmaster application sends DTMF before call if created.<br/><br/><!--<br/>sip.cpp<br/>-->
Trap in GK-CHANNEL when Dectmaster application sends DTMF before call if created.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
= V10 Beta 3 =
= V10 Beta 3 =
Line 665: Line 665:
|[http://mantis.innovaphone.com/view.php?id=85560 85560]
|[http://mantis.innovaphone.com/view.php?id=85560 85560]
|}
|}
Change the own user password from myPBX. The dialog is opened by using the settings button on the top right.<br/><!--<br/>mypbx10.htm<br/>mypbx10.js<br/>mypbx10_dialog_cancel.png<br/>pbx.mak<br/>-->
Change the own user password from myPBX. The dialog is opened by using the settings button on the top right.<br/><!--<br/>mypbx10.htm<br/>mypbx10.js<br/>mypbx10_dialog_cancel.png<br/>pbx.mak<br/>--><!---->
      
      
=== myPBX: DTMF ===
=== myPBX: DTMF ===
Line 676: Line 676:
|[http://mantis.innovaphone.com/view.php?id=85562 85562]
|[http://mantis.innovaphone.com/view.php?id=85562 85562]
|}
|}
DTMF keypad for myPBX version 10.<br/><!--<br/>mypbx10.htm<br/>mypbx10.css<br/>mypbx10.js<br/>--><br/>
DTMF keypad for myPBX version 10.<br/><!--<br/>mypbx10.htm<br/>mypbx10.css<br/>mypbx10.js<br/>--><br/><!---->
      
      
=== myPBX: Presence depending on user activity ===
=== myPBX: Presence depending on user activity ===
Line 687: Line 687:
|[http://mantis.innovaphone.com/view.php?id=86941 86941]
|[http://mantis.innovaphone.com/view.php?id=86941 86941]
|}
|}
The launcher can now detect user activity and set the IM status depending on the current state. If the user is inactive the IM status is set to closed (Appear Offline).<br/><br/>The feature can be turned on and off and an idle timeout can be configured using the option "Auto Appear Offline" in the configuration dialog. During installation the number of minutes can be configured using the MSI parameter AUTOAPPEAROFFLINE=[0|1|5|10|15]. 0 turns the feature off.<br/><!--<br/>Firmware:<br/>pbx_api.h<br/>pbx.h<br/>pbx.cpp<br/>pbx_client.h<br/>pbx_client.cpp<br/>mypbx10.js<br/><br/>Launcher:<br/>UserActivityMonitor.cs<br/>Native.cs<br/>Config.cs<br/>Config.Designer.cs<br/>Configuration.cs<br/>ctiwin.cs<br/>Installer.cs<br/>setup.vdproj<br/><br/>Test:<br/>unit-tests/client/iteration09/400-auto-status<br/>--><br/>
The launcher can now detect user activity and set the IM status depending on the current state. If the user is inactive the IM status is set to closed (Appear Offline).<br/><br/>The feature can be turned on and off and an idle timeout can be configured using the option "Auto Appear Offline" in the configuration dialog. During installation the number of minutes can be configured using the MSI parameter AUTOAPPEAROFFLINE=[0|1|5|10|15]. 0 turns the feature off.<br/><!--<br/>Firmware:<br/>pbx_api.h<br/>pbx.h<br/>pbx.cpp<br/>pbx_client.h<br/>pbx_client.cpp<br/>mypbx10.js<br/><br/>Launcher:<br/>UserActivityMonitor.cs<br/>Native.cs<br/>Config.cs<br/>Config.Designer.cs<br/>Configuration.cs<br/>ctiwin.cs<br/>Installer.cs<br/>setup.vdproj<br/><br/>Test:<br/>unit-tests/client/iteration09/400-auto-status<br/>--><br/><!---->
      
      
=== Kerberos: Use default realm if no realm is given ===
=== Kerberos: Use default realm if no realm is given ===
Line 698: Line 698:
|[http://mantis.innovaphone.com/view.php?id=90108 90108]
|[http://mantis.innovaphone.com/view.php?id=90108 90108]
|}
|}
If the user logs-in using Kerberos without specifying a realm the default realm is used.<br/><br/>\\user -> example.com\\user<br/>user@ -> user@example.com<br/><br/>The default realm can be configured on page General/Admin. If no default realm is configured, the Kerberos realm of the box is used.<br/><!--<br/>Files:<br/>command.h<br/>command.cpp<br/>command.xsl<br/><br/>Documentation:<br/>http://wiki.innovaphone.com/index.php?title=Reference10:Delegated_Authentication<br/>http://wiki.innovaphone.com/index.php?title=Reference10:General/Admin<br/>--><br/>
If the user logs-in using Kerberos without specifying a realm the default realm is used.<br/><br/>\\user -> example.com\\user<br/>user@ -> user@example.com<br/><br/>The default realm can be configured on page General/Admin. If no default realm is configured, the Kerberos realm of the box is used.<br/><!--<br/>Files:<br/>command.h<br/>command.cpp<br/>command.xsl<br/><br/>Documentation:<br/>http://wiki.innovaphone.com/index.php?title=Reference10:Delegated_Authentication<br/>http://wiki.innovaphone.com/index.php?title=Reference10:General/Admin<br/>--><br/><!---->
      
      
=== myPBX launcher: Choose webcam ===
=== myPBX launcher: Choose webcam ===
Line 709: Line 709:
|[http://mantis.innovaphone.com/view.php?id=90457 90457]
|[http://mantis.innovaphone.com/view.php?id=90457 90457]
|}
|}
Let the user choose the webcam to be used for video calls.<br/><!--<br/>myPBXwin\\RemoteVideo\\IRemoteVideoDisplay.cs<br/>myPBXwin\\RemoteVideo\\RemoteVideoConnection.cs<br/>myPBXwin\\RemoteVideo\\VideoDll.cs<br/>myPBXwin\\RemoteVideo\\Webcam.cs<br/>myPBXwin\\WebcamForm.cs<br/>myPBXwin\\WebcamForm.Designer.cs<br/>myPBXwin\\WebcamForm.resx<br/>myPBXwin\\Configuration.cs<br/>myPBXwin\\myPBXwin.csproj<br/>Video\\dll_interface.cpp<br/>Video\\dll_interface.h<br/>Video\\video.cpp<br/>Video\\video.h<br/>-->
Let the user choose the webcam to be used for video calls.<br/><!--<br/>myPBXwin\\RemoteVideo\\IRemoteVideoDisplay.cs<br/>myPBXwin\\RemoteVideo\\RemoteVideoConnection.cs<br/>myPBXwin\\RemoteVideo\\VideoDll.cs<br/>myPBXwin\\RemoteVideo\\Webcam.cs<br/>myPBXwin\\WebcamForm.cs<br/>myPBXwin\\WebcamForm.Designer.cs<br/>myPBXwin\\WebcamForm.resx<br/>myPBXwin\\Configuration.cs<br/>myPBXwin\\myPBXwin.csproj<br/>Video\\dll_interface.cpp<br/>Video\\dll_interface.h<br/>Video\\video.cpp<br/>Video\\video.h<br/>--><!---->
      
      
=== Display of Gateway Temperature, available Power Sources, Power Off Loop setting ===
=== Display of Gateway Temperature, available Power Sources, Power Off Loop setting ===
Line 720: Line 720:
|[http://mantis.innovaphone.com/view.php?id=90674 90674]
|[http://mantis.innovaphone.com/view.php?id=90674 90674]
|}
|}
additional information in general->info screen
additional information in general->info screen<!---->
      
      
=== PBX: New configuration option 'Hide connected Number' at object ===
=== PBX: New configuration option 'Hide connected Number' at object ===
Line 731: Line 731:
|[http://mantis.innovaphone.com/view.php?id=90693 90693]
|[http://mantis.innovaphone.com/view.php?id=90693 90693]
|}
|}
In some cases it is desireable not to reveal the final destination of a call to a caller. For example a call center agent should not be called directly by the customer.<br/><!--<br/>pbx.cpp<br/>pbx_api.h<br/>pbx_admin.cpp<br/>pbx_edit_object.xsl<br/>pbx_wait.cpp<br/>-->
In some cases it is desireable not to reveal the final destination of a call to a caller. For example a call center agent should not be called directly by the customer.<br/><!--<br/>pbx.cpp<br/>pbx_api.h<br/>pbx_admin.cpp<br/>pbx_edit_object.xsl<br/>pbx_wait.cpp<br/>--><!---->
      
      
=== myPBX launcher: Show webcam configuration at the same location as the video call window ===
=== myPBX launcher: Show webcam configuration at the same location as the video call window ===
Line 742: Line 742:
|[http://mantis.innovaphone.com/view.php?id=90779 90779]
|[http://mantis.innovaphone.com/view.php?id=90779 90779]
|}
|}
So that the user can configure the location and size of the video window without having a video call.<br/><!--<br/>ctiwin.cs<br/>VideoForm.cs<br/>WebcamForm.cs<br/>WebcamForm.Designer.cs<br/>WebcamForm.resx<br/>-->
So that the user can configure the location and size of the video window without having a video call.<br/><!--<br/>ctiwin.cs<br/>VideoForm.cs<br/>WebcamForm.cs<br/>WebcamForm.Designer.cs<br/>WebcamForm.resx<br/>--><!---->
      
      
=== New counter for device temperature ===
=== New counter for device temperature ===
Line 753: Line 753:
|[http://mantis.innovaphone.com/view.php?id=90831 90831]
|[http://mantis.innovaphone.com/view.php?id=90831 90831]
|}
|}
New counter for device temperature<br/><br/><!--<br/>ip24.cpp/h<br/>ip800.cpp/h<br/>ip6000.cpp/h<br/>ip6010.cpp/h<br/>log_count.xsl<br/>-->
New counter for device temperature<br/><br/><!--<br/>ip24.cpp/h<br/>ip800.cpp/h<br/>ip6000.cpp/h<br/>ip6010.cpp/h<br/>log_count.xsl<br/>--><!---->
      
      
=== PBX: Forward Messages in ringback to all ringing endpoints ===
=== PBX: Forward Messages in ringback to all ringing endpoints ===
Line 764: Line 764:
|[http://mantis.innovaphone.com/view.php?id=90976 90976]
|[http://mantis.innovaphone.com/view.php?id=90976 90976]
|}
|}
A message sent on a call which was not yet connected, was discarded. Now this message is forwarded to all endpoints which have received the call<br/><!--<br/>pbx.cpp<br/>-->
A message sent on a call which was not yet connected, was discarded. Now this message is forwarded to all endpoints which have received the call<br/><!--<br/>pbx.cpp<br/>--><!---->
      
      
=== Webmedia: Support for different tone patterns (countries) ===
=== Webmedia: Support for different tone patterns (countries) ===
Line 775: Line 775:
|[http://mantis.innovaphone.com/view.php?id=91134 91134]
|[http://mantis.innovaphone.com/view.php?id=91134 91134]
|}
|}
New URL param &amp;tones=num to select country-specific tone patterns.<br/><br/><!--<br/>webmedia.cpp/h<br/>-->
New URL param &amp;tones=num to select country-specific tone patterns.<br/><br/><!--<br/>webmedia.cpp/h<br/>--><!---->
      
      
=== myPBX launcher: Localisation for texts ===
=== myPBX launcher: Localisation for texts ===
Line 786: Line 786:
|[http://mantis.innovaphone.com/view.php?id=91151 91151]
|[http://mantis.innovaphone.com/view.php?id=91151 91151]
|}
|}
Support for localisation.<br/>Current languages: English and German<br/><br/><!--<br/>Config.cs<br/>WebcamForm.cs<br/>VideoForm.cs<br/>Configuration.cs<br/>myPBXwin.csproj<br/>lang/*<br/>ctiwin.cs<br/>IRemoteVideo.cs<br/>Resources.resx -> ResourcesIcons.resx<br/>-->
Support for localisation.<br/>Current languages: English and German<br/><br/><!--<br/>Config.cs<br/>WebcamForm.cs<br/>VideoForm.cs<br/>Configuration.cs<br/>myPBXwin.csproj<br/>lang/*<br/>ctiwin.cs<br/>IRemoteVideo.cs<br/>Resources.resx -> ResourcesIcons.resx<br/>--><!---->
      
      
=== PBX: Make PBX generated tones configurable ===
=== PBX: Make PBX generated tones configurable ===
Line 797: Line 797:
|[http://mantis.innovaphone.com/view.php?id=91175 91175]
|[http://mantis.innovaphone.com/view.php?id=91175 91175]
|}
|}
The same country specific tone schemes as in the gateway can be configured<br/><!--<br/>pbx.cpp<br/>pbx.h<br/>pbx_general.xsl<br/>pbx_api.h<br/>pbx_mobility.cpp<br/>pbx_icp.cpp<br/>pbx_icp.h<br/>pbx_dtmf.cpp<br/>pbx_dtmf.h<br/>pbx_dirsearch.cpp<br/>pbx_dirsearch.h<br/>-->
The same country specific tone schemes as in the gateway can be configured<br/><!--<br/>pbx.cpp<br/>pbx.h<br/>pbx_general.xsl<br/>pbx_api.h<br/>pbx_mobility.cpp<br/>pbx_icp.cpp<br/>pbx_icp.h<br/>pbx_dtmf.cpp<br/>pbx_dtmf.h<br/>pbx_dirsearch.cpp<br/>pbx_dirsearch.h<br/>--><!---->
      
      
=== Indicate Video on calls page ===
=== Indicate Video on calls page ===
Line 808: Line 808:
|[http://mantis.innovaphone.com/view.php?id=91213 91213]
|[http://mantis.innovaphone.com/view.php?id=91213 91213]
|}
|}
The video coder is displayed on the calls page<br/><!--<br/>pbx.cpp<br/>pbx.h<br/>pbx_calls.xsl<br/>h450.cpp<br/>h450asn1.h<br/>sip.cpp<br/>phonesig.cpp<br/>phone_lib.h<br/>phone_calls.xsl<br/>-->
The video coder is displayed on the calls page<br/><!--<br/>pbx.cpp<br/>pbx.h<br/>pbx_calls.xsl<br/>h450.cpp<br/>h450asn1.h<br/>sip.cpp<br/>phonesig.cpp<br/>phone_lib.h<br/>phone_calls.xsl<br/>--><!---->
      
      
=== PBX-SOAP: Handle '+' in destination number supplied with UserCall ===
=== PBX-SOAP: Handle '+' in destination number supplied with UserCall ===
Line 819: Line 819:
|[http://mantis.innovaphone.com/view.php?id=91280 91280]
|[http://mantis.innovaphone.com/view.php?id=91280 91280]
|}
|}
Treat a destination number starting with '+' as internation number and map it according PBX settings<br/><!--<br/>pbx_xml.cpp<br/>ep_lib.cpp<br/>-->
Treat a destination number starting with '+' as internation number and map it according PBX settings<br/><!--<br/>pbx_xml.cpp<br/>ep_lib.cpp<br/>--><!---->
      
      
=== PBX: Indicate video capability on registration page ===
=== PBX: Indicate video capability on registration page ===
Line 830: Line 830:
|[http://mantis.innovaphone.com/view.php?id=91312 91312]
|[http://mantis.innovaphone.com/view.php?id=91312 91312]
|}
|}
The state of the remote video service is shown on page PBX/Registrations:<br/>- available: the phone supports remote video<br/>- connected: a remote video client is connected to the phone<br/><!--<br/>pbx.cpp<br/>pbx_regs.xsl<br/>-->
The state of the remote video service is shown on page PBX/Registrations:<br/>- available: the phone supports remote video<br/>- connected: a remote video client is connected to the phone<br/><!--<br/>pbx.cpp<br/>pbx_regs.xsl<br/>--><!---->
      
      
=== IP-DECT: Login/logout changed for OEM PBX ===
=== IP-DECT: Login/logout changed for OEM PBX ===
Line 841: Line 841:
|[http://mantis.innovaphone.com/view.php?id=91417 91417]
|[http://mantis.innovaphone.com/view.php?id=91417 91417]
|}
|}
Login/logout feature is changed for OEM PBX.<br/><br/><!--<br/>Changed files:<br/>dtmffty.h<br/>dtmffty.cpp<br/>dectfty.h<br/>dectfty.cpp<br/>dectusers.cpp<br/>-->
Login/logout feature is changed for OEM PBX.<br/><br/><!--<br/>Changed files:<br/>dtmffty.h<br/>dtmffty.cpp<br/>dectfty.h<br/>dectfty.cpp<br/>dectusers.cpp<br/>--><!---->
      
      
=== IP-DECT: Configuration option 'Registration with system password' ===
=== IP-DECT: Configuration option 'Registration with system password' ===
Line 852: Line 852:
|[http://mantis.innovaphone.com/view.php?id=91460 91460]
|[http://mantis.innovaphone.com/view.php?id=91460 91460]
|}
|}
The configuration option 'Registration with system password' is added. If ticked, all users are registered with the system password. This is useful, if the PBX users are only allowed to register with the PBX password.<br/><br/><!--<br/>Changed files:<br/>dectmaster.h<br/>dectmaster.cpp<br/>dectmaster.xsl<br/>_inn_asc_dectmaster.xsl<br/>-->
The configuration option 'Registration with system password' is added. If ticked, all users are registered with the system password. This is useful, if the PBX users are only allowed to register with the PBX password.<br/><br/><!--<br/>Changed files:<br/>dectmaster.h<br/>dectmaster.cpp<br/>dectmaster.xsl<br/>_inn_asc_dectmaster.xsl<br/>--><!---->
      
      
=== myPBX launcher: Handle power state changes of the computer ===
=== myPBX launcher: Handle power state changes of the computer ===
Line 863: Line 863:
|[http://mantis.innovaphone.com/view.php?id=91566 91566]
|[http://mantis.innovaphone.com/view.php?id=91566 91566]
|}
|}
Suspend:<br/>- Disconnect web application<br/>- Disconnect remote video<br/>Wake-up:<br/>- Reconnect web application<br/>- Reconnect remote video<br/><!--<br/>ctiwin.cs<br/>-->
Suspend:<br/>- Disconnect web application<br/>- Disconnect remote video<br/>Wake-up:<br/>- Reconnect web application<br/>- Reconnect remote video<br/><!--<br/>ctiwin.cs<br/>--><!---->
      
      
=== myPBX: Show reason for failed login ===
=== myPBX: Show reason for failed login ===
Line 874: Line 874:
|[http://mantis.innovaphone.com/view.php?id=91592 91592]
|[http://mantis.innovaphone.com/view.php?id=91592 91592]
|}
|}
Show why a login failed. Currently there are two reasons:<br/>- Wrong username or password<br/>- No license<br/><!--<br/>Files:<br/>pbx_client.cpp<br/>pbx_client.h<br/>pbx_client_localisation.h<br/>mypbx10.css<br/>mypbx10.htm<br/>mypbx10.js<br/>Tests:<br/>test\\10.00\\unit-tests\\client\\iteration01\\030-client-login-wrong-pwd<br/>test\\10.00\\unit-tests\\client\\iteration01\\032-client-login-no-pwd<br/>test\\10.00\\unit-tests\\client\\iteration01\\033-client-unknown-user<br/>test\\10.00\\unit-tests\\client\\license\\login-version10-nok.xml<br/>-->
Show why a login failed. Currently there are two reasons:<br/>- Wrong username or password<br/>- No license<br/><!--<br/>Files:<br/>pbx_client.cpp<br/>pbx_client.h<br/>pbx_client_localisation.h<br/>mypbx10.css<br/>mypbx10.htm<br/>mypbx10.js<br/>Tests:<br/>test\\10.00\\unit-tests\\client\\iteration01\\030-client-login-wrong-pwd<br/>test\\10.00\\unit-tests\\client\\iteration01\\032-client-login-no-pwd<br/>test\\10.00\\unit-tests\\client\\iteration01\\033-client-unknown-user<br/>test\\10.00\\unit-tests\\client\\license\\login-version10-nok.xml<br/>--><!---->
      
      
=== myPBX launcher: Office Presence Logging can be switched on/off by myPBX ===
=== myPBX launcher: Office Presence Logging can be switched on/off by myPBX ===
Line 885: Line 885:
|[http://mantis.innovaphone.com/view.php?id=91642 91642]
|[http://mantis.innovaphone.com/view.php?id=91642 91642]
|}
|}
The office presence logging setting by Microsoft can be now enabled/disabled by myPBX.<br/><br/><!--<br/>Configuration.cs<br/>Program.cs<br/>Config.cs<br/>Resources*.resx<br/>setup.vdproj<br/>Installer.cs<br/>-->
The office presence logging setting by Microsoft can be now enabled/disabled by myPBX.<br/><br/><!--<br/>Configuration.cs<br/>Program.cs<br/>Config.cs<br/>Resources*.resx<br/>setup.vdproj<br/>Installer.cs<br/>--><!---->
      
      
=== PBX: Allow Name (instead of Long Name) to identify user for mobility data call thru ===
=== PBX: Allow Name (instead of Long Name) to identify user for mobility data call thru ===
Line 896: Line 896:
|[http://mantis.innovaphone.com/view.php?id=91660 91660]
|[http://mantis.innovaphone.com/view.php?id=91660 91660]
|}
|}
This should simplify Opticaller configuration<br/><!--<br/>pbx_admin.cpp<br/>-->
This should simplify Opticaller configuration<br/><!--<br/>pbx_admin.cpp<br/>--><!---->
      
      
=== IP-DECT: Static ports between Master and Radio ===
=== IP-DECT: Static ports between Master and Radio ===
Line 907: Line 907:
|[http://mantis.innovaphone.com/view.php?id=91815 91815]
|[http://mantis.innovaphone.com/view.php?id=91815 91815]
|}
|}
Now the VOIP connections between the Master and the Radio use static ports instead of dynamic ones. This is useful if only a few ports should be opened through a firewall. For calls from the Radio to the Master the ports 1716 and 1717 (TLS) are used. For the default Master connection for calls from the Master to the Radio the ports 1718 and 1719 (TLS) are used. For dynamic Radio-Master connections the ports from 1722 are used. Every connection needs two ports.<br/><br/><!--<br/>Changed files:<br/>dectmaster.cpp<br/>dectradio.h<br/>dectradio.cpp<br/>dectradio_reg.h<br/>dectradio_reg.cpp<br/>h323sig.cpp<br/>--><br/>
Now the VOIP connections between the Master and the Radio use static ports instead of dynamic ones. This is useful if only a few ports should be opened through a firewall. For calls from the Radio to the Master the ports 1716 and 1717 (TLS) are used. For the default Master connection for calls from the Master to the Radio the ports 1718 and 1719 (TLS) are used. For dynamic Radio-Master connections the ports from 1722 are used. Every connection needs two ports.<br/><br/><!--<br/>Changed files:<br/>dectmaster.cpp<br/>dectradio.h<br/>dectradio.cpp<br/>dectradio_reg.h<br/>dectradio_reg.cpp<br/>h323sig.cpp<br/>--><br/><!---->
      
      
== Bug Fixes ==
== Bug Fixes ==
Line 922: Line 922:
|[http://mantis.innovaphone.com/view.php?id=90597 90597]
|[http://mantis.innovaphone.com/view.php?id=90597 90597]
|}
|}
Disabled IP-DECT interface tries to register.<br/><br/><!--<br/>sip.cpp<br/>-->
Disabled IP-DECT interface tries to register.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== H.323: Timer to monitor response to setup too short for some traffic cases ===
=== H.323: Timer to monitor response to setup too short for some traffic cases ===
Line 933: Line 933:
|[http://mantis.innovaphone.com/view.php?id=90696 90696]
|[http://mantis.innovaphone.com/view.php?id=90696 90696]
|}
|}
This created unnecessary event in IP-DECT systems when calling powered off or out of range handsets<br/><!--<br/>h323sig.cpp<br/>-->
This created unnecessary event in IP-DECT systems when calling powered off or out of range handsets<br/><!--<br/>h323sig.cpp<br/>--><!---->
      
      
=== PBX-CDRs: On call to user without registration, the name/number info was missing in rel-from event ===
=== PBX-CDRs: On call to user without registration, the name/number info was missing in rel-from event ===
Line 944: Line 944:
|[http://mantis.innovaphone.com/view.php?id=90720 90720]
|[http://mantis.innovaphone.com/view.php?id=90720 90720]
|}
|}
For consistency reasons the name/number info should be present.<br/><!--<br/>pbx.cpp<br/>-->
For consistency reasons the name/number info should be present.<br/><!--<br/>pbx.cpp<br/>--><!---->
      
      
=== PBX Mobility: Connected number from mobile phone was forwarded to caller ===
=== PBX Mobility: Connected number from mobile phone was forwarded to caller ===
Line 955: Line 955:
|[http://mantis.innovaphone.com/view.php?id=90722 90722]
|[http://mantis.innovaphone.com/view.php?id=90722 90722]
|}
|}
If a call is answered on the mobile phone, it should look idebtical to the caller to the case that the call was answered locally. This means a connected number from the mobile phone must not be forwarded.<br/><!--<br/>pbx_mobility.cpp<br/>-->
If a call is answered on the mobile phone, it should look idebtical to the caller to the case that the call was answered locally. This means a connected number from the mobile phone must not be forwarded.<br/><!--<br/>pbx_mobility.cpp<br/>--><!---->
      
      
=== PBX Waiting: Potential Trap if editing while a call is initiated with SOAP ===
=== PBX Waiting: Potential Trap if editing while a call is initiated with SOAP ===
Line 966: Line 966:
|[http://mantis.innovaphone.com/view.php?id=90766 90766]
|[http://mantis.innovaphone.com/view.php?id=90766 90766]
|}
|}
The Waiting object can be used as outgoing dialing object with SOAP. If this is done and the configuration is changed while an outgoing call was pending, a trap could happen<br/><!--<br/>pbx_wait.cpp<br/>-->
The Waiting object can be used as outgoing dialing object with SOAP. If this is done and the configuration is changed while an outgoing call was pending, a trap could happen<br/><!--<br/>pbx_wait.cpp<br/>--><!---->
      
      
=== H.323: Potential Trap in special case which could only happen in version 10 ===
=== H.323: Potential Trap in special case which could only happen in version 10 ===
Line 977: Line 977:
|[http://mantis.innovaphone.com/view.php?id=90768 90768]
|[http://mantis.innovaphone.com/view.php?id=90768 90768]
|}
|}
This fixed is merged to version 9 only of consistency reasons<br/><!--<br/>h323_ras.cpp<br/>-->
This fixed is merged to version 9 only of consistency reasons<br/><!--<br/>h323_ras.cpp<br/>--><!---->
      
      
=== myPBX launcher: Multi-screen support for webcam window ===
=== myPBX launcher: Multi-screen support for webcam window ===
Line 988: Line 988:
|[http://mantis.innovaphone.com/view.php?id=90773 90773]
|[http://mantis.innovaphone.com/view.php?id=90773 90773]
|}
|}
Detect if the window has been moved to a different screen.<br/><!--<br/>IRemoteVideo.cs<br/>RemoteVideoConnection.cs<br/>VideoDll.cs<br/>VideoForm.cs<br/>VideoForm.Designer.cs<br/>VideoForm.resx<br/>WebcamForm.cs<br/>WebcamForm.Designer.cs<br/>WebcamForm.resx<br/>Video\\dll_interface.cpp<br/>Video\\dll_interface.h<br/>-->
Detect if the window has been moved to a different screen.<br/><!--<br/>IRemoteVideo.cs<br/>RemoteVideoConnection.cs<br/>VideoDll.cs<br/>VideoForm.cs<br/>VideoForm.Designer.cs<br/>VideoForm.resx<br/>WebcamForm.cs<br/>WebcamForm.Designer.cs<br/>WebcamForm.resx<br/>Video\\dll_interface.cpp<br/>Video\\dll_interface.h<br/>--><!---->
      
      
=== SIP: Respect changes in PAI/PPI header when receiving UPDATE with SDP offer ===
=== SIP: Respect changes in PAI/PPI header when receiving UPDATE with SDP offer ===
Line 999: Line 999:
|[http://mantis.innovaphone.com/view.php?id=90778 90778]
|[http://mantis.innovaphone.com/view.php?id=90778 90778]
|}
|}
PAI/PPI was processed when receiving UPDATE without SDP offer.<br/>PAI/PPI was ignored when receiving UPDATE with SDP offer.<br/>Now PAI/PPI is processed when receiving UPDATE with SDP offer.<br/><br/><!--<br/>sip.cpp<br/>--><br/>
PAI/PPI was processed when receiving UPDATE without SDP offer.<br/>PAI/PPI was ignored when receiving UPDATE with SDP offer.<br/>Now PAI/PPI is processed when receiving UPDATE with SDP offer.<br/><br/><!--<br/>sip.cpp<br/>--><br/><!---->
      
      
=== SIP: Possible buffer overrun ===
=== SIP: Possible buffer overrun ===
Line 1,010: Line 1,010:
|[http://mantis.innovaphone.com/view.php?id=90780 90780]
|[http://mantis.innovaphone.com/view.php?id=90780 90780]
|}
|}
Fix for possible buffer overrun.<br/><br/><!--<br/>siputil.cpp/h<br/>-->
Fix for possible buffer overrun.<br/><br/><!--<br/>siputil.cpp/h<br/>--><!---->
      
      
=== SIP: Wrong error log "Timeout during media negotiation for call" ===
=== SIP: Wrong error log "Timeout during media negotiation for call" ===
Line 1,021: Line 1,021:
|[http://mantis.innovaphone.com/view.php?id=90821 90821]
|[http://mantis.innovaphone.com/view.php?id=90821 90821]
|}
|}
Error log "Timeout during media negotiation for call" may occur after re-negotioation.<br/>Re-negotioation occurs during hold/retrieve/transfer.<br/><br/><!--<br/>sip.cpp<br/>-->
Error log "Timeout during media negotiation for call" may occur after re-negotioation.<br/>Re-negotioation occurs during hold/retrieve/transfer.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== Video: Webcam settings blocks Video Library ===
=== Video: Webcam settings blocks Video Library ===
Line 1,032: Line 1,032:
|[http://mantis.innovaphone.com/view.php?id=90834 90834]
|[http://mantis.innovaphone.com/view.php?id=90834 90834]
|}
|}
the video library blocks until the webcam settings window is closed avoiding processing an incoming connect. Start webcam settings in a new thread.<br/><br/><!--<br/>captureDevices.cpp<br/>captureDevices.h<br/>RemoteVideoConnection.cs (just traces)<br/>-->
the video library blocks until the webcam settings window is closed avoiding processing an incoming connect. Start webcam settings in a new thread.<br/><br/><!--<br/>captureDevices.cpp<br/>captureDevices.h<br/>RemoteVideoConnection.cs (just traces)<br/>--><!---->
      
      
=== PBX Trunk: Name to Number Feature did not work with calls to extern ===
=== PBX Trunk: Name to Number Feature did not work with calls to extern ===
Line 1,043: Line 1,043:
|[http://mantis.innovaphone.com/view.php?id=90858 90858]
|[http://mantis.innovaphone.com/view.php?id=90858 90858]
|}
|}
If an endpoint cannot be found by name, the call should be forwarded to extern<br/><!--<br/>pbx.cpp<br/>pbx.h<br/>pbx_api.h<br/>pbx_trunk.cpp<br/>pbx_trunk.h<br/>-->
If an endpoint cannot be found by name, the call should be forwarded to extern<br/><!--<br/>pbx.cpp<br/>pbx.h<br/>pbx_api.h<br/>pbx_trunk.cpp<br/>pbx_trunk.h<br/>--><!---->
      
      
=== Potential Trap when rapidly switching local Media connections (Conferencing) ===
=== Potential Trap when rapidly switching local Media connections (Conferencing) ===
Line 1,054: Line 1,054:
|[http://mantis.innovaphone.com/view.php?id=90933 90933]
|[http://mantis.innovaphone.com/view.php?id=90933 90933]
|}
|}
There was a race condition when switching local media channels (e.g. ISDN channels to conference interfaces), which could cause media not functioning or even a trap<br/><!--<br/>media.cpp<br/>medialib.h<br/>-->
There was a race condition when switching local media channels (e.g. ISDN channels to conference interfaces), which could cause media not functioning or even a trap<br/><!--<br/>media.cpp<br/>medialib.h<br/>--><!---->
      
      
=== PBX CSV Import: Corrupted objects at buffer boundaries ===
=== PBX CSV Import: Corrupted objects at buffer boundaries ===
Line 1,065: Line 1,065:
|[http://mantis.innovaphone.com/view.php?id=90942 90942]
|[http://mantis.innovaphone.com/view.php?id=90942 90942]
|}
|}
The upload is processed in chunks of 2K. At boundaries of these chunks data could be corrupted. This was fixed and the chunk size increased to 10K<br/><!--<br/>pbx_admin.cpp<br/>pbx_admin.h<br/>-->
The upload is processed in chunks of 2K. At boundaries of these chunks data could be corrupted. This was fixed and the chunk size increased to 10K<br/><!--<br/>pbx_admin.cpp<br/>pbx_admin.h<br/>--><!---->
      
      
=== Gateway Config: The wizard did not configure the default IP address on ETH1 ===
=== Gateway Config: The wizard did not configure the default IP address on ETH1 ===
Line 1,076: Line 1,076:
|[http://mantis.innovaphone.com/view.php?id=90995 90995]
|[http://mantis.innovaphone.com/view.php?id=90995 90995]
|}
|}
When doing a reset to manufacturing defaults (long reset) an address of 192.168.1.1 is configured for ETH1. This address was removed when the gateway was configured with the wizard.<br/><!--<br/>config_wizard.txt in various products<br/>-->
When doing a reset to manufacturing defaults (long reset) an address of 192.168.1.1 is configured for ETH1. This address was removed when the gateway was configured with the wizard.<br/><!--<br/>config_wizard.txt in various products<br/>--><!---->
      
      
=== Phone: Trap when selecting registration for a directory entry ===
=== Phone: Trap when selecting registration for a directory entry ===
Line 1,087: Line 1,087:
|[http://mantis.innovaphone.com/view.php?id=90999 90999]
|[http://mantis.innovaphone.com/view.php?id=90999 90999]
|}
|}
Trap when selecting registration for a directory entry,<br/>but only if the registration has either no name or no number.<br/><br/><!--<br/>phone_dir_ui.cpp<br/>-->
Trap when selecting registration for a directory entry,<br/>but only if the registration has either no name or no number.<br/><br/><!--<br/>phone_dir_ui.cpp<br/>--><!---->
      
      
=== H.323: No event should be generated in State 11 and 25 ===
=== H.323: No event should be generated in State 11 and 25 ===
Line 1,098: Line 1,098:
|[http://mantis.innovaphone.com/view.php?id=91020 91020]
|[http://mantis.innovaphone.com/view.php?id=91020 91020]
|}
|}
State 25 is incoming overlap sending. This means a call was received with incomplete dialing information and the caller failed to dial more digits within the timeout of 2min. This is no indication of any malfunction but only a usage problem, so no event should be generated.<br/><br/>State 11 is disconnecting with inband announcement. A timeout happens if a user listens to the announcement for more then 30s. This could be normal.<br/><!--<br/>h323sig.cpp<br/>-->
State 25 is incoming overlap sending. This means a call was received with incomplete dialing information and the caller failed to dial more digits within the timeout of 2min. This is no indication of any malfunction but only a usage problem, so no event should be generated.<br/><br/>State 11 is disconnecting with inband announcement. A timeout happens if a user listens to the announcement for more then 30s. This could be normal.<br/><!--<br/>h323sig.cpp<br/>--><!---->
      
      
=== IP-DECT: Escape name of logged-in admin user ===
=== IP-DECT: Escape name of logged-in admin user ===
Line 1,109: Line 1,109:
|[http://mantis.innovaphone.com/view.php?id=91021 91021]
|[http://mantis.innovaphone.com/view.php?id=91021 91021]
|}
|}
The name was not displayed correctly when it contained backslashes. This happens when Kerberos is used.<br/><!--<br/>dectusers.cpp<br/>-->
The name was not displayed correctly when it contained backslashes. This happens when Kerberos is used.<br/><!--<br/>dectusers.cpp<br/>--><!---->
      
      
=== SIP: Trap when cancelling call ===
=== SIP: Trap when cancelling call ===
Line 1,120: Line 1,120:
|[http://mantis.innovaphone.com/view.php?id=91023 91023]
|[http://mantis.innovaphone.com/view.php?id=91023 91023]
|}
|}
Double delete of a call entity.<br/><br/><!--<br/>sip.cpp/h<br/>-->
Double delete of a call entity.<br/><br/><!--<br/>sip.cpp/h<br/>--><!---->
      
      
=== SIP: Heavy TLS retry load when server certificate was rejected ===
=== SIP: Heavy TLS retry load when server certificate was rejected ===
Line 1,131: Line 1,131:
|[http://mantis.innovaphone.com/view.php?id=91033 91033]
|[http://mantis.innovaphone.com/view.php?id=91033 91033]
|}
|}
Collateral damage from earlier fixed for DNS refreshing.<br/><br/><!--<br/>sip.cpp<br/>-->
Collateral damage from earlier fixed for DNS refreshing.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== myPBX: Changed heuristics for telling numbers and URIs apart ===
=== myPBX: Changed heuristics for telling numbers and URIs apart ===
Line 1,142: Line 1,142:
|[http://mantis.innovaphone.com/view.php?id=91045 91045]
|[http://mantis.innovaphone.com/view.php?id=91045 91045]
|}
|}
Strings containing an @ are now always handled as an URI.<br/><!--<br/>mypbx10.js<br/>-->
Strings containing an @ are now always handled as an URI.<br/><!--<br/>mypbx10.js<br/>--><!---->
      
      
=== myPBX launcher: Automatically refresh list of webcams in the webcam preview window ===
=== myPBX launcher: Automatically refresh list of webcams in the webcam preview window ===
Line 1,153: Line 1,153:
|[http://mantis.innovaphone.com/view.php?id=91133 91133]
|[http://mantis.innovaphone.com/view.php?id=91133 91133]
|}
|}
If new webcams are connected or existing webcams are disconnected the webcam preview window is refreshed with an updated list.<br/><!--<br/>RemoteVideoConnection.cs<br/>VideoDll.cs<br/>Video/dll_interface.cpp<br/>Video/dll_interface.h<br/>Video/video.cpp<br/>Video/video.h<br/>-->
If new webcams are connected or existing webcams are disconnected the webcam preview window is refreshed with an updated list.<br/><!--<br/>RemoteVideoConnection.cs<br/>VideoDll.cs<br/>Video/dll_interface.cpp<br/>Video/dll_interface.h<br/>Video/video.cpp<br/>Video/video.h<br/>--><!---->
      
      
=== H.323: Incoming faststart call was sometimes not accepted as faststart ===
=== H.323: Incoming faststart call was sometimes not accepted as faststart ===
Line 1,164: Line 1,164:
|[http://mantis.innovaphone.com/view.php?id=91136 91136]
|[http://mantis.innovaphone.com/view.php?id=91136 91136]
|}
|}
Only happens if non EFC is used on the incoming call, so this only happens in interop cases with other H.323 equipment<br/><!--<br/>h323ch.cpp<br/>-->
Only happens if non EFC is used on the incoming call, so this only happens in interop cases with other H.323 equipment<br/><!--<br/>h323ch.cpp<br/>--><!---->
      
      
=== SIP: Better handling of incoming calls ===
=== SIP: Better handling of incoming calls ===
Line 1,175: Line 1,175:
|[http://mantis.innovaphone.com/view.php?id=91153 91153]
|[http://mantis.innovaphone.com/view.php?id=91153 91153]
|}
|}
Msg sequence INVITE,CANCEL,INVITE may result into second call rejected.<br/><br/><!--<br/>sip.cpp/h<br/>-->
Msg sequence INVITE,CANCEL,INVITE may result into second call rejected.<br/><br/><!--<br/>sip.cpp/h<br/>--><!---->
      
      
=== myPBX launcher: Improve dialing using hotkey ===
=== myPBX launcher: Improve dialing using hotkey ===
Line 1,186: Line 1,186:
|[http://mantis.innovaphone.com/view.php?id=91163 91163]
|[http://mantis.innovaphone.com/view.php?id=91163 91163]
|}
|}
Detect clipboard content type and skip useless information. For example the time and date of an email should not be used as a phone number.<br/><br/><!--<br/>Files:<br/>TextPeeker.cs<br/><br/>Forum:<br/>http://class.innovaphone.com/moodle2/mod/forum/discuss.php?d=1928<br/>-->
Detect clipboard content type and skip useless information. For example the time and date of an email should not be used as a phone number.<br/><br/><!--<br/>Files:<br/>TextPeeker.cs<br/><br/>Forum:<br/>http://class.innovaphone.com/moodle2/mod/forum/discuss.php?d=1928<br/>--><!---->
      
      
=== myPBX: Hide pickup button for own calls ===
=== myPBX: Hide pickup button for own calls ===
Line 1,197: Line 1,197:
|[http://mantis.innovaphone.com/view.php?id=91220 91220]
|[http://mantis.innovaphone.com/view.php?id=91220 91220]
|}
|}
If the user calls one of his favourites a pickup button is shown for the alerting call at the favourite.<br/><!--<br/>mypbx10.js<br/>-->
If the user calls one of his favourites a pickup button is shown for the alerting call at the favourite.<br/><!--<br/>mypbx10.js<br/>--><!---->
      
      
=== SIP: Handling of OPTIONS from registered client did not work ===
=== SIP: Handling of OPTIONS from registered client did not work ===
Line 1,208: Line 1,208:
|[http://mantis.innovaphone.com/view.php?id=91232 91232]
|[http://mantis.innovaphone.com/view.php?id=91232 91232]
|}
|}
Handling of OPTIONS from registered client did not work.<br/><br/><!--<br/>siptrans.cpp<br/>-->
Handling of OPTIONS from registered client did not work.<br/><br/><!--<br/>siptrans.cpp<br/>--><!---->
      
      
=== SIP: Media negotiation for video fails if called through waiting queue or multi reg ===
=== SIP: Media negotiation for video fails if called through waiting queue or multi reg ===
Line 1,219: Line 1,219:
|[http://mantis.innovaphone.com/view.php?id=91235 91235]
|[http://mantis.innovaphone.com/view.php?id=91235 91235]
|}
|}
Media negotiation for video fails if called through waiting queue or multi reg.<br/>In this case the PBX has to handle offer/offer-collision.<br/>In this case the PBX must select audio and video codec.<br/>In this case the PBX must send SDP answers to both endpoints.<br/><br/><!--<br/>sip.cpp<br/>-->
Media negotiation for video fails if called through waiting queue or multi reg.<br/>In this case the PBX has to handle offer/offer-collision.<br/>In this case the PBX must select audio and video codec.<br/>In this case the PBX must send SDP answers to both endpoints.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== SIP: Secondary target (hostname) is not resolved ===
=== SIP: Secondary target (hostname) is not resolved ===
Line 1,230: Line 1,230:
|[http://mantis.innovaphone.com/view.php?id=91287 91287]
|[http://mantis.innovaphone.com/view.php?id=91287 91287]
|}
|}
Usually a response to a SRV query delivers additional records containing the ip address of any target (hostname).<br/>Some DNS servers do not.<br/>Additional A querys are required.<br/>An A query was issued for the primnary target (most preferred hostname).<br/>No A query was issued for the secondary target (less preferred hostname).<br/>Fixed now.<br/><br/><!--<br/>sip.cpp/h<br/>-->
Usually a response to a SRV query delivers additional records containing the ip address of any target (hostname).<br/>Some DNS servers do not.<br/>Additional A querys are required.<br/>An A query was issued for the primnary target (most preferred hostname).<br/>No A query was issued for the secondary target (less preferred hostname).<br/>Fixed now.<br/><br/><!--<br/>sip.cpp/h<br/>--><!---->
      
      
=== IP-DECT: Trap in Radio module (IP1202) ===
=== IP-DECT: Trap in Radio module (IP1202) ===
Line 1,241: Line 1,241:
|[http://mantis.innovaphone.com/view.php?id=91315 91315]
|[http://mantis.innovaphone.com/view.php?id=91315 91315]
|}
|}
A trap in the IP-DECT Radio module occurs if the Mobility Master is used and a duplicate IPEI command is sent to the Master. The Master handles it with a location cancel and an endpoint delete command sent to the radio. If the two commands arrives with no delay, the Radio module traps. This is fixed now.<br/><br/><!--<br/>Changed files:<br/>dectradio.cpp<br/>dectlocalusers.cpp<br/>-->
A trap in the IP-DECT Radio module occurs if the Mobility Master is used and a duplicate IPEI command is sent to the Master. The Master handles it with a location cancel and an endpoint delete command sent to the radio. If the two commands arrives with no delay, the Radio module traps. This is fixed now.<br/><br/><!--<br/>Changed files:<br/>dectradio.cpp<br/>dectlocalusers.cpp<br/>--><!---->
      
      
=== myPBX: Prompted input fields lost title when logging-out ===
=== myPBX: Prompted input fields lost title when logging-out ===
Line 1,252: Line 1,252:
|[http://mantis.innovaphone.com/view.php?id=91320 91320]
|[http://mantis.innovaphone.com/view.php?id=91320 91320]
|}
|}
Error in the prompted input library.<br/><!--<br/>mypbx10_prompted_input.js<br/>-->
Error in the prompted input library.<br/><!--<br/>mypbx10_prompted_input.js<br/>--><!---->
      
      
=== myPBX: Sending chat message with line break terminated the session ===
=== myPBX: Sending chat message with line break terminated the session ===
Line 1,263: Line 1,263:
|[http://mantis.innovaphone.com/view.php?id=91323 91323]
|[http://mantis.innovaphone.com/view.php?id=91323 91323]
|}
|}
Solution: Remove additional white space before sending.<br/><!--<br/>mypbx10_im.js<br/>-->
Solution: Remove additional white space before sending.<br/><!--<br/>mypbx10_im.js<br/>--><!---->
      
      
=== SIP: Wrong call was disconnected after successful transfer ===
=== SIP: Wrong call was disconnected after successful transfer ===
Line 1,274: Line 1,274:
|[http://mantis.innovaphone.com/view.php?id=91349 91349]
|[http://mantis.innovaphone.com/view.php?id=91349 91349]
|}
|}
Wrong call was disconnected after successful transfer.<br/><br/><!--<br/>sip.cpp<br/>-->
Wrong call was disconnected after successful transfer.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== SIP: SDP answer for T.38 switch-over must contain multiple media descriptions ===
=== SIP: SDP answer for T.38 switch-over must contain multiple media descriptions ===
Line 1,285: Line 1,285:
|[http://mantis.innovaphone.com/view.php?id=91377 91377]
|[http://mantis.innovaphone.com/view.php?id=91377 91377]
|}
|}
... if SDP offer contains multiple media descriptions.<br/><br/><!--<br/>sip.cpp<br/>-->
... if SDP offer contains multiple media descriptions.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== Video: webcam remains active after a video call ===
=== Video: webcam remains active after a video call ===
Line 1,296: Line 1,296:
|[http://mantis.innovaphone.com/view.php?id=91404 91404]
|[http://mantis.innovaphone.com/view.php?id=91404 91404]
|}
|}
This effect does not appear with all webcams and neither with the same webcam plugged at different computer.<br/><br/><!--<br/>video.cpp<br/>videoReader.cpp<br/>captureDevices.cpp<br/>-->
This effect does not appear with all webcams and neither with the same webcam plugged at different computer.<br/><br/><!--<br/>video.cpp<br/>videoReader.cpp<br/>captureDevices.cpp<br/>--><!---->
      
      
=== PBX: Not possible to login as user with non-full admin rights if 'Password protect all Pages' ===
=== PBX: Not possible to login as user with non-full admin rights if 'Password protect all Pages' ===
Line 1,307: Line 1,307:
|[http://mantis.innovaphone.com/view.php?id=91414 91414]
|[http://mantis.innovaphone.com/view.php?id=91414 91414]
|}
|}
Some pages needed for the UI, which are normally not password protected, could not accessed with the reduced rights<br/><!--<br/>http.cpp<br/>-->
Some pages needed for the UI, which are normally not password protected, could not accessed with the reduced rights<br/><!--<br/>http.cpp<br/>--><!---->
      
      
=== SIP: Follow offers ptime proposal ===
=== SIP: Follow offers ptime proposal ===
Line 1,318: Line 1,318:
|[http://mantis.innovaphone.com/view.php?id=91421 91421]
|[http://mantis.innovaphone.com/view.php?id=91421 91421]
|}
|}
Better follow offers ptime proposal.<br/>Otherwise SAMwin operator does not stop sending re-INVITE.<br/><br/><!--<br/>sip.cpp<br/>-->
Better follow offers ptime proposal.<br/>Otherwise SAMwin operator does not stop sending re-INVITE.<br/><br/><!--<br/>sip.cpp<br/>--><!---->
      
      
=== H.323: Allow update of Registration password ===
=== H.323: Allow update of Registration password ===
Line 1,329: Line 1,329:
|[http://mantis.innovaphone.com/view.php?id=91440 91440]
|[http://mantis.innovaphone.com/view.php?id=91440 91440]
|}
|}
needed in case a password is changed, which is replicated to a DECT system<br/><!--<br/>h323sig.cpp<br/>h323.h<br/>voip.cpp<br/>voip.j<br/>-->
needed in case a password is changed, which is replicated to a DECT system<br/><!--<br/>h323sig.cpp<br/>h323.h<br/>voip.cpp<br/>voip.j<br/>--><!---->
      
      
=== Phone: Illegal errcode in returnError for ctInitiate ===
=== Phone: Illegal errcode in returnError for ctInitiate ===
Line 1,340: Line 1,340:
|[http://mantis.innovaphone.com/view.php?id=91474 91474]
|[http://mantis.innovaphone.com/view.php?id=91474 91474]
|}
|}
Illegal errcode in returnError for ctInitiate.<br/><br/><!--<br/>fty.h<br/>phonesig.cpp<br/>sip.cpp<br/>-->
Illegal errcode in returnError for ctInitiate.<br/><br/><!--<br/>fty.h<br/>phonesig.cpp<br/>sip.cpp<br/>--><!---->
      
      
=== H.323: PROGRESS in connected state was treated as 'unexpected' ===
=== H.323: PROGRESS in connected state was treated as 'unexpected' ===
Line 1,351: Line 1,351:
|[http://mantis.innovaphone.com/view.php?id=91483 91483]
|[http://mantis.innovaphone.com/view.php?id=91483 91483]
|}
|}
This happened with H.323 connections without registration when disconnecting a call with inband information (e.g. a call to an ISDN interface). Unnecessary events were generated.<br/><!--<br/>h323sig.cpp<br/>h323sig.h<br/>h323_tbl.tbl<br/>-->
This happened with H.323 connections without registration when disconnecting a call with inband information (e.g. a call to an ISDN interface). Unnecessary events were generated.<br/><!--<br/>h323sig.cpp<br/>h323sig.h<br/>h323_tbl.tbl<br/>--><!---->
      
      
=== Video: disable stand by/sleep modus during a video call ===
=== Video: disable stand by/sleep modus during a video call ===
Line 1,362: Line 1,362:
|[http://mantis.innovaphone.com/view.php?id=91502 91502]
|[http://mantis.innovaphone.com/view.php?id=91502 91502]
|}
|}
due to inactivity the computer will go in stand by and video call could be lost.<br/><br/><!--<br/>video.cpp<br/>-->
due to inactivity the computer will go in stand by and video call could be lost.<br/><br/><!--<br/>video.cpp<br/>--><!---->
      
      
=== myPBX: Show meaningful error message when the connection to the PBX failed ===
=== myPBX: Show meaningful error message when the connection to the PBX failed ===
Line 1,373: Line 1,373:
|[http://mantis.innovaphone.com/view.php?id=91604 91604]
|[http://mantis.innovaphone.com/view.php?id=91604 91604]
|}
|}
"Could not connect to PBX. Try again!" instead of generic error page.<br/><!--<br/>mypbx10.htm<br/>mypbx10.js<br/>-->
"Could not connect to PBX. Try again!" instead of generic error page.<br/><!--<br/>mypbx10.htm<br/>mypbx10.js<br/>--><!---->
      
      
=== Video: write webcam output formats/resolutions to trace file if no suitable format is found ===
=== Video: write webcam output formats/resolutions to trace file if no suitable format is found ===
Line 1,384: Line 1,384:
|[http://mantis.innovaphone.com/view.php?id=91671 91671]
|[http://mantis.innovaphone.com/view.php?id=91671 91671]
|}
|}
although we have tested more than 30 Webcams from different vendors we may find a webcam with other output formats or resolutions. Write more traces to have this information available.<br/><!--<br/>captureDevices.cpp<br/>captureDevices.h<br/>video.cpp<br/>-->
although we have tested more than 30 Webcams from different vendors we may find a webcam with other output formats or resolutions. Write more traces to have this information available.<br/><!--<br/>captureDevices.cpp<br/>captureDevices.h<br/>video.cpp<br/>--><!---->
      
      
=== IP-DECT: Trap with data calls ===
=== IP-DECT: Trap with data calls ===
Line 1,395: Line 1,395:
|[http://mantis.innovaphone.com/view.php?id=91807 91807]
|[http://mantis.innovaphone.com/view.php?id=91807 91807]
|}
|}
The IP-DECT Radio traps if a data call is released and the release includes a facility.<br/><br/><!--<br/>Changed file:<br/>dectradio_fty_call.cpp<br/>-->
The IP-DECT Radio traps if a data call is released and the release includes a facility.<br/><br/><!--<br/>Changed file:<br/>dectradio_fty_call.cpp<br/>--><!---->
      
      
=== myPBX: Online status was not displayed in search screen ===
=== myPBX: Online status was not displayed in search screen ===
Line 1,406: Line 1,406:
|[http://mantis.innovaphone.com/view.php?id=91826 91826]
|[http://mantis.innovaphone.com/view.php?id=91826 91826]
|}
|}
Show the presence like at the favourites.<br/><!--<br/>mypbx10.js<br/>-->
Show the presence like at the favourites.<br/><!--<br/>mypbx10.js<br/>--><!---->
      
      
=== Kerberos administration: Increase maximum number of Kerberos users from 20 to 50 ===
=== Kerberos administration: Increase maximum number of Kerberos users from 20 to 50 ===
Line 1,417: Line 1,417:
|[http://mantis.innovaphone.com/view.php?id=91847 91847]
|[http://mantis.innovaphone.com/view.php?id=91847 91847]
|}
|}
Increase limit on page General/Kerberos.<br/>Use POST for submitting form, instead of GET.<br/><!--<br/>kerberos_db.xsl<br/>-->
Increase limit on page General/Kerberos.<br/>Use POST for submitting form, instead of GET.<br/><!--<br/>kerberos_db.xsl<br/>--><!---->
      
      
=== SRTP: Avoid one-way media with high start sequence numbers ===
=== SRTP: Avoid one-way media with high start sequence numbers ===
Line 1,428: Line 1,428:
|[http://mantis.innovaphone.com/view.php?id=91892 91892]
|[http://mantis.innovaphone.com/view.php?id=91892 91892]
|}
|}
In some cases SRTP calls had one-way media because the RTP sequence number wrapped from 65535 to 0 at be beginning of the call before the receiver started receiving and processing packets.<br/><br/>The scope of start sequence numbers for RTP streams is changed from [0;65535] to [0;32767] to make sure that the receiver can always receive packets before the overflow happens.<br/><br/>The calculation of the roll-over counter (ROC) is also improved to be more reliable.<br/><br/><!--<br/>media.cpp<br/>cipher_api.h<br/>cipher_api.cpp<br/>-->
In some cases SRTP calls had one-way media because the RTP sequence number wrapped from 65535 to 0 at be beginning of the call before the receiver started receiving and processing packets.<br/><br/>The scope of start sequence numbers for RTP streams is changed from [0;65535] to [0;32767] to make sure that the receiver can always receive packets before the overflow happens.<br/><br/>The calculation of the roll-over counter (ROC) is also improved to be more reliable.<br/><br/><!--<br/>media.cpp<br/>cipher_api.h<br/>cipher_api.cpp<br/>--><!---->
      
      
=== H.323: Unnecessary re-initializing of rtp-channel on incoming calls to phone ===
=== H.323: Unnecessary re-initializing of rtp-channel on incoming calls to phone ===
Line 1,439: Line 1,439:
|[http://mantis.innovaphone.com/view.php?id=91898 91898]
|[http://mantis.innovaphone.com/view.php?id=91898 91898]
|}
|}
This did not create any problems except CPU load and together with another problem in RTP it caused no media on incoming SRTP calls approximately every 1000th call.<br/><!--<br/>h323ch.cpp<br/>-->
This did not create any problems except CPU load and together with another problem in RTP it caused no media on incoming SRTP calls approximately every 1000th call.<br/><!--<br/>h323ch.cpp<br/>--><!---->
      
      
=== IP22,IP24,IP28,IP302,IP305: RTP-DTMF not offered when using a/b interface ===
=== IP22,IP24,IP28,IP302,IP305: RTP-DTMF not offered when using a/b interface ===
Line 1,450: Line 1,450:
|[http://mantis.innovaphone.com/view.php?id=91905 91905]
|[http://mantis.innovaphone.com/view.php?id=91905 91905]
|}
|}
For example:<br/><br/>\tv=0<br/>\to=- 14 1 IN IP4 10.17.1.91<br/>\ts=-<br/>\tt=0 0<br/>\tm=audio 16414 RTP/AVP 8 0 18 4 97<br/>\tc=IN IP4 10.17.1.91<br/>\ta=rtpmap:97 CLEARMODE/8000<br/>\ta=fmtp:18 annexa=yes<br/>\ta=fmtp:18 annexb=yes<br/>\ta=ptime:20<br/>\ta=silenceSupp:off - - - -<br/>\ta=sendrecv<br/><br/><!--<br/>ab_sig.cpp<br/>-->
For example:<br/><br/>\tv=0<br/>\to=- 14 1 IN IP4 10.17.1.91<br/>\ts=-<br/>\tt=0 0<br/>\tm=audio 16414 RTP/AVP 8 0 18 4 97<br/>\tc=IN IP4 10.17.1.91<br/>\ta=rtpmap:97 CLEARMODE/8000<br/>\ta=fmtp:18 annexa=yes<br/>\ta=fmtp:18 annexb=yes<br/>\ta=ptime:20<br/>\ta=silenceSupp:off - - - -<br/>\ta=sendrecv<br/><br/><!--<br/>ab_sig.cpp<br/>--><!---->
      
      
=== PBX: MOH URL parameters for parked calls should refer to the parked-to and not parking user ===
=== PBX: MOH URL parameters for parked calls should refer to the parked-to and not parking user ===
Line 1,461: Line 1,461:
|[http://mantis.innovaphone.com/view.php?id=91931 91931]
|[http://mantis.innovaphone.com/view.php?id=91931 91931]
|}
|}
The MOH URL Paramter (%l, %h, %n, ...) can be used to use different MOH Files based on the User who is holding the call. In case of a parked call this should refer to the object where the call is parked, not to the user who has initiated the parking.<br/><!--<br/>pbx.cpp<br/>-->
The MOH URL Paramter (%l, %h, %n, ...) can be used to use different MOH Files based on the User who is holding the call. In case of a parked call this should refer to the object where the call is parked, not to the user who has initiated the parking.<br/><!--<br/>pbx.cpp<br/>--><!---->
      
      
=== IP-DECT: Wrong XML data in Radio endpoint ===
=== IP-DECT: Wrong XML data in Radio endpoint ===
Line 1,472: Line 1,472:
|[http://mantis.innovaphone.com/view.php?id=91933 91933]
|[http://mantis.innovaphone.com/view.php?id=91933 91933]
|}
|}
The XML data in the Radio endpoint is wrong and fixed now. The data is only used for the command show-endpoints, not for the GUI.<br/><br/><!--<br/>Changed file:<br/>dectlocalusers.cpp<br/>-->
The XML data in the Radio endpoint is wrong and fixed now. The data is only used for the command show-endpoints, not for the GUI.<br/><br/><!--<br/>Changed file:<br/>dectlocalusers.cpp<br/>--><!---->
      
      
=== Video: show video card model in trace ===
=== Video: show video card model in trace ===
Line 1,483: Line 1,483:
|[http://mantis.innovaphone.com/view.php?id=91934 91934]
|[http://mantis.innovaphone.com/view.php?id=91934 91934]
|}
|}
this was only done if the Dxva2 was correctly initialized or supported. Now this information will always be displayed since it could be useful.<br/><!--<br/>dxva2.cpp<br/>-->
this was only done if the Dxva2 was correctly initialized or supported. Now this information will always be displayed since it could be useful.<br/><!--<br/>dxva2.cpp<br/>--><!---->
      
      
=== Video: windows macro SUCCEEDED returns success for S_FALSE ===
=== Video: windows macro SUCCEEDED returns success for S_FALSE ===
Line 1,494: Line 1,494:
|[http://mantis.innovaphone.com/view.php?id=91938 91938]
|[http://mantis.innovaphone.com/view.php?id=91938 91938]
|}
|}
I assumed S_FALSE was good enough to report an error but this macro expects a negative number to fail.<br/><br/><!--<br/>captureDevices.cpp<br/>device3D.cpp<br/>h264_intel_encoder.cpp<br/>videoReader.cpp<br/>videoWriter.cpp<br/>-->
I assumed S_FALSE was good enough to report an error but this macro expects a negative number to fail.<br/><br/><!--<br/>captureDevices.cpp<br/>device3D.cpp<br/>h264_intel_encoder.cpp<br/>videoReader.cpp<br/>videoWriter.cpp<br/>--><!---->
      
      
=== myPBX launcher: Possible exception when closing webcam window ===
=== myPBX launcher: Possible exception when closing webcam window ===
Line 1,505: Line 1,505:
|[http://mantis.innovaphone.com/view.php?id=91969 91969]
|[http://mantis.innovaphone.com/view.php?id=91969 91969]
|}
|}
Null reference exception in WebcamForm_FormClosing<br/><!--<br/>WebcamForm.cs<br/>-->
Null reference exception in WebcamForm_FormClosing<br/><!--<br/>WebcamForm.cs<br/>--><!---->
      
      
=== PBX Mobility: Call from mobile endpoint to a user with mobility, but without PBX phone was disconnected ===
=== PBX Mobility: Call from mobile endpoint to a user with mobility, but without PBX phone was disconnected ===
Line 1,516: Line 1,516:
|[http://mantis.innovaphone.com/view.php?id=91976 91976]
|[http://mantis.innovaphone.com/view.php?id=91976 91976]
|}
|}
This was a collateral damage of<br/><br/>fix: #86813: PBX Mobility: Take precaution against hanging calls because of misbehaving mobile phone or client<br/><br/><!--<br/>pbx.cpp<br/>-->
This was a collateral damage of<br/><br/>fix: #86813: PBX Mobility: Take precaution against hanging calls because of misbehaving mobile phone or client<br/><br/><!--<br/>pbx.cpp<br/>--><!---->
      
      
=== SIP/DNS: Wrong port used on secondary SIP server ===
=== SIP/DNS: Wrong port used on secondary SIP server ===
Line 1,527: Line 1,527:
|[http://mantis.innovaphone.com/view.php?id=91995 91995]
|[http://mantis.innovaphone.com/view.php?id=91995 91995]
|}
|}
If SRV query returns 2 hosts with different port, but no IP address in additional records,<br/>SIP starts two A queries for the two host names.<br/>Both resolved IP addresses are combined with the port of the most preferred host of the SRV answer.<br/><br/><!--<br/>sip.cpp/h<br/>-->
If SRV query returns 2 hosts with different port, but no IP address in additional records,<br/>SIP starts two A queries for the two host names.<br/>Both resolved IP addresses are combined with the port of the most preferred host of the SRV answer.<br/><br/><!--<br/>sip.cpp/h<br/>--><!---->

Revision as of 13:28, 14 December 2012

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 (100585)

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 Closed
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 Closed
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 Closed
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 Closed
Id 90483

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

SIP: New interop tweak "No Remote Hold Signaling"

Status Closed
Id 90532

New config option on gateway interfaces "No Remote Hold Signaling".
Disables interworking of "inactive" into remoteHold.

PBX-SOAP: Support for 'rc' and 'srce164' on UserCall on Waiting Queue

Status Closed
Id 90537

If a Waiting Queue is used for outgoing calls, these features can be usefull for some applications

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 Closed
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 Closed
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 Closed
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 Closed
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.

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

Status Closed
Id 89840

If the connection between an Office application and myPBX gets lost, the COM Server is now restarted.
This forces a reload of the web UI and a reset of the video connection too.

'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 Closed
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 Closed
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 Closed
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 Closed
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 Closed
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 Closed
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 Closed
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 Closed
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 Closed
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.

SIP: Locally configured DNS entries were not used if no DNS server configured

Status Closed
Id 90508

If no DNS server was configured, but DNS names are to be resolved,
local DNS entries can be added (Services/DNS/Hosts).
SIP stack fails with SRV query and does not try A query which would deliver IP address.

PBX: CDR was missing for a call rejected because of Busy on ... Calls

Status Closed
Id 90518

On the user with Busy on ... calls set no CDR was generate for a call which was rejected because of this. The user would like to see this as a missed call in this case.

PBX: Registration with name was possible even without matching device

Status Closed
Id 90531

This is a security issue, because of this it was not possible to enforce a police which allows registration by hardware id only. No fix in version 9, because of compatibility reasons.

IP-DECT: RTP stream

Status Closed
Id 90539

If a remote hold event is received, no RTP data should be sent by the IP-DECT device.
A CTI initiated call is established with a call transfer and a "No Media data received" error event can occur.
This is fixed now.

PBX: Twin-Phones: On connect from twin-phone endpoint disconnect additional ringing calls

Status Closed
Id 90567

If two calls are ringing at a twin phone user with multiple endpoints, and no call is conneceted, these calls are ringing at all endpoints. When the first call is connected, the remaining call legs ringing at other endpoints should be disconnected.

SIP: Trap on IP-DECT

Status Closed
Id 90569

Trap in GK-CHANNEL when Dectmaster application sends DTMF before call if created.

V10 Beta 3

Changes included in Version 10 beta3 Definition

New Features

myPBX: Change password

Status Closed
Id 85560

Change the own user password from myPBX. The dialog is opened by using the settings button on the top right.

myPBX: DTMF

Status Closed
Id 85562

DTMF keypad for myPBX version 10.

myPBX: Presence depending on user activity

Status Closed
Id 86941

The launcher can now detect user activity and set the IM status depending on the current state. If the user is inactive the IM status is set to closed (Appear Offline).

The feature can be turned on and off and an idle timeout can be configured using the option "Auto Appear Offline" in the configuration dialog. During installation the number of minutes can be configured using the MSI parameter AUTOAPPEAROFFLINE=[0|1|5|10|15]. 0 turns the feature off.

Kerberos: Use default realm if no realm is given

Status Closed
Id 90108

If the user logs-in using Kerberos without specifying a realm the default realm is used.

\\user -> example.com\\user
user@ -> user@example.com

The default realm can be configured on page General/Admin. If no default realm is configured, the Kerberos realm of the box is used.

myPBX launcher: Choose webcam

Status Closed
Id 90457

Let the user choose the webcam to be used for video calls.

Display of Gateway Temperature, available Power Sources, Power Off Loop setting

Status Closed
Id 90674

additional information in general->info screen

PBX: New configuration option 'Hide connected Number' at object

Status Closed
Id 90693

In some cases it is desireable not to reveal the final destination of a call to a caller. For example a call center agent should not be called directly by the customer.

myPBX launcher: Show webcam configuration at the same location as the video call window

Status Closed
Id 90779

So that the user can configure the location and size of the video window without having a video call.

New counter for device temperature

Status Closed
Id 90831

New counter for device temperature

PBX: Forward Messages in ringback to all ringing endpoints

Status To-decide
Id 90976

A message sent on a call which was not yet connected, was discarded. Now this message is forwarded to all endpoints which have received the call

Webmedia: Support for different tone patterns (countries)

Status Closed
Id 91134

New URL param &tones=num to select country-specific tone patterns.

myPBX launcher: Localisation for texts

Status Closed
Id 91151

Support for localisation.
Current languages: English and German

PBX: Make PBX generated tones configurable

Status To-decide
Id 91175

The same country specific tone schemes as in the gateway can be configured

Indicate Video on calls page

Status To-decide
Id 91213

The video coder is displayed on the calls page

PBX-SOAP: Handle '+' in destination number supplied with UserCall

Status To-decide
Id 91280

Treat a destination number starting with '+' as internation number and map it according PBX settings

PBX: Indicate video capability on registration page

Status Closed
Id 91312

The state of the remote video service is shown on page PBX/Registrations:
- available: the phone supports remote video
- connected: a remote video client is connected to the phone

IP-DECT: Login/logout changed for OEM PBX

Status Closed
Id 91417

Login/logout feature is changed for OEM PBX.

IP-DECT: Configuration option 'Registration with system password'

Status Closed
Id 91460

The configuration option 'Registration with system password' is added. If ticked, all users are registered with the system password. This is useful, if the PBX users are only allowed to register with the PBX password.

myPBX launcher: Handle power state changes of the computer

Status Closed
Id 91566

Suspend:
- Disconnect web application
- Disconnect remote video
Wake-up:
- Reconnect web application
- Reconnect remote video

myPBX: Show reason for failed login

Status Closed
Id 91592

Show why a login failed. Currently there are two reasons:
- Wrong username or password
- No license

myPBX launcher: Office Presence Logging can be switched on/off by myPBX

Status Closed
Id 91642

The office presence logging setting by Microsoft can be now enabled/disabled by myPBX.

PBX: Allow Name (instead of Long Name) to identify user for mobility data call thru

Status To-decide
Id 91660

This should simplify Opticaller configuration

IP-DECT: Static ports between Master and Radio

Status Closed
Id 91815

Now the VOIP connections between the Master and the Radio use static ports instead of dynamic ones. This is useful if only a few ports should be opened through a firewall. For calls from the Radio to the Master the ports 1716 and 1717 (TLS) are used. For the default Master connection for calls from the Master to the Radio the ports 1718 and 1719 (TLS) are used. For dynamic Radio-Master connections the ports from 1722 are used. Every connection needs two ports.


Bug Fixes

SIP: Disabled IP-DECT interface tries to register

Status Closed
Id 90597

Disabled IP-DECT interface tries to register.

H.323: Timer to monitor response to setup too short for some traffic cases

Status Closed
Id 90696

This created unnecessary event in IP-DECT systems when calling powered off or out of range handsets

PBX-CDRs: On call to user without registration, the name/number info was missing in rel-from event

Status To-decide
Id 90720

For consistency reasons the name/number info should be present.

PBX Mobility: Connected number from mobile phone was forwarded to caller

Status To-decide
Id 90722

If a call is answered on the mobile phone, it should look idebtical to the caller to the case that the call was answered locally. This means a connected number from the mobile phone must not be forwarded.

PBX Waiting: Potential Trap if editing while a call is initiated with SOAP

Status Closed
Id 90766

The Waiting object can be used as outgoing dialing object with SOAP. If this is done and the configuration is changed while an outgoing call was pending, a trap could happen

H.323: Potential Trap in special case which could only happen in version 10

Status Closed
Id 90768

This fixed is merged to version 9 only of consistency reasons

myPBX launcher: Multi-screen support for webcam window

Status Closed
Id 90773

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

SIP: Respect changes in PAI/PPI header when receiving UPDATE with SDP offer

Status Closed
Id 90778

PAI/PPI was processed when receiving UPDATE without SDP offer.
PAI/PPI was ignored when receiving UPDATE with SDP offer.
Now PAI/PPI is processed when receiving UPDATE with SDP offer.


SIP: Possible buffer overrun

Status Closed
Id 90780

Fix for possible buffer overrun.

SIP: Wrong error log "Timeout during media negotiation for call"

Status Closed
Id 90821

Error log "Timeout during media negotiation for call" may occur after re-negotioation.
Re-negotioation occurs during hold/retrieve/transfer.

Video: Webcam settings blocks Video Library

Status To-decide
Id 90834

the video library blocks until the webcam settings window is closed avoiding processing an incoming connect. Start webcam settings in a new thread.

PBX Trunk: Name to Number Feature did not work with calls to extern

Status Closed
Id 90858

If an endpoint cannot be found by name, the call should be forwarded to extern

Potential Trap when rapidly switching local Media connections (Conferencing)

Status To-decide
Id 90933

There was a race condition when switching local media channels (e.g. ISDN channels to conference interfaces), which could cause media not functioning or even a trap

PBX CSV Import: Corrupted objects at buffer boundaries

Status Closed
Id 90942

The upload is processed in chunks of 2K. At boundaries of these chunks data could be corrupted. This was fixed and the chunk size increased to 10K

Gateway Config: The wizard did not configure the default IP address on ETH1

Status To-decide
Id 90995

When doing a reset to manufacturing defaults (long reset) an address of 192.168.1.1 is configured for ETH1. This address was removed when the gateway was configured with the wizard.

Phone: Trap when selecting registration for a directory entry

Status Closed
Id 90999

Trap when selecting registration for a directory entry,
but only if the registration has either no name or no number.

H.323: No event should be generated in State 11 and 25

Status Closed
Id 91020

State 25 is incoming overlap sending. This means a call was received with incomplete dialing information and the caller failed to dial more digits within the timeout of 2min. This is no indication of any malfunction but only a usage problem, so no event should be generated.

State 11 is disconnecting with inband announcement. A timeout happens if a user listens to the announcement for more then 30s. This could be normal.

IP-DECT: Escape name of logged-in admin user

Status Closed
Id 91021

The name was not displayed correctly when it contained backslashes. This happens when Kerberos is used.

SIP: Trap when cancelling call

Status Closed
Id 91023

Double delete of a call entity.

SIP: Heavy TLS retry load when server certificate was rejected

Status Closed
Id 91033

Collateral damage from earlier fixed for DNS refreshing.

myPBX: Changed heuristics for telling numbers and URIs apart

Status Closed
Id 91045

Strings containing an @ are now always handled as an URI.

myPBX launcher: Automatically refresh list of webcams in the webcam preview window

Status Closed
Id 91133

If new webcams are connected or existing webcams are disconnected the webcam preview window is refreshed with an updated list.

H.323: Incoming faststart call was sometimes not accepted as faststart

Status Closed
Id 91136

Only happens if non EFC is used on the incoming call, so this only happens in interop cases with other H.323 equipment

SIP: Better handling of incoming calls

Status Closed
Id 91153

Msg sequence INVITE,CANCEL,INVITE may result into second call rejected.

myPBX launcher: Improve dialing using hotkey

Status Closed
Id 91163

Detect clipboard content type and skip useless information. For example the time and date of an email should not be used as a phone number.

myPBX: Hide pickup button for own calls

Status Closed
Id 91220

If the user calls one of his favourites a pickup button is shown for the alerting call at the favourite.

SIP: Handling of OPTIONS from registered client did not work

Status Closed
Id 91232

Handling of OPTIONS from registered client did not work.

SIP: Media negotiation for video fails if called through waiting queue or multi reg

Status Closed
Id 91235

Media negotiation for video fails if called through waiting queue or multi reg.
In this case the PBX has to handle offer/offer-collision.
In this case the PBX must select audio and video codec.
In this case the PBX must send SDP answers to both endpoints.

SIP: Secondary target (hostname) is not resolved

Status Closed
Id 91287

Usually a response to a SRV query delivers additional records containing the ip address of any target (hostname).
Some DNS servers do not.
Additional A querys are required.
An A query was issued for the primnary target (most preferred hostname).
No A query was issued for the secondary target (less preferred hostname).
Fixed now.

IP-DECT: Trap in Radio module (IP1202)

Status Closed
Id 91315

A trap in the IP-DECT Radio module occurs if the Mobility Master is used and a duplicate IPEI command is sent to the Master. The Master handles it with a location cancel and an endpoint delete command sent to the radio. If the two commands arrives with no delay, the Radio module traps. This is fixed now.

myPBX: Prompted input fields lost title when logging-out

Status Closed
Id 91320

Error in the prompted input library.

myPBX: Sending chat message with line break terminated the session

Status Closed
Id 91323

Solution: Remove additional white space before sending.

SIP: Wrong call was disconnected after successful transfer

Status Closed
Id 91349

Wrong call was disconnected after successful transfer.

SIP: SDP answer for T.38 switch-over must contain multiple media descriptions

Status Closed
Id 91377

... if SDP offer contains multiple media descriptions.

Video: webcam remains active after a video call

Status To-decide
Id 91404

This effect does not appear with all webcams and neither with the same webcam plugged at different computer.

PBX: Not possible to login as user with non-full admin rights if 'Password protect all Pages'

Status Closed
Id 91414

Some pages needed for the UI, which are normally not password protected, could not accessed with the reduced rights

SIP: Follow offers ptime proposal

Status Closed
Id 91421

Better follow offers ptime proposal.
Otherwise SAMwin operator does not stop sending re-INVITE.

H.323: Allow update of Registration password

Status Closed
Id 91440

needed in case a password is changed, which is replicated to a DECT system

Phone: Illegal errcode in returnError for ctInitiate

Status To-decide
Id 91474

Illegal errcode in returnError for ctInitiate.

H.323: PROGRESS in connected state was treated as 'unexpected'

Status Closed
Id 91483

This happened with H.323 connections without registration when disconnecting a call with inband information (e.g. a call to an ISDN interface). Unnecessary events were generated.

Video: disable stand by/sleep modus during a video call

Status To-decide
Id 91502

due to inactivity the computer will go in stand by and video call could be lost.

myPBX: Show meaningful error message when the connection to the PBX failed

Status Closed
Id 91604

"Could not connect to PBX. Try again!" instead of generic error page.

Video: write webcam output formats/resolutions to trace file if no suitable format is found

Status To-decide
Id 91671

although we have tested more than 30 Webcams from different vendors we may find a webcam with other output formats or resolutions. Write more traces to have this information available.

IP-DECT: Trap with data calls

Status Closed
Id 91807

The IP-DECT Radio traps if a data call is released and the release includes a facility.

myPBX: Online status was not displayed in search screen

Status Closed
Id 91826

Show the presence like at the favourites.

Kerberos administration: Increase maximum number of Kerberos users from 20 to 50

Status Closed
Id 91847

Increase limit on page General/Kerberos.
Use POST for submitting form, instead of GET.

SRTP: Avoid one-way media with high start sequence numbers

Status To-decide
Id 91892

In some cases SRTP calls had one-way media because the RTP sequence number wrapped from 65535 to 0 at be beginning of the call before the receiver started receiving and processing packets.

The scope of start sequence numbers for RTP streams is changed from [0;65535] to [0;32767] to make sure that the receiver can always receive packets before the overflow happens.

The calculation of the roll-over counter (ROC) is also improved to be more reliable.

H.323: Unnecessary re-initializing of rtp-channel on incoming calls to phone

Status To-decide
Id 91898

This did not create any problems except CPU load and together with another problem in RTP it caused no media on incoming SRTP calls approximately every 1000th call.

IP22,IP24,IP28,IP302,IP305: RTP-DTMF not offered when using a/b interface

Status To-decide
Id 91905

For example:

\tv=0
\to=- 14 1 IN IP4 10.17.1.91
\ts=-
\tt=0 0
\tm=audio 16414 RTP/AVP 8 0 18 4 97
\tc=IN IP4 10.17.1.91
\ta=rtpmap:97 CLEARMODE/8000
\ta=fmtp:18 annexa=yes
\ta=fmtp:18 annexb=yes
\ta=ptime:20
\ta=silenceSupp:off - - - -
\ta=sendrecv

PBX: MOH URL parameters for parked calls should refer to the parked-to and not parking user

Status To-decide
Id 91931

The MOH URL Paramter (%l, %h, %n, ...) can be used to use different MOH Files based on the User who is holding the call. In case of a parked call this should refer to the object where the call is parked, not to the user who has initiated the parking.

IP-DECT: Wrong XML data in Radio endpoint

Status Closed
Id 91933

The XML data in the Radio endpoint is wrong and fixed now. The data is only used for the command show-endpoints, not for the GUI.

Video: show video card model in trace

Status To-decide
Id 91934

this was only done if the Dxva2 was correctly initialized or supported. Now this information will always be displayed since it could be useful.

Video: windows macro SUCCEEDED returns success for S_FALSE

Status To-decide
Id 91938

I assumed S_FALSE was good enough to report an error but this macro expects a negative number to fail.

myPBX launcher: Possible exception when closing webcam window

Status Closed
Id 91969

Null reference exception in WebcamForm_FormClosing

PBX Mobility: Call from mobile endpoint to a user with mobility, but without PBX phone was disconnected

Status To-decide
Id 91976

This was a collateral damage of

fix: #86813: PBX Mobility: Take precaution against hanging calls because of misbehaving mobile phone or client

SIP/DNS: Wrong port used on secondary SIP server

Status To-decide
Id 91995

If SRV query returns 2 hosts with different port, but no IP address in additional records,
SIP starts two A queries for the two host names.
Both resolved IP addresses are combined with the port of the most preferred host of the SRV answer.

Retrieved from "https://wiki.innovaphone.com/index.php?title=ReleaseNotes10:Firmware&oldid=27912"