Tech

Country Code

Published on:

December 3, 2013

In the latest PBX version, a warning sign has been added to the general settings page for domains to help manage international number formats. The system handles two primary number formats: the NANPA region (USA and Canada) with its predictable 10-digit format and the rest of the world, where numbers can start with a country code, area code, or local number. To ensure proper routing, users can enter numbers starting with a plus sign (+), indicating a global format. It's crucial that the PBX knows the country code to route calls accurately. The update also highlights the issue with the outdated practice of dialing a “9” to seize a line, which is no longer necessary in today’s digital and multi-trunk environments.

In the latest version we have added a warning sign on the general settings page for the domain. This is for a reason. Telling the PBX how to interpret numbers makes it a lot easier to deal with the various ways to represent numbers in the different parts of the world.

Essentially there are two areas. The so-called NANPA region is essentially USA and Canada. NANPA stands for North American Number Plan Association. The organization deals with the distribution of the 10-digit number block allocated for the area. The area has the international dial code “1”. Usually numbers have exactly 10 digits, and they are commonly written in xxx-xxx-xxxx or (xxx) xxx-xxxx notation. In the old days when most calls were local, people could call just the 7 last digits and leave out the area code. This is why the area code was written in brackets. However today practically all calls include the area code. There are some numbers like 911, 411 or 555-xxxx which are an exception to the 10-digits rule. Because the number length in the NANPA region is predictable, it is possible to provision phones with a phone dial plan that automatically starts dialing when the number is complete. In that case users have to start dialing with a “1” when they want to call a 10-digit number.

The rest of the world is using numbers where the PBX is not able to predict how long the numbers are. In those areas the challenge is to guess how the number begins. Depending on the context, numbers may start with the country code, with the area code or just the local number. If the PBX has the country code and the area code, it can automatically convert numbers into the globally routable number. For example if the call comes in on trunk A through a local PSTN gateway, it will be able to call that number back through another trunk B.

In order to tell if a number is in a global format, the number must start with a plus sign. Users may even enter numbers starting with a plus sign to tell the PBX that no matter what the country code is, where to send the call. This has also become a common feature of many cell phones, especially in countries that have a lot of international calls. If users are entering numbers in the PBX starting with a plus sign, the PBX will happily accept it.

Otherwise, it is important that the PBX knows which country the number is in. That’s why we encourage everybody to check what country code has been set on the domain.

In the light of this discussion it becomes clear why putting a “9” in front of every number is a bad idea. In the old times when PBX were connected through analog lines (one cable for every possible phone call), this number was used to grab one of those lines and get the dial tone. However in today’s digital world and with the modern requirements such seizing of lines is not needed and looking at multiple trunks in a domain, even impossible. For example, when users dial 911 to call the emergency service, it seems ridiculous that they have to dial 9, wait for a dial tone and then dial 911. Most of the users have cell phones today. Fortunately this educates users that they can first enter and edit the number and then press the send button to start the call. There is no reason why they should not do the same thing on the VoIP phone.

Latest Articles

View All

Vodia Visits IT Expo 2025

Vodia was excited to attend IT Expo 2025 in Ft. Lauderdale, where Sales Engineer Eric Altman connected with industry leaders such as Tommy Lee from Fanvil, Gary Harbeck from Dinstar, Spencer Lee from Telin, Sebastian Balan from Fidelity, Todd Weikle from Soar Communications, Steve Scott from Borderless.com, and Mitch Kahl from BCM One. The discussions highlighted the role of AI in business communications, Vodia’s Microsoft Teams-certified PBX, and our integration with Realtime AI via APIs. This event followed a strategic planning session with key partners to outline Vodia’s goals for 2025. We look forward to connecting with you at future events!

February 19, 2025

AI-Powered Hotel Phone System: OpenAI for Guest Services

Vodia has integrated OpenAI’s Realtime API with its PBX, enabling real-time AI-powered hotel phone systems that enhance guest services. By leveraging natural speech processing, guests can make reservations, request services, and access hotel amenities in multiple languages - all through voice commands. This integration streamlines hotel operations, reduces staff workload, and improves guest satisfaction. Whether booking a room, ordering room service, or arranging transportation, AI-powered phone systems provide seamless communication and efficiency. Hotels can now offer personalized, automated experiences while maintaining reliable, high-quality service.

February 18, 2025

Vodia and Microsoft Teams: Your Call Center Solution

ConnectPlus, a fictional call center with 150 agents and 20 support team members, faced several challenges in managing its phone systems and customer interactions. The company struggled with inefficient call routing, long wait times, and inadequate reporting, especially as it relied on Microsoft Teams for internal communication. To improve operational efficiency and enhance the customer experience, ConnectPlus sought a solution that could streamline its processes across multiple devices and platforms. Integrating Vodia’s PBX with Teams provided the ideal solution, optimizing their call handling and overall communication capabilities.

February 12, 2025