1. SCCP build FW has been ipdated to get sources auto generated
2. Win32 Visual Studio builds have been updated as well to get ISUP and SCCP sources generated(requires perl although), regional variants (R and ITU) have been split to 2 solutions accordingly- SS7-R and SS7-ITU
I have significantly changed ISUP build framework on Linux (did not do that for Win32 though yest):
1. configure allows to choose protocol version
2. According to choosen version parser sources are generated on the fly during the build
3. An ability to customize parser sources (certain parameters etc) has been added- just put particular sources to the import folder in particular message description folder
After long silence I have found a chance to use ISUP parcer in the prototyping in my actual work (in the real SS7 network). SO, now I'm working closely on ISUP.
Nearest plans:
1. Bugfixing against actual messaging coming from ss7 network (in progress)
2. Build FW improvements (in progress)
3. Added an ability to import custom parser messages/parameters instead of generation dummy ones (done)
Just done some org changes in build environment- moved configuration makefiles to autoconf
Okey dokey...
I have added sccp implementation (generated as well as isup and done the same script)... the parser is not 100% complete yet and first of all I'll concentrate my efforts on SCCP management messages.
Also I have moved to MS VS 2005 and therefore added project files for it.
Also I have finally managed to write makefiles and the project is sort of compilable on Linux using gcc 3.4
I have started publishing the sources/
The following have been published:
base message parsing code (especially applicable for ISUP and SCCP),
generated ISUP message classes- the generator itself is not in shape for publishing yet ;-)