DIDx Simplifies Buyer Agreement Process

Our DIDx buyers asked for a simpler agreement process, and we responded, “Yes!”
B. Login to your DIDx account, and click on Profile button on the left menu bar.
C. Fill, sign, and initial each page, and then click on Upload document section in the PROFILE section of your DIDX account to upload to our team.
We appreciate you.

Net4Things & Telefonica Offer Telcos Connected Car Biz Opp

Didx and Deutschland telecom at itw 2018 red shoesDIDX participated in International Telecoms Week 2018 in Chicago, IL. So impressed with Net4Things and Telefonica offering telcos a great new way to increase customer retention and bring in new revnue while getting on board the new trend of connected cars in an IoT and M2M world.

Net4Things communications and marketing expert Maria Gonzalez explains how this works in the video. We can’t wait to share this with our 35,000 communications company members that use our http://www.didx.net. Visit http://www.net4things.com now to get started.

Two Reasons to Reactivate Your DIDX Account

Reason 1:
Let the DIDx wholesale DID marketplace help you kickstart your business with $25 worth of credit to activate your DIDx account.

Reason 2:
When you buy a minimum of 100 DIDs of USA, UK, and Canada, enjoy another 25% discount. (Conditions apply.)

With DIDx, you can become a telco or voIp operator in your country today. That’s exciting! 

Contact sales at didx.net and get started right away! 

Short Case Study: How Nonprofits Like Dove Gospel Go International with DIDX DID Numbers

A Pensacola, Florida headquartered VP of DIDX Suzanne Bowen, Karachi-based DIDX senior customer service exec Ali Muhammad and Australian James Hughes of Dove Gospel Global met up online via webRTC to discuss in short form how the nonprofit organization and DIDX work together to meet the needs of DGG and its community that is now as global as its name.

Dove Gospel Global global network director and pastor James Hughes says, “My heart is for a church without politics, and where Jesus moves in power and authority through his Holy Spirit.”

One major goal of Dove Gospel Global is to connect with religious leaders anywhere and of any religion. They searched for ways to make these leaders have an easy, efficient way to contact Dove Gospel Global, and for DGG to stay in touch. There are many communications issues such as poor cellular, landline and/or Internet networks in different areas of the world whether 3rd world, rural, emerging and also cost and security.

Because of the organization’s tireless search and testing of several solutions, they found happiness with a FreeSWITCH-based platform and DIDX for incoming calls. Now, the group has headquarters in Kampala, Uganda; Bhattiprolu, India; Lahore, Pakistan; Kent, United Kingdom; and with the main headquarters in Sydney, Australia. Anyone can call Dove Gospel Global via a local phone number of over 50 countries, and we have learned that those phone lines stay very busy. Call logs tell it all. Those 50 countries include USA, UK, Uganda, Turkey, Thailand, Sweden, Spain, South Korea, South Africa, Slovac Republic, Singapore, Russia, Rumania, Portugal, Poland, Pakistan, Nigeria, New Zealand, Netherlands, Mexico, Malaysia, Liberia, Latvia, Kenya, Japan, Italy, Israel, Ireland, Hong Kong, Ireland, Germany, France, Finland, Denmark, Czech Republic, Brazil, Belgium, Austria and Australia.

The number and scope of communications, new community members and collaborators and growth of their nonprofit movement in every way has grown and experienced more success, but that’s not to say, they have not had some tough times such as communications solution trials that never really worked, DIDs purchased from other virtual phone number service providers where price fluctuated, mostly upward, and service stopped for weeks at a time. The group’s growth was not matched by a flexible, scalable communications set-up. But once they developed in-house with paid guidance from a FreeSWITCH developer their own platform and integrated DIDX.net DID number service, they are now able to grow without the “growing pains.”

Watch Ali and James talk about Dove Gospel Global’s technological path to success.

 

WhatsApp Messages from People I Don’t Know with Foreign Phone Numbers

DIDX CTO Kamal Panhwar explains, “Phone numbers are available in different directories and sometimes such information is revealed. There are many companies that spam their messages on Whatsapp numbers. If I have a Google Voice number (always a +1 US number), I can set it up as my WhatsApp number and send someone messages that way. This is true no matter where I am in the world. Now the person who receives my messages, that person has the option to report any of those messages to Whatsapp… as spam. Once the receiver reports this, it is up to Whatsapp to deactivate my number.

