Okay I’ll admit I’ve taken a bit of a break. You know kids, 2 acquisitions, a public company oh and this new position leading the best Microsoft Practice in the world….
The content will be different than before, but will be relevant and interesting.
Talk to you all soon!
I decided to give my blog URL a more personal touch for 2015. You can now access my blog via http://blog.mcgreanor.com
The current URL cmcgreanor.wordpress.com will still be active for those of you that have it saved.
Today a colleague of mine was having an issue with ring back on calls originating from the PSTN to Lync. You would basically here dead air or if you listened close enough you could hear the “Comfort Noise”.
Background:
The PSTN connectivity is being provided by Comcast via a SIP trunk that terminates to an Adtran. From the Adtran there is a T1/ESF/B8ZS trunk to a Sonus UX 1000. The Sonus is configured to pass calls to the mediation server in Lync Server 2013.
Issue:
When a call was placed to a Lync Enterprise Voice user from the PSTN you would not hear ring back and you could hear comfort noise if you listened hard. In the UX log traces we saw the SIP 180 and 183 messages being sent and received. The issue was related to a SIP 180 being sent back to the T1 and the T1 not understanding it. T1’s view ringing as an “Alerting” message as defined in RFC 4497 Interworking between the Session Initiation Protocol (SIP) and QSIG and based on the RFC a SIP 180 should be sent as a QSIG Alerting message to support ring back:
http://tools.ietf.org/html/rfc4497#section-8.3.4
8.3.4. Receipt of QSIG ALERTING Message
The gateway SHALL map a QSIG ALERTING message to a SIP 180 (Ringing) response to the INVITE request. If the SIP INVITE request contained either a Require header or a Supported header with option tag 100rel, the gateway SHALL include in the SIP 180 response a Require header with option tag 100rel.
Resolution:
The resolution to this is to implement a “Message Translation” table and add the following rule:
This is basically stating that when a SIP 180 is received to send out a corresponding QSIG Alerting message.
Just creating this table does not address the problem. Once the table has been created you need to assign it to the Call Routing Table
Once we completed this ring back worked as it should. This seems to be related to the unique setup of the Comcast SIP trunk being terminated to the Adtran then converted to T1 back to the Sonus. If this was common we would see this a lot more in typicall configurations since it is very common to have a T1 terminate to a UX.
The San Francisco Lync User Group will be having our next meeting Thursday November 13th, 2014 from 3:00PM-6:00PM. This meeting will include two sessions, the first session will cover Lync SDN & Wi-Fi. The second session will dive into Office 365 Lync Online
Location Details:
835 Market Street
Suite 700
Golden Gate North Room
San Francisco, CA 94103
There is a parking garage right behind Market Street on 5th and Mission. BART station at Powell street and is a 2 minute walk to the Microsoft offices.
Please register on our webpage at http://www.LyncUG.com
Microsoft has released a new Cumulative Update for Lync Server 2013. Below is a consolidated list of the fixes that are included.
Download link here: http://www.microsoft.com/en-us/download/details.aspx?id=36820&WT.mc_id=rss_alldownloads_all
List of fixes included:
Update for Standard or Enterprise Edition server (Front End Servers and Edge Servers):
2976568(http://support.microsoft.com/kb/2976568/ ) Address book delta files are not generated in a Lync Server 2013 Enterprise Edition environment
2967626(http://support.microsoft.com/kb/2967626/ ) Error “creating procedure RtcResetAbAttributes” when you run “Install-CsDatabase” for rtcab database in Lync Server 2013
2967629(http://support.microsoft.com/kb/2967629/ ) Significant bandwidth usage increase by SIP traffic in a Lync Server 2013 environment
2967630(http://support.microsoft.com/kb/2967630/ ) Callee receives a missed call notification after answering a call on an IP telephone in a Lync Server 2013 environment
2979931(http://support.microsoft.com/kb/2979931/ ) Error “I can’t find the meeting with that number” when PSTN user dials in to conference in Lync Server 2013 environment
Update for Web Components server
2978444(http://support.microsoft.com/kb/2978444/ ) Update for Lync Server 2013 to disable Lync Web App users’ ability to upload and show PPT in online meetings
2976906(http://support.microsoft.com/kb/2976906/ ) Incorrect time zone is displayed when you create a meeting by using Web Scheduler in a Lync Server 2013 environment
2967623(http://support.microsoft.com/kb/2967623/ ) Error “This content cannot be displayed” or blank webpage when you click a dial-in URL in a Lync Server 2013 environment
2967624(http://support.microsoft.com/kb/2967624/ ) HD video stutters in a Lync Server 2013 based video conference in Lync 2013
2967628(http://support.microsoft.com/kb/2967628/ ) Telephone numbers are missing in a contact card in a Lync Server 2013-based Lync mobile client
Update for Core Components
2967621(http://support.microsoft.com/kb/2967621/ ) Error 404 when Lync phones sign in to Lync Server 2013 front-end servers during SBS failure recovery
2967631(http://support.microsoft.com/kb/2967631/ ) Error “”DistributionGroupAddress” and “AgentsByUri” must be set.” when you migrate the RG service to Lync Server 2013
Update for Administrative Tools
2983199(http://support.microsoft.com/kb/2983199/ ) “Limited functionality is available due to outage” in Lync client when Lync Server 2013 replication queue is full
Update for Web Conferencing server
No Specific fixes listed
Update for Windows Fabric
2983199(http://support.microsoft.com/kb/2983199/ ) “Limited functionality is available due to outage” in Lync client when Lync Server 2013 replication queue is full
I was recently working on an issue where Lync was marking a single gateway of 3 in a voice policy route as down. This customer is using 3 gateways and outbound calls are using all 3 together via round-robin routing. The only item that was unique about this particular gateway was that there is a FXS paging trunk connected to it. Our support team restarted the mediation service and saw all the necessary event log entries indicating that the gateway was back online only to see it be marked as unreachable after a period of time. The issue was escalated to me since I did the original implementation and suggested that we try testing a few things:
Issue
Cause
Resolution
In order to solve this issue I suggested that we utilize the New-CsSipResponseCodeTranslationRule Lync PowerShell command to take a 503 message and translate it to a 483 (Busy Here). By doing this we take a permanent failure like 5xx and translate that to a temporary failure that Lync does not count towards the 5 failures before a gateway is marked down.
Here is the command that was run:
New-CsSipResponseCodeTranslationRule -Identity “PstnGateway:xx-xxx-gateway1.contoso.corp/Rule503_Paging” -ReceivedResponseCode 503 -TranslatedResponseCode 483
After we implemented the command we ran several tests. We had a user connect to paging and then another user call the same trunk over and over. Lync never marked the gateway as down. We validated this by reviewing the Lync logs and seeing that we were in fact getting a 483 message back now.
Hope this helps someone!
The San Francisco Lync User Group will be having our next meeting Wednesday April 23rd, 2014 from 3:00PM-6:00PM. This meeting will include two sessions, the first session will cover the Top Ten Takeaways from Lync Conference 2014. The second session will dive into Advanced Troubleshooting Tools for Lync.
Location Details:
835 Market Street
Suite 700
Golden Gate North Room
San Francisco, CA 94103
There is a parking garage right behind Market Street on 5th and Mission. BART station at Powell street and is a 2 minute walk to the Microsoft offices.
Please register on our webpage at http://www.LyncUG.com
