Bug fix release update: sipXecs 4.4.0 update #17

[Douglas Hubler]

Update #17 : Tue, 10, Jul 2012
==============================================================
- ** No security updates in this update **
- ISO has *not* been rebuilt as decided in release policy. Yum update
after installation is recommended for getting these updates.
- There were numberous commits and reverts regarding MOH not mentioned here
ending in commit aac6d (or tag build017)
- Thank you all for your continued testing and fixes.
- Full change log here
http://download.sipfoundry.org/pub/sipXecs/ChangeLog-4.4.0

Build Log
======================

commit 4493f62d169e601affeeab06c2b68e86542aa745
Author: Eda Ercan <***@karel.com.tr>
Date: Wed Jun 6 16:52:06 2012 +0300

XX-10219 Add missing parameters (DID, Office mail stop) export to csv file

commit 37f8ce8d438fa26b652a86b51f366b8132dfb1ff
Author: Eda Ercan <***@karel.com.tr>
Date: Mon Jun 18 14:36:03 2012 +0300

XX-10220 Forwarding voicemail results in email message in wrong language

commit 35fb37c21d386e80823981c66537c52329e879c3
Author: George Niculae <***@ezuce.com>
Date: Fri Jun 22 11:09:19 2012 +0300

XX-10213: In Park feature "Allow Transfer" is not working and
causing park service to shutdown

commit f7cc80e96be84bd7002ae61d0bce86dbe71e9e11
Author: Mircea Carasel <***@ezuce.com>
Date: Wed Jun 13 11:23:48 2012 +0300

XX-10130: Multi domain LDAP authentication and user import support

- implement multiple ldap connection configuration
- implement LDAP authentication across multiple ldap instances
- implement import scheduling for each ldap instance separately
- fixed, improved tests
- added domain field in LDAP configuration page
- added domain setting in edit user page
- pick ldap authenticator that belongs to user domain
- parsing mechanism of login ***@domain domain\user entries
- fix ldap import to be able to corectly save aliases
- if alias collision, do not save alias for that user, show
warning in status page, log warning
- fixed/improved tests

commit d94b37e15a8172f22fc68eae05a56c93bb32dbcf
Author: George Niculae <***@ezuce.com>
Date: Fri Jun 8 10:22:00 2012 +0300

XX-10187: config to allow SIPX_SEND_ALL_CONTACTS

- added new option for registrar service ui (default to false so
current beahavior is preserved)
- read option in SipRegistrarServer and if enable send all active
contacts in REGISTER final response

commit a097d4179ea5c2e0ed64a3ca59f5526e93f93f4f
Author: George Niculae <***@ezuce.com>
Date: Fri Jun 1 15:40:37 2012 +0300

XX-10182: snom fkeys generation problem


commit 79f1189c947765b5c2e6d8e999e8f2583dee4275
Author: George Niculae <***@ezuce.com>
Date: Tue May 22 23:08:51 2012 +0300

Add missing dependency to CiscoPlus plugin

commit e652a2fb607044da03da163cce4f6be7b476a66f
Author: George Niculae <***@ezuce.com>
Date: Tue May 15 10:54:47 2012 +0300

CiscoPLus improvements

commit ce640819d8663d897ceaa8872ff8d420b7de536b
Author: Mircea Carasel <***@ezuce.com>
Date: Fri May 18 15:01:43 2012 +0300

XX-10158: LDAP schema parsing error

-fix regular expression that parses DESC, to stop at first ' occurence

commit 990b8e65edb4d4cd8919ea13fe8c7d7a6d29a2e3
Author: Joegen Baclor <***@ezuce.com>
Date: Thu May 17 12:51:25 2012 +0800

Removed stray cnonce variable within a private block. the global
cnonce must be used instead.

commit 5c9168459176786aa0a17c6ebe9bc4df99723716
Author: Joegen Baclor <***@ezuce.com>
Date: Tue May 8 15:47:23 2012 +0800