mapping virtual numbers to whatsapp“It is easy also if I buy a DID number from, for example:

http://www.tossabledigits.com/http://virtualphoneline.com or https://callhippo.com/virtual-phone-number and if that number is SMS-capable, then I can set up a software on my computer that will connect to Whatsapp server to register my virtual number. I will get an SMS on the portal of a virtual phone number provider such as the three above, and then I can confirm my API and get the password. If I have these kinds of numbers, I can broadcast Whatsapp numbers until someone reports my number, and WhatsApp blocks my number. WhatsApp does not allow such actions, and they are lightning fast in blocking the numbers that are not complying with their rules of use.

“At the same, there are some libraries in PHP that can still connect*. Hope I am clear. I welcome comments and requests for more information. I actually ran several tests in the past week to make sure the information I am sharing is correct.”

*This means there are some open source PHP libraries which can connect, but the programmer is not updating them to the latest version. For some professional people, these libraries can connect and send a message to WhatsApp, and others can’t.

If your business would like to have a more global presence via DID numbers, A.K.A., virtual phone numbers, ask your phone service provider to join DIDX.net. Then they make available numbers of 130 + nations for you. If you cannot convince them, go for Tossable Digits, Virtual Phone Line, Call Hippo or other like company that will!

In addition, DIDX never has and never will condone not following government regulations nor not following communications platforms’ guidelines. Privacy and freedom from spam, we absolutely understand how important they are.

As of March 25, 2018, DIDX Sends Calls Via Most Universally Accepted Codec G711

A very important goal of DIDX.net is to provide a consistently reliable service for each of its buyers and sellers of DID (direct inward dialing). This is the reason that we share this communication that references a very important email we sent via direct email to each of them and via DIDX blog post in August 24, 2017 and again today March 26, 2018… regarding codec translation.
Just as we announced in that email, we have stopped transcoding beginning the date of 25th March 2018. Now we will send all calls via the most common and most universally compatible codec which is G711.
We hope you will feel the more positive quality and be sure to keep growing as DIDX grows its coverage in quantity and quality! Let us know anything we can do to make this business relationship better than ever. Just log in to your DIDX dashboard and send us an email or call us today.

Budget-Conscious Travelers 💖 DID Numbers

Budget-conscious travelers  💖 and need DID numbers, aka virtual numbers. Hello, from DIDX.net. Communications companies like cell phone, voIP, and other service providers have this huge market of people like you and me who have made over 35,060,921 trips to another country in 2017. That’s just us in the US. We would rather spend money enjoying the local culture, developing business and friendships and bringing back cool souvenirs than to waste it on high-priced devices and temporary, pay-as-you-go phone service plans abroad.
Here is what is possible because of DIDX.net. You and I can buy DID numbers of 140 nations, set them up to be used within minutes. They can ring to any existing device like our phones. We can own as many DID numbers as we like on one device (phone). We can get rid of any of them when we don’t need them or keep them forever. Most of the communications companies who buy DID numbers via DIDX marketplace to resell to people like you and me… also offer extra cool free features like voicemail, call forwarding, call recording, call logs and more.
When we are traveling on business, DID numbers can help us manage different departments of our company on one device and track search engine optimization projects via call logs.
Here’s the real cool thing, whether we travel a lot for business or personal reasons or both, we can port our current landline, business of mobile phone number to companies that use the DIDX.net platform for their wholesale communications service provision.
Now, we will never lose that important phone number.
When people call that number, they will still reach us. All we have to do is either have the calls forwarded to voicemail or to another phone line or to a SIP service that our communications provider offers us.
Now, if our current phone … communications service provider does not offer DID number service,we should send them to DIDX.net today! DIDX has offered this service to phone companies since 2005. Let’s not have them missing out on making us budget-conscious travelers really happy.

How to change the “Ring To” address at DIDX to your Asterisk SIP server

We’ll include a demo video here soon! Let’s learn more about configuring your Asterisk Server with DIDX. Today we will learn how to forward DID you have purchased via DIDX.net to your server.

For that, you will select the option “My Purchased DIDs”.

