Re: DPC + OPC Routing
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Cathy, Well, if you follow ETSI TS 102 142-V1.1.1 (2003-05) then you will not assign an RK more granular than a point code and there is no issue. It does mean, however, that if you have 50 M3UA blades, each serving a different AS, you will need 50 point codes for the rack. In the case of SCCP, it is better to use SUA (RFC 3868). It requires only a single point code for a rack of blades, and it can route down to an individual subsystem or global title range (AMF). --brian Newman, Catherine J wrote: (Fri, 13 Apr 2007 13:41:35) > Ansi T1.112.4-1996 doesn't have the SCCP Flow Control procedures. > Ansi T1.112.4-2001 and T1.112.4-2005PPP have these procedures as > optional: > "5.5 SCCP Flow Control (Optional)" > > And Section 5.3.6.7 & 8 and other related requirements have footnote 20: > 20. Flow Control procedures in clause 5.5 are optional. > > Telcordia GR-246, T1.112.4-2005 (the latest version) states these > procedures aren't used: > "5.5 SCCP Flow Control > > NOTE: SCCP Flow Control procedures are not specified for use in Client > Company networks." > > I'm pointing this out since I think there is likely to be > interoperability issues if UPU (re: SCCP) is sent in ANSI networks - > processing a received UPU (re:SCCP) is optional. ANSI T1.112.4 Section > 5.5 should be made mandatory if this solution is agreed upon, but then > there will be backward compatibility issues. > > Alternately, limitations could be put on RK use (e.g., force user to > provision a separate SSN for each of the AS1 and AS2 in the original > example) to avoid such circumstances so no changes to standard SS7 > procedures are needed. > > Cathy > -- Brian F. G. Bidulock [email protected] http://www.openss7.org/