Introducing a new type of plugin (TransactionPlugin) that allows
modification of both request and responses. The primary goal of this
plugin is to provide a compatibility layer between sipX and
misbehaving phones by providing a means for a plugin to
modify/remove/add sip headers to ensure proper interop.

commit 53594653caba439488eb6c986789b432cb93f813
Author: Baris Yanar <***@karel.com.tr>
Date: Fri May 4 16:46:48 2012 +0300

XX-10145 sipx-chkspace script could not get the correct path for
voicemail_clean

commit 606b856cd0ee4e33310ed6ffa4173dd5385add3c
Author: Joegen Baclor <***@ezuce.com>
Date: Tue May 1 13:21:10 2012 +0800

A re-invite without a corresponding dialog can result to that
INVITE getting processed as a new INVITE. It eventually loops back to
sipXbridge because the request-uri and probably a route header is set
to point back to itself. Adding a new else block to check the dialog
state using raw access to presence of tags takes care of detecting
this scenario.

commit d280b95be32512efae3838d395fd03010b87473c
Author: Mircea Carasel <***@ezuce.com>
Date: Sun Apr 29 17:48:39 2012 +0300

XX-10128: Phones cannot be auto - provisioned when wildcard web
certificate is installed on the system

use apache HostnameVerifier instead of custom hostname verifier

commit 955363a1819bc939177a0f1070c4a35afc3db0c3
Author: Mircea Carasel <***@ezuce.com>
Date: Sun Apr 22 19:35:42 2012 +0300

XX-10128: Phones cannot be auto - provisioned when wildcard web
certificate is installed on the system

-create a custom Hostname Verifier, to validate all hosts in the
system domain

commit e8376560ba5bc043860809fdc2fdfd0397fe5114
Author: George Niculae <***@ezuce.com>
Date: Thu Apr 19 23:33:36 2012 +0300

XX-9479: Activating RTCPXR reporting on Polycom phones with PPS

- enabled qualityMonitoring section

[Claas Hilbrecht]

Hello,

just a quick question. As I mentioned here I have some trouble to get speed
dials BLF working on a VPN setup (too much bandwidth is going trough the
vpn link). Would it be possible to filter out the BLF request that show the
"ringing" information with these kind of plugin? If this is true maybe I
could create a plugin that removes the "ringing" messages that will leave
the subnet and lettings the "user is on the phone" messages alive. So I
would only loose a small part of the BLF possibilities.

Post by Douglas Hubler
Introducing a new type of plugin (TransactionPlugin) that allows
modification of both request and responses. The primary goal of this
plugin is to provide a compatibility layer between sipX and
misbehaving phones by providing a means for a plugin to
modify/remove/add sip headers to ensure proper interop.

[Joegen Baclor]

Unfortunately not. The outbound processor only allows you to modify SIP
headers but not retarget nor to drop certain messages.

Post by Claas Hilbrecht
Hello,
just a quick question. As I mentioned here I have some trouble to get speed
dials BLF working on a VPN setup (too much bandwidth is going trough the
vpn link). Would it be possible to filter out the BLF request that show the
"ringing" information with these kind of plugin? If this is true maybe I
could create a plugin that removes the "ringing" messages that will leave
the subnet and lettings the "user is on the phone" messages alive. So I
would only loose a small part of the BLF possibilities.

Post by Douglas Hubler
Introducing a new type of plugin (TransactionPlugin) that allows
modification of both request and responses. The primary goal of this
plugin is to provide a compatibility layer between sipX and
misbehaving phones by providing a means for a plugin to
modify/remove/add sip headers to ensure proper interop.

[Claas Hilbrecht]

Hello Joegen,

thanks for the quick replay.

Post by Joegen Baclor
Unfortunately not. The outbound processor only allows you to modify SIP
headers but not retarget nor to drop certain messages.

What a pitty. I thought this could be a solution to solve the bandwidth
problem. Is dropping of certain messages a further enhancement or is this
impossible at all?

[Joegen Baclor]

Post by Claas Hilbrecht
Hello Joegen,
thanks for the quick replay.

