Hi Mike,
Thanks for the reply, I understand that we are looking at development work to achieve what we need. My task was first to ascertain whether sipXecs had functionality which we could use out of the box to solve our requirements. >From the information you have provided it seem we will need to do some work on these our self which we are happy to contribute back the open source community. Regards, Hiral Patel OnRelay Elizabeth House | 39 York Road, London SE1 7NQ, UK | +44 (0) 2079028138| [email protected] <mailto:[email protected]> | www.onrelay.com <http://www.onrelay.com/> | This electronic message transmission contains information from OnRelay, Ltd., that may be confidential or privileged. The information is intended solely for the recipient and use by any other party is not authorised. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information or any attachment, is prohibited. If you have received this electronic transmission in error, please notify us immediately by electronic mail ([email protected]) and delete this message, along with any attachments, from your computer. Registered in England No 04006093 | Registered Office 1st Floor, 236 Gray's Inn Road, London WC1X 8HL ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Michael Picher Sent: 01 October 2010 15:26 To: Discussion list for users of sipXecs software Cc: Bimpe Adedotun Subject: Re: [sipx-users] SipXecs survivable Branch office server Hiral, Problem 1 - First off, there is no tenanting in this system. It is not meant to be a solution for multiple companies. This has been discussed to death on this list. If you'd like tenanting functionality I'd suggest digging in and working with the development team and start coding (or contribute to development costs for this feature) because you asking for something that this system is not. I know OnRelay is developing their commercial product on top of sipXecs so I would hope that this would fit right in with OnRelay's plans for contributing back to the project. I do think that TOD tied to a user or group is a good idea because these systems are becoming more distributed... but that still does not a multi-tenant system make. Problem 2 - I think the developers are moving towards separating the config server from having to be on the same server as other services... at the moment the config server must exist on the voicemail server. Again, see comment in problem 1 regarding development assistance. Branch office solution - The present branch office solution is a means for securing gateways by a branch/location. It is basically another security layer on top of permissions (this actually started out as other security groups). Branches are not separate systems where there is a PBX at every branch or virtually separate workspaces within sipXecs... Future versions of sipXecs may move in that direction but if you are looking for full branch survivability / separate voicemail services, today you're talking about two different SIP domains with their own servers and services. Mike On Fri, Oct 1, 2010 at 7:00 AM, Hiral Patel <[email protected]> wrote: Hi Mike, Thanks for the reply, below is the detail, when reviewing the point below if you could think in terms of virtual end point which are mobile devices it will help. Problem 1: Impact of no time zone capability at the user group (tenant) level By adding a branch office server to the sipXecs cluster we can provide timezone capability per user or user group. E.g. if we have two customers who are based in two different time zones like New York and L.A we have the following issues: * With no timezone capability voicemail retrieval has the time and date of the central sipXecs cluster. So by adding a branch server which is based in L.A virtually, we hope we can configure different customers/ tenants to different timezones or branch servers. * Time of Day Routing will be based on the central server time and date setting so if we have a customer with two sites NY and L.A TOD routing will be incorrect or the end user and administrator would have to make an adjustment to the configure to work around the problem, which is considered a management overhead. * Same applies to Auto-Attendant routing based on time for tenant GDN numbers of huntgroups This is a key requirement as we aim to provide a multi-tenanted solution to customers. Problem 2: We would like to provide end users with the ability to change user specific parameters via the end user portal which must be accessible over the internet. The challenge we have is our internal infosec division have a policy that users on the internet must not have direct access to the business application i.e. sipXecs. Therefore we want to investigate the idea of using a branch off server to place in the DMZ which would provide the sipXconfig function and we would install the central sipXecs call control cluster in a trusted part of our network. Do you know if the branch office server has it own instance of sipXconfig which can be used to stratify the above requirement? Could you point me in the right direction to better understand whether branch office functionality will solve our above problems? Also if you have any other suggestion I would greatly appreciate input Regards, Hiral Patel ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Michael Picher Sent: 30 September 2010 22:53 To: Discussion list for users of sipXecs software Cc: Bimpe Adedotun Subject: Re: [sipx-users] SipXecs survivable Branch office server Hiral, I don't think the branch solution is what you think it is... At this point in time. Why don't you describe what you are trying to accomplish as an end-goal (don't just say 'get a branch server working'). Mike On Thu, Sep 30, 2010 at 12:17 PM, Hiral Patel <[email protected]> wrote: Hello, Does anyone have any information on how we install and configure the branch office server, we have been trying for one week now and have got no where. We are not able to find any documentation on the wiki, so we are a bit stuck. If anyone has configured the branch office server can you tell me how you configured the servers. Regards, Hiral Patel OnRelay Elizabeth House | 39 York Road, London SE1 7NQ, UK | +44 (0) 2079028138 | [email protected] <mailto:[email protected]> | www.onrelay.com <http://www.onrelay.com> | OnRelay in the News: OnRelay Named in Tech Media Invest Top 100 http://www.guardian.co.uk/tech-media-invest-100/top-100 This electronic message transmission contains information from OnRelay, Ltd., that may be confidential or privileged. The information is intended solely for the recipient and use by any other party is not authorised. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information or any attachment, is prohibited. If you have received this electronic transmission in error, please notify us immediately by electronic mail ([email protected]) and delete this message, along with any attachments, from your computer. Registered in England No 04006093 | Registered Office 1st Floor, 236 Gray's Inn Road, London WC1X 8HL _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- There are 10 kinds of people in this world, those who understand binary and those who don't. [email protected] blog: http://www.sipxecs.info call: sip:[email protected] <mailto:sip%[email protected]> _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- There are 10 kinds of people in this world, those who understand binary and those who don't. [email protected] blog: http://www.sipxecs.info call: sip:[email protected] <mailto:sip%[email protected]>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
