comspec

I'm in the process of testing this and will update the community on my findings. One thing though, the vodia install documentation states the default login is "root" this is incorrect as the actual login details are "pi"

Is anyone running Raspberrypi in a live enviroment with 10 busy extensions?

Has anyone built a Raspberrypi and hosted the Vodia pbx software on it? I'm curious of it's performance with extenstions between 5 and 10 on busy systems. If anyone has or the guys at Vodia who have tested this, I'd like to hear your comments.

It was thanks.

I'm struggling to get my license activated on a brand new Windows Server 2012 This is a new license that's never been activated before. I've checked the logfile and notice this... [5] 19:05:24.468 GENE: License: Activate license with code ########### [5] 19:05:39.469 GENE: License: Received response 408 [0] 19:06:48.670 GENE: TCP(IPv4): Could not bind socket to port 443 on IP 0.0.0.0 [0] 19:06:48.670 GENE: Could not open TCP port 443 [0] 19:06:48.670 GENE: TCP(IPv4): Could not bind socket to port 389 on IP 0.0.0.0 [0] 19:06:48.670 GENE: Could not open TCP port 389 I've opened the ports on the firewall, tried various things in the admin/ports to no avail. A ticket was raised for this but now I'm getting desperate as the customer is screaming at me for their PBX as they have NO phones. Anyone?

Not many using uc client? I've just tried this and cannot get the client to register even by following what looks to be simple instruction on setting it up. it appears that the Server: field populates with tls:// which isnt' correct, you need to remove this and enter // IP address of your pbx. This will then connect as long as you have the other details entered correctly,

The SnomOne product is standard out of the tin stuff but I do feel let down with the lack of training material on installation and advanced configuration. Is there any intent within the framework of Vodia allow resellers training material, workships or CBT? I find myself constantly having to browse through the forums for snippets of information which isn't always relavant to the issue.

Is there a roadmap in the production to look at adding wallboard features that will allow us to sell this product the call centre market?

I don't think you fully understand what I'm saying. In the web interface it is supposed to who you the calls you have recorded (I guess with a link so you can open them) but.....it doesn't.

This was a user initiated call (I hit the record button on the handset). You say "show up in the mailbox" ?? Shouldn't that be under 'calls' then 'recordings' tab in the user interface?

Hi, I've tested call recording today and although it recorded the message from my snom 870 to the recording folder in program files/snom/snomeone/recordings it has failed to show up in the GUI when logging into the snomeone pbx under accounts/features/recorded calls. I also took at look by logging into the extension by the GUI and that also didn't show the call which was recorded. Is there a bug or a configuration change to allow this to show up for both admin and the end user?

Here are the logs when trying to make an outbound call. As you say it's almost there but until I can make an outbound call this option of failover with the Vega 50 isn't an option just yet. Your help as always is greatly appreciated. [5] 2013/07/24 12:10:15: Identify trunk (domain name match) 4 [8] 2013/07/24 12:10:15: To is <sip:##########@pbx.mydomain.com>, user 0, domain 1 [9] 2013/07/24 12:10:15: Generating hf header using {from} [9] 2013/07/24 12:10:15: Generating ht header using {to} [9] 2013/07/24 12:10:15: Generating hpai header using {trunk} [9] 2013/07/24 12:10:15: Generating hf header using {trunk} [9] 2013/07/24 12:10:15: Generating ht header using {request-uri}

I have a similar problem. I'm trying to setup a Vega 50 so that in the event of a SIP failure the customer can make inbound and outbound. Currently the Vega 50 is sending the POTS fine to the PBX, so inbound is fine when the trunk goes down. The trouble I'm having is trying to work-out how to get the PBX to dial out when the SIP Out fails. Currently I'm getting "Request Timeout". I have the following settings which may shed some light on what is wrong if you can help? Trunk A Routing Destination for incoming calls: Sends calls to... Failover behaviour: Always, except.... Request Timeout: 10 Accept Redirect: No Error message: 500 Line.... Trunk B (Vegastream) Routing Destination for incomming calls: Send all calsl to... Default account: xxx Failover Timeout: 10 Accept Redirect: No Error message..:500 line... Redirect destination.. : 0201 (this is the FXO port) Dialplan Name: Outbound Call Dialplan Pref 100 Trunk A Pattern * Service Flag unassigned Pref 300 Trunk B Pattern * Service Flag unassigned Standard Dialplan Pref 200 Trunk A Pattern * Service Flag 9am-5pm M-F

