Develop Bugs

Universal WM6 Voip

Hi guys.
I have Intsalled WM6 on my universal do you know how to user Voip Functions?

I wonder about that, too. I have read into the matter a bit and it seems that the test ROM might still be missing an actual sip core? As of now the today plugin just looks like a mask with nothing behind it (unless I am missing some hidden options). It would be great if I could ditch the 3rd party voip solutions as they are totally uncomfortable to use when compared to a native integration.

Me too! I'm dead keen to hook up my Universal with my asterisk PBX. Anyone know any more about the client? It appears to either be absent or just non-configurable atm?

I think it is simply a VoIP through MSN messenger? Hardly a SIP client I know...
If you have MSN Live set up the today plugin allows you to make calls through MSN Live if it is available.
So its still SJPhone for me to hook up to our asterisk server... (works with Midgets ROM BTW)

All the Reviews said that has sip function.

The MSN option would at least be something, but I also think that what was meant is real SIP support as searching through the registry reveals at least a few corresponding entries (sip port for example). My guess is that as the ROM was not finished when it got leaked that the VoIP functions were still not implemented... the reviews didn't show detailed configuration pages for this either if I recall it correctly.

if I remember correctly the msn voip client is a SIP client anyway? it just points at a microsoft sip proxy and only handles uris of other msn voip users (ie, the sip proxy doesn't route outside the msn voip client uri namespace?). I have to admit I have not used it myself tho. I may sign up for msn voip to see if the windows mobile client starts automagically working (its only a tenner or something)

Would be great if someone could test it out to confirm which version is actually true. If the MSN phone function is SIP indeed there should be ways to hack it and use our own services; but that's going into speculations a bit too much for now. I hope to hear your report

MSN SIP for VOIP
I can confirm that Microsoft MSN Messenger uses standard SIP for voice. It's one thing the M$ got right, deciding to use an open, properly implemented standard protocol.

Corp Blackberry using WM5 ?

Hi folks,
I have a T-mobile dash (WM5) with a data plan (but no blackberry plan). My new employer uses only Palm OS Treo's and Blackberries for mobile corp email - although they use Outlook for desktop corp email !
The IT guys were a little puzzled with the Windows Mobile Device ! Anyway, I was wondering if there is a way to
1) Use my T-mobile dash's data plan
2) Along with a WM5 app
3) to connect to my corp blackberry's server.
I downloaded the WM5 blackberry app but it doesn't seem to connect anywhere, nor could I figure out how to set it up. Is there a step by step guide somewhere ?
Also, is that app very similar to the Treo/blackberries ? Then I could simply give my dash+BB connect to the IT guys and they could configure it (if the UI etc are similar to blackberries ... they know only treos and blackberries).
On a final note, I wanted to convince the head IT tech to support WM5 Outlook 'officially'. For this I need some information on how easy, secure it is to deploy this setup. Their current exchange server is mostly inside the corp firewall, so copying the desktop outlook settings to the dash doesn't work (desktop is inside corp firewall, dash is outside).
Thanks folks
Sid

Hello Sid!
I just came from a similar scenario- here's how I resolved my issues.
To be able to support direct push in Microsoft Exchange, a patch has to be applied to the server (The patch is called "Messaging and Security Feature Pack (MSFP) for Windows Mobile 5.0"). Direct Push allows your WM device to be in constant communication with the exchange server by pinging the exchange box for any changes to that user account (email). When a new email arrives in your inbox, your phone then downloads the new message. You can also sync your contacts, calendar, etc.
Unfortunately, my company has not applied this patch yet. When I went from my blackberry to WM5 device, they were not thrilled.
Thankfully, T-Mobile offers a push service called T-Mobile MyEmail which allows you to push email from any exchange/POP3 address. It will automatically locate the server address for you, just provide it your company email address and password.
From a security stand point, Microsoft's Direct Push is the most secure. It will also allow your system admin to remotely flash your handset if happens to get lost or stolen.
If you are interested in learning more about T-Mobile's MyEmail, go to:
http://www.myemail.t-mobile.com
For more information regarding Microsoft's Direct Push Technology, check out:
http://www.microsoft.com/windowsmobile/articles/directpush.mspx
Cheers

