Menu

Category Archives: Uncategorized

Post navigation

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).

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.

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:

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.

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:

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.

Whether, you are using 3CX, Asterisk, OpenSIPS, Kamailio, FreeSWITCH, Callision, Telinta, VoIPSwitch or other, DIDX is ready to help you move your DID number business and service forward to success. The following is set up a 3CX SIP server with DIDX for DID number provisioning.

After forwarding the DID to your SIP server from the DIDX portal, you are going to make a SIP trunk on 3CX web portal with the IPs of DIDX. We’ll add a demo video here on this blog post soon.

1. Select the option “SIP Trunks”.
2. Click on the “Add SIP Trunk” option.
3. Choose the “Generic” on “Select Country” section.
4. Select the “Generic SIP Trunk” on “Select Provider in your Country” option.
5. Type in your chosen DID number that you have bought from DIDX in “Main Trunk No”. For example: 15672441578. Then click on “Ok”.
6. After clicking the “Ok”, a new window will appear. On this page you will create the SIP trunk with all the IPs of DIDX. You can find these on this link “https://www.didx.net/pages/asterisk/”.
7. Copy the IP address and paste it on the section called “Register/Server/Gateway Hostname or IP”.
8. Please set the value of “Number of SIP Calls”. This means how many calls you want to receive on this DID simultaneously. Here we set the value 10.
9. If you want to add more DIDs, then select the “DIDs” option which is on the right of the “General” section.
10. Then click on the “Add DID” button, write the DID number and then press enter. If do not want to add more DIDs, let it remain the same.
11. Click on the “Ok” button. A new window will pop up and show the SIP trunk which is successfully created.
12. Select the “Extensions” option. After that select the “Add” button.
13. A new window will pop up. By default the 3CX will automatically provide the extension number. You can change the password that is given by the 3CX or you can use the same.
14. If you want to add the personal details, you can add that but it is not compulsory.
15. You will see that the extension is created successfully. In this case, it indicates the red dot because it was not registered on any softphone. The green dot would indicate that the extension is registered on the softphone.
16. Select the “Inbound Rules”. After that select the “Add DID” option. A new window will pop up.
17. Type any “Name” in the General area. But we are defining didx-incoming. Then select the DID to which you want to forward it.
18. In the “Route call to” section, you will see the Destination for calls during office hours and after office hours.
19. You can define one extension in both sections, if you want to receive call on your extension without the office hours restriction.
20. If your office is closed and you want to forward those calls to on Voicemail rather than softphone, then you can define voicemail extension as after office hours.
But here we are using same extension in both of the fields.
21. Click on the “Ok” button. Now the “Inbound rule” has been successfully define.
22. Open the extension on “Web Client” portal on 3CX or you can use the softphone. But for now we are showing testing on “Web Client”.
23. Test the call on the DID. We will able to receive the call on this extension which is “0000”.
24. In the demo video, we are able to receive the call on this extension. This means we have successfully set up the SIP trunk on the 3CX portal website! Welcome to DIDX!

Just back from ITEXPO East and completed new business development with top quality DID providers and really excited to announce new DID phone numbers added today that are available for our DID buyers to show as available to purchase and provision immediately. All DIDX buyers may use the DIDX API to show all DID numbers of up to 140 nations as available to their clients. They do not pay in advance for all these DIDs. They are billed from their account balance when their clients buy. That’s the reason so many DIDX buyers are growing fast.

LinkedIn has a reputation for efficient use of social media to develop business. In general, people do not fill up their timelines with fluff. Most are genuine business invitations, advice, demos and discussions. After studying 1000s of of our customers and vendors’ LinkedIn profiles, we share some of our own tips.

Post a professional picture that reflects you today.

When you meet anyone in professional arenas, sure…trade business cards but also…immediately add each other on LinkedIn. It is very likely that you will lose the business card.

Connect with as many businesspeople as you can. The more people you are connected with, the more likely you will gain real leads and develop new, exciting partnerships.

Be sure to use the “Share an Update” feature to note that you want to enable a certain kind of prospect that has certain types of problems by a specific date. I.e., we are look forward to meet with communications service provider and vendor companies that want to in expand their business to USA and 139 other nations.

Give and ask for at least one LinkedIn recommendation per week from clients, vendors and business friends who know your impressive accomplishments, attitude, and value. Remember that recommendations are more specific and are more influential than simple LinkedIn endorsements.

Write one article per month that is meaningful and inspiring to your LinkedIn community.

Add one video per month that is meaningful and ends with an authentic call to action.

Add your Power Point and Slide Share presentations that you deliver at events. Make sure their focus is on the visual as in images, not just a bunch of text.

We wish you well in business, and we definitely look forward to meet you online and offline to see how we can help you expand your business to up to 140 nations via something as wonderful and practical as local DID phone numbers. Visit http://www.didx.net to get started!

We work smart to make sure the experience that our DIDX customers and vendors have in our direct inward dialing DID number marketplace… keeps a smile on their faces, that helps them get more customers and that helps them retain those customers. Some of our projects include the following to keep DIDX improving!

