Release Notes 2.1.6
From Pbxnsip Wiki
Contents |
Agent Group
There were several enhancements to the agent group. A new algorithm as been added to the agent selection. Callers can now be redirected after waiting for too long in the queue, this should be useful when all agents log out and go home while there are still callers in the queue. Daily emails can now show how many calls were connected to what agent and how many minutes in total an agent spend processing the queue.
Auto Attendant
The when using the pattern "start" the auto attendant now can go immediately to the dial by name directory. The auto attendant will also use the personal address book before sending a call to a specific extension to set the display name for the caller. The auto attendant can now also have a display-name, as all other accounts.
Codecs
The codec preference can now also be set on per-extension bases. Before, it was only possible for trunks and on a global level. Also, the codec negotiation is now stricter, so that codec mismatches between two call legs are less probable.
Recording
Directories for recordings can now be created on the fly, so that it is now possible to sort recordings for example by day. Also, there is a domain default for recording, so that the domain administrator can generally recording on and off and set only the exceptions per extension.
License
There is a new license setting that may limit the call duration. This setting may be used for demo keys that do not expire. Also, it is now possible to use the dongle in Debian 4.0, SuSE and RedHat Linux images.
CDR
There is a new setting that sends a personal CDR email after each call with the extension. Also, there was a problem showing the right caller-ID after a attended transfer in the CDR.
New Settings
There is a new setting that makes it possible to change several previously hard coded values. Those values include the maximum length for CDR emails, DTMF gain. The maximum length is now also used in showing the address book; this avoids memory problems when customers load large address books into the system.
Trunks
The trunks can now propose a expiry value. Although this value is not binding according to the SIP RFC, many registrars got "fooled" by the proposed one hour and did not refresh the binding fast enough.
NTP
NTP continued to be a problem in the appliance. Therefore we made the NTP server available from the web interface and changed the startup script, so that setting is used. This makes it possible to use a different NTP server and there is no need for DNS.
TAPI
When using the TAPI, the user does not have to press "1" to connect the call any more.
Backup Link
The backup does nit include the tftp and cdr directory any more. There were too many operational problems with this as a lot of installations have huge amount of data in these directories.
SIP Issues
There were devices that would use hold patterns outside the m-line. Surprisingly, that is legal and has been changed also on the PBX. SIP responses are no longer sent when the underlying connection has been closed already. Registration timeout jitter now so that the registration refresh spreads out much more easily.
Microsoft Interop
By using the Outlook Play On Phone feature the user typically calls his own phone number. In the previous versions, that was hard coded to go the account's mailbox. The result was a voicemail record back to Exchange 2007 UM server. Play On Phone to a other external or internal numbers did not have the problem.
In the new version, there is a settings that turns this behavior off ("Calling own extension number goes to mailbox" in the system admin settings).
Also, there was a problem when initiating calls from Microsoft Office Communications Server 2007 (Mediation) where the PBX would present the caller-ID of the charged account. Now it is presenting the original caller-ID selected by OCS 2007.
Spanish
Spanish is now included in the web interface as the third maintained version (thanks to Maribel!).
2.1.6.2450
2.1.6.2450 fixes a problem with SIP devices that respond very slowly to INVITE requests. If the duration was longer than 3.5 seconds, then the PBX treated the transaction as terminated, and did not send out a CANCEL request to those devices (see RFC3261). Also, there was a file missing in the internal file system that was necessary for sending ACD reports.
