Child pages
  • sipXcom 16.02
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Pre-Beta Issue List

Expecting Beta release in the second week of February.

 

 JIRA nameRN ContentEnhancement/Fix/Known IssueKey words
UC-3628REST API for call action doesn't escape + charFixed an issue with REST call action API such that it didn't excape the '+' character properly.FixAPI
SIPX-59Scheduled backup by specified day does not workFixed an issue caused when scheduling backup for one particular day and time.

Steps to recreate:
1.Go to Backup and setup a scheduled backup :
let's say Monday 17:00 PM (if current day is Monday)
2.Wait for specified time to arrive

Reported issue : backup is not triggered.

Additional info : scheduled backup setup as "Everyday" 17:PM will work.
Backup Now also works.
There is nothing related reported in the backup/sipxconfig.log
FixBackup
SIPX-158Main cdr fixesFix an issue with CDR to properly handle forwarded calls.

When a call goes out of sipx through a gateway or a sipTrunk, we relay on the contact that other part sent back to us to build cdr, and this is often useless to get information about the called party.

This is even worse when you have some call forwarding active, in this case you miss the actual entity reached from the call.

Often can be useful to know about which gateway/trunk is engaged when a call exit from sipx.
FixCDR
SIPX-61Call Forwarding CDR problemFixed an issue where if an extension (e.g. 200) is forwarded to mobile phone, and another extension or incoming number dials 200, and talks to the mobile number, mobile phone number of the callee cannot be displayed in the CDR.FixCDR
SIPX-4003 level plugin overwrite supportAdded an enhancement so that GUI plugins woudl work to 3 levels making customization of portal easier.

Ensure a depth of 3 for plugin overwritting
level 1 - sipxplugin2.beans.xml
level 2 - sipxplugin.beans.xml
level 3 - sipxplugin0.beans.xml

level 2 overwrites level 1
level 3 overwrites level 2

level 1 beans will be loaded
level 2 beans will be loaded and will overwrite any beans with same name from level 1
level 3 beans will be loaded and will overwrite any beans with same name from level 2
EnhancementConfig
UC-3859Defaults Related to Transfers should be changedSystem enhancement to change the following 3 values to the opposite of what they default to in order to avoid transfer issues.

We should change the default values of these options.

Parameters and current defaults:
System-->Media Services (Allow Blind Transfer) default: unchecked
System-->Media Services (Simplify Call After Transfer) default: checked
System--Voicemail (Transfer by Bridging the call) default: false

Parameters and proposed new defaults:
System-->Media Services (Allow Blind Transfer) default: checked
System-->Media Services (Simplify Call After Transfer) default: unchecked
System--Voicemail (Transfer by Bridging the call) default: true
EnhancementConfig
SIPX-279User registration page error on user with multiple bria phones assignedFixed an issue with registration page for an user assigned to more than one Bria phone.

Workaround is to search registrations in global page for that particular user using the web browser find function.
FixConfig
SIPX-398Remove IMAP settings from Unified Messaging settings in User GroupsIMAP is no longer supported. Remove IMAP server host, IMAP server port and TLS from User and User Group settings.FixConfig
UC-3153Do not allow presence subscriptions to selfFixed an issue caused when users subscribed to their own presence. Changed config webui to not allow users to subscribe to themselves. If the user has "Use Group Speed Dials" checked, this should also be filtered to exclude the user him/herself from the group list. Slightly related to UC-134.FixConfig
UC-3226For distribution lists, increase setting_value table from its "value" field currently limited to 1000 charactersFixed an issue caused by creating very large distribution lists whereas the field that contained this only allowed for 1000 characters.FixConfig
UC-3864/var/log/messages " There was a mount error, trying to mount one of the filesystems on this host."Fixed an issue with the new SIP packet capture tcpdump based service when running on multiple servers.

Log entry noted on fresh install Uniteme 15.12 /var/log/messages seems to be related to new tcpdump service .. :

