SMG-SS7 Basic Call Operation

1. Standard SMG-SS7 for Asterisk Incoming Call
2. Standard SMG-SS7 for Asterisk Outgoing Call
3. Distributed SMG-SS7 for Asterisk Incoming Call
4. Distributed SMG-SS7 for Asterisk Outgoing Call
5. Clustered SMG-SS7 for Asterisk Incoming Call
6. Clustered SMG-SS7 for Asterisk Outgoing Call
7. Redundant-Clustered SMG-SS7 for Asterisk Incoming Call
8. Redundant-Clustered SMG-SS7 for Asterisk Outgoing Call

Standard SMG-SS7 for Asterisk Incoming Call

In a Standard SMG-SS7 for Asterisk install SMG-SS7 and Asterisk are on the same computer and the complexity is quite simple.  By default an incoming call will enter the Asterisk dial plan using a unique context for each ISUP trunk group.  By default this context is "[sangoma<TG # + 1>]".

In the ISUP layer configuration the CICs are grouped into at least 1 trunk group (each span can be it's own trunk group and each SSP must have it's own trunk group).  The trunk groups here are identified by a number starting from 0.

In the Chan_Woomera configuration file the "default" profile has an option to specify the base name that will be used.  By default we use "sangoma".

For example:

You have a simple F-Link setup....you are connected directly to a single SSP switch with 1 E1 of CICs.  You therefore have a single ISUP trunk group with an index value of "0"...ISUP knows this trunk group as "tg0".

Using all default values you would need to have a single context in Asterisk named "[sangoma1]" to handle all incoming calls.  Here is a simple dial plan for testing and incoming call:

[sangoma1]
exten => _X., 1, answer()
exten => _X., n, playback(demo-congrats)
exten => _X., n, hangup()