Jump to content


  • Posts

  • Joined

  • Last visited

comspec's Achievements


Newbie (1/14)



  1. 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"
  2. Is anyone running Raspberrypi in a live enviroment with 10 busy extensions?
  3. 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.
  4. 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] 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] 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?
  5. 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,
  6. 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.
  7. 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?
  8. 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.
  9. 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?
  10. 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?
  11. 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}
  12. 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
  13. I can reband mine via the templates, so I'm not sure why you cannot do this also?
  14. 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?
  • Create New...