WhitePages Pro [custom API]

[RBS]

It would be nice to be able to add API of your choice in addition to limited number of integrations available.

For Caller ID, address etc...

 

[edossantos]

You can create your own integrations following this guide:
https://www.3cx.com/docs/crm-integration/

 

[RBS]

Oh thank you!

Follow up question: we are particularly interested in "Phone Reputation" incoming calls, and reject "603" if it's a known scam. Does this sound feasible?

 

[edossantos]

The CRM integration will not reject calls, it will search for the caller number in your CRM or database, and then show the contact name as the caller name.

If you need to reject a call, then you might need to create a CFD application. Then, you can route inbound calls to this CFD app, which can check a web service, database, etc. if the caller number is a scam, and then reject the call. Or transfer the call to the proper destination is the caller is valid.

 

[RBS]

Here is what I got. One last obstacle (or so it seems). It's not passing the result.

<?xml version="1.0"?>
<Crm xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Country="US" Name="Whitepages" Version="7">
  <Number Prefix="Off" MaxLength="" />
  <Connection MaxConcurrentRequests="2" />
  <Parameters>
    <Parameter Name="api_key" Type="String" Editor="String" Title="API Key:" />
  </Parameters>
  <Authentication Type="Basic">
    <Value>[api_key]:X</Value>
  </Authentication>
  <Scenarios>
    <Scenario Id="" Type="REST">
      <Request SkipIf="" Url="https://proapi.whitepages.com/3.0/phone_reputation?api_key=[api_key]&amp;phone=[Number]" Message="" RequestContentType="Json" RequestEncoding="UrlEncoded" RequestType="Get" ResponseType="Json" />
      <Rules>
        <Rule Type="Any" Ethalon="PHONE">phone_number</Rule>
      </Rules>
      <Variables>
        <Variable Name="id" LookupValue="" Path="id">
          <Filter />
        </Variable>
        <Variable Name="phone_number" LookupValue="" Path="phone_number">
          <Filter />
        </Variable>
        <Variable Name="country_code" LookupValue="" Path="country_code">
          <Filter />
        </Variable>
        <Variable Name="country_calling_code" LookupValue="" Path="country_calling_code">
          <Filter />
        </Variable>
        <Variable Name="reputation_level" LookupValue="" Path="reputation_level">
          <Filter />
        </Variable>
        <Variable Name="reputation_details" LookupValue="" Path="">
          <Filter />
        </Variable>
        <Variable Name="score" LookupValue="" Path="reputation_details.score">
          <Filter />
        </Variable>
        <Variable Name="type" LookupValue="" Path="reputation_details.type">
          <Filter />
        </Variable>
        <Variable Name="category" LookupValue="" Path="reputation_details.category">
          <Filter />
        </Variable>
        <Variable Name="volume_score" LookupValue="" Path="volume_score">
          <Filter />
        </Variable>
        <Variable Name="report_count" LookupValue="" Path="report_count">
          <Filter />
        </Variable>
        <Variable Name="error" LookupValue="" Path="">
          <Filter />
        </Variable>
        <Variable Name="name" LookupValue="" Path="error.name">
          <Filter />
        </Variable>
        <Variable Name="message" LookupValue="" Path="error.message">
          <Filter />
        </Variable>
        <Variable Name="warnings" LookupValue="" Path="warnings">
          <Filter />
        </Variable>
      </Variables>
      <Outputs Next="" AllowEmpty="false">
        <Output Type="PhoneMobile" Passes="1" Value="[report_count]+[reputation_level]+[volume_score]+[country_calling_code][phone_number]" />
      </Outputs>
    </Scenario>
  </Scenarios>
</Crm>

The template produces a perfect Response Tree. "Test" gives me one value, the only one I would care to use:
"PhoneMobile": "55+3+3+phone_number"

[report_count]+[reputation_level]+[volume_score]+[country_calling_code][phone_number]

A clean caller would look like "0+1+1+phone_number".

I could sort all this out tweaking inbound rules.

If only I could get it to pass the value on from CRM (code above) as a "caller id" intact.

 

[edossantos]

The problem is that inbound rules are applied before this CRM engine does its work. So, the inbound rule works on the number as it arrives from your SIP trunk, the changes you do here to the caller name are just to display it to the agent that will pick up the call. It's not useful to reject a call using inbound rules...

As I mentioned, you should us a CFD app for this.

 

[RBS]

As I mentioned, you should us a CFD app for this

I have come to understanding of this, thank you. Please check back on my CFD thread (and close this one).