Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LBG Lync integration

Status
Not open for further replies.

Rockza

Technical User
May 6, 2008
39
ZA
Hello and a happy new year to all.

I have installed LBG at a customer, and as far as I can figure out, I have it working correctly. From the Lync client, if I dial a number it dials the digits on the Mitel phone. And if I receive a call, I can answer on Lync and the Mitel phone will answer it. Also the presence is there on Lync.

However, the customer wants to be able to dial on Lync and have the speech path be on his USB handset. And also if answering, Lync should be able to answer and not simply lift the Mitel handset.
As far as I know, this is not what LBG does.

Would SIP trunks to the Lync server be a better option with External hot desking to the Lync extension?
That way Lync can use the Mitel as a PSTN gateway for calls and also allow a personal ring group the ability to ring both the Mitel and Lync phones?

Thanks

Ian
 
That would be my thought. The is a knowledge base article on dual forking for this which basically is using PRG and EHDU.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
The LBG to Lync integration provides an ability to control the deskphone from the Lync client.
If users want voice over their Lync client then you will require SIP trunking from the 3300 to Lync.
SIP trunking licenses + MCD 4.2 or above required
PRG with EHDU license will enable ability to talk on deskphone and/or softphone
Dual Forking is not available with the direct Lync integration (OCS 2007 R2 does still support this)
 
Thanks guys.

I appreciate the help. I have setup the LBG and it works perfectly. It is not what the customer requires. So I have begun setting up the SIP trunks.
I just cannot get it to work. I have followed the document I found on the knowledge base but am still battling. The link is established and I can call the Linc server, however they cannot call from the Linc client.
The only difference that I have to the document is the port is 5068. This is what the Lync guy asked to use.

I have setup many SIP links in the past to various vendors and never used anything but 5060. Is this correct?

Also is there a way to see if the request hits the Mitel? I have my doubts. Certainly nothing goes to a CCS trace.

Thanks in advance.

Ian
 
Rockza, its SIP so you can actually use Wireshark to trace your calls. You will need a mirror port of either the Lync or the 3300. Wireshark captures will show the messes between the two parties during call setup and the is a "ladder" feature in wireshark allows you to get a diagram of the interaction between the two products. If you have access to MOl and training Mitel did a webinar they recorded with a discussion of SIP. Is shows a bit on using wireshark with SIP.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Got it working. The issue was on the Lync side.
Thanks LoopyLou I have access to MOL and wireshark but most of this has been set up remotely. I am comfortable with SIP and have a pretty good feeling for where the issue lies. Next stage would have been a wireshark trace on site.

Wrt training, we battle a bit down here. Not very many courses so most things we figure out by ourselves.

Ian
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top