LYNC Protocols and Ports app is now available for download from the WP7 Marketplace. If you prefer Zune, then directly go here

Why this app?

1. LYNC is still a new product
2. I have identified 225 possible communication links in the LYNC environment (15 x
   15). For example, FE to internal edge, external client to external edge etc

What am I attempting?

I am attempting to

1. Bring down the time involved in designing LYNC architecture and deployment by having
   a quick reference app 
2. clear out any doubts or issues that are arising from wrong protocol or port being
   configured or not allowed in the firewall rules.
3. Spread the knowledge.

Known UI issues? To be fixed in next update

The selection (area and font) for source and destination is
too small

Known limitations? To be fixed in next update

• Port 5065 and 5067 not shown for FE to UM
• Port 8404 for RGS match-making not shown between
  the FE to FE.

Special Thanks

Thanks Rui Maximo, Rick Kingslan for the direct feedback with using the app.

Thanks,

Kaushal Mehta

I am working on this to make the output more readable so expect more updates to this blog. For now, the following command returns the current inbound calls to LYNC Mediation server.

PS C:\Users\administrator.contoso> Get-Counter -Counter "\LS:MediationServer - 01 - inbound Calls(_total)\- 000 - Current" -Continuous

Timestamp                 CounterSamples
---------                 --------------
7/7/2011 6:47:30 PM       \\lyncfe\ls:mediationserver - 01 - inbound calls(_total)\- 000 - current :                         5

7/7/2011 6:47:37 PM       \\lyncfe\ls:mediationserver - 01 - inbound calls(_total)\- 000 - current :                         4

Make sure you have the correct settings for a new LYNC flag called EnableReferSupport.

Figure 1: Flowchart to decide on EnableReferSupport flag requirement

Please visit https://technet.microsoft.com/en-us/library/gg413021.aspx for more information on the powershell commands

Visit https://technet.microsoft.com/en-us/lync/gg131938.aspx for LYNC Interop Partners

To troubleshoot 2007 Exchange UM fax issues,

1. always check with the Exchange/Voice administrator on the fax tone detection method they use.
2. collect a netmon/wireshark trace and filter it for SIP protocol. Verify the SIP INVITEs, Re-INVITES, 200OK, ACK as appropriate for the call flow
3. Filter on rfc2833 if the UM is expected to receive out-of-band RFC2833 packets. Of note, RFC2833 is used for sending the DTMF as well
4. Filter on t.38 and verify the direction of t.38 packets.

 As per https://technet.microsoft.com/en-us/library/bb691398(EXCHG.80).aspx 

Inband fax tone detection   Fax tone detection enables an IP gateway, an IP PBX, or Exchange Unified Messaging to determine the type of incoming call that is being received. Fax tone detection can work in the following three ways:

• The IP PBX or IP gateway detects the fax tone and sends a reinvite request by using T.38 Session Description Protocol (SDP).   --> This method should continue to work after the Service Pack upgrade
  
• Fax tone detection can be performed by using both an IP PBX or IP gateway and Unified Messaging. In this method, when the IP gateway or IP PBX detects the fax tone, it does not send a re-invite but instead sends CNG tones (out of band) as named telephony events as defined in RFC 2833. As soon as the IP PBX or IP gateway has sent the CNG tones, the Unified Messaging server performs out-of-band fax tone detection and sends a reinvite by using T.38 SDP.   --> This method should continue to work as well after the Service Pack upgrade
  
  
• If the IP PBX or IP gateway does not use either of these methods, Unified Messaging inband fax tone detection should be turned on. This will enable the Unified Messaging server to detect incoming inband fax tones. By default, this feature is turned off. However, it can be enabled in environments that use IP PBXs or IP gateways that cannot detect fax tones. You enable inband fax tone detection by changing the EnableInbandFaxDetection setting to True in the globcfg.xml file. The globcfg.xml file is located in the \Program Files\Microsoft\Exchange\bin folder on a computer that is running the Unified Messaging server role.
  

In scenarios, where fax stops working after upgrading to a newer Service Pack the issue may be with the globcfg.xml file getting overwritten. This is applicable when customer has the fax detection through EnableInbandFaxDetection flag.

Change EnableInbandFaxDetection flag to true. Save the file without changing any other file content or file properties. UM and speech services needs a restart to get the EnableInbandFaxDetection flag into effect.

There is no other special configuration on UM for fax.

If the folder is empty then the voicemail files have left the UM and on its way to the Hub Transport.

If you see voicemail audio files there it means the connection between UM and HT is broken somewhere. This can arise because of one of the following scenarios.

