
DIDx Buyer Members Free Porting in DID Numbers of 23 Nations | Deadline Oct 31, 2018

New DID number areas are added to our direct inward dialing marketplace at DIDx.net: Romania +40 country code … of 19 cities! The vendor 710082 has a 5 star vendor rating, too. Log in to your DIDx account today to take advantage. New DID number areas are added to our direct inward dialing marketplace at DIDx.net: Romania +40 country code … of 19 cities! The vendor 710082 has a 5 star vendor rating, too. Log in to your DIDx account today to take advantage.
Why would organizations and individuals like to own Romania phone numbers even if they do not live in or have an office in Romania? Here are some examples:
1. To be a local call to anyone who the following is really important to … the Carpathian mountains, sculptor Constantin Brancusi, wine, salt mines, George Enescu, medieval fortresses, Eugene Ionesco, “Dacia” cars, Dracula, stuffed cabbage leaves, Nadia Comaneci, primeval dense forests, the Black Sea, Gheorghe Hagi, sunflower fields, wolves and bears, painted monasteries, the Danube Delta.
2. If you are a citizen of Canada, Japan and the United States and you want to get a job in Romania. You are permitted to work in Romania without the need to obtain a visa or any further authorisation for the period of their 90 day visa-free stay.
3. Since Romania is Europe’s richest country in gold resources, and if you want to do business with them somehow in that industry…
4. If you know the next “Sasha Baron Cohen” … 😉
5. If you want to partner with vehicle parts, insulated wire, cars, wheat and/or rubber tire industries there in any way. These are their biggest exports. On the other hand…
6. If you want to partner with organizations there in their biggest import need areas of vehicle parts, packaged medicines, crude petroleum, wheat, corn and pork.
7. Stay in touch with your family in Romania while you are away at school, on business and/or just traveling. You’ll be a local phone call for them in Romania no matter where you are in the world.
8. To hire and retain a remote work force there!
9. To enable your contact center anywhere in the world to be a local call for anyone in Romania to reach you.
Area codes and cities available:
21 Bucuresti (Bucharest)
31 Bucuresti (Bucharest)
330 Suceava
331 Botosani
332 Iasi
334 Bacau
335 Vaslui
336 Vaslui
337 Vrancea
338 Buzau
339 Braila
340 Tulcea
341 Constanta
342 Calarasi
343 Ialomita
345 Dambovita
346 Giurgiu
347 Teleorman
348 Arges
349 Olt
350 Vrancea
351 Dolj
352 Mehedinti
353 Gorj
355 Caras Severin
356 Timis
357 Arad
358 Alba
360 Salaj
361 Satu Mare
362 Maramures
344 Prahova
363 Bistrita Nasaud
364 Cluj
365 Mures
366 Harghita
367 Covasna
368 Brasov
369 Sibiu
Your phone number is important like your zip code, driver’s license number and tax ID number. All these help you establish who you are, where you are, what you are capable of and how you can be accountable. The right phone numbers allude to your business reliablity, ease of sales and purchasing, local presence and global reputation. Toll-free and international DID phone numbers are just as important to own and make available for customers, vendors and other industry partners as a DID phone number that is local to your brick and mortar location.
At DIDx, we make available freephone, national, toll-free, local, mobile and SMS-supported DID phone numbers via your DIDx buyer dashboard, all self-service! You can even use our Advanced Search function to find DID phone numbers that spell out any alpha-numeric combination that represents importance to your business. Vanity phone numbers are still a beauty. Just think of how cool these are that have been owned by cool companies:
1800FLOWERS
1800HURTNOW
1855COOKIES
1800DOLUNCH
The thing is this… we do not know who is reading this article right now, but if you are an MNO, MVNO, CLEC, voip company, international set of contact centers, international transportation or educational network, you can “join” DIDx, complete a short interop set of tests and buyer agreement and have 17 million phone numbers as if they belong to you, but you don’t pay for them until you need them or until your customers need them. If you are an end-user, share with your phone service provider the advantages of joining DIDx.net and enabling you to own phone numbers of any of 130 nations. You get that local presence outside your geo area you need, and your provider BRINGS IN NEW REVENUE and KEEPS YOU with them. No churn.
You do this via our API connected behind the scenes to your website and ecommerce engine or by manually logging into your dashboard and click to buy and use or buy and resell anytime.
We also offer free local number porting… that’s free of cost for most numbers of 33 nations! Here is a list:
Austria
Belgium
Brazil
Canada
Costa Rica
Chile
Croatia
Czech Rep.
Denmark
France
Germany
Greece
Ireland
Israel
Italy
Latvia
Lithuania
Luxembourg
Mexico
Netherlands
New Zealand
Norway
Panama
Peru
Puerto Rico
Romania
Slovakia
Slovenia
South Africa
Spain
United Kingdom
United States
Prior to DIDx roll out in 1999, it was practically impossible to keep one’s business or personal phone numbers when moving from one geographical location to another, but now, that is a relic of the past!
Last, we offer SMS-supported DID phone numbers of 19 nations: Australia, Austria, Belgium, Canada, Croatia, Czech Republic, Denmark, France, Israel, Latvia, Lithuania, Netherlands, Norway, Poland, Romania, Spain, Sweden, United Kingdom, and United States. Lots of great news from DIDx to you. Please log in to your DIDx account to get started. We are here to help anytime.
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!
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.
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.
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.
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.