Jump to content

Suri

Members
  • Posts

    33
  • Joined

  • Last visited

Posts posted by Suri

  1. Hello,

    Thank you for the fix, we were able to test the integration and it works. The incoming and outgoing calls create new contacts and log the activity.

    I wanted to know if there was more we could achieve from the integration? Does it plug on into the hubspot web interface so that we can use it as a softphone from the web UI? 

    Or are we just able to have the incoming and outgoing calls logged and contacts created in Hubspot?

    Thank you

  2. 61 is the country code for Australia so the numbers follow the pattern (61)(area code)(8 digit number).

    I had a look at our general information page and can see the "CRM Support" listed there. 

    The logging level has been set to 9 for the domain which we are making the calls to and from. I have attached the domain logs below. 

    So the way it is supposed to work is, when there is an incoming call to an extension in a domain, the system checks hubspot if the contact is there. If it is, it logs the call duration and details under than contact. If there is no contact, it creates a new one. This is what I understood from reading the documentation. In the case a new contact is to be created, does it create a contact with just the phone number? Does not need details like first name, last name and email address to create a contact? 

    We tried connecting a gmail account to hubspot and can see new contacts created when an email is sent or received. But for Vodia system, we still can not see a communication attempt being made the pbx and hubspot when we call in or out.

    Domain incoming log.txt Domain outgoing log.txt

  3. 14 minutes ago, Vodia PBX said:

    It only saves if you have entered the address data in the first tab. That is not ideal, but try if you get the customer data into stripe this way. We'll make the updating of the address and credit card data easier to use later.

    We are unable to save any address data in the first tab as well. Whatever data we input for "Billing Address" in the "Billing Settings" under "Advanced" in the domain, we are unable to save that. We click on "Save" and nothing happens. The other thing with the form is when we select Australia as the country, the fields do not change, we still have the list of the US states for "State" field. 

    At one point I even tried using a test US address to see if that would save but it that does not save either. I don't know if that was because it was a test address or something else.

  4. 8 hours ago, Vodia PBX said:

    For Australia and actually for every country this is the human readable format as it is e.g. being fed into the dial plan. If you have the country code set, it would use something like 0234567 for +61234567. You should see this when you get the first CDR in HubSpot - the point is to stick with the format and not change it along the way.

    In order to see if anything is being sent out just enable the logging of the web client - you can then see the traffic from and to HubSpot. If there is nothing well then there must be some fundamental problem, e.g. the license does not permit it.

    Thank you for explaining the number format. The number comes up as a 61****** number in the CDRs.

    I have enabled web client logs and can not see anything to or from Hubspot like you said. When you say the license does not permit it, was that the Vodia license or Hubspot? Or what could be the other potential errors that you could think of so that we can look into that.

  5. 11 hours ago, Vodia PBX said:

    Did you go into the domain and set the credit card for the customer? In test mode, you can use VISA card 424242424242. 

    Yes I did, but the information does not save on the form. I did post about this issue in a previous reply. Whatever information we enter for the credit card for customer and click "Save" the information field is blank again. We can not see any information being saved. I have tried using a test details before.

  6. On 3/9/2019 at 1:56 AM, Vodia PBX said:

    There is some documentation now at https://doc.vodia.com/hubspot_crm

    Hello,

    The documentation says "For US numbers this format is a 10-digit format (for example, 6173998147). "

    Is there a particular standard for Australian numbers as well? We were wondering if that was why the integration was not working. The format of the numbers we are using is 614******** (11 digits in total where 61 is the country code). 

    As I mentioned previously, at the current stage, we have a valid hubspot api key in our system. And when we try calling in or out of the extension, we do not see any log entries referring to hubspot to see if the integration is working or not. Was there any additional setting that was required on either the Vodia side or Hubspot side apart from the api keys?

  7. On 3/23/2019 at 12:31 AM, Vodia PBX said:

    Yea the original message thread was about Freshbooks. Stripe should work, though we still have things like taxes on the open issues list.

    Oh okay, I just asked since I had an unanswered question sitting above the response.

    This is the log file generated when we attempt to generate a test invoice:

    POST /v1/invoiceitems HTTP/1.1
    Host: api.stripe.com
    Authorization: Bearer sk_test
    Content-Type: application/x-www-form-urlencoded
    Content-Length: 84
    
    customer=undefined&currency=aud&description=Setup%20Fee&quantity=1&unit_amount=10000
    [9] 16:13:05.330 WEBC: Initialize TLS connection
    [9] 16:13:05.997 WEBC: Received 858 bytes
    HTTP/1.1 400 Bad Request
    Server: nginx
    Date: Mon, 25 Mar 2019 05:13:05 GMT
    Content-Type: application/json
    Content-Length: 231
    Connection: keep-alive
    access-control-allow-credentials: true
    access-control-allow-methods: GET, POST, HEAD, OPTIONS, DELETE
    access-control-allow-origin: *
    access-control-expose-headers: Request-Id, Stripe-Manage-Version, X-Stripe-External-Auth-Required, X-Stripe-Privileged-Session-Required
    access-control-max-age: 300
    cache-control: no-cache, no-store
    request-id: req_gv9lKCqXu3V5SS
    stripe-version: 2019-02-19
    Strict-Transport-Security: max-age=31556926; includeSubDomains; preload
    
    
    [9] 16:13:05.997 WEBC: https:api.stripe.com:443: Return content (231 bytes)
    {
      "error": {
        "code": "resource_missing",
        "doc_url": "https://stripe.com/docs/error-codes/resource-missing",
        "message": "No such customer: undefined",
        "param": "customer",
        "type": "invalid_request_error"
      }
    }
    
    [7] 16:13:17.060 WEBC: Closing connection https:api.stripe.com:443

     

    It says "No such customer : undefined" and we do not receive the invoice. We provided a valid email address on the billing address field in the "Edit domain" page. When it looks for "customer" what is the system looking for? 

  8. Okay. We are trying to simulate a multi tenant system at the moment so we were looking to see how this setting worked. The problem is that the data we entered in the fields would not save on the system. Unless it is meant to look like there is no data saved even though there is. 

    Apart from this, when you said 

    On 3/15/2019 at 6:53 AM, Support said:

    We agree about the first part of the message and agree with it. 

    does this mean the system being unable to generate an invoice is a bug that is to be fixed soon? We are still unable to generate a test invoice from the "Test" button that is in the "Edit Domain" page.

  9. Thank you.

    I noticed that the stats were not sent as an attachment to be downloaded. I tried different settings for the midnight report (text, html and embedded html) but they all were delivered embedded in the email and not an attachment. 

    Was this an issue that was going to be fixed in the newer version?

  10. We have the billing plans defined and the domains have a plan assigned to them. When we are in the "edit domain" page where you can select what plan to assign, there is a field called "Billing email address". I have tried inputting a valid email address in that section multiple times but every time I click Save and reload the page again, the email address is not saved on the form. 

    Also in the "Billing Settings" of the domain, when we input the billing address and click save, the info is not saved. We are based in Australia but we even tried using a US address to see if that would work but the form goes blank after a reload.

    So when we click "Test" on "edit domain" page, we do not get an invoice, nothing happens when we click it.

     

  11. Okay. I have removed all the action urls now so all we have got in the system is the hubspot api key and set it to send information for all calls, just the basic setting.

    When I make a call into the domain, there is nothing in the logfile that shows that it is attempting to send information to hubspot. Hubspot has a contact with that phone number which I am calling to. Was there any particular setting that is required on the hubspot end? How do we verify that the integration is working in general? 

    Thank you

  12. Thank you for the response. It seems to be trying to connect to hubspot and it does receive some content but we do no see any activity on the hubspot side. I had contacted them as well regarding this and they said we would need to talk to the vodia support for this. 

    On the hubspot end, I have manually created a contact with the phone number (say 123456789) and validated it using the standard hubspot phone number validation process. 123456789 is one of the numbers assigned to an extension in our vodia domain. When I make a call from that Hubspot contact to my mobile, the call goes through and I can see the call messages in domain log file in our Vodia system. But when I make a call to or from the same extension, from or to my mobile, the log entries look like this (I was only logging webserver and webclient events at this time). It has the cdr report for the call which looks like it is being forwarded to hubpsot. But, there is no activity on hubpost end, there is no contact added or log entry added for that particular call. 

     

    [5] 11:17:28.243 WEBC: Action URL request https://app.hubspot.com/
    [7] 11:17:28.244 WEBC: https:app.hubspot.com:443: DNS A returned 104.16.251.5
    [7] 11:17:28.244 WEBC: https:app.hubspot.com:443: Connect to 104.16.251.5
    [7] 11:17:28.244 SIP: Use codec PCMU/8000 for call-leg 991
    [9] 11:17:28.246 WEBC: https:app.hubspot.com:443: Send request (143 bytes)
    GET / HTTP/1.1
    Host: app.hubspot.com
    Authorization: Basic VXNlcm5hbWU6UGFzc3dvcmQ=
    Content-Type: application/json
    Content-Length: 0
    
    
    [9] 11:17:28.246 WEBC: Initialize TLS connection
    [9] 11:17:28.589 WEBC: Received 765 bytes
    HTTP/1.1 301 Moved Permanently
    Date: Tue, 05 Mar 2019 00:17:28 GMT
    Content-Type: text/html
    Content-Length: 178
    Connection: keep-alive
    Set-Cookie: __cfduid=dbbf19b607034c2df3ffc1407dc4214521551745048; expires=Wed, 04-Mar-20 00:17:28 GMT; path=/; domain=.hubspot.com; HttpOnly
    Access-Control-Allow-Credentials: false
    Location: https://app.hubspot.com/home
    Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
    Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
    Server: cloudflare
    CF-RAY: 4b27e8383f0a1d44-MEL
    
    
    [9] 11:17:28.589 WEBC: https:app.hubspot.com:443: Return content (178 bytes)
    <html>
    <head><title>301 Moved Permanently</title></head>
    <body bgcolor="white">
    <center><h1>301 Moved Permanently</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    
    [5] 11:17:28.589 WEBC: Action URL response
    <html>
    <head><title>301 Moved Permanently</title></head>
    <body bgcolor="white">
    <center><h1>301 Moved Permanently</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    
    [9] 11:17:31.799 SIP: Using outbound proxy sip:xxx.xxx.xxx.xx:16797;transport=udp because of flow-label
    [7] 11:17:31.874 SIP: Port 992: Clear last request
    [7] 11:17:34.018 SIP: Port 992: Clear last INVITE
    [7] 11:17:34.019 SIP: Use codec PCMU/8000 for call-leg 992
    [5] 11:17:34.021 WEBC: Action URL request https://app.hubspot.com/rest/call/
    \{"cdr":\{"from:""\"61488888888\" <sip:614888888888@vodia1.domain.com.au>","to":"{tv}","duration":"{duration}"\}\}
    [9] 11:17:34.021 WEBC: https:app.hubspot.com:443: Send request (266 bytes)
    POST /rest/call/ HTTP/1.1
    Host: app.hubspot.com
    Authorization: Basic VXNlcm5hbWU6UGFzc3dvcmQ=
    Content-Type: application/json
    Content-Length: 110
    
    \{"cdr":\{"from:""\"614888888888\" <sip:6148888888888@vodia1.domain.com.au>","to":"{tv}","duration":"{duration}"\}\}
    [9] 11:17:34.272 WEBC: Received 752 bytes
    HTTP/1.1 500 Internal Server Error
    Date: Tue, 05 Mar 2019 00:17:34 GMT
    Content-Type: text/html; charset=utf-8
    Content-Length: 186
    Connection: keep-alive
    Set-Cookie: __cfduid=d0152c84ca5b544fdfe51e695e252d6761551745054; expires=Wed, 04-Mar-20 00:17:34 GMT; path=/; domain=.hubspot.com; HttpOnly
    Access-Control-Allow-Credentials: false
    Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
    Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
    Server: cloudflare
    CF-RAY: 4b27e85ba8231d44-MEL
    
    
    [9] 11:17:34.272 WEBC: https:app.hubspot.com:443: Return content (186 bytes)
    <html>
    <head><title>500 Internal Server Error</title></head>
    <body bgcolor="white">
    <center><h1>500 Internal Server Error</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    
    [5] 11:17:34.272 WEBC: Action URL response
    <html>
    <head><title>500 Internal Server Error</title></head>
    <body bgcolor="white">
    <center><h1>500 Internal Server Error</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    
    [7] 11:17:37.576 SIP: Port 992: Clear last request
    [5] 11:17:37.577 SIP: BYE Response: Terminate 73587ecf@pbx
    [9] 11:17:39.012 WEBS: Request /rest/domain/vodia1.domain.com.au/log
    [9] 11:17:39.012 WEBS: REST: GET /rest/domain/vodia1.domain.com.au/log
  13. On 1/29/2019 at 10:24 PM, Vodia PBX said:

    You might want to skip this and move on to Stripe - we can provide you a beta image (what OS) to try out the new stripe integration. With this the PBX will automatically charge the customer at the end of the month and when the trunk balance falls below a definable value.

    Hi, we are running version 62.1 and have got our test Stripe public and private keys entered under the Stripe tab in billing. We have setup a billing plan as well. How would we go on from here to generate a test invoice? Can we generate an invoice manually when we need to or do we wait until the end of the month for the platform to generate an invoice? Is the same billing plan used for all domains or do we have an option of choosing which plan we want to assign to what domain?

  14. Okay. Do we need any specific account type to get the integration working like marketing, sales or service? 

    Once we have the API keys in the platform, do we setup the individual extension's "Action URL" page to get that particular extension send information to hubspot?

    I was reading through this thread to see how the integration was supposed to work in general 

    "You enter the CRM URL (version included) in a setting together with the username and password of the account in the CRM where the entries should be made. These settings are extension based so every person who has an account in the CRM will have his/her calls recorded in his/her account on the CRM." Is this valid for hubspot as well? Do we set up the crm url and the account login credentials in Action url page for whatever action we want to create an entry? 

×
×
  • Create New...