New SMG Release and Configuration Change Proposal

There will be a new SMG release today or tomorrow. The follow entry from the release notes summarize what to expect:

Patch 32 (2009-01-28 We)
* call processing, ISUP Transmission Medium Requirement pass to/from
Asterisk CALLTYPE channel variable via the sigboost callstart message
in the bearer.capability field found in sigboost.h
* Sangoma driver 3.3.15.6 required
* CMM, bug fixed, a span was being reported as clear and ready when the logs
indicated the ckt reset requests were being ignored by the telco; fix made
sure the ckt report showed the ckts in reset under this condition
* smgcfg.py, bug fix, numeration of formated wanpipe xmtp2 interface names
corrected
* transparent IAM, new feature work in progress, code added that does not
affect operations yet

As mentioned in a recent post here, the current method of configuring the association of span/chan to CIC and trunk group is too restricted. A new method is needed that allows configuring CIC and trunk group for each individual span/chan. But this approach might mean having to fill out a table for 16 E1s for a total of 496 entries. Since it is rare that individual control of all 496 span/chans is needed, then supporting configuration language that allows table minimization will be useful.

An example of explicit per channel configuration would be as follows:

Span	Chan	CIC	Trunk Group
0	0	1024	0
0	1	1025	0
0	2	1026	0
0	5	1027	0
0	6	1028	0
0	7	1029	0

Here is an example of minimizing language that accomplishes the same thing:

Span	Chan	CIC	Trunk Group
0	0-2.5-7	1024	0

Here's a slightly different example done explicitly:

Span	Chan	CIC	Trunk Group
0	0	1024	0
0	1	1025	0
0	2	1026	0
0	5	1029	0
0	6	1030	0
0	7	1031	0

And the same configuration using minimizing language:

Span	Chan	CIC	Trunk Group
0	0-2	1024	0
0	5-7	1029	0

There will also need to be a similar configuration technique to assign specific span/chans SS7 linkset, link, and SLC (noting that in ss7box, the link is always equal to the SLC value). Any span/chan in the CIC/trunk group table must not appear in the SS7 linkset/link table, and vice-versa.

Span	Chan	linkset	link and SLC
0	15	0	0
2	15	1	0

There will be no table minimization language used with the linkset/link table at this time.