Post by Joegen Baclor
Unfortunately not. The outbound processor only allows you to modify SIP
headers but not retarget nor to drop certain messages.

What a pitty. I thought this could be a solution to solve the bandwidth
problem. Is dropping of certain messages a further enhancement or is this
impossible at all?

No this is not possible. Dropping messages on the proxy will not stop
the UA sending the request (in you case RLS) to retransmit it when it
did not get any response and would eventually result to a time out.
Giving the ability to mess around with transactions on this level is
calling for trouble.

[Nathaniel Watkins]

Are there any realistic options that would allow blf to be contained/fractured to a specific local server. For example, say customer x has two locations connected via a 5 mb link, each location has a node of an HA configuration. Make the assumption that users at location A only need to see 'status' of other users at location 'A' the same holds true for location 'B'. Would it make sense to have a phone then tied to a location (server) - which puts them in that localized 'BLF' group?

This would allow for a unified system to support multiple locations with a mediocre connection between servers. The alternative is to run multiple, separate sipXecs systems - which works fine, but is less than ideal.


-----Original Message-----
From: sipx-users-***@list.sipfoundry.org [mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Joegen Baclor
Sent: Wednesday, July 11, 2012 6:23 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Bug fix release update: sipXecs 4.4.0 update #17

Post by Claas Hilbrecht
Hello Joegen,
thanks for the quick replay.

Post by Joegen Baclor
Unfortunately not. The outbound processor only allows you to modify
SIP headers but not retarget nor to drop certain messages.

What a pitty. I thought this could be a solution to solve the
bandwidth problem. Is dropping of certain messages a further
enhancement or is this impossible at all?

No this is not possible. Dropping messages on the proxy will not stop the UA sending the request (in you case RLS) to retransmit it when it did not get any response and would eventually result to a time out.
Giving the ability to mess around with transactions on this level is calling for trouble.

_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

This message and any files transmitted with it are intended only for the individual(s) or entity named. If you are not the intended individual(s) or entity named you are hereby notified that any disclosure, copying, distribution or reliance upon its contents is strictly prohibited. If you have received this in error, please notify the sender, delete the original, and destroy all copies. Email transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Garrett County Government therefore does not accept any liability for any errors or omissions in the contents of this message, which arise as a result of email transmission.


Garrett County Government,
203 South Fourth Street, Courthouse, Oakland, Maryland 21550 www.garrettcounty.org

[Tony Graziano]

Would it be better to discuss the blf/rls standards available to see if
there is a more efficient standard for a wan environment and whether they
are functionally possible.

Post by Nathaniel Watkins
Are there any realistic options that would allow blf to be
contained/fractured to a specific local server. For example, say customer
x has two locations connected via a 5 mb link, each location has a node of
an HA configuration. Make the assumption that users at location A only
need to see 'status' of other users at location 'A' the same holds true for
location 'B'. Would it make sense to have a phone then tied to a location
(server) - which puts them in that localized 'BLF' group?
This would allow for a unified system to support multiple locations with a
mediocre connection between servers. The alternative is to run multiple,
separate sipXecs systems - which works fine, but is less than ideal.
-----Original Message-----
Sent: Wednesday, July 11, 2012 6:23 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Bug fix release update: sipXecs 4.4.0 update #17

Post by Claas Hilbrecht
Hello Joegen,
thanks for the quick replay.

Post by Joegen Baclor
Unfortunately not. The outbound processor only allows you to modify
SIP headers but not retarget nor to drop certain messages.

What a pitty. I thought this could be a solution to solve the
bandwidth problem. Is dropping of certain messages a further
enhancement or is this impossible at all?

No this is not possible. Dropping messages on the proxy will not stop the
UA sending the request (in you case RLS) to retransmit it when it did not
get any response and would eventually result to a time out.
Giving the ability to mess around with transactions on this level is calling for trouble.
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
This message and any files transmitted with it are intended only for the
individual(s) or entity named. If you are not the intended individual(s) or
entity named you are hereby notified that any disclosure, copying,
distribution or reliance upon its contents is strictly prohibited. If you
have received this in error, please notify the sender, delete the original,
and destroy all copies. Email transmissions cannot be guaranteed to be
secure or error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. Garrett County
Government therefore does not accept any liability for any errors or
omissions in the contents of this message, which arise as a result of email
transmission.
Garrett County Government,
203 South Fourth Street, Courthouse, Oakland, Maryland 21550
www.garrettcounty.org
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Claas Hilbrecht]

