Mino – The UC Guy

Microsoft Unified Communications Blog

Posts Tagged ‘Enterprise voice’

How to enable inbound fax for OCS 2007 Enterprise Voice and Exchange 2007 UM enabled users?

Posted by Mino on March 9, 2009

Any Post starting with this disclaimer means that this post was not written by me however I have liked it and added to my blog. I will also include the link to the original or Similar post to provide credit to the original author.

http://blogs.technet.com/jenstr/archive/2007/11/13/how-to-enable-inbound-fax-for-enterprise-voice-and-exchange-2007-um-enabled-ocs-2007-users.aspx

Exchange 2007 SP1 UM supports both voice mail and incoming fax to a given extension. However, if the user is both UM-enabled and enabled for Enterprise Voice using OCS 2007, incoming fax is not supported using the same extension. The reason being that OCS 2007 Mediation Server does not currently support T.38.

How is it possible to provide incoming fax support for Enterprise Voice enabled users? The answer is to use a separate extension for fax and route fax calls to this extension directly to Exchange 2007 SP1 UM outside of OCS 2007.

Let’s assume we have a company called Contoso with the environment shown below and we will use that company to explain the issue and the solution

12

The OCS 2007 environment is connected to the PBX via a SIP/PSTN gateway called PSTNOCSGWY. The PBX routes all calls to the DID range +131255xxxxx to OCS 2007. OCS 2007 is integrated with the Exchange 2007 SP1 UM server called UMSRV1. It hosts a UM Dial Plan called OcsUmDialPlan of UriType = SipName (required for OCS 2007 integration). There is a UM Mailbox Policy associated with this UM dial plan called OcsUm. Exchange 2007 SP1 UM is connected to the PBX via OCS 2007.2

The Contoso user Test User is enabled for Enterprise Voice with the DID +13125510001 and SIP URI TestUser@contoso.com. His extension is 10001. His Enterprise Voice configuration is shown below.

 

 

To be enabled for Exchange 2007 SP1 UM the administrator would issue the following Exchange Management Shell command:

Enable-UmMailbox -id TestUser -UmMailboxPolicy OcsUmPolicy -Extensions 10001 -SIPResourceIdentifier TestUser@contoso.com -Pin 1234

Test User is now enabled for Exchange 2007 SP UM, but will not be able to receive incoming fax on extension 10001 or DID +13125510001.

As indicated above the solution is to give Test User a separate extension for fax and the extension needs to be routed to Exchange 2007 SP1 UM directly without going through OCS 2007. Contoso will therefore have to create a configuration as shown below. There is a dedicated SIP/PSTN gateway for connectivity to Exchange 2007 SP1 UM. The PBX routes the DID range +131266xxxxx to this SIP/PSTN gateway. There is a new UM Dial Plan called UmDialPlan with UriType=TelExtn. There is a UM Mailbox Policy associated with this UM dial plan called Um. The UM server UMSRV1 hosts both UM Dial Plans.

The administrator now decides that Test User should have the extra extension 11001 and DID +13126611001 as the fax number.

To enable Test User to receive fax the administrator need to issue the following Exchange Management Shell command:

Set-Mailbox -id TestUser -SecondaryAddress 11001 -SecondaryDialPlan UmDialPlan

With the above configuration Test User is now able to receive fax on DID +13126611001.

3

Advertisements

Posted in AVAYA, Cisco 4.x Integration, Cisco 5.x Integration, Cisco 6.x Integration, Cisco 7.x Integration, Mediation Server, Nortel CS1000, OCS & Exchange07, OCS 2007 R2, PBX Integration, Quintum's gateways, Unified Messaging | Tagged: , , , , , , , , , , , , , , , , | 13 Comments »

Phone Numbers are not displayed for Communicator 2007 Users

Posted by Mino on October 8, 2008

we’ve had Enterprise Voice with Office Communication Server (OCS) 2007 set up for quite a while and we have been adopting the usage of it more and more as time goes on. So I told someone to call my Mobile Phone number via Communicator 2007 and they said they didn’t see my Mobile Phone number.  I definitely thought this was odd as Active Directory (AD) has me configured for Home Phone, Mobile Phone, and Business Phone.  My Mobile Phone number and my Home Phone number are the same numbers while my  Business Phone number is different.

So it will help to give you a little background on how phone numbers show up to Communicator 2007 clients in relation to how my account is configured in our production AD environment.

In Office Communicator 2007, I am going into the Options > Phones Tab.  You will see that my Work Phone, Mobile Phone, and Home Phone are all greyed out.  This is because OCS 2007 is integrated with AD.  My AD account has Work Phone, Mobile Phone, and Home Phone all set.  As stated earlier, my Mobile Phone and Home Phone are the same while my Work Phone is different.

All Work, Mobile, and Home phone numbers are visible to all contacts in an AD environment if they have either Company, Team, or Personal Access Levels which you can assign to someone by Right-Clicking this individual within your Contacts list.  Because my phone numbers are published in AD, Communicator 2007 does not provide the ability to modify the phone numbers.

For contacts not in your Active Directory environment, you have more flexibility with who sees what phone numbers.  For example, if I am federated with another organization who also has OCS 2007, those contacts are not part of our Active Directory.  Because of that, the same rules in the previous paragraph do not apply.  They do not see my Work, Mobile, and Home numbers if they have either Company, Team, or Personal Access Levels to which I associated with their contact.

