Free sip user agent software for linux

mod_auth_useragent allows you to forbid clients based on their User-Agent by placing a single line in your Apache httpd.conf.

Be aware that this is by no means a security measure as it is trivial to change your User-Agent in most browsers.

pam_ssh_agent is a PAM module that spawns a ssh-agent and adds identities using the password supplied at login.

SipUnit provides a test environment geared toward unit testing SIP applications. SipUnit project extends the JUnit test framework to incorporate SIP-specific assertions, and it provides a high-level API for performing the SIP operations needed to interact with or invoke a test target.
A test program using the SipUnit API is written in Java and acts as a network element that sends/receives SIP requests and responses. The SipUnit API includes SIP User Agent Client (UAC), User Agent Server (UAS), and basic UAC/UAS Core functionality - the set of processing functions that resides above the SIP transaction and transport layers - for the purpose of interacting with the test target.
SipUnit uses the JAIN-SIP reference implementation as its underlying SIP stack/engine. The primary goal of SipUnit is to abstract the details of SIP messaging/call handling and facilitate free-flowing, sequential test code so that a test target can be exercised quickly and painlessly.
A test program using SipUnit API:
1. Extends SipTestCase
2. Creates SipUnit API objects - SipStack, SipPhone, SipCall, etc.
3. Calls methods on the object(s) to set up and initiate action toward a SIP test target. For example: SipPhone.makeCall("sip:roger@nist.gov", SipResponse.OK, ....) makes a vanilla call to sip:roger@nist.gov and blocks until an OK is received or a timeout occurs. The test target could be any node up to and including the final destination of the INVITE request message.
4. Verifies the results of the action involving the test target using both the SIP-specific assert methods provided by SipUnit and the standard JUnit assert methods. For example: assertHeaderContains(sipCall.getLastReceivedResponse(), "From", "sip:amit@nist.gov"), assertEquals("Unexpected response received", SipResponse.OK, sipCall.getReturnCode()).
Main features:
- A basic set of SIP-specific assert methods - assertHeaderPresent(), assertHeaderContains(), assertBodyPresent(), etc.
- High level API for interacting with a test target.
- Low-level SIP messaging access for interacting with a test target.
- Registration/unregistration and call processing with or without authentication (DIGEST).
- Support for testcase-specified timeouts.
- Support for different routing configurations.
Enhancements:
- Support was added to the SipPhone and SipSession classes for running SipUnit tests from behind a NAT and communicating with a SIP server on the Internet.
- A STUN example test was included.
- An enhancement that allows more flexible multiple SIP stack creation was incorporated.

Agent is the Transportable Agent Perl module.

SYNOPSIS

use Agent;

my $a = new Agent( Name => path_to_agent.pa, %args );

$a->run();

Agent Perl is meant to be a multi-platform interface for writing and using transportable perl agents.

A Perl Agent

Is any chunk of Perl code that can accomplish some user-defined objective by communicating with other agents, and manipulating any data it obtains.
A Perl Agent consists of a knowledge base (variables), a reasoning procedure (code), and access to one or more languages coupled with methods of communication. These languages remain largely undefined, or rather, user-defined; support for KQML/KIF is under development.

Developing An Agent

Note that the developer must devise the reasoning procedure and knowledge base described above. Agent Perl does not place any restrictions on what you may do; it only tries to make the doing part easier.

An agent is written as an inheriting sub-class of Agent. Each agents class should be stored in a .pa file (perl agent), and must contain an agent_main() method. All agents are objects. See the examples for more details, and learn how Agent.pm works so you wont step on its toes!

sipsak is a small comand line tool for developers and administrators of Session Initiation Protocol (SIP) applications. sipsak can be used for some simple tests on SIP applications and devices.
Main features:
- sending OPTIONS request
- sending text files (which should contain SIP requests)
- traceroute (see section 11 in RFC3261)
- user location test
- flooding test
- random character trashed test
- interpret and react on response
- authentication with qop supported
- short notation supported for receiving (not for sending)
- string replacement in files
- can simulate calls in usrloc mode
- uses symmetric signaling and thus should work behind NAT
- can upload any given contact to a registrar
- send messages to any SIP destination
- Nagios compliant return codes
- search for strings in reply with regluar expression
- use multiple processes to create more server load
- read SIP message from STDIN (e.g. from a pipe |)
- supports DNS SRV through libruli
Version restrictions:
- The hostname is used in the Via line, which is not correct in all cases (e.g. if the loopback interface is used, or if the host has several interfaces). The rport parameter should fix problmes with the incorrect hostname, but for backward compatibility whith implementations which do not support rport this should be fixed.
- The DNS responses are not parsed compeltly which can result in strange output during hostname detection.
- TCP is not supported as transport protocol.
- IPv6 is not supported as transport protocol.
- Missing support for the Record-Route and Route header.
- Not fully RFC3261 compatible.
- Some smaller problems are listed in the TODO file.
Enhancements:
- A new option allows to add any header to the outgoing requests.
- The variable replacement option now accepts any number of attribute value pairs.
- Besides MD5 now SHA1 is support as digest authentication algorithm.
- The password for authentication can be read from stdin to prevent password disclosure in the process list.
- Fixed problems when executed as user root and compiles fine again under cygwin.

SeSAm (Shell for Simulated Agent Systems) provides a generic environment for modelling and experimenting with agent-based simulation.
We specially focused on providing a tool for the easy construction of complex models, which include dynamic interdependecies or emergent behaviour.
SeSAm agents consist of a body, that contains a set of state variables and a behaviour that is implemented in form of UML-like diagram. Based on an extensive number of primitive components, a user is able to design a simulation graphically without knowing the syntax of a traditional programming language.
The model specification is executable in the same environment and the dynamics of this simulation may be observed. As there are freely configurable instruments for gathering data and scripting options for constructing simulation experiments, SeSAm is a highly valuable tool for MAS simulations especially for complex models with flexible agent behaviour and interactions.
Main features:
- Easy visual agent modelling,
- Flexible environment and situation definition,
- The whole power of a programming language,
- Integrated graphical simulation analysis ,
- Distribution of simulation runs in your LAN ,
- and many further features.....