I can reband mine via the templates, so I'm not sure why you cannot do this also?

You're missing the point of what i'm trying to say here. When you open system settings then general, you are giving the options of the IVR and dialtone etc to English UK. Then you are given the option of entering the TimeZone to which if you select London the date format is shown in US not UK. From what you are saying it may not be an issue when the actual templates are rolled out but it is confusing to us who select the London TimeZone to see it is not in the UK format as it makes us wondering how can the system configure the correct TimeZone when it appears the wrong way round by this I mean it shows MMDDYY which is incorrect for the UK. This may be totally irrelevant when pushing out the templates as the templates themselves may switch the TimeZone format around to reflect UK as DDMMYY. Is the latter correct? If the templates themselves change the format to DDMMYY why does my snom870 say MMDDYY when I've selected everything UK?

Hi, I'm using Version: 5.0.10m (Win64) and notice that we cannot change the time zone format from US to UK. The difference is in the UK we use DDMMYY were in the US you guys always use MMDDYY. This I presume causes problems when provisioning the phones too as they are in US format when our customers require DDMMYY. I have a snom870 on my system and although the date doesn't worry me, it would for the more fussy customers. I know I've requested this for the Yealink handsets which I've been sent a beta copy, but is this being address under the whole system to push out the UK time zone format to 'all' handsets such as snom, yealink and such like?

Once the update has been applied to the PBX do I need to click 'open accounts for mac based provisioning' then reboot each handset? or will 're-sync the selected accounts' update the handsets with the correct details?

I'm going to be trialling a Sangoma Vega 50 soon to work alongside snom one for failover.

Thanks for trying this. The current version is 5.0.10h (CentOS32)

The pbx is remote so I cannot check just yet but this shouldn't be the issue here. When you set the timzone under 'domain' / 'general settings' to London - 7/9 09:47 indicating that you want your handsets to be provisioned using that region, date and time format, this doesn't not get pushed out to the handsets. Having to go into each handset via the webpage to change the settings is not what should happen. It maybe ok if you have 1-3 handsets but any more, then the pbx should automatically provision the settings you require. This doesn't seem to be the case.

Hi, A customer has 8 T22P Yealink handsets and each are registered fine under version 5.0.10 The trouble is that the zone time needs settings to 0 United Kindon (London) Daylight Saving Time Automatic Time format 24 Hour Date format DD-MMM-YY Where can these be added in under templates? If it needs to be added into yealink_common.text what would the correct format be for PNP to work. Obviously I don't want it to change any other settings such as names and passwords just the zone time etc as above.

Thanks for your comments and duly noted. It sounds like an seperate piece of kits is required. I now need some recomendations on PSTN Gateways that are tested and work fine with the some one software. The scope of the work is to save having to port a PSTN number into VoIP and then having to install a new PSTN landline while running ADSL over it. This obviously becomes costly to the customer and would make more sense using their existing PSTN landline and route that into the snome one pbx via a gateway. Any suggestions?

Hi, I'm looking for hardware that offers the option of using PSTN into a PBX and then uses SIP trunks for outbound traffic. or maybe using the PSTN element as failover. The PIKA WARP embedded appliance looks ideal with the addition of adding a 4 port analogue FXO card. Has anyone any experience of the PIKA WARP and more to the point, has it been setup with the snom one software?

I have setup the snomone v 5.0.10a (Win64) so that it call a hunt group then hits an extension (40). The extension under the rediction tab has incoming anonymous calls set to 'Reject Call' but it doesn't. Is there a step or procedure missing to make sure that all anonymous calls are reject? PS I would have prefered the 'ask for name' to work, but that didn't work either.

I went for the ZOTAC ZBOX ID81 running CentOS with 64Gb SSD and 2Gb RAM. Runs well with no issues.