Here you will see all your purchased DIDs and their details. Now, in order to change the forwarding of your DID, just click on the “Ring To” address.

Next, set the “Ring To” address like this “DID@Your-Server-IP-Address”.

If you are using the default port that is # 5060, then there is no need to define it. If you are using any other port, then you have to define like “DID@Your-Server-IP Address:5060”. Here we are using the default port.

After completing the steps, click on “Update” button.

You have successfully configured the DID forwarding from DIDX.net to your SIP server. After that, you will want to configure SIP trunk on your Asterisk server. Thank you for enabling us to serve you. Welcome to DIDX DID number coverage of 140 nations, no pre-purchase required!

We will add a demo video to this blog post soon.

SIP clients typically use TCP or UDP on port numbers 5060 or 5061 for SIP traffic to servers and other endpoints. Port 5060 is commonly used for non-encrypted signaling traffic whereas port 5061 is typically used for traffic encrypted with Transport Layer Security (TLS).

Configure OpenSIPS to Receive Calls from DIDX DID Number Coverage

Hello to your new rich IP comunications business that includes OpenSIPS Open Source SIP proxy/server for voice, video, IM, presence and any other SIP extensions … multi-functional, multi-purpose signaling SIP server and DIDX direct inward dialing!


There is a misspelling of “Interop” at the beginning of this video. We apologize. We deeply appreciate Bogdan Iancu, founder of OpenSIPS for making it really easy to understand how to configure OpenSIPS to receive calls from DID of DIDX.net!

How To: Achieve Interoperability Between DIDX and OpenSIPS

 

In this tutorial, we will expand an existing OpenSIPS server configuration so that it will accept incoming traffic from a given list of DIDX servers.

 

To find out which particular DIDX IP address will send traffic for a given DID number, you may login to your DIDX account and visit the “DID INFO” page of that number. Alternatively, you may visit https://www.didx.net/pages/configs for the list of all DIDX IPs.

 

Regarding OpenSIPS, we assume that it is already running alongside an SQL database. Depending on your Linux OS, you may install and immediately start OpenSIPS from either https://apt.opensips.org or https://yum.opensips.org. For the database, a quick tutorial on how to import the OpenSIPS database schema into your SQL engine of choice is available at https://www.opensips.org/Documentation/Install-DBDeployment-2-4

 

The typical way to authenticate the SIP sender is via digest authentication (with username and password). As this mechanism is suitable for authenticating endpoints (users), it does not fit when comes to authenticate gateways, DID servers or other types of remote SIP Servers. For such purposes is it better to use IP authentication – the SIP sender is recognized and authenticated based on the source IP at the IP level.

 

Typically, most OpenSIPS config files (including the default config file) provide support for digest authentication, so we need to add to your config file the support for IP authentication in order to recognize and trust the calls sent by the DIDX servers.

 

First, open the /etc/opensips/opensips.cfg OpenSIPS configuration file using your favorite text editor. If OpenSIPS is installed from sources, the default path is /usr/local/etc/opensips/opensips.cfg. Within the initial section of the script, load the “permissions” module and configure a database URL for it:

 

loadmodule “permissions.so”