sublevel said:
Hello Sid!
Thankfully, T-Mobile offers a push service called T-Mobile MyEmail which allows you to push email from any exchange/POP3 address. It will automatically locate the server address for you, just provide it your company email address and password.
From a security stand point, Microsoft's Direct Push is the most secure. It will also allow your system admin to remotely flash your handset if happens to get lost or stolen.
Click to expand...
Click to collapse
But my corp email isin't POP or IMAP ... its exchange and blackberry. So while its a good suggestion, it won't help my situation. (?) I tried setting up my email via the "setup my email icon" but it doesn't work.
Also, exchange is inside the firewall so only "real" computers can access it via VPN/corp ethernet. Blackberry is outside the firewall. This is why my WM5 outlook can't even reach the real outlook server. I think I have two options
1) convince them to setup Exchange to talk to mobile devices
--> I'm going to forward your link to the IT guys so they can evaluate this option - thanks!
2) make my own WM5 device look/work reasonably similar to the Treo/Blackberries they are used to configuring. Then say "please set this up like a blackberry like you normally do".
For 2) I think I have found the app (bb connect?) but don't know
2.1) how to configure it
2.2) if it's the latest version (where do I get the latest version?)
2.3) If having just the data plan is good enough or do I need the special blackberry plan for this to work.
Hope that sheds more light .... thanks folks
Sid

Stoneage
Hi,
I have the same problem, only there's no convincing my IT department to support WM5 device. It supports only BB that are company property.
I have an external outlook privately setup with push mail and an alias for my corporate email, but the it seems like the redirect and auto forward rules I've defined in my outlook are forbidden or something, since they won't forward the mails I get from my exchange account to my external account.
Any idea how to go around this?
Some outlook plugin/software that will automatically forward mails to my external account?
Thanks.

Why don't you just get a blackberry data plan added to your account and use the blackberry connect client? That is all you need, as long as IT setup an account on your BES server at work.

Not that simple
If only life was that simple.
Not everybody can get a BB in our company and the IT department will not support devices that aren't owned by the company.
So, I'm looking for the workaround.

MS Push OTA Error

I have been trying to get my 8525 to do OTA Push Mail from our corporate Exchange 2003 SP2 server here where I work. I am the admin so I have access to the Exchange server and all settings are correct on the server itself to deal with OMA.
I can use the web browser of my 8525 and actually browse to our server and view both OWA and OMA directly, but when I configure the server through Activesync it always comes back with error code 80072ee7 (server name not resolved) error.
I am running vp3g's official v3 AT&T rom, and radio 1.48 if that matters. But here's where I think my problem lies and maybe someone with more experience regarding this can correct me if I'm wrong. We are running our OWA site on a high port number above 50000. We also have the OWA site under a subdirectory of the server. When I configure the server in Activesync, I enter the servername, port number and path to the OWA site, but once AS fails and I look at the server setting I find that it has dumped any path information and only keeps the server name and port number info.
So am I correct in assuming that M$ direct push only works with a server where the OWA site exists off the root directory of the IIS server? Or can it support paths into the site?

Actually push email relies on the Microsoft-Server-Activesync web application, and has little to do with OWA/OMA. I seem to recall that specifying port numbers and/or directory paths won't work though... May I ask why you're running the Exchange web services in such an unusual manner? Are you hosting other sites in that same IIS server as well?

kltye said:
Actually push email relies on the Microsoft-Server-Activesync web application, and has little to do with OWA/OMA. I seem to recall that specifying port numbers and/or directory paths won't work though... May I ask why you're running the Exchange web services in such an unusual manner? Are you hosting other sites in that same IIS server as well?
Click to expand...
Click to collapse
Actually that's the way it was set up before I started with the company. We have outside sales people that use the site and they felt it would be slightly more secure if it wasn't sitting on port 80 like most web sites. The boss won't let me change the port number at this time.
So activesync on the 8525 won't allow a port number? I thought it would because it keeps that in the server config info it'll dump any path info, but I figured out the path was not needed after a little tweaking. I just can't do anything about the port at this time.

I'm with kltye... don't think push has much (if anything) to do with OWA/OMA. It runs over port 443 (https). I believe it actually starts on port 80 (http) then switches to 443, but I'll spare you the ugly details on that one. Only need to know that for firewall config purposes.
Drop the port # and path and see how that goes.

