Release Notes 2.1.11
From Pbxnsip Wiki
Contents |
Emergency Calling
There were a couple of adjustments regarding the emergency calling. The first change affected calling extensions that have the same number as the emergency number. For example, if there was an extension with the number 911, the PBX would call that extension instead of calling the external number 911 (assuming that 911 is on the list of emergency numbers). In the new version, the PBX will not call the extension 911, but rather use the dial plan to place an outbound call.
The second chance was in the area of hot desking. When an extension is calling from a host desk registration, the call would take the identity of the logged in account. However in an emergency call, it should rather take the identity of the device. This is because in emergency calling the location counts, not the user.
Symmetrical RTP
Trunks without an outbound proxy were causing problems if the RTP follow policy was different between the trunk and the system. A typical case was that the trunk was using strict RFC RTP routing rules, while the rest of the system was using loose RTP routing. When the call came into the system, the PBX would assume that the call comes from the trunk, and only after the authentication change that to an extension call. However, the RTP policy was set during the trunk identification step. If the trunk was using the strict RTP policy, that would lead to one-way audio if the phone came from a user agent behind NAT.
In order to solve this problem, the PBX now reset the RTP policy after identifying the account. This should avoid these tricky one-way problems with unbound trunks.
Conference
The display of the moderator pin and the user pin was mixed up in the user interface. That has been fixed now. There were also cases where the PBX would mix up domain email addresses and user email addresses when sending out the conference invitation email.
Administrator Emails
Administrator text emails got stuck in the system. For example, this affected emails that were sent when the trunk status changed.
Busy on Busy
The PBX now supports "busy on busy" when a user enters the magic keyword "busy" into the redirection target for busy.
Wakeup Calls
When the user entered the wakeup call from the web interface the PBX would not call back.
Alias Name Restore
Alias names in accounts were not restored correctly when a domain was loaded through the web interface.
MWI missing
When deleting a message from the user portal, the PBX did not update the MWI count on the phone.
Simple CDR type
The type argument in the Simple CDR (see Simple CDR Format) had a conflict between the To-header and the Type. Now the type is using 'v' instead of 't'.
Address Book Provisioning
When the PBX was generating a fixed address book for a phone, it took not only the domain address book, it included all address books in the domain. In the 2.1.11 it now only takes the domain address book and the personal address book of the user that is being provisioned.
Dial Plan Assignment During Account Creation
The parameter "Dial Plan" for the creation of an account was ignored. The workaround was to assign the dial plan later. Now the dial plan is assigned as selected during the creation of the account.