[root@uc1 ~]# grep -c 'mount' /var/log/messages
169
[root@uc1 ~]# grep 'mount' /var/log/messages | tail -n 5
Jan 11 11:42:59 uc1 cf3[1656]: There was a mount error, trying to mount one of the filesystems on this host.
Jan 11 11:42:59 uc1 cf3[1656]: There was a mount error, trying to mount one of the filesystems on this host.
Jan 11 11:42:59 uc1 cf3[1656]: There was a mount error, trying to mount one of the filesystems on this host.
Jan 11 11:42:59 uc1 cf3[1656]: There was a mount error, trying to mount one of the filesystems on this host.
Jan 11 11:43:00 uc1 cf3[1656]: There was a mount error, trying to mount one of the filesystems on this host.
FixConfig
SIPX-335In mongo, users point to the old location name after a location name changeFixed an issue caused by changing a location name for a user, the old location name would remain.

Steps to reproduce:
1. Create a location
2. Assign user group to this location and verify in mongo User points to the correct location
3. Change location name to a new one and verify in mongo

Issue: Users still point to the old location name.

Workaround: Click Apply on the user group
FixLocations
SIPX-397Polycom SPIP 4.0.8 & Later firmwareAdded an enhancement for some new parameters to firmware 4.0.8 and later firmware for the SoundPoint IP phones.

One in particular causes the phone to close TCP socket connections which can break remote phone operation.

Add the following new parameter and ensure phone is configured with the value set as 1.

tcpIpApp.keepalive.tcp.sip.persistentConnection.enable 0 or 1 (0 = default)
If 0, the TCP Socket connection is closed after 1 minute. When the phone sends a new SIP message, a new connection is opened.
If 1, the TCP Socket connection remains open indefinitely.

Large installations may want to be able to set the value to 0 to keep TCP socket connections lower.
EnhancementPolycom
SIPX-92Change Polycom Phone QOS Default for Call Control so DSCP = 24Change Polycom defaults for QoS for call control so DSCP = 24.

In SipXConfig Polycom Phones QOS settings page

The default TOS settings equate to a DSCP of 44.

Call Control (current)
Prec Dly Thpt Rlb
5 Chk UnCk UnCk
101 1 0 0 seventh bit (Cost) 0
As DSCP = 44

Call Control (proposed)
Prec Dly Thpt Rlb
3 UnCk UnCk UnCk Seventh bit (Cost) Uncheck
011 0 0 0 seventh bit (Cost) 0
As DSCP = 24

RTP equates to a DSCP of 46 and if this Jira is implemented, that the Call Control settings equate to 24.

A call control setting of 24 is consistent with recommendations by eZuce and Cisco.
EnhancementPolycom
UC-1382Consultative transfer must point to the exact gateway that accepted the initial INVITEFixed an issue caused by multiple gateways on a single dial plan, consultitive transfer needed to point to the exact gateway that accepted the initial INVITE.

When there are multiple gateways configured to handle the call, there is no guaranty that the initial INVITE and the transferred INVITE with replaces will follow the same forked path. The proxy should be able to tag the REPLACEs header with the absolute URI of the gateway that accepted the initial INVITE. The registrar fallback plugin should be able to parse this tag and return it as a solitary contact.

How to replicate:
1. Create 2 gateways in the same branch. Lets call them gw01 and gw02 respectively.
2. Point a dial plan to both gw01 and gw02 as tandem failover
3. Bring down gw01
4. Call a user and put it on hold.
5. Using line 2, call the dialplan you have created (gw01 is down so gw02 should accept the call).
6. Bring up gw01
7. Transfer the call.

Since gw01 is now online, the transferred call will go to gw01. This will fail because the call being replaces is in gw02.

This is just a manual scenario. In a real deployment, all sorts of timeouts can happen making forks failover which increases the chance that an attended transfer hits a different gw.
FixSIPCore
UW-168Allow upload of avatar from the user portalAdded an enhancement to allow users to be able to upload avatar from user portal.EnhancementUnite
UW-321In UniteWeb and Unite Lite voicemail is not sorted by dateAdded an enhancement to sort voicemail messages by date instead of by name.EnhancementUnite
SIPX-424Yealink plugin V8XEhanced the Yealink plugin with new phones, add firmware version 8 model files, and correct number of lines on T4 phones.EnhancementYealink
  • No labels