Codevyper said:
Actually that's the way it was set up before I started with the company. We have outside sales people that use the site and they felt it would be slightly more secure if it wasn't sitting on port 80 like most web sites. The boss won't let me change the port number at this time.
So activesync on the 8525 won't allow a port number? I thought it would because it keeps that in the server config info it'll dump any path info, but I figured out the path was not needed after a little tweaking. I just can't do anything about the port at this time.
Click to expand...
Click to collapse
Security through obscurity eh?
I'm with vp3g as well: doesn't the https site run over 443? If it doesn't, maybe you can create a new Website and use the same settings as the original Exchange-Activesync web app, but have it listen on 443 for https. Are you able (i.e. "have permission") to open up port 443 on your corporate firewall?

Just did a quick perusal of my Exchange Server... appears as though push is an extension of OMA. If you don't have a Microsoft-Server-ActiveSync virtual directory off the Default Web Site (or some site listening on ports 80 & 443), you may be hosed.

Possibly related, but do you have a trusted SSL cert installed on the server? Without that, you might have a problem connecting.

vp3G said:
Just did a quick perusal of my Exchange Server... appears as though push is an extension of OMA. If you don't have a Microsoft-Server-ActiveSync virtual directory off the Default Web Site (or some site listening on ports 80 & 443), you may be hosed.
Click to expand...
Click to collapse
Yeah that's what I figured. I have the ActiveSync virtual directory within the Default Website along with OMA, but the server is listening on ports 60000 & 443 rather than the typical port 80.
You would think there would be a registry hack for AS on the mobile device whereby you could specify a non-standard port for syncing.
TaurusBullba, to answer your question. We don't have a cert (yet) for the Exchange server. That however doesn't matter for normal http connections, only if I attempt to use port 443 as the connect point for AS. Before the year is out, we'll more than likely acquire a cert for that server as well as our http server, but at the moment. I got nothing.

Inline........
Codevyper said:
Yeah that's what I figured. I have the ActiveSync virtual directory within the Default Website along with OMA, but the server is listening on ports 60000 & 443 rather than the typical port 80.
60000 is probably the killer as I noted earlier that push starts on 80 and jumps to 443.
You would think there would be a registry hack for AS on the mobile device whereby you could specify a non-standard port for syncing.
I think it was built around 80/443 to avoid client-side firewall issues.
TaurusBullba, to answer your question. We don't have a cert (yet) for the Exchange server. That however doesn't matter for normal http connections, only if I attempt to use port 443 as the connect point for AS. Before the year is out, we'll more than likely acquire a cert for that server as well as our http server, but at the moment. I got nothing.
You can do a "self-signed" certificate (i.e., generated by Windows Server) at zero cost. Downside is that it must be exported, copied to the device and installed.
Click to expand...
Click to collapse

vp3G said:
Inline........
Click to expand...
Click to collapse
Thanks for the help everyone. We will be building a new Exchange server later this year and I'll push to throw the site back on 80 at that time. In the meantime, I'll try the self-signed cert and see if that gets me in. Thanks everyone for your help! This site is a great resource for WinMo newbies like myself. BTW vp3g... lovin your AT&T v3 ROM. Solid and no problems overall!

BTW, I don't think ActiveSync starts off with port 80 - I was running a personal Exchange server off my cable connection whose incoming port 80 is blocked and everything worked fine using only 443. Good luck with the setup!

SOLUTION - Sending email on Cingular/ATT

I looked and saw there were a number of posts on the subject of sending POP3/IMAP email via Cingular/ATT and no actual working answers. When trying to send email via the carrier's wireless connection, not WiFi or Activesync, the status line would say "looking for changes" for a long time and then an error message reported that it could not connect to a server with the current settings or something to that effect. I too had this problem and found the solution on their support boards. The outgoing server for mail must be set to "cwmx.com" in order for POP3/IMAP mail to be sent correctly. The incoming server is your normal POP3 server like you'd set it up on your desktop for Outlook etc., such as "mail.bellsouth.net" or whatever you're using. Only the outgoing server is changed. I found no need for SSL or outgoing server authentication. This solution should work on WM5 and 6, although the setup screens are different. Make sure to set this up accordingly on all your POP3/IMAP accounts.
Hope this helps and sorry if it's a repeat.

Great tip, thanks

Excellent tip. Probably belongs in the Hermes WIKI. Shortly after I got my 8525, a friendly Cingular tech support person told me about this. I use it for my personal and office e-mail accounts, and it works great.
Setup is much easier on WM6. In WM5, I had to go into the advanced settings for the outgoing server (cwmx.com) and give it the name of the real server, as well as the user name and password. You don't have to jump through that particular hoop with WM6.

