Friday, March 13, 2009

Transparent IAM Passes Unit Testing

The transparent IAM feature works in the unit test environment. We are now working on enlarging the ISUPinRDNIS buffer in the sigboost callstart message to 900 octets. This change also demands that we convert to passing dynamically sized callstarts. At the same time we are adding a new field to the sigboost messages to indicate the version of sigboost a particular message adheres to. This is a safety mechanism for when sigboost interfaces are used by parties outside the closely associated original developers (CAOD). More than likely it will serve the CAOD well too.

We're struggling with installing some 3rd party protocol stacks in opensuse 11.1. It appears that the stack maintainers have not kept their products in step with recent major Linux distros. The job of sorting out the mess falls to me and this is not my strong suit. I am happy to learn as I go but others waiting on me would prefer to forego the learning and move directly to the doing part. I agree with them but find myself unable to comply.

CNAM work is bubbling up to the top. This time around we will be able to finish the project. I am refreshing myself on the code and I'm devising what the first step is restart this dormant project.

Some new features are being added to the list. One is providing trunk group and circuit status up to the Asterisk command line. Another is to add a session id to inbound ISUP calls to improve management of callstop and callstopack messages that arrive late and out of context. Comparing the session ids of messages to session ids of circuits will improve identification of messages that are useful, useless and discardable, or nonsense. The improvement will be that some messages are identified as safely discardable instead of confusing. If a message is confusing it can lead to a circuit being quarantined, which means a valid call might be disconnected, and the circuit becomes unavailable for use for several minutes.