Tuesday, 31 July 2012

Lync IP Phones Software Update

The update process for Lync IP Phones is a simple process with five (5) steps:

  1. Download the UCUpdates.zip file from MS for the required phone types
  2. Unpack the .exe file to get the .cab file
  3. Upload the phone firmware to the Lync Front End Servers
  4. Approve the update from Lync Control panel
  5. Wait for the phone to update
Step 1.
Phone firmware can be found from the MS site at: http://technet.microsoft.com/en-us/lync/gg131945

Step 2.
The downloaded file from step 1 is an .exe file, this file needs to be run to get the required .cab file.
Double click the UCUpdates.exe file
Agree to the MS Licencing Agreement
Select the location for the .cab file to be stored
Click Finish, this will now have create a file called UCUdates.cab in the required location

Step 3.
Next step is to upload the .cab file upto the web server service on the Lync Front End Servers, this step needs to be completed for all FE severs in your Lync deployment.

From the Lync Management Shell run the following command:
Import-CsDeviceUpdate -Identity service:webserver:lyncserver.FQDN -FileName "path to file just extracted"


Step 4.
From the Lync Server Control Panel, select "Cleints --> Device Update"

This will show the updates for Phones installed, approved versions of firmware and Pending versions.

Select the phone hardware type, select "Action --> Approve", this will allow ALL phone to update to the newly installed version of firmware.  

If you wish to only update selected phones for "testing" select "Clients --> Test Device", this will show a list of phones addressed via either Serial number or MAC address that the update will be available for.

Step 5.
Once a Lync IP phone has been idle for approx 10mins it will check the web service to see if any available updates are available. If updates are available the phone will start the update process.
The update process generally requires the IP Phone to reboot, if PC are network attached via the Phone they will loose connectivity.  So be careful when you approve the updates.


Tuesday, 17 July 2012

Lync Server 2013


There has been some information released overnight with a preview release of Lync 2013.  Hoping to have some time over the next few days to get it installed in my lab and see how it looks.


Some links if you are after more information.


Monday, 16 July 2012

NET UX MoH

So everyone knows by now that the Lync IP phones don't support Music on Hold (MoH), the some of the early Lync phone clients would let you place calls on hold from the Lync client on the PC and then MoH would be played from the PC.  But this seems to have been "removed" as a feature during a CU update.


From version 2.1.x of the NET UX gateway you can now have MoH played to PSTN callers when a Lync IP Phone places a call on hold.

The supported file types include:
  • PCMA
  • PCMU
  • WAV 
  • PCM
  • G726
The supported file must have a sampling rate of 8KHz and be a mono channel.

There is also a limit to the size of the file that can be uploaded. On the UX1000 the max file size is 1MB and 4MB for the UX2000.


Steps in configuring the UX for MoH include:
Upload the selected file to the DSP of the UX gateway, from the Settings tab, select "Media --> Media System Configuration" and select "Upload Music File"
Once the upload has been completed you will get the following "Upload Status"
Verify that the MoH file has been uploaded into the UX DSP's by selecting "System --> DSPs"
The next steps involve updating the signalling groups to allow for the MoH, select the SIP signalling group to the Lync Mediation server, there are three (3) options
  • Disabled
  • Always Enabled
  • Enabled for 2-Way Hold Only
MoH
Meaning
Disabled
Music is never played
Always Enabled
Music is always played for the extension placed on hold. This is one-way only
Enabled for 2-Way Hold Only
Music is only played when both parties to a call have placed the call on hold. For example, if party A and party B both place the call on hold music will be heard by whichever party takes the call off hold first, indicating that the other person has placed the call on hold.
The usual setting for this value is "Always Enabled"

Wednesday, 11 July 2012

NET UX Tone Tables - Australia

The tone tables is a PSTN gateway is used to play different tones for specific actions, tone include ring back (used when the phone is ringing), busy (used to let the caller know that the phone number is busy), now not having these set wont break anything, as far as I have seen, but it will confuse callers as they are used to getting a specific tone for these scenarios.


In the NET UX gateway, tone table are configured under "Settings --> Tone Tables"


The following table outlines the required frequency and settings:

Tone Type
Freq 1
Amp 1
Freq 2
Amp 2
Cadence Configuration
Continuous Tone
Cadence On
Cadence Off
Double Cadence
Cadence On
Cadence Off
Ringback
400
-19
450
-19
Cadence
400
200
Yes
400
2000
Dial
425
-13
450
-13
Yes
Busy
425
-24
Cadence
375
375
No
Congestion
480
-24
620
-24
Cadence
250
250
No
Call Waiting
440
-13
Cadence
300
9700
No
Disconnect
480
-24
620
-24
Cadence
250
250
No

The following screen shots show the tone tables from the UX Gateway;

Monday, 2 July 2012

Call failed due to network issue

The error message "Call failed due to network issue" can be caused from a number of different reason, the following post outlines some of the issue that I have so far found.

Monitoring Server
The first thing to check is to check the monitoring server reports for an error message.  Usually the error is some thing like "Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote"

Candidate information
Checking the  candidate information from the SIP packets during the call.  What we are looking for is that both the Edge AV Service IP address and the NAT IP address (of your home router etc) is being sent and received by the two clients.

DNS
If the candidate information is not being sent first thing to check is that the internal client can resolve the DNS host name of the Edge Server to the INTERNAL interface.  

If the DNS results returned don't match the IP address of the internal check DNS to make sure that a error hasn't been made with a static entry and check that the Internet facing NIC's in the edge server.  If there are dynamic entries in the DNS check that the "Register this connection's address in DNS" 

From the NIC properties select "Internet protocol Version 4 (TCP/IP)

Select Advanced

Select the DNS tab, then un-tick the "Register this connection's address in DNS"

Firewall:
The Media Relay Authentication Service (MRAS) is responsible for notifying the Lync client of the STUN and TURN IP address for ICE.  This service run on UDP port 3478.

To check that the UDP port is open on the firewall between the Internal Lync clients and the Edge server running this service you can use the Microsoft tool PortQry


Lync Client Policy
There is a Lync client policy setting called "DisableICE", from Technet the DisableICE value is described as "When set to True, Lync 2010 will not use the Interactive Connectivity Establishment (ICE) protocol to traverse firewalls and network address translation (NAT) devices; this effectively prevents users from making Lync 2010 calls across the Internet. When set to False, Lync 2010 will use the ICE protocol to enable Lync 2010 calls to traverse firewalls and (NAT) devices."  If this has been set to TRUE then the Lync Client wont communicate with the MRAS service.