The network is built based on Huawei VC solution, SMC2.0 and Huawei MCU in the root. MS lync infrastructure exists at the same time. VC network are include terminals both from Huawei, Cisco and soft-client from Microsoft.
The following equipment were used:
MCU9610 - V100R002C02B020SP02
SMC 2.0 - V100R002C01B017SP08
Tandberg 75MXP EDGE - F9.1 PAL
Microsoft Lync Server 2010 - Standard edition
Microsoft Lync Client 2010 - *.*.*.* .
There is a notification on Cisco EP that call cannot be set because the called subscriber not exists. The Cisco EP is unreachable from Lync side, short dial received from Lync Server.
Precondition: Huawei MCU should be correctly registered on Lync Server before implementation of conference with Lync client. The registration of MCU could be made according to Huawei VP deployment guide.
If there is a need in p2p call between Cisco EP and Lync 2010 client you can follow to the listed steps:
1. Register both lync client and Cisco terminal in SMC
2. Create an Adhoc conference and add single users to it (Cisco or Lync depend on Call direction).
You can add additional prefix for such clients. For example prefix for H.323 clients is 001 and the number of Cisco terminal is 00001. You can create the prefix 002 and use the same EP number. The conference name can comply with terminal E.164 number (it will simplify management).
3. Create an account for conference number in Active Directory and register it with Lync server 2010
4. From lync client you should call to the conference ID.
There are two ways to set emulated p2p call between lync and Cisco (when Huawei VC infrastructure used):
a) Call to Auto attendant ID of MCU and set a call with help of IVR
b) Call directly to Conference ID (registered in AD and Lync Server) from Lync client. Call to Conference ID
registered in SMC from Cisco EP
The problem of communication is based on the differences between SIP addresses resolution from H.323 end-point. Huawei SMC read SIP address which is sent from H.323 video terminals.
However, SMC is able to set conference between lync clients and Cisco clients.
The SMC ability of creating conference between different clients could lead to opportunity of p2p call emulation between Cisco EP (or other H.323 terminal) and MS lync clients.
The mentioned solution describes emulation of p2p calls between Cisco EP and Microsoft lync 2010 through Huawei VC infrastructure.
1)Emulate p2p call from H.323 terminals are unable to support direct registration on Lync Server
2)The mentioned emulation is very useful if participant want to add additional user to the conference, just need to add Conference ID to another participant.
3) The mentioned solution could be used in both directions from lync to Cisco and vice versa.
4) Reduce additional expanses for purchasing gateway for SIP-H.323 signaling
5) Maintenance of conference ID in SMC is very smooth and adjustable
1)p2p emulation of call occupy MCU resources
2)If there is a lot of H.323 terminals and Lync clients it's become hard to maintain their conference ID in SMC
To simplify management and decrease part of AD entries you can register only Auto attendant ID and set call with help of IVR.