Jump to content
Vodia PBX forum
Sign in to follow this  
grichardomi

Windows 64 Issues

Recommended Posts

Just downloaded latest windows 64 version. Have an Office10 license w/two trunks. It keeps crashing (This webpage is not available ...) when more than one phone extensions are added. Got messages while registering snom or asstra phone.

Share this post


Link to post
Share on other sites

most often this is due to http or other ports already being used by windows/linux.

Any chance http port being used by windows?

 

snom:It sure would be nice if this error would be either logged in windows event log or or message pop up when snom ONe/pbxnsip starting. Even better would be to detect on install.

Share this post


Link to post
Share on other sites

most often this is due to http or other ports already being used by windows/linux.

Any chance http port being used by windows?

 

snom:It sure would be nice if this error would be either logged in windows event log or or message pop up when snom ONe/pbxnsip starting. Even better would be to detect on install.

 

 

It's most likely a port conflict. This must be a win64 only issue, cause I've not had this problem on other win32's. Any idea on how to resolve this?

Share this post


Link to post
Share on other sites

Looks like pbx is LISTENING on port 80 - how do i get around this problem?

 

 

i'm about to give up on pbx win64. is it possible to install win32 on windows 64 bit. if so what are the tricks?

Share this post


Link to post
Share on other sites

yes, you can run 32b snom one on 64b o/s.

 

i'm convinced it's a win64 hardware issue - experiencing same with 32bit software version. or at the very least the pbx software should have made necessary hardware settings during installation. i'm running a remote virtual 2008 r2 server. any ideas anyone?

Share this post


Link to post
Share on other sites

okay just to make sure: are you trying to run tapi driver or snom ONE itself?

(i wasn't paying attention to what group this question was in and that you might be trying to run tapi driver--i was thinking snom ONE app earlier.;-)

 

I know there are issues with running the tapi driver on a 64bit system.

I'm not aware of any issues run 32bit snom ONE on 64bit Windows7 for example.

Share this post


Link to post
Share on other sites

okay just to make sure: are you trying to run tapi driver or snom ONE itself?

(i wasn't paying attention to what group this question was in and that you might be trying to run tapi driver--i was thinking snom ONE app earlier.;-)

 

I know there are issues with running the tapi driver on a 64bit system.

I'm not aware of any issues run 32bit snom ONE on 64bit Windows7 for example.

 

thanks for the follow-up. i dont know what "tapi driver" is. i'm simply an end user, not too technical, trying to install pbxnsip unto a window 2008 64 bit machine. as mentioned, i've installed this software successfully on 32 bit hardware. i'm baffled and stunned of lack of software stability on win 64. for example, i can successfully register one phone, come back 1 hour later and the site become unavailable or crashed. Then without any changes, it comes back to life 4 hours later. i'm sure someone had some success tweaking it, requiring more than just an automated installation.

Share this post


Link to post
Share on other sites

thanks for the follow-up. i dont know what "tapi driver" is. i'm simply an end user, not too technical, trying to install pbxnsip unto a window 2008 64 bit machine. as mentioned, i've installed this software successfully on 32 bit hardware. i'm baffled and stunned of lack of software stability on win 64. for example, i can successfully register one phone, come back 1 hour later and the site become unavailable or crashed. Then without any changes, it comes back to life 4 hours later. i'm sure someone had some success tweaking it, requiring more than just an automated installation.

 

Without really know what else is running on your system, here are some inputs(mattlandis already covered some)

- If it is a port issue, depending on the version you are using, there should be a pbx_startup_err.txt file created under the PBX working directory. If you do not see this file, either you are running a version that does not generate this file or there is no error. Please upgrade to http://pbxnsip.com/snomone/beta/win64/pbxctrl-2011-4.2.0.3969.exe. If there was any port issue this version will create the error file

 

- If you can register a phone, that means the PBX is running. So you probably can ignore the above suggestion. Now, make sure that any other program is not interfering with the PBX (some scheduled task killing the program)

 

- Make sure that there is no attack and PBX is not adding your system/network to the "access list". Based on "...it comes back to life 4 hours later", this seems to be the case.

 

FYI...there are folks running the PBX on 64-bit windows servers.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...