Windows Mobile

Status
Not open for further replies.

PegasusPrint

Joined
Jan 28, 2016
Messages
3
Reaction score
0
I have been eagerly awaiting the windows 10 update for my phone so that I could install 3CX, which is advertised as 'the only IP client for windows mobile', to integrate with my existing 3CX setup.
Here's the announcement from the 3CX website:

"Yes, we’ve done it again! After popular demand from our partners and end users we have developed a 3CXPhone client for Windows Smartphone. The 3CXPhone for Windows Phone can be used on Windows 10 devices only. Just like our existing 3CXPhone clients for iOS and Android the new Windows Phone client will allow you to take your office extension with you wherever you are! Increased mobility and productivity as well as reduced phone bills are some major advantages that Windows Phone users will now have the chance to experience."

I've installed it but am very disappointed to find that it loses registration as soon as the lockscreen comes on makeing it virtually useless for receiving calls.

I would like to point out that Zoiper & Linphone both work with the lockscreen activated although they have to be the active program. Even that is be acceptable although not ideal.
Is there any improvent to the 3CX mobile client in the pipeline?
 
Yes, we also need immersive experience with sideloaded AppX!
Tablet mode gives customers the flexibility to use their device in a way that is most comfortable for them. For example, a customer might want to use their 8” tablet in “tablet mode” exclusively until they dock it to an external monitor, mouse, and keyboard. At that point the customer will exit “tablet mode” and use all their apps as traditional windows on the desktop—the same way they have in previous versions of Windows. Similarly, a user of a convertible 2-in-1 device might want enter and exit “tablet mode” as they use their device throughout the day (for example, commuting on a bus, sitting at a desk in their office), using signals from the hardware to suggest appropriate transition moments.

Code:
using Windows.UI.Xaml;
using Windows.UI.ViewManagement;

public sealed partial class MainPage : Page
{
  public MainPage()
  {
    InitializeComponent();
    // Every view gets an initial SizeChanged, so we will do all our
    // work there. This means that our view also responds to dynamic
    // changes in user interaction mode.
    Window.Current.SizeChanged += SizeChanged;
  }

  private void SizeChanged(object sender, RoutedEventArgs e)
  {
    switch(UIViewSettings.GetForCurrentView().UserInteractionMode)
    {
      case UserInteractionMode.Mouse:
        VisualStateManager.GoToState(this, "MouseLayout", true);
        break;

      case UserInteractionMode.Touch:
      default:
        VisualStateManager.GoToState(this, "TouchLayout", true);
        break;
    }
  }
}
 
We acquired the PBX in January 2017 and was easy to set it up. First on the Windows Server platform then on the Debian.
Now, part of our decision was the WP 10 support about 25% installed base is WP. In March, purchase 2 new Windows phone, could install on one phone, One months later tried to install the second phone, but the install option from the store was disabled.
Now Nick Galea mentioned development was halted because of installed base.
To my understanding, the Windows Phone 10 platform is a more business oriented and not a consumer solution, like a 3CX PBX, which I think would a reason to continue development. Consider a UWP solution.
 
Status
Not open for further replies.