Exchange Server

Long time user of windows mobile devices and long time reader of this great forum ( well nearly 2 years anyway )
I've not contributed much as I dont posses the knowledge that some of you guys have.
For those new people that come on here the only advice I would ever give is search and read, the answers are nearly always there.
Anyway on to my point.
I have just set up an exchange server ( windows small business server 2003 ) and have things syncing across the airwaves nicely.
Laptop, desktop and mobile device all saying the same thing with no duplicates poping up. ( Always seemed to be a problem when syncing between two computers, for me anyway )
Also able to use Outlook Web Access.
Set this up for myself for a couple of reasons, firstly to make sure all computers where synced properly and secondly because it was worth a challange to learn how to do it.
If there are any people out there that would like the facility that exchange server gives PM me, as i will give it a go setting it up.
You will get exchange server syncing ( calender, contacts, tasks and emails ) with desktop/laptop outlook, outlook web access and an email address that you will can use to forward existing mail to. ( sorry only way to get emails to you )
Going to open this up for a couple or more people mainly to get it working properly. ( so far no problems for myself )
If I do open it up for more a donation would be nice to help pay for the outlay of equipment and for the increase in my electric bill to keep it going.
So if anyone is interested feel free to PM me.

What do you have it running on? Looking at doing the same myself.

Just a bog standard computer, nothing special
An old MSI K8 Neo motherboard with an Athlon 64 3000 2 Gig ram
Dual 250 gig discs in raid mirror for data
and a 120gig for operating system
Windows 2003 small buisness server with R2 technologies
it was also an excuse to upgrade by desktop as well.
well chuffed with how seamlessly it works with the syncing.

do you have microsoft direct push enabled on that exchange server? I would like to do that myself, don't know if it's possible

Yes got it set up.
They call it direct push but i think it goes more along the lines of your phone keeping a link open to the exchange server then as soon as an email is recieved it gets pushed across.
From what ive seen so far i'm sure the battery life is longer now than having the phone looking at a set time period for new mail.
Easy to set up as well, especially the phone side.

thanks, is the direct push functionality included in exchange server. Is it on the install cd's? I'd like to install it for my own domain, don't want to spend lots of money on blackberry server or services.
2.edge is enabled all the time on your phone, just as with blackberry? Does your phone send data at an interval, or is it the server that sends?

You need to make sure you have SP1 or R2 Technologies version for direct push with the server software
you have to set up a user profile that has permission to you the mobile services.
Also if your on a dynamic ip address its handy to have an external service set up to keep track of any changes there. And to get the full use of the server a domain name.
on the phone side you go to activesyn, and in the menu is configure server option. configure the server and thats it done.
The phone does seem to have a data connection all the time.
While i'm at work today i will write out the steps i had to do to get it working fully.
at work now so here we go :-
1) Get a domain name www.
2) If on broadband and on a dynamic IP use the services of someone like zoneedit for redirection.
(for remote access) vpn.yourdomainname to your broadband ip address
(for mail ) mail.yourdomainname to your broadband ip address
(for web ) www.yourdomainname to either your ip address if hosting it on your server or to the ip address of your web host.
(for ftp access ) ftp.yourdomainname to either your ip address if hosting it on your server or to the ip address of your web host.
follow the other instructions on zoneedit to forward the dns server addresses to your domain name admistrator.
3) Get Windows SBS or Server 2003 SP1 With R2 Technologies
4) Load onto a PC
5) Make sure all service patches and updates are loaded.
6) Download a program for updating any changes of dynamic IP address such as DirectUpdate and set up a couple of updates to the vpn mail and ftp.yourdomainname. ( easy enough follow the instructions )
7) Go through the todo list and set up wizards on the server.
a) make sure when setting up email and internet that in the creation of a certificate you put in vpn.yourdomainname
b) also make sure when setting up user access they have privilages for mobile access
8) go into internet explorer, content menu and find the certificate you have created and export it.
9) connect your phone via activesync to a computer connected to the server network and copy over the certificate.
10) run the certifcate on the phone to install it.
11) go to activesync on the phone ( can disconnect for this bit ) and set up exchange server using the vpn.yourdomainname
12) after that it should sync
I may have missed a couple of steps in that or have done something wrong but it is all the steps i can remember and it worked for me.