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.

Derniers articles

Voir tous

Integrating OpenAI's Realtime API with Vodia PBX: Webinar Recording Now Available

In our recent webinar, "Integrate OpenAI’s Realtime API with Vodia PBX," we explored how integrating AI with your communication systems can revolutionize the way your business operates. From automating repetitive tasks to improving workflow efficiency, the webinar covered how the collaboration between Vodia PBX and OpenAI’s Realtime API can streamline operations, enhance collaboration - especially for Microsoft Teams users - and provide intelligent automation to stay ahead in a competitive landscape. If you missed the live session or want to revisit the insights, the recording is now available for you to access.

December 18, 2024

Unlock the Power of OpenAI’s Realtime API with Vodia PBX: Join Our Exclusive Webinar!

Join our exclusive webinar to explore how Vodia PBX seamlessly integrates with OpenAI’s Realtime API, unlocking powerful new capabilities for your communication systems. This session will showcase how AI-driven features can streamline workflows, improve operational efficiency and elevate the PBX experience for both general users and those on Microsoft Teams. Whether you’re looking to stay ahead of the competition or leverage the latest AI trends, this webinar offers practical knowledge and actionable strategies. Register now to secure your spot and take the first step toward transforming your telecom infrastructure with AI innovation!

December 4, 2024

Connecting to OpenAI Realtime API

This document details the beta version of the Vodia PBX that connects to the OpenAI realtime API, enabling users to interact with a chatbot via telephone. The backend JavaScript code facilitates the connection, handling audio input and output, and the WebSocket connection to the OpenAI API. The setup requires a Vodia PBX version 69.5.3 or higher, an API key, and a license with an IVR node. The demo can be accessed by editing the ivrnode.js template and creating an IVR node in the tenant. The system supports various VoIP devices and offers good voice quality. Future improvements include voice activity detection and the ability to take actions based on OpenAI responses.

November 26, 2024