Coen

Hi Jan, Thanks for repleying, you are the first! I guess my problem has been solved today, but I don't know how I did it. I had some spare time to begin with the R2 upgrade. So I started with the R2 AD prepareation. When starting the Schema Prep, I found out Microsoft has changed their recommendations about storing the Global Settings. So first I migrated the Global Settings from the System Container to the Configuration Container. After migrating the Global Settings I prepared my Active Directory. No problems at all. So the only steps I've been taken today is migrating the Global Settings en preparing my AD. I will upgrade my OCS Standard Pool later this week. The strange thing now is that I'm able to connect to the edge server without any problems. So maybe there was a glidge in my Active Directory. If you have a technical explanation for this behavoir please let me know. I'm clueless. Thanks for your help anyway. Greetings, Coen My blog: www.digitalfreakz.nl

Hi All, I know this problem has nothing todo with PBXNSIP or the integration of the product, but maybe an somebody (a OCS specialist) can help me with a problem. I'm working on a OCS test setup. I started with a simple setup containing a Exchange 2007 and a OCS 2007 standard edition server. This all works great, without any problems! Communicator client starts without any error and is function correctly. The last two weeks I was trying to extent this setup with external access. Deploying a CWA server was not so hard. I published CWA using a ISA 2006 SP1 server. After that I did publish OWA and Outlook Anywhere + Autodiscover. So far no problems at all. My latest goal is to implement an OCS Edge server. To begin simple I decided to use OCS Edge only for IM and not for Web Conferencing and/or A/V. A/V is currently no option for me, because of the IP requirements (2 routable public IP addresses). After reading some whitepapers and a lot of blogs I ended up with a working situation. I'm able to connect my Outlook 2007 fat client over the internet (HTTPS) with my Exchange server. Also Autodiscovery (externally and internally) works fine. Because I'm using a wildcard certificate (created by my own CA) I had to make some modifications to my Exchange server. See URL: http://www.pro-exchange.be/modules.php?nam...cle&sid=898 So everything works??? No, there is one thing that gives me a headache. The communicator client is able to connect over the internet but, always gives a outlook integration error. This error appears only when I connect over the internet. Internally I have no errors at al. Because of this error, the communicator client is not able to read my calendar information. So my presence info is not changing when I'm in a meeting. I know the communicator client uses the autodiscover part of exchange, but is seems not to work over the internet. Can somebody helps me out or points me in the right direction. Greeting, Coen

FYI: After installing the latest versie (3.1.0.3043), the translation to the e.164 works! When calling from a pstn line to my pbxnsip setup the call is translated to the e.164 format. OCS is now able to do a reverse number lookup and showing the correct contact name. I'm happy

I've tried to use the Outbound proxy IP address instead of the DNS name, but the problem persist. My PBXnSIP server is connected to the internet by using a NAT router. The PBXnSIP server is reachable form the internet on TCP and UDP port 5060. The PBX sends out a REGISTER package.

Okee, keep me informed . Thanks for your help so far.

I have some issues with my trunks. I've got two trunks, one is setup for VOIP Buster and the other one for Budget Phone (Dutch VOIP provider). When I click on the register link, the trunk seems to register without any problems. I see the status "200 OK (Refresh interval 20 seconds)". Everything works normally, I can call in- and outside. But after some seconds the trunk status change to "408 Request Timeout (Registration failed, retry after 60 seconds)". Why is this happening?? Greetings, Coen

I like to know if the OCS R2 Mediation server will support T.38 fax protocol. Right now it is only possible to receive faxes if you create multiple dialplans in Exchange UM

I have installed the lasted 3.1 build. After that I've configured the trunk settings (Rewrite global numbers: "+" style). And also change the country code to 31 in the domain settings. But it didn't solve my problem. Inbound call are still in the wrong format. (0351234567 instead of +31351234567) Do I need to change the trunk settings of my VOIP provider or the one to the OCS mediation server?

Great! I'm running Windows Server 2003 (32bit)

I'm having some trouble to translate incoming calls to the e.164 format. My PBXnSIP installation is connect to OCS 2007 server with a mediation server in between. I've created a PBXnSIP trunk to a Dutch VOIP provider (Budget Phone). The trunk is configured to forward all the calls to a user extension. (Send call to extension: 600). When I call my Budget Phone number from a PSTN phone the trunk will accept the call and forward it to extension 600. My communicator client will ring and is show the caller-id of the incoming phone call. This displayed number is not compatible with the e.164 standard. With means OCS is unable to do a reverse number lookup in AD or Outlook. Can somebody tell me how to translate incoming calls to a e.164 standard before they are forwarded to OCS?? Greeting, Coen

Thanks for all the tips. I finally got my UM voicemail intergration working. I did follow the "Configure Exchange UM to Work with Communications Server" guide, but there where some issues. After some reading I did found out that my UM dialplan didn't matched the location profile name. After fixing the names and running the "OcsUMUtil.exe" util again, the integration was succesfull. In PBXnSIP I changed the mailbox setting "Mailbox Enabled:" to "No", now everything works! Greetings, Coen

Rightnow this field is still empty. I guess this field needs to be filled with a extension. Can you give me some help?

I've succesfully installed a test-setup which contains pbxnsip, ocs 2007 and exchange 2007. The guide (http://wiki.pbxnsip.com/index.php/Office_Communications_Server) was very usefull. I'm able to call from one pbxnsip extension to another pbxnsip extension. The call will also be forked to the ocs extension. Now I like to use Exchange UM as the voicemail system. But when I call a extension and let it ring I won't get Exchange 2007 as a voicemail system. Exchange UM voicemail works when I call from communicator to a ocs extension. Is there anybody how can help me? Greets, Coen