Infrastructure
We must have super reliable communication infrastructure. We are working to improve our SIP proxy server. Currently we have for 30 Asterisk servers to connect with proxy. Our infrastructure uses IBMCloud (used to be SoftLayer cloud) and DigitalOcean cloud servers. OTOH, thousands of our DIDX customers and vendors use FreeSWITCH and other softswitches, and we work with them every day to ensure excellent interoperability between their switches and the DIDX API.

We’re scripting for load balancing and proxy server with OpenSIPS. Our CTO Kamal Panhwar, DIDX sales manager Muhammad Ali and the whole team made that choice after several online and offline meetings and testing with OpenSIPs developers and businesses that currently use OpenSIPS. Several 100 of our DIDX members use Kamailio, too.

API (Application programming interface)
Last year, we made a decision we need to improve our DIDX API. Our system was using SOAP (simple object access protocol) format. The challenge while upgrading is that many of our clients use SOAP, so we will continue to give backward compatibility. Our new API will use Restful, so we can provide both Json and XML support.

Appearance
We just changed the appearance of our DIDX interface from the black, yellow and burgundy bumble bee look to a much calmer turquoise, white and black. I like them both. (I am Suzanne Bowen.)

Automation
We are researching Dockers and Kubernetes (to create a virtual machine template). When one of our servers fails or we need to load balance, a new server will automatically be created.

We are beta testing Homer software to capture SIP packets. The use of this gives us more robust information about the DIDs that are available to buy and that are sold on DIDX in file PCAP format. With this … customers will have more info about the SIP with DID numbers available on DIDX.net.

Though the Internet of Things are exciting and important, we still keep an emphasis on the fact that the Internet of People are even more so. We strive to serve our vendors and buyers of DID numbers with TLC on DIDX because the people are what is important.

DIDX has a new opportunity to make available DIDs of 21 cities of India for sale on the DIDX portal. These DIDs are from a top quality provider who is the source of DIDs for some very popular competitors of Whatsapp and Skype as well as top tier telecom carriers in Asia, Europe and Africa. These DIDs can be used for conference calls only. Any number of entities can call from within India to the India DID numbers. Each DIDX buyer interested can log in to the DIDX portal today and place requests.

India DID of 21 cities with unlimited number of channels are available. They take approximately 15 days to provision. The cities include:

CITY\Number Type

Prefix\Number Format

Delhi

91-11

Pune

91-20

Mumbai

91-22

Kolkata

91-33

Hyderabad

91-40

Chennai

91-44

Ahmedabad

91-79

Bangalore

91-80

Chandigarh

91-172

Cochin

91-484

Gurgaon

91-124

Trivandrum

91-471

Jammu

91-191

Coimbatore

91-422

Jaipur

91-141

Bhopal

91-755

Lucknow

91-522

Guwahati

91-361

Bhubaneswar

91-674

Indore

91-731

Noida Ghaziabad

91-120

No porting is available. They cannot be used for calling cards, only call conferencing with unlimited channels.

DIDX.net, a wholesale service since 2005, offers communications companies the opportunity to buy and sell DID phone numbers of 67 countries and more with fast activation and low monthly rates. These numbers are used for all types of business such as calling card, contact center, home phone, virtual phone line, callback, call forwarding, PBX, mobile phone app, voicemail, faxing, IoT, texting, and other communications services in the minds of the world’s most creative entrepreneurs, our DIDX members!

Numbers are available per channel, per minute or per trigger basis. DIDX provides you with 2 free numbers to test compatibility and interconnection with your switch. All buying and selling runs on your company website with DIDX working quietly in the background, provisioning the phone numbers on your server over SIP.

Our API and web service will empower you to integrate the entire inventory of DID (direct inward dialing) numbers on your website. You will be able to make available choices of millions of phone numbers to your company and customers. Your company gains an excellent reputation as fast growing with increased revenue, more satisfied customers and a global presence. Sellers of DIDX numbers on the DIDX platform have a ready wholesale buying audience of over 30,000 members.

More important, sign up to day to sell DID numbers to our thousands of communications service provider customers and/or to buy DID numbers of 140 nations to resell to your customers at www.didx.net. Don’t have a SIP / CRM service set up yet. DIDX works with Telinta, Callision, 2600hz. Twilio, Plivo and hundreds of others for your new communications service startup. Tell them DIDX sent you.

A Japanese business and industrial imaging products company buys 48-person managed service provider to better assist businesses with moving voice services to the cloud. And why not? So…voice is alive and kicking. What is a managed service provider? It delivers managed services. Those managed services are usually provided via a subscription model. Businesses will outsource and subscribe to a managed service provider who manages the certain responsibilities and functions. The MSP uses tried-and-true, strategic methods to improve operations and cut costs for the company that makes the agreement with them.

Konica Minolta call this the Workplace of the Future portfolio they will now offer their clients nationwide. The company has acquired more than 20 different managed service providers since 2012. These acquisitions enable a smart transition from just selling hardware (business and industrial imaging products company) and managed print services to the addition of selling a much more diverse portfolio of total managed IT services. Watch other companies who traditionally sell products to acquire more managed service provider companies and voice will be a major target.

DIDX offers management of direct inward dialing sales and purchases with a portfolio of DID numbers of 140 nations. Sign up today at http://www.didx.net.