dear friends... this is my first post here and i am not a lync  guy so my sincere apologies if my question is not directly related to this forum topic...

I have a requirement from one of my client's to implement telephony system and i was thinking to implement cisco call manager but then i have been asked to do a research on Lync .. things like .

1. How can we setup lync as pabx

2. Assign extensions.

3. What kind of server or card is needed to take ISDN circuit.

4. Recording and other features..

basically as of now i need quick answers on this as can i integrate lync with PSTN/ISDN and assign SIP phone to end users and they dial out and in place of cisco call manager can lync take the charge..

I know i have asked big things here which i tough to contain in this ..but if some one can please give me idea on the above queries and from where to start digging into the s

1. A free guide to Lync Enterprise Voice: http://info.sonus.net/snet-lync-dummies

2. Extensions can be assigned from the Web control Panel or Powershell: http://blogs.technet.com/b/nexthop/archive/2011/11/30/assigning-telephone-numbers-to-lync-enterprise-voice-users.aspx

3. Lync will require a gateway if connecting to an ISDN circuit (Qualified IP-PBXs $ Gateways):  http://technet.microsoft.com/en-us/lync/gg131938.aspx

4. Conferences and Content can be recorded on demand by the Lync client but for call recording this is provided by third party add-ons like: http://www.audiocodes.com/products/smarttap-call-recording-solution-for-microsoft-unified-communications

 

• Proposed as answer by Anthony Caragol Thursday, January 02, 2014 4:17 PM
• Unproposed as answer by 'Jatin' Monday, January 06, 2014 6:35 PM

1. A free guide to Lync Enterprise Voice: http://info.sonus.net/snet-lync-dummies

2. Extensions can be assigned from the Web control Panel or Powershell: http://blogs.technet.com/b/nexthop/archive/2011/11/30/assigning-telephone-numbers-to-lync-enterprise-voice-users.aspx

3. Lync will require a gateway if connecting to an ISDN circuit (Qualified IP-PBXs $ Gateways):  http://technet.microsoft.com/en-us/lync/gg131938.aspx

4. Conferences and Content can be recorded on demand by the Lync client but for call recording this is provided by third party add-ons like: http://www.audiocodes.com/products/smarttap-call-recording-solution-for-microsoft-unified-communications

 

• Proposed as answer by Anthony Caragol Thursday, January 02, 2014 4:17 PM
• Unproposed as answer by 'Jatin' Monday, January 06, 2014 6:35 PM

For a list of Lync features poke around at: http://office.microsoft.com/en-ca/lync/lync-server-2013-features-video-conferencing-and-instant-messaging-FX103789592.aspx

To use Lync with Enterprise voice is very easy. Take a certified ISDN Gateway. I would prefer a Audiocodes GW with an ISDN Port T1 (24 channels) or several T0 (2 channels), depend on the amount of users.

As sip Phone you May use the Lync Phones or other quallified devices from Snom etc.

The cheapest way is to use the Lync client with a qualified headset.

Hi,

You can refer to the link below about Deploy Enterprise Voice:

http://technet.microsoft.com/en-us/library/gg412876.aspx

You can assign extensions with the link below:

http://ucken.blogspot.in/2011/05/enterprise-voice-best-practices-in-lync.html

You can do PSTN connectivity with the following options:

1. SIP trunks to an Internet telephony service provider (ITSP)
2. Direct SIP connections to a PSTN gateway
3. Direct SIP connections to a PBX

More details:

http://technet.microsoft.com/en-us/library/gg425749.aspx

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

Best Regards,

Eason Huang

guys very thanks for all the replies and all r really helpful ...

I need one help if some one can show me the path..

1. I am testing the setup with Lync 2013 standard. But after all the readin i am still confused about the number of server physically required.

2. Physical connection of the server to support ISDN for calling. - My client has a ISDN line but i am not sure how i will connect that line to Lync box. i need the architecture. Can some one please provide me some help

1) This depends on the features you want, if you just have internal users who just want to make calls, a single standard edition server with the collocated mediation role would suffice.  If you want remote access, you'll want a second server for the edge role.  If you want to present PowerPoint presentations in web conferences, this would be a third server.  In terms of "physically" required, these can all be virtualized.

2) As was mentioned, you'll need a gateway.  Qualified devices can be found here: http://technet.microsoft.com/en-us/lync/gg131938.aspx but a good AudioCodes Mediant 1000 would do the trick.  These can be purchased with remote implementation support, so AudioCodes staff can do all the configuration work for you.  The rest is just the Lync setup.

One final note, if those answers didn't answer the question but were helpful, make sure to click the little vote button next to them to mark them as helpful.  If they were answers in the end, make sure to mark them as

thanks Anthony.. for the good help and comments..

I am able to arrange the setup but i am not feeling very happy about the gateway things.. one is how the physical wire will connect means ... do i need a special card on Lync or its gonna b same as Cisco CUCM server with LAN port goes to router as gateway and all happens on RJ-45 and on router we have ISDN line terminating. This i understand but is there any connectivity difference for Lync .. as i am able to see many tutorials but nothing on physical connectivity.

and at last it says using Cisco as a gateway will be only limited to basic functionality only. What are your views. In cisco world we just have to configure lines on router and rest is done by call manager nothing related to voice is configured on router.. but here in Lync world i see many things getting configured on router as per above link ..and guide which is available in cisco section. What are your views as i have a cisco router to terminate router... I was expecting i could use any router but looks like i cnt. Plz a

You will not need a special card on Lync.  Lync will talk to the gateway over IP.  Basically, it will send SIP packets or encrypted SIP TLS.  This is from the IP of your mediation server to the IP of your gateway.  The gateway translates all of that and sends it through the ISDN line.  The ISDN line physically plugs into the gateway. 

Don't worry about the tutorials so much on physical connectivity because as far as Lync is concerned, you're just connecting to a SIP trunk.  The gateway is your router that translates the SIP and sends it over ISDN.  When you pick your gateway, make sure the vendor is willing to set it up for you.  AudioCodes does this with their remote implementation support. 

I've used Cisco as a router without issues.  I'm not a Cisco expert, I rely on others in my firm for that, but basically if you set up a SIP trunk to Lync, and the calls can pass to and from to the ISDN you're fine. 

You can't just use any router however, because not everyone will support TCP or TLS for Lync. 

thanks Anthony for helping me thought out...

really appreciated. as for cisco as based on your guidance i am feeling bit OK now.. but by any chace do you have the cisco config which you are using and u dont mind sharing .. i can pass my email ID you can hide/remove the confidential stuff... as i know Cisco but not Lync and for third party i am not sure if management will accept the same... so i have to stick to Cisco

and as for SIP trunk there will be no SIP trunk .. calls will be in and out on ISDN only so i need help towards that

Sorry, I do not have a Cisco config.  I generally rely on others for this as my expertise is on the Microsoft side.  For the ISDN, I'd just suggest the AudioCodes route if you don't want to use Cisco.