Call Via Phone ADVANCED for Lync 2010 & Lync 2013 , deep review and download link

Hi all ,

As i wrote in my previous article that you can find here : CallViaPhoneAdvanced  , this plugin is developed for SNOM phone and Lync 2010/2013 and permit to control the phone with right click on a contact in Lync (Lync contacts, Outlook contacts , Active Directory contacts) and start calls directly from the phone, like CTI (Computer Telephony Integration) .

We know that in WPC 2013 , SNOM demonstrate Enhanced Better Together that could be available at the end of 2013 , in Matt Landis blogpost here , you can find a detailed description.  This new SNOM feature add a new driver in Lync that let you choose what default Audio device use for every call that you made from lync , these calls start from the phone , also when you receive a call you pick up the call from the phones and not from the client (if you have already configured  the snom audio device in Lync down- left menu ), but a good things is that you when you are in conversation , you can switch this call between Lync client and snom phone.

So what’s the difference between CallViaPhoneAdvanced and SNOM EBT ? There are more than one difference and benefits :

  • CallViaPhone Advanced doesn’t not require Lync user to have Enterprise voice for Outgoing call functionality (for example if you use snom phone connected to other vendors like asterisk, cisco ,etc.. and you use Lync with or without PBX integration )
  • When you start a call , if you want to decide call per call which phone use (snom phone or lync client) with CallViaPhoneAdvanced you can.
  • CallViaPhone Advanced allows  future customization and it’s in continuous developing  (Programming Phone keys, full interaction with any functionality available on the Phone)

Thanks to Michael LaMontagne,  a very skilled Lync Expert in Canada , i also develop the incoming call feature that let you to answer an inbound call from the phone, this simple adding another toast in left side of Lync toast with an “Answer by Phone” button, simply and immediate for user experience. But starting from this imagine how many customization we can implement :

  • when and incoming call arrive, start an external application with caller information (CRM?)
  • Busy on second call or based on presence status

In addition i want to encourage who want try the application (15 days limited) to download from link below  :

For last version please refer to this post.

if you want to learn more you can find an awesome review here made by  Michael LaMontagne.

Don’t hesitate to comment or ask information about it .

Advertisements

Call Via Phone ADVANCED for Lync

Hi all ,

I’m glad to announce the new Call Via Phone ADVANCED for Lync 2010 & Lync 2013 .

Call Via Phone Advanced application is a plug-in developed for interoperability between Microsoft Lync 2010/2013 and SNOM (but not limited to). This plug-in permits making call from your phone directly using your Lync client 2010/2013, via a simple click on a contact or a number and selecting “Call Via Phone” from Lync menu; the call will start directly from your phone without having to dial the number or search your contacts on the phone itself. The usage scenarios can be many, and the common denominator is surely to simplify and consequently save time in day by day activities.

Call Via Phone Advanced is fully integrated with Lync client, in fact after  installation you don’t need to run any additional service or application, but it’s called through a menu inside Lync client.

CallViaPhoneADV2

Below some scenarios in which Call Via Phone ADV can be used  :

  • Infrastructure Lync 2010/2013 integrated with voice, and phones connected directly to Lync .
  • Infrastructure Lync 2010/2013 not integrated with voice, and ip-phones connected to any other PBX .
  • As we know Lync 2013 and Skype are integrated also with audio, with Call Via Phone Advanced you can quickly call a skype users from Lync client and use IP-Phone insted of Lync client.

Call Via Phone Advanced installation is very simple and can be installed centrally because it’s provided with the installation package MSI (Microsoft Installer) and distributed through group policy on all clients.

The configuration of each client is due by entering IP Address of the phone to associate with, Lync extension or username, password or Lync PIN.

With “Call via Phone Advanced” you can also have the ability to handle the call (today only for SNOM phones) with various tools that allow to :

  • End Call
  • Hold call
  • Party adding
  • Transfer
  • Conference

The product is under continuous development with additional features, and on specific demand it can be also change to adapt to your enviroment.

Today Call Via Phone Advanced is available for SNOM ip-phones.

Under specific request to sales@callviaphoneapp.com , Call Via Phone Advanced can also be used in enviroment with these ip-phone vendors but not all models  :

  • Cisco
  • Polycom
  • Grandstream
  • 3CX
  • Yealink

Don’t hesitate to contact sales@callviaphoneapp.com for information and to request your evaluation copy.

If you want you can also download free-version here :

Link to : Call Via Phone freeware

Here below you can find brief functions description that you can have with freeware version :

Call Via Phone Description

PBX replacement with MS Lync (with Dual Forking) Part 2

As i mention in my last post (part 1) we can choose to use the Voice gateway in pass-through as shown here :

PBXReplacementPart2_Example_base scenario

but to do this , we have to consider various steps before moving the IP-PBX in production  and insert voice gateway between PSTN and the enviroment, so let start from the beginning,  these are necessary steps :

1.  Voice gateway configuration for PSTN trunk (only configuration not yet connected), in the other side (to lync and to PBX) configuration of SIP trunk to Lync and SIP trunk to IP-PBX (IMPORTANT : to obtain a dual forking of calls in this scenario we must use only sip trunk to and from  PBX , so we must have an IP-PBX with sip trunk enabled ).

At this step we don’t have any disservice on IP-PBX production environment but we are ready to switch PSTN from IP-PBX to Voice gateway .PBXReplacement_part2_Example_step1

2.  We can schedule session tests to verify that all configuration made before work    fine (for example during time range in which we couldn’t have any outages to users, for example during the night?), in this way if not all scheduled tests list will be fine , we can rollback easily and move PSTN trunk to IP-PBX again.

To achieve this we must locate the Voice gateway properly sized, to mantain compliance on  requirement in terms of business continuity, for example redundant power supply , right number of SIP channels to/from lync, and to/from IP-PBX.

In this way we can also test a SIP trunking from a provider instead of PSTN (or buy another PSTN trunk to do a test pilot for Lync voice for example) , because until we switch the PSTN from IP-PBX to Voice Gateway, we can work easily in Voice Gateways side without give any problem in IP-PBX side.

About call flow management and dual forking we have the same behavior as i wrote in my previous post (part 1) , unique difference is that all configuration for dual forking is made in Voice gateways side , and in PBX side we have only to switch all inbound and outbound call to the new SIP trunk instead of PSTN trunk already switched off.

At this point we can assert that we have a lot of way to do a soft migration or simply to use the existence telephony infrastructure for Lync and generally Microsoft UC. We know that Microsoft Lync just for presence/audio/video/conference is really wasted and with a good approach and a small effort we can implement an excellent Lync Voice project for a really Unified Communications experience.