Release Notes 2.0.2
From Pbxnsip Wiki
Calls between domains
It was already possible to make calls between domains using the tel: alias. However, it was not very clear in which domain these calls were supposed to be. We also added a feature that may change the headers, so that an assistant can see by the From/To-headers from which domain the call comes. The domain may now have a descriptive name that is used in these cases.
Camp-On on Timeout
The auto attendant was not offering a callback when nobody answered the call. This has been added now. When call times out, the PBX may offer this in addition to going to the mailbox.
Empty Feature Codes
When feature codes were left empty, this could cause quite a confusion. Therefore, we did a code review regarding this problem and found several places where this could cause an issue.
Dangling Calls for Click-to-Dial
When using click to dial, the PBX could have orphan calls that never get deleted from the internal database. The result could be that there are no more calls possible on the PBX. The calls did not appear in the active call list; however they were visible in the SNMP calls sensor.
Jitter-Buffer
When the jitter on one side of the call was too big, the PBX did not try to make it shorter later. The result was that the jitter buffer could grow, but now shrink in a call. Now the PBX tries to make the jitter buffer smaller if there was no under run during this period. This behavior can still be turned off if it should have a negative impact.
DoS on TCP/TLS
The PBX now limits the number of TCP and TLS connections that can be opened per second. This makes sure that the PBX does not get overloaded. The rate can be controlled by a setting.
Bulk Creation of Extensions
When several extensions were created at the same time, they were only saved if at least one setting was changed later. For example, if the extension had a password set, it was working ok. But if there was not a single setting set, the PBX did not commit those changes to the file system. The result was that after a restart, those extensions disappeared. The case was probably rare in most installations, however very surprising when it occurred.
There was another bug which did not allow to set the tel: alias of an account again.
Microsoft Exchange Integration
Microsoft Exchange is able to send REFER on the trunk. However, the PBX did generally not accept transfers that come from a trunk. This is not possible. In order to avoid security issues with regular trunks, that behavior is only enabled if the “accept redirection” flag is set for that trunk. Now this new feature makes it possible to dial number from Microsoft Exchange, for example call someone back.
There was a bug that treated 4xx codes like redirect codes if the trunk was to accept redirects. Now the PBX only accepts those contacts if in 3xx code classes.
CDR generation
There was a bug in the XML serialization for CDRs. The CDR generation for calls that were generated from the calling card account type was buggy.
The HTTP client could hang if there is a problem with the DNS resolution of the target.
Language for New Domain
The language for a new domain was set to the first available language, which was causing some annoyances. Now the system chooses the default system language.
Account Status Indication, Call Pickup
The account status indication was not working correct if the account was a CO-line. The subsystem was reviewed again. Call pickup from LED keys seems to be more stable now.
The same problem existed for call pickup. While undirected pickup was working, directed call pickup was not very stable. The subsystem logic has been changed to meet customer’s typical expectations.
Thread Priority in Linux
In Linux systems, the thread priority was not set the right way. In systems that are loaded heavily, that did have a negative impact on the RTP play out. It seems to be much better now; however on some embedded systems it is still a problem.
Presence Lists
The support for presence lists was missing and has been added. Now user agents can subscribe to a list of buddies.
Via Header without Port
If the Via header had no port and rport was not used, the PBX would send the response to the wrong port.
UDP Problems
It seems that Windows under some unknown circumstances is able to cancel a UDP packet although the IP subsystem already indicated that it has been received. This could cause temporarily starvation problems. In order to avoid those problems, the PBX now explicitly tells the system not to wait for a packet.