1. The HT receive connector is mis-configured. Check the AUTH on the receive connectors
2. Verify if you can telnet on hub transport's IP and port number 25
3. Verify if HT FQDN is resolving to the correct IP
4. Check if any anti-virus software is installed

As an example, see the following events that may come when voicemail delivery is failing.

Event IDs 1436, 1423 and 1446

- <Event xmlns="https://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="MSExchange Unified Messaging" />
  <EventID Qualifiers="49156">1446</EventID>
  <Level>2</Level>
  <Task>2</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2010-12-20T16:50:40.000000000Z" />
  <EventRecordID>252718</EventRecordID>
  <Channel>Application</Channel>
  <Computer>optimus.com</Computer>
  <Security />
  </System>
- <EventData>
  <Data>C:\Program Files\Microsoft\Exchange Server\V14\UnifiedMessaging\voicemail\1c3ebe7b-c1a4-4b31-8ef4-ebfd978a6239.txt</Data>
  <Data>23</Data>
  </EventData>
  </Event>
 
  - <Event xmlns="https://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="MSExchange Unified Messaging" />
  <EventID Qualifiers="32772">1436</EventID>
  <Level>3</Level>
  <Task>2</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2010-12-20T16:52:17.000000000Z" />
  <EventRecordID>252730</EventRecordID>
  <Channel>Application</Channel>
  <Computer>optimus.com</Computer>
  <Security />
  </System>
- <EventData>
  <Data>SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}@optimus.com</Data>
  <Data>Microsoft.Exchange.Data.Storage.FolderSaveException: An error occurred while saving the changes on the folder "vAAAAAAbVfogqmYRzZvIAKoAL8RaCQBIAFNSVjYwLUVYMS1XMks4LnctZHVidXF1ZS5rMTIuaWEudXMAL289V2VzdGVybiBEdWJ1cXVlIFNjaG9vbCBEaXN0cmljdC9vdT1FeGNoYW5nZSBBZG1pbmlzdHJhdGl2ZSBHcm91cCAoRllESUJPSEYyM1NQRExUKS9jbj1SZWNpcGllbnRzL2NuPVN5c3RlbU1haWxib3h7ZTBkYzFjMjktODkA/w==". Error details: Failed, Property: [0x3428000b] HasUMReportData, PropertyErrorCode: AccessDenied, PropertyErrorDescription: . ---> Microsoft.Exchange.Data.Storage.PropertyErrorException: Property: [0x3428000b] HasUMReportData, PropertyErrorCode: AccessDenied, PropertyErrorDescription: . at Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.FlushChanges() at Microsoft.Exchange.Data.Storage.CoreMailboxObject.Save() --- End of inner exception stack trace --- at Microsoft.Exchange.Data.Storage.MailboxStoreObject.Save() at Microsoft.Exchange.UM.UMCommon.UMReportUtil.SetMailboxExtendedProperty(MailboxSession session, Boolean hasUMReportData) at Microsoft.Exchange.UM.UMCore.CDRPipelineContext.TrySetExtendedProperty(MailboxSession mbxSession)</Data>
  </EventData>
  </Event>
 
  - <Event xmlns="https://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="MSExchange Unified Messaging" />
  <EventID Qualifiers="49156">1423</EventID>
  <Level>2</Level>
  <Task>2</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2010-12-20T16:51:59.000000000Z" />
  <EventRecordID>252729</EventRecordID>
  <Channel>Application</Channel>
  <Computer>optimus.com</Computer>
  <Security />
  </System>
