- Vladimir Toncar (Kerio)
Kerio Operator 1.1.1 has been published. This service release solves several issues with SIP providers. It also addresses a few glitches with SIP phones.
SIP provider issues:
- Up to now, Operator used Asterisk's default "User-Agent" string. This is a string in the SIP protocol which identifies the underlying SIP software. A SIP provider in the Netherlands refuses to connect clients who use the default identifier ("Asterisk PBX"). It is now possible to
change the "User-Agent" string but the value "Asterisk PBX" remains as default value for backward compatibility.
- Up to know, Operator used a maximum SIP registration interval of 140 seconds. Some SIP providers like freephonie.net require longer intervals and prefer sending keep-alive packets instead because this approach reduces CPU load on their servers. Operator 1.1.1 sets the maximum allowed interval to 1 hour.
- Added support for German SIP provider QSC. This provider uses a specific method of signalling the called telephone number. The actual called number is in the "To:" field, the INVITE header contains a shortened number that serves just as the customer ID.
- SIP provider configuration was incorrectly generated by Operator if the provider required a non-standard SIP port (i.e. other than 5060). The error was fixed.
SIP telephone issues:
- Grandstream HT286 could not register with the Asterisk version used in Operator 1.1.0 (i.e. Asterisk 1.4.41). We have backported an existing Asterisk patch for this issue.
- Auto-provisioned Polycom phones signaled a new voicemail message with a short beep repeated every 2 minutes. This sound was slightly annoying on some Polycom models, so it was disabled. The signalling only uses the MWI light now.
- Dial patterns generated for auto-provisioned Polycom phones were incorrect when there was not dial-out prefix in the dial plan.
Other bug fixes:
- When integrated with an Active Directory server, the error log sometimes contained messages about directory server communication failures after a reboot. This was caused by attempts to access the directory too soon after the boot. The bug was fixed.
- The integrated TFTP server (used by automatic provisioning) could sometimes crash when using AD integration. The crash occured when there was a race condition between an LDAP communication error and a memory de-allocation sequence.
- Corrected several small translation glitches in Czech, German, and Russian (Administration GUI)
- The administration GUI did not warn when trying to activate a user from the directory server who collided with an existing local user.
- A call loop created by incorrect fallback configuration could cause 100% CPU utilization. The new implementation prevents loops from overloading the CPU.
product development manager for Kerio Operator
[Updated on: Mon, 31 October 2011 15:11]
Kerio discussion forums are intended for open communication between forum
members and may contain information and material posted by members which may
be useful in learning about Kerio products. The discussion forums are not
intended to provide technical support for any specific product. Any
information implied or expressed in the discussion forums is that of the
posting member. Kerio is in no way responsible for the information posted in
the forums, or its accuracy. Kerio employees may participate in the
discussions, but their postings do not represent an offical position of the
company on any issues raised or discussed. Kerio reserves the right to
monitor and maintain the forums to promote free and accurate exchange of