Category Archives: IT Guide

For IT to prepare, install and maintain Dynamics Telephony

Log file retrieval

The Dynamics Telephony log file is required if you have to report an issue. There are two ways to locate it.

Method 1

There is a link in the application to retrieve it. Use “Save As..” to save it to a convenient location and then attach it to the email to us.

retrieveLogFile

Method 2

The log file is named: DynamicsTelephony.NN.log  Where NN is the day of the month.

The file can be retrieved at the following location. If you do not have permission to access this location then you need to speak with your IT Administrator.

C:\Users\user_name\AppData\Roaming\
CT Solutions\DynamicsTelephony

Users on SIP (Asterisk, FreePBX etc.) may also be asked to retrieve the SIP log.  Go to the App Folder on the DT Menu and retrieve pjsip.log

First Client Install

The FIRST time you install a client requires special procedures. Follow the instructions below.

What you will need:
  • Telephony Registration Details (e.g. for SIP you need the SIP server/host, username and password)
  • URL to your CRM instance. 
  • The Service User details. See here for more. This user is referred to as dt_user below. 
  • Once you have the above, the install will take less than 10 minutes.
Steps
  1. Install the CRM Solution from the link sent to you.
  2. Client install. Go to the link sent to you in your contract email and click Install to download the  click-once installer (setup.exe). You can do this in parallel with step 1 above but pause at step 6 below until the solution import is completed OK.
  3. You may be prompted to install Visual C++ Runtime before the main install of Dynamics Telephony, if it is not already present on your PC.
  4. Run the installer, and follow on-screen instructions. It takes less than a minute. Depending on your virus checker and environment, you may have to click to trust the publisher a few times.
  5. Dynamics Telephony starts automatically.
  6. Enter the base CRM URL determined in “What you will need” above in the screen shown
    enter_crm_uri
  7. Only for first time install of the first client, you need to enter username and password as shown below. Pick Auth Type OAuth or Client Secret. Microsoft no longer support Office 365 for this type of user.



    NOTE: If this step has been done before, then all the fields in the screen above will auto-fill once you enter the CRM URL and click/tab out of that field.

  8. This part can take a minute or 2 (only for the first client)
  9. From within Dynamics Telephony, logon to Dynamics CRM as a normal user, (not the “dt_user”, although this is allowed).
  10. Go to Menu > Settings, in the default (General Settings) tab, select the type of telephony provider you want to use.
    settings_general
  11. Then click the Provider Account tab. Fill in your own Specific telephony settings as highlighted below. 
    settings_provider_account
  12. If you have Windows Firewall running, you may be presented with an “Allow Access” dialog. You must allow this access for Dynamics Telephony to run.
  13. Make a test call by clicking on a phone number in CRM

 

Vonage Settings

You need to add a Softphone Device to your Vonage Extension. Vonage allow up to 3 devices on an Extension. See here for details of how to do this.

The following table highlights the specific settings you should apply in Dynamics Telephony:

Dynamics Telephony Tab Dynamics Telephony Setting Value Comment
Provider
Configuration
DTMF Mode DM_Outband This is RFC 2833
Expires 1800
Provider
Account
Username e.g. VH123456 SIP/Authorization ID
Password SIP Password
Host Name E.g. sip-1234.accounts.vocalocity.com Registrar
Domain Name * A single asterisk ‘ * ‘
Transport Mode TM_UDP

 








Evolve IP Settings

The following table highlights the specific settings you should apply in Dynamics Telephony:

Dynamics Telephony Tab Dynamics Telephony Setting Value Comment
Provider
Configuration
DTMF Mode DM_Outband This is RFC 2833
Expires 1800
Provider
Account
Username e.g. 6107654321 SIP Authorization ID. You can arrange with Evolve IP for a “Shared Call Appearance” if you like
Password SIP Password
Host Name voip.evolveip.net Evolve IP Domain or Realm. If this does not work use the Evolve IP proxy Address (could be voip-b.evolveip.net)
Domain Name * A single asterisk ‘ * ‘
Proxy Address Blank.
Transport Mode TM_UDP








ShoreTel On Site Settings

The following table highlights the specific settings you should apply in Dynamics Telephony:

Dynamics Telephony Tab Dynamics Telephony Setting Value Comment
Provider
Configuration
DTMF Mode DM_Outband This is RFC 2833
Expires 1800
Provider
Account
Username e.g. 7788 Extension number on ShoreTel system.
Password SIP User Password
Host Name E.g.10.11.12.13 IP address of the SIP Domain or Realm.
Domain Name * A single asterisk ‘ * ‘
Proxy Address Leave blank
Transport Mode TM_UDP








RingCentral settings

The following table highlights the specific settings you should apply in Dynamics Telephony for RingCentral:

Go to RingCentral document on getting settings HERE

Dynamics Telephony Tab Dynamics Telephony Setting Value Comment
Provider
Configuration
DTMF Mode DM_Outband This is RFC 2833
Expires 3600
Provider
Account
Username e.g. 16147788991 Usually users phone number
Password SIP Password
Host Name sip.ringcentral.com SIP Domain from RingCentral
Domain Name * A single asterisk ‘ * ‘
Proxy Address  e.g. sip10.ringcentral.com:5090

