Attention is currently required from: neels, pespin.
3 comments:
File common/chapters/cs7-config.adoc:
Patch Set #1, Line 349: Osmocom SS7 supports dynamic routing, allowing minimal SS7 configuration. If all of your components support dynamic
dynamic routing through Routing Key Management (RKM)
I'd do a s/dynamic routing/dynamic routing key management/ all over the text. That's what's "dynamic" after all. not the routing itself, but the management of routing keys.
Alternatively, even more explicit: "dynamic routing key registration via M3UA RKM" is an equally explicit description that any reader familiar with the M3UA spec should understand.
Patch Set #1, Line 365: Every component has a distinct M3UA port. For
I don't follow why that would be the case? Are you describing a setup
a) without routing context (clearly not)
b) with routing context but without RKM
c) with routing context and static (non-dynamic) RKM (I think so)
d) with routing context and dynamic RKM
In cases c+d, I don't see why there would be a need for hard-coding the m3ua port numbers? In both of these, the client performs RKM registration - the difference should only be that on 'b' they are statically configured on both sides, and in case 'd' they are dynamically created.
In cases a + b, there indeed is nothig except the 5-tuple (src_ip,src_port,dst_ip,dst_port,proto==sctp) to identify a given ASP, and hence it must be hardcoded.
Patch Set #1, Line 454: synchronize
I would replace synchronize with "manually configure", as "synchronize" might refer to some kind of (even an automatic) synchronization procedure.
To view, visit change 32273. To unsubscribe, or for help writing mail filters, visit settings.