Skip to main content

Asterisk catch e164 patterns

Catching e164 patterns with Asterisk

In the realm of telephony, ensuring seamless call routing and processing hinges on the ability to accurately identify and handle phone numbers in a standardized format. Enter e164, a widely adopted standard that provides a consistent structure for international telephone numbers. This blog post delves into the intricacies of working with e164 patterns within the context of Asterisk, a powerful open-source communication platform.

What is e164?

E164 format is a standard for the international telephone numbering plan that ensures each number is unique. It follows a specific structure, starting with a "+" sign, followed by the country code, and finally the local telephone number. For instance, the e164 format for a French number could be +33123456789.

Why do e164 is not matched by "_X."?

Let's consider a scenario where we aim to match an incoming call from a French number using Asterisk. Initially, we might attempt to use the pattern "_X." within our dialplan, assuming it would match any sequence of digits. However, we encounter an issue: the "+" sign, being a non-digit character, is not matched by the "_X." pattern.

Let's illustrate this with a code snippet:


exten => +33234567890,1,NoOp(Before Goto SDA de test, with ${EXTEN})
exten => +33234567890,2,Goto(sda_de_test,${EXTEN},1)

Then, lower in the file:


[sda_de_test]
exten => _X.,1,NoOp(Entering SDA de test)
 same => 2,Dial(PJSIP/0123456789@trunkoftelco1)
 same => n,Hangup()

In this example, the incoming call with the e164 number "+33234567890" would not be matched by the "_X." pattern in the "sda_de_test" context.

To rectify this, we need to explicitly include the "+" sign in our pattern. Modifying the pattern to "_+X." would successfully match the e164 number.

However, a more robust approach involves incorporating the entire e164 pattern directly into the extension. This eliminates the need for separate patterns and simplifies the dialplan.


[sda_de_test]
exten => +33234567890,1,NoOp(Entering SDA de test)
 same => 2,Dial(PJSIP/0123456789@trunkoftelco1)
 same => n,Hangup()

By specifying the complete e164 number in the extension, we ensure accurate matching and streamline call handling within our Asterisk dialplan.

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

VMWare Keyboard Latency

Workstation VM UI lag when typing When using a VMWare Workstation VM, I noticed there is a latency when typing in the keyboard and the real appearance of the typed character. I searched and found: Noticeable typing lag in Linux VM terminals since v16.2 upgrade on Linux host To make it short, what solved it for me: Disable 3D acceleration in the VM setting .