modparam(“permissions”, “db_url”,                  “mysql://opensips:opensipsrw@localhost/opensips”)

 

The “permissions” module is an in-memory storage for lists of IPs and network masks. We will use it to store the list of DIDX servers and validate all incoming calls against this list. With regards to the “validation” part, we only want to perform it when a call starts (i.e. initial INVITE receival). We recommend placing this check near your SIP digest authentication script code, and skipping the digest authentication altogether if the source is whitelisted:

 

 

if (!is_method(“REGISTER”)) {

if (check_source_address(“11”)) {

xlog(“Call from DIDX, skipping SIP digest authentication\n”);

} else if (is_myself(“$fd”)) {

# authenticate local subscriber

}

}

 

We apply the config file changes by restarting OpenSIPS:

 

opensipsctl stop

opensipsctl start

# or

/etc/init.d/opensips restart

 

Next, we provision the DIDX IPs under group 11 into the SQL database using opensipsctl. Note that you need to provision the DB support via opensipsctlrc file (typically under /etc/opensips/ directory):

 

# list the  current addresses from DB (should show nothing)

opensipsctl address show

# add the addresses one by one to DB

opensipsctl address add 11 198.199.87.53 32 0 udp

# list again to see all the addresses from DB

opensipsctl address show

 

Finally, we refresh the OpenSIPS “permissions” module cache with the new IPs:

 

# list the current in-memory addresses (should show nothing)

opensipsctl address dump

# instruct OpenSIPS to refresh in-memory cache with the DB content

opensipsctl address reload

# list again to see the addresses loaded from DB

opensipsctl address dump

And we’re done! OpenSIPS will now accept IP authenticated inbound traffic from the DIDX service. Awesome!

BTW, also don’t miss a single OpenSIPS Summit! Super informative, hands-on, welcoming event each year in Amsterdam, Netherlands.

Welcome to Asterisk Configuration with DIDX DID Coverage of 100 + Nations

Millions of individuals and businesses on planet Earth use a communications system in which the Asterisk and DIDX direct inward dialing are used for convenient, feature-rich, inexpensive calling. Here is how to configure the technical side of this empowering combination. (We will include a demo video on this blog that goes with this description soon.)

Let’s create SIP trunks in Asterisk with the IP addresses of DIDX SIP server. Use any
preferred editor to edit the “SIP.conf” file. The file path is “/etc/asterisk/sip.conf”.

Here you have to define the SIP trunks with the IP addresses of DIDX.

All the IP addresses of DIDX are mentioned on this link which is “www.didx.net/pages/asterisk”. If you are using USA DID, then the call can come from sip4, us1 and us2 addresses. If you are using UK DID, then call can come from eu2 and eu3 addresses. It is recommended to create the SIP trunk with all the IP addresses which are mentioned on this page.

Let’s create the SIP trunk with “sip4”.
The format for this follows:

[sip4]
type=peer
host=198.101.50.4
context=incoming

Let’s make a second SIP trunk of “sip8”.

[sip8]
type=peer
host=67.228.182.162
context=incoming

Similarly, in this format you will define the remaining IP addresses of DIDX.

Next, you will create an extension in this file. The format for creating the “10005” extension is like
this:

[10005]
type=peer
username=10005
secret=DIDx (Please make sure to use strong, complex password.)
host=dynamic
context=incoming
disallow=all (This will disallow all the codecs.)
allow=alaw (You will allow only “ulaw” and “alaw.”)
allow=ulaw

You have created the extension successfully in the file. Now save and exit the file.

Let’s go to the extension file using the preferred editor. The file path is same; just replace …
“sip.conf” with “extensions.conf”.

You will define your “Dial Plan” in this format where we are using DID 15672446030 as an example:

[incoming]
exten => 15672446030,1,Dial(SIP/10005)
exten => 15672446030,2,Hangup()

All incoming calls on this “DID” will land on this extension “10005”.

Instead of defining all the DIDs separately in the “Dial Plan”, you can customize your Dial plan like this:

exten => _X.,1,Dial(SIP/10005) (Here “X” means number from 0-9 and “.” means any length.)
exten => _X.,1,Hangup()

After this, save and exit the file.

Now you will go to Asterisk CLI to reload all your configuration. For that type “Asterisk -rvvvv”. Then hit Enter.

Now type “reload” and hit Enter. Your configuration is reloaded successfully.

Now you will register the extension on your softphone that you have created in your “sip.conf” file. You can use any softphone such as your own or Zoiper, X-lite, Jitsi, SwitchVox softphone, and Eyebeam because they are easily available and can be configured in no time. In our demo video, we use Zoiper.

In Zoiper, click on “Setting” and then use the SIP protocol. Click “next”.

Type your extension in the “User” box. Type the password that you have defined in your extension.

Last, type the IP address of your Asterisk server and then click “next”. Again “next”.

You will see: “Your account has been added to account list”.

Again, go to your Asterisk CLI. Check if your extension is registered on the softphone or
not by using this command “sip show peers”. Here you can see your extension has been registered.

Once your configuration is completed successfully, dial the DID that you have purchased and had provisioned from the DIDX marketplace, you will see the incoming call on this DID reach this extension successfully which is registered on your softphone.

Feel free to double-check the call on the “Asterisk CLI”. Welcome to your Asterisk server with DIDX direct inward dialing with a coverage of 100 + nations.