Skip to main content

Asterisk Python Module Pyst

Using the Asterisk Python Module "Pyst"

The Asterisk Python module "Pyst" provides a simplified way to interact with Asterisk, an open-source framework for building communications applications, including VoIP gateways, conference servers, and more. "Pyst" enables Python developers to automate and manage Asterisk functionalities, integrating them into Python-based applications. This document explores the history, features, and usage of the Pyst module.

There was pyst2, then pyst3, and now it is pyst. The Short History

The evolution of the Pyst module reflects the broader transition within the Python ecosystem from Python 2 to Python 3:

  • Pyst2: Initially, Pyst was developed to work with Python 2, leveraging its capabilities to connect and control Asterisk servers. Its initial iterations aimed at providing basic functionalities like call initiation, monitoring, and terminations.

  • Pyst3: With the advent of Python 3, "Pyst2" was updated and rebranded as "Pyst3" to ensure compatibility with the newer Python version. This version included enhancements such as improved syntax, better error handling, and more efficient performance to match Python 3’s capabilities.

  • Pyst: As both Python and Pyst matured, the sequential naming was dropped in favor of a unified module simply named "Pyst". This version is designed to work seamlessly with the latest Python releases while also maintaining backward compatibility with previous Pyst functionalities. The move symbolizes a stabilized API and user experience.

Simple Asterisk Dialplan Example

Asterisk uses dialplans as a scripting language to handle call processing logic. Here is a simple example of an Asterisk dialplan:

[default]
exten => 100,1,Answer()
 same => n,Playback(hello-world)
 same => n,Hangup()

This dialplan does the following:

  • Answers a call to extension 100.
  • Plays a pre-recorded message "hello-world".
  • Hangs up the call.

Using the Asterisk Python Module "Pyst", and It Is import asterisk Not import pyst

Contrary to what the module name might suggest, when using the "Pyst" module in a Python script, you need to import it using import asterisk. This naming convention aligns with Python's common practice of naming modules after their primary functionality or the core library they interact with.

import asterisk.ami

# Create a connection to the Asterisk server
client = asterisk.ami.AMIClient(address='127.0.0.1', port=5038)
client.login(username='admin', secret='yourpassword')

# Event listener
def on_event(event):
    print(f"Received event: {event}")

client.add_event_listener(on_event)

# Send a simple command to the Asterisk server
response = client.send_action({'Action': 'Ping'})

print(f"Response: {response.response}")

client.logoff()

In this example:

  • The asterisk.ami.AMIClient class is used to establish a connection to an Asterisk server using the Asterisk Manager Interface (AMI).
  • We define an event listener that prints received events to the console.
  • The Ping action checks connectivity with the server.

This illustrates how the "Pyst" module can facilitate remote control and monitoring of Asterisk servers, simplifying the process of integrating telephony features into Python applications.

Popular posts from this blog

Undefined global vim

Defining vim as global outside of Neovim When developing plugins for Neovim, particularly in Lua, developers often encounter the "Undefined global vim" warning. This warning can be a nuisance and disrupt the development workflow. However, there is a straightforward solution to this problem by configuring the Lua Language Server Protocol (LSP) to recognize 'vim' as a global variable. Getting "Undefined global vim" warning when developing Neovim plugin While developing Neovim plugins using Lua, the Lua language server might not recognize the 'vim' namespace by default. This leads to warnings about 'vim' being an undefined global variable. These warnings are not just annoying but can also clutter the development environment with unnecessary alerts, potentially hiding other important warnings or errors. Defining vim as global in Lua LSP configuration to get rid of the warning To resolve the "Undefined global vi...

wget maven ntlm proxy

How to make wget, curl and Maven download behind an NTLM Proxy Working on CentOS, behind an NTLM proxy: yum can deal without problem with a NTLM Proxy wget, curl and Maven cannot The solution is to use " cntlm ". " cntlm " is a NTLM client for proxies requiring NTLM authentication. How it works Install "cntlm" Configure "cntlm"  by giving it your credentials by giving it the NTLM Proxy Start "cntlm" deamon (it listens to "127.0.0.1:3128") Configure wget, curl and Maven to use "cntlm" instead of using directly the NTLM Proxy Note: You will have then a kind of 2 stages Proxy : cntlm + the NTLM proxy Configure CNTLM After installing cntlm, the configuration file is in "cntlm.conf". You must have your domain (in the Windows meaning), proxy login and  proxy password. Mine are respectively: rktmb.org, mihamina, 1234abcd (yes, just for the example) You must have you NTLM Proxy Hostnama or IP ...

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