Post by Tony Graziano
Would it be better to discuss the blf/rls standards available to see if
there is a more efficient standard for a wan environment and whether they
are functionally possible.

+1 for this. Maybe the blf/rls request can be merged/compressed at the
server at each location and sent via wan in merged/compressed format and
expanded afterwards at the second server.

As far as I understand the specs from PolyCom the blf/rls request are
something like p2p. I can't find something that works similar and uses a
client/server approch.

Post by Tony Graziano
Are there any realistic options that would allow blf to be

[...]

Post by Tony Graziano
a mediocre connection between servers.  The alternative is to run
multiple, separate sipXecs systems - which works fine, but is less than
ideal.

Even this solution is much better than the current way. Since we discovered
that our problems are related to BLF we completely disabled BLF and this is
somewhat worse if the BLF function is a top argument to use PolyCom phones
with two sidecars ;)

[Kyle Haefner]

Joegen,

Is there any documentation on the transaction plugin? I didn't see a
Jira number.

Thanks!

Kyle

Post by Joegen Baclor
Unfortunately not. The outbound processor only allows you to modify SIP
headers but not retarget nor to drop certain messages.

Post by Claas Hilbrecht
Hello,
just a quick question. As I mentioned here I have some trouble to get speed
dials BLF working on a VPN setup (too much bandwidth is going trough the
vpn link). Would it be possible to filter out the BLF request that show the
"ringing" information with these kind of plugin? If this is true maybe I
could create a plugin that removes the "ringing" messages that will leave
the subnet and lettings the "user is on the phone" messages alive. So I
would only loose a small part of the BLF possibilities.

Post by Douglas Hubler
Introducing a new type of plugin (TransactionPlugin) that allows
modification of both request and responses. The primary goal of this
plugin is to provide a compatibility layer between sipX and
misbehaving phones by providing a means for a plugin to
modify/remove/add sip headers to ensure proper interop.

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
Kyle Haefner, M.S.
Communication Systems Programmer
Colorado State University
Fort Collins, CO
Phone: [phone]
Email: ***@colostate.edu

01010010 01100101 01100001 01101100 00100000 01101101 01100101
01101110 00100000 01110000 01110010 01101111 01100111 01110010
01100001 01101101 00100000 01101001 01101110 00100000 01100010
01101001 01101110 01100001 01110010 01111001 00101110

[Joegen Baclor]

There isn't any yet but there is already an implementation of this
plugin in 4.6. See
https://github.com/dhubler/sipXhomer/tree/master/proxy-plugin

Post by Claas Hilbrecht
Joegen,
Is there any documentation on the transaction plugin? I didn't see a
Jira number.
Thanks!
Kyle

Post by Joegen Baclor
Unfortunately not. The outbound processor only allows you to modify SIP
headers but not retarget nor to drop certain messages.

Post by Claas Hilbrecht
Hello,
just a quick question. As I mentioned here I have some trouble to get speed
dials BLF working on a VPN setup (too much bandwidth is going trough the
vpn link). Would it be possible to filter out the BLF request that show the
"ringing" information with these kind of plugin? If this is true maybe I
could create a plugin that removes the "ringing" messages that will leave
the subnet and lettings the "user is on the phone" messages alive. So I
would only loose a small part of the BLF possibilities.

Post by Douglas Hubler
Introducing a new type of plugin (TransactionPlugin) that allows
modification of both request and responses. The primary goal of this
plugin is to provide a compatibility layer between sipX and
misbehaving phones by providing a means for a plugin to
modify/remove/add sip headers to ensure proper interop.

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/