#Cisco cucm 8.6 end of support full#
In the debugs the very first invite I see is already normalized to the E.164 full notation and therefore this call works. In the first call I successfully dialed extension 645 from a Lync IM client. I just did two test calls and am analyzing the debugs.
#Cisco cucm 8.6 end of support how to#
I am just not sure how to accomplish this.įrom the Cisco side I have tried forwarding just the extension exactly as you have shown right there both with and without the + sign, however the normalization rule is not applying. I agree with your assessment that a normalization rule on the Lync side to convert extensions to full E.164 would solve this for me. Hi Tarzanboy and thanks for your response. I was thinking of trying a workaround on the CUCM side within the route pattern, but Cisco wont accept a semi-colon for the transformation either.ĭoes anyone on here have any experience with Lync voice and Cisco CUCM? Or any SIP trunk with Lync for that matter along with no-DIDs? Any thoughts for how to proceed from here? Rules) so I am unable to accomplish this in the way I was hoping. I thought the Called Number Translation Rule section on the trunk configuration would be the perfect place to transform the number into the full notation Lync is expecting but it won't take a semi-colon for the input field here (unlike the normalization Here as well but the normalization rule I configured within the dial plan does not seem to work for incoming SIP connections (I guess it only works for numbers dialed from within Lync?)
In order for extension dialing to work between our end users within Lync, it was necessary to create a Normalization rule as described in this article A translation like this is what I think is necessary Our CallManager is just forwarding the dialed extension Lync seems to be getting stuck and dropping the call. Uses an E.164 number format and expects the numbers to be in full notation like this for extensions: tel:+60383830160 ext=123. I created a separate test extension range to use for Lync. Our company is setup without DIDs and all users have extensions. Lync is receiving this INVITE and responding with a message of User Not Found and the call is dropping. Upon analyzing the debugs, it seems that CallManager is properly sending a SIP INVITE for the extension being dialed at Lync's address. I cannot, however, manage to get calls from outside or our Cisco devices to reach the lync phones.
I have read through many of the guides several times and have reached a state where I can successfully makes calls from Lync software clients and phones between each other, out to our Cisco infastrcuture, and externally. I am doing some testing of Lync 2013 voice features and trying to setup calling between a UC 8.6 cluster and Lync.
0 kommentar(er)