Instead, these contacts go by the following Access Levels ONLY if I selected to publish my phone numbers.  As you can see, I have all three of my phone numbers set to be published.  Because of that, all federated contacts can see my phone number information if I give them the proper Access Levels to do so.  By default, all new contacts are provided Work Access Levels which means federated contacts will only be able to see your Work Phone number by default.  Again, remember, if the contact is a part of your AD environment, they will be able to see all your phone numbers if they have either Company, Team, or Personal Access Levels which they will be default.

So because my Home Phone number and my Mobile Phone number are the same but my Business Phone Number is different, if someone goes to Communicator 2007 to select a phone number to call, they will only see Home Phone number and Business Phone number.

I have verified that this works the same way in a couple of OCS 2007 environments using Communicator 2007 and I don’t see any options to change this behavior.  You would think that all three options would display or that Mobile Phone number would have preference as the display number as Home Phone number.  After all, Communicator 2007 is a business tool.  Would you rather contact someone on their Mobile Phone number or their Home Phone number?  I would say most likely the favored choice would be the former.

Posted in communicator client | Tagged: , , | 1 Comment »

How to enable inbound fax for Enterprise Voice and Exchange 2007 UM enabled OCS 2007 users?

Posted by Mino on October 7, 2008

OCS 2007 users enabled for Enterprise Voice will use Exchange 2007 SP1 Unified Messaging (UM) as the Voice Mail system. In such a configuration the users Direct Inward Dialing (DID) numbers are homed on OCS 2007 and OCS 2007 is connected to the PSTN or PBX system via a OCS 2007 Mediation Server and a SIP-PSTN gateway. How to configure integration between OCS 2007 and Exchange 2007 SP1 UM is described here.

Exchange 2007 SP1 UM supports both voice mail and incoming fax to a given extension. However, if the user is both UM-enabled and enabled for Enterprise Voice using OCS 2007, incoming fax is not supported using the same extension. The reason being that OCS 2007 Mediation Server does not currently support T.38.

How is it possible to provide incoming fax support for Enterprise Voice enabled users? The answer is to use a separate extension for fax and route fax calls to this extension directly to Exchange 2007 SP1 UM outside of OCS 2007.

Let’s assume we have a company called Contoso with the environment shown below and we will use that company to explain the issue and the solution

The OCS 2007 environment is connected to the PBX via a SIP/PSTN gateway called PSTNOCSGWY. The PBX routes all calls to the DID range +131255xxxxx to OCS 2007. OCS 2007 is integrated with the Exchange 2007 SP1 UM server called UMSRV1. It hosts a UM Dial Plan called OcsUmDialPlan of UriType = SipName (required for OCS 2007 integration). There is a UM Mailbox Policy associated with this UM dial plan called OcsUm. Exchange 2007 SP1 UM is connected to the PBX via OCS 2007

 

 

The Contoso user Test User is enabled for Enterprise Voice with the DID +13125510001 and SIP URI TestUser@contoso.com. His extension is 10001. His Enterprise Voice configuration is shown below.

To be enabled for Exchange 2007 SP1 UM the administrator would issue the following Exchange Management Shell command:

Enable-UmMailbox -id TestUser -UmMailboxPolicy OcsUmPolicy -Extensions 10001 -SIPResourceIdentifier TestUser@contoso.com -Pin 1234

 

Test User is now enabled for Exchange 2007 SP UM, but will not be able to receive incoming fax on extension 10001 or DID +13125510001.

As indicated above the solution is to give Test User a separate extension for fax and the extension needs to be routed to Exchange 2007 SP1 UM directly without going through OCS 2007. Contoso will therefore have to create a configuration as shown below.

There is a dedicated SIP/PSTN gateway for connectivity to Exchange 2007 SP1 UM. The PBX routes the DID range +131266xxxxx to this SIP/PSTN gateway. There is a new UM Dial Plan called UmDialPlan with UriType=TelExtn. There is a UM Mailbox Policy associated with this UM dial plan called Um.

The administrator now decides that Test User should have the extra extension 11001 and DID +13126611001 as the fax number.

To enable Test User to receive fax the administrator need to issue the following Exchange Management Shell command:

Set-Mailbox -id TestUser -SecondaryAddress 11001 -SecondaryDialPlan UmDialPlan

With the above configuration Test User is now able to receive fax on DID +13126611001

Posted in OCS & Exchange07 | Tagged: , , , | 1 Comment »

How to implement Enterprise Voice in a non-DID scenario?

Posted by Mino on October 7, 2008

When implementing Enterprise Voice in OCS 2007 the assumption is that each user homed on OCS will have his/her own dedicated phone number directly reachable from the PSTN, a so called Direct Inward Dialing (DID) or Direct Dial-In (DDI). It is the DID defined for the user in E.164/RFC 3966 format in the msRTCSIP-Line attribute, i.e. tel:+4544890101. Some customers might not have a DID for each user. In stead they have 1 DID for the company, i.e. the main number, and all recipients have a unique extension assigned. An Interactive Voice Response (IVR) system or a switch board operator answers the main number and redirect the calls to the recipient.

So how could you implement Enterprise Voice in such a scenario? In a non-DID scenario you will have to define the msRTCSIP-Line attribute for each user in the format tel:+<main number in E.164>;ext=<extension>, i.e. tel:+4544890101;ext=200.

When implementing this type of solution you need to make sure that your PSTN Gateway/PBX  can understand this format. Why? It needs to be able to understand the components of the string and work with them. On outgoing calls from OCS to the PBX they need to be able to extract the extension from the Calling Line Id and present only the extension to the PBX (i.e. strip “tel:+<main number in E.164>;ext=”). On  incoming calls to OCS from the PBX they need to generate the format for Calling Line Id and Called Line Id.

Posted in PBX Integration | Tagged: , , | 2 Comments »