https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14255
--- Comment #2 from simo...@189.cn ---
(In reply to Jeff Morriss from comment #1)
> Where/when is the SCCP variant ever different than the MTP3 variant? I'm
> not even sure how it would work: if SCCP GTT translates to a PC which format
> does it use in the new MTP3 DPC? The format that SCCP is aware of (e.g.,
> ITU) or that of MTP3 (Chinese - which is what would presumably actually be
> routable)?
Dear Jeff,
Thanks for your attention. I accept this is not a usual scenario. But it’s
still possible in some special cases, actually needed in our real network.
Suppose following message path condition, entity A ---> STPx ---> STPy --->
entity Z, link <A---STPx> has Chinese PC format, link <STPx---STPy---Z> has ITU
PC format. STPx preconfigures a Chinese to ITU PC format mapping rules, it can
convert a DPC=STPy from Chinese to ITU format and perform following ITU format
DPC rout decision.
Now for some policy routing control reason, we may want STPx perform MTP3
routing and STPy perform SCCP PC+SSN routing. Because link <A---STPx> and
<STPx---STPy---Z> have different PC format, the message sent by entity A must
has MTP3 DPC with Chinese format, and SCCP called PC with ITU format.
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
