CIC as a RK

Ilie,

I'm not sure that we have ever answered this basic issue:

Do we want to use CIC as a Routing Key (meaning that I can have separate
AS with all the same RKs except CIC range).  CIC range will be the
determining factor for how the SG routes between AS.

Or, do we want to use CIC for loadsharing.  Meaning that the SG will
choose AS based upon other criteria besides CIC (DPC, OPC, SI), and then
use CIC to distribute within the AS (similar to TID/DRN in SUA).

I think the second is more practical as it avoids issues of CIC
management that are apparent in the first case.  To illustrate, I have
this simple scenario.  We have two different AS.  Each with a single
ASP.  They share the same PC as the SG, but use a CIC range as RK to
differentiate the two.


---------
| AS1   |\
| PC=1  | \
| CIC=1 |  \
---------   \ |------|
             \| SG   |
             /| PC=1 |<====SS7 Network===>
---------   / |------|
| AS2   |  /
| PC=1  | /
| CIC=2 |/
---------

When AS1 loses the association to SG, how does it handle an incoming IAM
for CIC=1?  

Or if there is a call in progress, how does it handle an incoming REL
for CIC=1?

These are real scenarios that, if not handled, either affect billing or
use of network resources.  No network provider will be happy if these
problems are not solved.  If you expect your SG to interface to somebody
else's AS, they must be solved in an agreed upon manner.  If it is your
SG and your AS, no problem.  You can determine some internal solution.

Regards,
Lincoln