or

199.255.120.176:5090

 Outbound Proxy from RingCentral. NOTE you might need to use the ip address for this instead – so PING it and get the ip address
Auth Username  e.g. 210987654321 Authorization ID from RingCentral
Transport Mode TM_UDP

 

If inbound calls are not working, try turning off ringing of the RingCentral Desktop and Mobile App, per this screenshot

ringCentralDesktopFwdOff








Avaya Aura Contact Center (AACC)

GET A TRIAL GOING IN 20 MINUTES !
– NO SERVER REQUIRED.

YOU ARE RISKING BEING FIRED, if you have Avaya Aura Contact Center and Dynamics 365, and you do not try out Dynamics Telephony.

Check it out on Microsoft AppSource HERE.

Dynamics Telephony for Avaya Aura Contact Center provides the perfect Unified Agent Desktop for Dynamics 365 and Avaya Aura Contact Center agents – out-of-the-box.

Related: Microsoft Omnichannel & Avaya AACC Blended

Dynamics Telephony provides real agent efficiencies, saving time on every inbound and outbound call. All through a beautifully simple and seamless integration between CRM and AACC.

All calls logged in CRM automatically. This means your customer records in CRM have a full trace of all inbound and outbound conversations.

Agents have all the Contact Center controls they need: Login/ Logout, Ready / Not Ready, Not Ready Reasons, accept / reject calls, hold transfer and conference.

avaya_cct_nrdy

Inbound screen pop means the handling time of every call is reduced. Dynamics Telephony retrieves the callers number from Avaya Aura and uses it to find the callers record in CRM. This can be CRM lead, opportunity, case, contact or account

Skillset support means the skillset called is passed to your CRM page to be logged in CRM, and to influence the data displayed to the agent so they can deal with the call correctly.

Inbound Dialed Number or DNIS support means that agents can see which phone line, or DNIS, the call is coming in on. This can be via name and logo, like this..

incomingCallTabPopup

Also, the DNIS can cause the popped CRM page to be populated based on DNIS. For example, to select the Marketing Campaign or Source of the call.

IVR Data can be used for the screen pop (e.g. an order number), or to show IVR choices made (e.g. the caller wants to make a purchase), or to show the caller has been pre-authenticated by the IVR.

Avaya Outbound contacts can be processed by Dynamics Telephony. This means that contacts presented to an agent by Avaya Outbound will pop the related record in CRM and will be processed by the Dynamics Telephony progressive dialer algorithm. See HERE for more details

CRM Dashboards showing unified CRM & Telephony data are provided. You can adjust these for your own needs using standard CRM tools, as all data is stored in CRM. See HERE for more.

Dynamics Telephony is specifically designed to be flexible to meet many advanced need – out-of-the-box. But in addition, it is designed to be extensible to meet your specific needs easily. See the full list of Dynamics Telephony features HERE


Compatibility: CCT version 6 (Nortel) and greater. Knowledge worker or Contact Center Agent

Citrix: Yes, Dynamics Telephony is Citrix compliant

Hot Desking: Yes, Dynamics Telephony supports Avaya CCT based hot desking.

Avaya Aura Agent Desktop: Yes, Dynamics Telephony can work at the same time as AAAD on an agents PC.

Settings: CCT User, password, CCT Server, port number. You can use one user for all or dedicated users. See these settings:

avaya_cct_settings_1

avaya_cct_settings_2

Single Sign On (SSO):  Yes Dynamics Telephony supports Windows single sign on. Simply leave the CCT username blank and DT will use the current windows user to sign on to CCT

Architecture Diagram: avaya_architecture

Please contact us for a personal demonstration of Dynamics Telephony for Avaya Aura Contact Center

GET A TRIAL GOING IN 20 MINUTES !
– NO SERVER REQUIRED.

btn_FreeTrial btn_MainSite








VOIP on Terminal Services

See also: TMCnet blog

VOIP is supported on a Terminal Services session. The audio (microphone and speaker) of the local PC is used via redirection from the remote session. You need Windows Server 2008 RDS or later.

However, you do need to make sure you have sufficient bandwith (especially from server to PC as this has to carry video and audio now) and that the Terminal Server itself can handle the load.

Bandwidth requirement for a Terminal Services session is around 30kbps and a VOIP session would usually be 16kbps or 24kbps, but could be as high as 64kbps if the G.711 codec is used. So check which codec you use for VOIP.








Fonality Settings

The following table highlights the specific setting you should apply in Dynamics Telephony

Dynamics Telephony
Tab
Dynamics Telephony
Setting
Value Comment
Provider
Configuration
DTMF Mode DM_Outband This is RFC 2833
Expires 1800
Provider
Account
Username SOFTPHONEXXX All CAPS
Password SIP Password
Host Name sNNNNNN.tribox.fonality.com
or
sNNNNNN.pbxtra.fonality.com
Where NNNNNN is the 6-digit system ID
Auth Username Leave blank when the same as username
Domain Name * A single asterisk ‘ * ‘
Transport Mode TM_UDP

See also: Fonality help