by Vedisoft

Avaya Integration is a computer telephony integration between SugarCRM/SuiteCRM and Avaya PBX. Add-on supports PBX "Avaya IP Office"

Free Trial

By clicking you consent to be contacted by the developer

#3585 - CO - FISDEN - Configuration Issue

Open Installation created by Faye Verified Purchase 4 years ago

Although the documentation states that under the All-In-One CTI configuration "Note! You can leave Password empty. Password is used only if you set Password in PBX-connector configuration file." we received a "Missing required field: Password" message although we did not setup a password. How can we work around this?

FISDEN_CTI Password.png

Also, if we try to enter a "dummy" password of "123" we get the following "Cross Site Forgery (XSRF) Attack Detected" message then when going back to the configuration all fields are empty again. Please assist. FISDEN_CTI Error.png

  1. FBSG member avatar

    Faye Verified Purchase

    4 years ago

    We are pressed to get this issue resolved. Please provide guidance as soon as possible.

  2. FBSG member avatar

    Faye Verified Purchase

    4 years ago

    Hello Vedisoft, any update or response to support case?

  3. Vedisoft member avatar

    Vedisoft Provider

    4 years ago

    Hi, I'm sorry we didnot reply you earlier. 1. You can put any value in oassword. 2.1. Put in host parameter "ws://" prefix. For example, your PBX-connector locates on 192.168.1.143, then you should put ws://192.168.1.143. 2.2. Run your CRM under http (not by https). 2.3. When you successfully run integration without ssl, we will help you to run integration with SSL (I mean under httos and wss://)

  4. Vedisoft member avatar

    Vedisoft Provider

    4 years ago

    In case you run your CRM on SugarCRM servers, you will not be able to run CRM under http. In that case, just let me know, and i will describe how to cobfigure SSL on your pbx-connector

  5. FBSG member avatar

    Faye Verified Purchase

    4 years ago

    Yes, the client runs Sugar on SugarCRM's on demand servers with SSL so we can't run it under http. Please provide instruction on how to configure SSL within the PBX connector. Right now, when I add the password (I just use "password" since no password is setup in the PBX) and I populate the host with the"ws://" prefix, I still get the following error which I gather is related to the https restriction. FISDEN_CTI Error.png

  6. FBSG member avatar

    Faye Verified Purchase

    4 years ago

    Hello Vedisoft, I'm chasing you again for a response to my last note, because this is a high priority project that needs to go live this week. Please provide me with instructions for configuring SSL in the PBX connector since we can NOT access the client's Sugar instance via http, because it is hosted on Sugar's on demand server. Also, let me know if this will resolve the "cross site request forgery (XSRF) attack detected" error that I reported when populating the password field.

    • Vedisoft member avatar

      Vedisoft Provider

      4 years ago

      Hi, Threre are 2 problems now 1). XSRF issue 2). SSL issue

      XSRF issue - Please let me know the exact version of SugarCRM. - Could you please give us http-access to CRM with admin privileges (you can send credential here a@vedisoft.info)

      SSL issue Regarding SSL: you need to generate your own SSL-certificate and substitute old certificates:

      You should get 2 files from your SSL-certificate provider • Certificate • Private key

      Rename file with certificate into newsert.pem and replace it in PBX-connector folder Rename file with private key into privkey1.pem and replace it in PBX-connector folder

  7. Vedisoft member avatar

    Vedisoft Provider

    4 years ago

    XSRF issue Could you please try this version of our module - https://www.sugaroutfitters.com/download/10340 (file - sugar-7.9.x-Avaya-dec17.zip) - you have to uninstall old version in CRM - install new one

  8. FBSG member avatar

    Faye Verified Purchase

    4 years ago

    Thank you for the latest package. It resolved the configuration issue and I am no longer receiving errors. However, now that the configuration is complete, Rebuild JS Grouping Files performed, and User Phone records are created with "Click-to-Call" selected, clicking on a phone number in the standard Sugar module does not activate dialing. Nothing happens when clicking on a phone number field in Sugar at all.

    Questions: 1. Should the "Pnone" field (see below screenshot) contain the user's phone extension OR their full direct dial number? We've tried both and neither has worked, but I want to confirm the correct setting. 2. Typically, when dialing directly from a user's telephone, the user must press "9" first to get an outside line before dialing the destination phone number. Does any special configuration need to be made to handle this? FYI, for testing, I asked the user to manually press "9" prior to clicking on the telephone number in Sugar, but still nothing happened. We tried by pressing the "9" first AND by not doing so to no avail. 3. Is there any additional configuration required on the PBX? Within the PBX connector we've configured the IP and port, but I'm not sure if something else is required. 4. Can we schedule a screen share session with a resource at Vedisoft, FayeBSG, and our client to review the configuration and get Sugar connected with Avaya?

    FISDEN_UserPhone.png

  9. FBSG member avatar

    Faye Verified Purchase

    4 years ago

    Vedisoft, any update on this ticket?

  10. Vedisoft member avatar

    Vedisoft Provider

    4 years ago

    It was snswered by email last week. Did you get it? I can resend you this email in 10 hours if you need.

  11. Vedisoft member avatar

    Vedisoft Provider

    4 years ago

    Hi I have sent you email just a minute ago

  12. FBSG member avatar

    Faye Verified Purchase

    4 years ago

    I have not received it. Please send directly to me at chin.ogba@fayebsg.com.

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...