FindMe calling Lync URI

[Edward Northcott]

Hi all,

I have Lync setup with FindMe where the FindMe ID is the same as the Lync URI however as soon as FindMe is enabled on the VCS the calsl do not route to Lync anymore.

In the TMSPE deployment guide it states the the following: "To associate video endpoints and Lync devices, the Cisco VCS's B2BUA for OCS/Lync devices should be enabled and the FindMe ID should be made the same as the Lync URI.". This is what I have done.

To my understanding the call needs to be setup to fork, so it will call the FindMe ID at the same time as calling the Lync URI using a CPL script. Is this correct, if so is there an example on what the script shoud look like?

Thanks

Edward

[Zac Colton]

This can be done without CPL, and the design could get a bit complicated. I ran across the same thing in my lab, and what I did was created a FindMe device teplate with a bogus SIP domain that I use just for call routing to Lync.

Example:

My FindMe domain (also my Lync SIp Domain): zacolton.local

Device template to identify Lync device: {username}@lync.zacolton.local

search rule pointing to B2BUA removes "lync" from the SIP URI and then only sends username@zacolton.local

Call flow:

Dialed SIP URI : zacolton@zacolton.local

It hits FindMe and forks:

zacolton.movi@zacolton.local

zacolton.jabbertablet@zacolton.local

zacolton@lync.zacolton.local

Stop search rule matches: (.+)@lync\.zacolton\.local(:.*|;.*|)

And replaces: \1@zacolton\.local\2

Search Rule Target: B2BUA