- <EventData>
  <Data>C:\Program Files\Microsoft\Exchange Server\V14\UnifiedMessaging\voicemail\4d4b108e-a592-4eae-8aeb-0089baa4b537.txt</Data>
  <Data>Microsoft.Exchange.UM.UMCore.SmtpSubmissionException: Submission to the Hub Transport server failed. The operation will be retried. --->
  System.IO.IOException: Unable to read data from the transport connection:
  A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because
  connected host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at Microsoft.Exchange.Net.ExSmtpClient.SmtpSslStream.Handshake() at Microsoft.Exchange.Net.ExSmtpClient.SmtpTalk.StartTls() at Microsoft.Exchange.Net.ExSmtpClient.SmtpClient.Submit(Boolean disableDelayedAck) at Microsoft.Exchange.UM.UMCore.SmtpSubmissionHelper.SubmitMessage(MessageItem message, String senderAddress, String recipientAddress, OutboundConversionOptions submissionConversionOptions, InternalExchangeServer smtpServer) at Microsoft.Exchange.UM.UMCore.SmtpSubmissionHelper.SubmitMessage(MessageItem message, String senderAddress, String recipientAddress, OutboundConversionOptions submissionConversionOptions, String requestId) --- End of inner exception stack trace --- Server stack trace: at Microsoft.Exchange.UM.UMCore.SmtpSubmissionHelper.HandleTransientSmtpFailure(Exception e, InternalExchangeServer smtpServer, String recipientAddress) at Microsoft.Exchange.UM.UMCore.SmtpSubmissionHelper.SubmitMessage(MessageItem message, String senderAddress, String recipientAddress, OutboundConversionOptions submissionConversionOptions, String requestId) at Microsoft.Exchange.UM.UMCore.SmtpSubmitStage.InternalDoSynchronousWork() at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase) at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData) at Microsoft.Exchange.UM.UMCore.SynchronousPipelineStageBase.SynchronousWorkDelegate.EndInvoke(IAsyncResult result) at Microsoft.Exchange.UM.UMCore.SynchronousPipelineStageBase.EndSynchronousWork(IAsyncResult r)</Data>
  </EventData>
  </Event>
 

In the above example, uninstalling the anti-virus software and rebooting the UM server helped. Apparently, there were recent anti-virus definitions applied to the UM server that may cause this.

Symtoms: - 

PBX --> Dialogic --> UM 2007 --> 2007 UM user .......... --> worked
PBX --> Dialogic --> UM 2010 --> 2010 UM User .................. --> worked
PBX --> Dialogic --> UM 2010 --> 2007 UM User ............... --> Didn't work

Checks: -

1. VoIP GW (Dialogic in this case) should point to 2010 UM Server during the migration
2. The Dial-plan should have Tel URI extension configured
3. The Dial-plan should have both 2007 and 2010 UM servers attached

• Check the Event IDs to notice any failures or warnings
• Check the Dialogic DMG 2120, to see any errors in the logs
• Check if the call is logged as "user moved temp"
• Verify that the UM 2010 is correctly sending the 302 User Moved Temporarily back to Dialogic.
• The 302 Contact has to be set to 2007 UM server.
• If this is an FQDN and not IP verify if dialogic is able to handle the DNS resolution
• Go to config --> voip --> General --> DNS to publish the DNS IP
• Confirm that the DNS server has correct mappings for 2007 UM servers
• Add the DNS IP and restart the Dialogic DMG

Hope this helps during the transition of Exchange UM from 2007 to 2010 in a media GW scenario involving Dialogic (or Audiocodes).

Thanks,

Kaushal (Microsoft Escalation)

 Below is the call flow for such a scenario. Microsoft UM receives 3 ICMP Port Unreachable messages from the Media GW, an indication of media device not being ready to exchange RTP packets.

 As per the RFC3264, section 5.1 on page 7, it states:

Once the offerer has sent the offer, it MUST be prepared to receive media for any recvonly streams described by that offer.  It MUST be prepared to send and receive media for any sendrecv streams in the offer, and send media for any sendonly streams in the offer (of course, it cannot actually send until the peer provides an answer with the needed address and port information).  In the case of RTP, even though it may receive media before the answer arrives, it will not be able to send RTCP receiver reports until the answer arrives.

If there is no immediate fix available to address this from the GW end, then the admin can use "Windows Firewall with Advanced Security" from "Administrative Tools" to block the ICMP port unreachables from reaching the application. Below are the screenshots to configure this.

Give it a friendly name and the firewall should now block the specific ICMPs from going to the application.

Below is the summary for the complete conversation in the CDR DB. It helps to understand how the UserJoinTime and UserLeaveTime are reported for every MCU. The DB identifies the MCUs as Chat, AV and App Sharing.

The NULL values reported in the UserJoinTime can be ignored for OCS 2007 R2. It is addressed in the next release of OCS.

The different UserJoinTime and UserLeaveTime reported for every MCU Type gives an idea about how these can be used for calculating the billable minutes or calculating Return-On-Investment (ROI).

The following SQL query helps in generating that list.

SELECT     rtc.dbo.Contact.OwnerId, rtc.dbo.Resource.UserAtHost AS "SIP Name"
FROM         rtc.dbo.Contact
INNER JOIN rtc.dbo.Resource ON rtc.dbo.Contact.OwnerId=rtc.dbo.Resource.ResourceId
GROUP BY rtc.dbo.Contact.OwnerId, rtc.dbo.Resource.UserAtHost
HAVING      (COUNT(rtc.dbo.Contact.OwnerId) >= 2)

The output looks like below. You can customize the script to add mroe columns.