Jump to content

HostCorp

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by HostCorp

  1. my opinon is that it would be okay to stop supporting old technology...but it should be planned and communicated...just my thot...

     

    Matt

     

    I agree, if SSE2 makes a major difference, then fantastic we should do it, but there are plenty of reliable older boxes around so its tough to wipe them all out for the sake of a few more calls per box.

     

    A great option would be for SSE(PIII+) or SSE2(P4+) to be admin selectable in preferences, This way upgrading an older server to a newer platform would be pretty painless. With the default being SSE for compatibility.

     

    Testing build 3430 now, thank you!

     

    Cheers,

    Marcus.

  2. Same Error trying to start V4 service replacing pbxctrl.exe with V4 version

    Same error as above on full installation of V4 Beta after removing 3.4

    Test Lab Server: Dell 1650 Server - Dual P3 1.4Ghz - 4Gb RAM - 32Bit Windows Server 2003

    No services running using any common web or pbx ports

     

    V3.4 re-installs and runs fine.

  3. Thank you so much for the reply.

     

    No user complaints is a fix in my books! - I was ready to ditch the yealinks and get snoms but have just applied this now and will watch it for the day and see how we go..

     

    very excited that this may be the fix! I had looked at that jitter buffer setting and was tempted to set it to fixed but had not tried this to date.

     

    Will let you know how we go.

     

    Cheers,

    Marcus.

×
×
  • Create New...